With the free-of-charge Adform Site Tracking extension for Chromium-based browsers (Chrome, Edge), you can test and troubleshoot your current site tracking implementation. This extension helps to ensure that the right tracking points are firing from the right pages, buttons and events.
You can also use it to identify tracking points, variables, and IDs that are passed via site tracking. You can then use the tracking point ID from the extension to:
find it in your tracking point overview on the Adform platform and archive the tracking point when you no longer needed. This helps to keep your setup clean and effective.
find it in your tracking point overview on the Adform platform to see the full path and name for easier customization.
select tracking points for setting tracking filters for reporting.
select tracking points when creating conversions.
You can also use the extension to identify the desired tracking point ID for retargeting campaigns.
To retarget or extend the users that interacted with the specific tracking point, copy and paste the tracking point ID from the extension to the audience rule builder.
The Adform Site Tracking Chromium extension supports first-party and extended IDs (IDs that are provided by publishers or vendors). In the extension, these are called "eIDs".
To use the Adform Site Tracking Chrome extension:
Download the Adform STT TTE extension in the Chrome E-Shop. If using Edge, you can still install the extension using the same URL and path. (In Adform, you can click Site Tracking > Tracking Settings and then click .)
Click Add Extension.
Verify that the extension is active in the browser's Manage extensions page. (When you add the extension to your browser, it's usually turned on by default.)
Open the website with the tracking point.
Click in Chrome's menu bar (next to Extensions icon) and check the information in the pop-up window.
If you see the Client ID, the tracking point's path, and its name, you have implemented the tracking point correctly. If you don't see any information in the window, then something's wrong with the implementation.
You can also read about other ways to Check If the Tracking Point is Working.