Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /nas/content/live/liveintentkbd/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the knowledge domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /nas/content/live/liveintentkbd/wp-includes/functions.php on line 6131
Supported Third-Party Tags - LiveIntent Knowledge Base

Supported Third-Party Tags

Supported Third-Party Tags

While creating campaigns on the LiveIntent Platform, you may use third-party ad tags. The tags below have been tested to ensure LiveIntent can support tracking accordingly. 

Modification instructions for the ad servers and brand safety tags below can be found here

  • Google Campaign Manager 360 (CM360)
  • Sizmek
  • DoubleVerify
  • Integral Ad Science (IAS)
  • Mediaplex/Conversant
  • CAKE
  • Flashtalking 
  • AdForm

Third-Party Tracker Click Discrepancies

LiveIntent uses click-filtering logic as a measure to isolate various types of fraudulent click patterns within email newsletters. As we identify click patterns that are fraudulent, our click filtering logic adapts to remove these anomalous click counts from client reporting.

  • A few examples of potentially fraudulent traffic that can lead to anomaly clicks are bot traffic and high counts of clicks from the same IP and user-agent.

Due to LiveIntent’s use of click-filtering logic, it is fairly common that LiveIntent reports less clicks than third-party reporting. This is largely in part due to the majority of third-party tag providers not being designed for the email environment.

Back to top