Page tree

Release 6.0.2



Finds the host value from a valid URL. Input values must be of URL or String type and can be literals or column references.

In this implementation, a host value includes everything from the end of the protocol identifier (if present) to the end of the extension (e.g. .com).

Basic Usage

URL literal examples:

derive type:single value: HOST('' ) as: 'myHost'

Output: Generates a column containing the value

Column reference example:

derive type:single value: HOST(myURLs) as: 'myHost'

Output: Generates the new myHost column containing the host values extracted from the myURLs column. 

Syntax and Arguments

derive type:single value: HOST(column_url)

ArgumentRequired?Data TypeDescription
column_urlYstringName of column or String or URL literal containing the host value to extract

For more information on syntax standards, see Language Documentation Syntax Notes.


Name of the column or URL or String literal whose values are used to extract the host value.

  • Missing input values generate missing results.
  • Multiple columns and wildcards are not supported.

Usage Notes:


Required?Data TypeExample Value
YesString literal or column reference (URL)


Tip: For additional examples, see Common Tasks.

Example - Domain, Host, Subdomain, and Suffix functions

This examples illustrates how you can extract component parts of a URL using the following functions:
  • DOMAIN - extracts the domain value from a URL. See DOMAIN Function.
  • SUBDOMAIN - extracts the first group after the protocol identifier and before the domain value. See SUBDOMAIN Function.
  • HOST - returns the complete value of the host from an URL. See HOST Function.
  • SUFFIX - extracts the suffix of a URL. See SUFFIX Function.
  • URLPARAMS - extracts the query parameters and values from a URL. See URLPARAMS Function.
  • FILTEROBJECT - filters an Object value to show only the elements for a specified key. See FILTEROBJECT Function.


Your dataset includes the following values for URLs:



When the above data is imported into the application, the column is recognized as a URL. All values are registered as valid, even the IPv4 address.

To extract the domain and subdomain values:

derive type:single value: DOMAIN(URL) as: 'domain_URL'

derive type:single value: SUBDOMAIN(URL) as:'subdomain_URL'

derive type:single value: HOST(URL) as:host_URL'

derive type:single value: SUFFIX(URL) as:'suffix_URL'

You can use the Alteryx® pattern in the following transform to extract protocol identifiers, if present, into a new column:

extract col:URL on:`{start}%*://`

To clean this up, you might want to rename the column to protocol_URL.

To extract the path values, you can use the following regular expression:

NOTE: Regular expressions are considered a developer-level method for pattern matching. Please use them with caution. See Text Matching.

extract col: URL on: /[^*:\/\/]\/.*$/

The above transform grabs a little too much of the URL. If you rename the column to path_URL, you can use the following regular expression to clean it up:

extract col:path_URL on:/[!^\/].*$/

Delete the path_URL column and rename the path_URL1 column to the deleted one. Then:

derive type:single value: URLPARAMS(URL) as: 'urlParams'

If you wanted to just see the values for the q1 parameter, you could add the following:

derive type:single value: FILTEROBJECT(urlParams,'q1') as: 'urlParam_q1'



For display purposes, the results table has been broken down into separate sets of columns.

Column set 1:


Column set 2:

URLprotocol_URLsubdomain_URLdomain_URLsuffix_URL wwwexamplecom  examplecom www.appexamplecom www.some.appexamplecom some.appexamplecom someexamplecom  examplecom

Column set 3:

URLurlParamsurlParam_q1{"q1":"broken record"}{"q1":"broken record"}{"query":"khakis","app":"pants"}{"q1":"broken record", "q2":"broken tape",
"q3":"broken wrist"}
{"q1":"broken record"}


This page has no comments.