Page tree

Release 5.0.1



Finds the suffix value after the domain from a valid URL. Input values must be of URL or String type.This function is part of a set of functions for processing URL data.


Basic Usage

URL literal examples:

derive type:single value: SUFFIX('' ) as: 'myDomain'

Output: Generates a column containing the value com

derive type:single value: SUFFIX('' ) as: 'myDomain'

Output: Generates a column containing the value com

Column reference example:

derive type:single value: SUFFIX(myURLs) as: 'myDomain'

Output: Generates the new myDomain column containing the suffix values extracted from the myURLs column. 

Syntax and Arguments

derive type:single value: SUFFIX(column_url)

ArgumentRequired?Data TypeDescription
column_urlYstringName of column or String or URL literal containing the suffix 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 suffix 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, Subdomain, Host, 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:/[!^\/].*$/

Drop the path_URL column and rename the path_URL1 column to the dropped 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'



URLhost_URLpath_URLprotocol_URLsubdomain_URLdomain_URLsuffix_URLurlParamsurlParam_q1  wwwexamplecom  examplecom http://  www.appexamplecom  www.some.appexamplecom  some.appexamplecom  someexamplecom   examplecom http://wwwexamplecom{"q1":"broken record"}{"q1":"broken record"} http://wwwexamplecom{"query":"khakis","app":"pants"} http://wwwexamplecom{"q1":"broken record", "q2":"broken tape", "q3":"broken wrist"}{"q1":"broken record"}


This page has no comments.