From September, Flash will no longer be supported by Chrome. Prepare for the shift towards HTML5 by visiting our Flash to HTML5 help page

Check it out!

Custom naming


Adform iframe custom naming tracking code is used to track visits of a website either on one specific page, or multiple pages at once - this code will generate a unique tracking point based on the tracking point name which is passed to the code.
The tracking code utilizes functions, which gather visit count, basic visitor information (e.g. browser type, operating system or screen size) and sends this information along with campaign data to Adform servers.


Defining pagename parameter

The pagename parameter is responsible for the tracking point name which is assigned once the code is activated. The pagename parameter should correspond to the page where the tracking code is activated in order to recognize the tracking points later in the platform using analytics or retargeting.

Example tracking code with pagename to be modified:

<iframe src="{trackingID}&ADFPageName=WebsiteName|SectionName|SubSection|PageName&ADFdivider=|&ADFtpmode=4" style="display:none;"></iframe>

Where default mandatory parameters:

Parameter name Value Value type
pm Tracking setup ID of Adform client numeric
ADFPageName Name of tracking point string

Values here can be passed from any source which would define the page which is tracked, for example, part of page URL, page title, bread-crumbs, CMS variables or any other source as long as assigned value allows to identify the tracked page.

Implementing the tracking code

Once the pagename is defined the code can be added to the source code of the page or respective tag management field which supports HTML code.
In case of dynamic tracking point naming, make sure the code is set on as many pages or sections as necessary, or unconditionally on all website.

Example HTML page implementation:

<iframe src="{trackingID}&|&ADFtpmode=4" style="display:none;"></iframe>

As the tracking point generates tracking points dynamically, it is recommended to exclude it from pages that are not required to be tracked, such as development, CMS or test pages.


  • Custom variables

    Additional information can be collected by the tracking point with the use of variables, such as sales, order ids, product names or other custom values.

    For conversion page tracking we recommend implementing Unique naming tracking point.

    To collect values from your website macros from the CMS or tag manager system could be used - this information should be passed to the code via respective system variables, data layer or other tools to get variable values from the site.

    Example of the tracking code output with sales, order id and two products passed:

    <iframe src="{trackingID}&ADFPageName=Example%20name&ADFdivider=|&ADFtpmode=4&itm={sl:'95.29',id:'YWZ-487921','itms':[{pnm:'Product A'},{pnm:'Product B'}]}" style="display:none;"></iframe>

    For more information and examples of supported variables please refer to the variables page here.


 Implementation check

After the tracking code has been implemented on the page it can be confirmed if it has been activated with the Adform site tracking testing browser extension - it is available to be downloaded for Chrome browser here.

Alternatively, you can check network requests via browser’s developer tools:

Iframe Network

Successful activation will result in a tracking point network request, which contains the tracking setup id, tracking point name and other information sent.

For additional information please contact site tracking team at [email protected]