Articles in this section

Adform Connector

The Adform Connector is used to send data to both the Adform Pixel and Conversion API.

Prerequisites

You will need the following to complete the setup of the connector successfully:

  • Adform Account
  • Adform Campaign
  • Adform Tracking Points

Adform Connector Setup

Please note before setting up the Adform Connector in Tracklution: If you have previously included the pixel code in your website's header or footer HTML or e.g. via GTM, you must remove or deactivate existing pixels. Otherwise, the pixel will fire twice and lead to inconsistent data in your reporting. Adform Connector in Tracklution includes both the Pixel and Conversions API which allows Adform to deduplicate events.

Choose the Adform Connector from the "Connectors" section on your tracking container dashboard. Click "Add" or "Edit" on the Adform Connector:

select_adform


Authenticate your Adform account, click the 'Start Authentication' button:

You'll be redirected to login to your Adform account before you are redirected back to continue with the next step in Tracklution.

adform_info_v2


Next you should select the Adform campaign that you want to receive your Tracklution events. To do this, start by clicking the 'Sync Campaigns' button:

Ability to send your Tracklution events to multiple Adform campaigns is a coming feature.

select_campaign

This will make your Adform campaigns appear in the 'Campaigns' drop-down list.


Next you should map which of your events in Tracklution should be counted as Adform Tracking Points. This is done by clicking the 'Select Tracking Point' drop-down list next to the event you want to send there:

select_TP

When you click 'Map', this event will go Live and start sending these events to Adform.

Supported Parameters

TOP-LEVEL VARIABLES (mapped to variables)
- value → variables.sales
- order_id → variables.orderid
- transaction_id → variables.orderid (fallback)
- currency → variables.currency
- content_type → variables.content_type

ITEM-LEVEL VARIABLES (mapped to subVariables)
From items array:
- product_id → subVariables.productid (1st choice)
- id → subVariables.productid (2nd choice)
- item_id → subVariables.productid (3rd choice)
- price × quantity → subVariables.productsales (1st choice)
- total → subVariables.productsales (2nd choice)
- subtotal → subVariables.productsales (3rd choice)
- price → subVariables.productsales (4th choice)
- name → subVariables.productname (1st choice)
- item_name → subVariables.productname (2nd choice)
- category → subVariables.productcategory (1st choice)
- item_category → subVariables.productcategory (2nd choice)
- content_type (top-level) → subVariables.productcategory (3rd choice)

The Adform connector will automatically process and rename the supported parameters. If you name your parameter something custom that isn't included in the supported parameters list, it will not be processed by the Adform connector.

Example: When you include value and currency in your Purchase event, these parameters will be delivered as sales and currency to your Adform Tracking Points with the Purchase event.

Sending Custom Events from Tracklution to Adform

When you have created a custom event in your data collection setup and send at least one such event to Tracklution, these custom events will be available in your Adform event mapping list and you can send them to an Adform Tracking Point just like any other event.

Troubleshooting

Issues with a connector? Visit our Troubleshooting and FAQ to find answers to most common issues for each connector.

Comments (0)
Access denied
Access denied