Adform

Adform is a global digital media advertising technology company specializing in real-time programmatic marketing automation technologies. Using this destination you can implement server-side tracking.

Key features

The Adform destination provides the following key features:

  • Events structure: our Events reference covers Adform server-side tracking, meaning that your data is properly bridged to the expected fields in an optimized way.

  • Prebuilt mappings: data mapping for event-based destinations happens automatically, which simplifies user inputs.

  • Smart mapping: data mapping can be readjusted using your datalayer defined fields.

  • Support for multi-item data: information included in the item array is bridged to Partnerize.

Destination setup

A client-side tag template named "Adform - Get 3rd Party Cookie ID" is available in our library to help you retrieve the Adform Third-Party Identifier. Use Destination filters to refine events and/or other properties matching your specific needs.

Configuration

SettingsDescription

Tracking Domain

Required Your tracking domain as set on Adform UI (E.g. "a1.adform.net", without quotes). More details are available following this LINK. This setting supports dynamic values [1][2].

Tracking Setup Id

Required Your client tracking ID, which can be found under "Site Tracking" in Adform UI (E.g. "1257163", without quotes). This setting supports dynamic values [1][2].

Tracking Point Name Property

Your property holding the tracking point name. In case it's not set, Page URL (pageUrl) will be used.

Select your Adform third-party holder

This can be either Cookie or Event property, depending on how you provide Adform third-party identifier value. A client-side tag template named "Adform - Get 3rd Party Cookie ID" is available in our library to help you retrieve this value.

Third-Party Id Cookie Name

If you select Cookie in Select your Adform third-party holder, you can set your Adform third-party cookie name here.

Third-Party Id Property

If you select Event property in Select your Adform third-party holder, you can set your Adform third-party property name here.

Select your Adform first-party holder

This can be either Cookie or Event property, depending on how you provide Adform first-party identifier value.

First-Party Id Cookie Name

If you select Cookie in Select your Adform first-party holder, you can set your Adform first-party cookie name here. Only use for hybrid setups, where part of site tracking is implemented client-side to be able to pass its value that Adform has set previously.

First-Party Id Cookie Domain

If you select Cookie in Select your Adform first-party holder, you can set your Adform first-party cookie domain here. Only use for hybrid setups, where part of site tracking is implemented client-side to be able to pass its value that Adform has set previously.

First-Party Id Property

If you select Event property in Select your Adform first-party holder, you can set your Adform first-party property name here.

Custom Event Properties

Map your custom event properties by setting their field names in Adform property name and adding the field name holding the value in Your event property. E.g. if you inputsizein the Partnerize property name and items.0.product.size in Your event property, you'll have a custom event property in Adform calledsizewith a value based on the content of the field items.0.product.size [2].

In the column Your event property path you should keep the default value Default (root) as it fits most scenarios. In case you select either In "items" {items.X} or In "product" {items.X.product} this destination will look for the input event property starting from the items or product level respectively and add its value as a custom entry in the "subVariables" array. The advanced operation As Adform subVariables Data can be paired with the property path option Default (root) so your property value is set as a custom entry in the "subVariables" array for each item. More details on Adform custom variables are available following this LINK (section: "Add Custom Variables").

[1] This feature allows you to set an event property holding a dynamic value by adding two open braces ({{) in front of your property name and two close braces (}}) at the end (E.g. {{myEventPropertyPathAndName}}). [2] Using "dots" (".") you can navigate deeper to the specific field you want to get the value of. See Events reference for more details on the standard field names by event. You can also freely set custom fields: there are no boundaries.

Quick reference

Commanders Act EventsAdform Tracking

[Any Event] [1]

[Tracking Point Names]

[1] Ensure to apply Destination filters configuring your relevant events for this destination. Custom events are also supported.

Field mappings

Most properties can be remapped using our "Smart Mapping" feature. For audience building and retargeting, make sure to pass a user identifier. Geo and device information come from the provided user ip and agent. Adform standard attribution works only if identity.cookieId (Adform 3rd party cookie) or identity.advertisingId (mobile advertising ID) is passed correctly. Adform Cookieless Insights reporting is enabled by passing values in both userContext.userAgent and userContext.userIp .

Commanders Act PropertiesAdform Properties

Third-Party Id Cookie Name

Third-Party Id Property

identity.cookieId [1]

First-Party Id Cookie Name

First-Party Id Property

identity.firstPartyId.id [1]

First-Party Id Cookie Domain

(context.page.url)

identity.firstPartyId.domain [2]

Tracking Point Name Property

name

context.page.url

pageUrl

context.page.referrer

refererUrl

context.device.advertising_id

identity.advertisingId

partners.adform.provider_id

identity.eids.0.source

user.id

identity.eids.0.uids.0.id

context.device.user_agent

userContext.userAgent

context.device.ip

userContext.userIp

value

variables.sales

id

variables.orderid

items.X.id

variables.subVariables.X.productid

items.X.product.price

variables.subVariables.X.productsales

partners.adform.consent_string

compliance.gdprConsent [3]

[1] Cookie name or property is used based on your Configuration. [2] Priority order is listed in the left column. [3] IAB TCF consent string.

Last updated