The Teads Pixel is a requirement for Traffic Quality and Conversions campaigns only.

Using the pixel is optional for Clicks campaigns (although recommended to get additional website traffic insights), and it is not available for Branding campaigns.

The Teads Universal Pixel serves two main purposes: measurement and optimization.

It allows Teads Ad Manager to optimize your media towards outcomes on your website, leading to powerful middle and lower funnel results.

Without the Teads Pixel, Teads Ad Manager can only optimize towards upper funnel goals like Video Completion or Viewability; or middle funnel goals such as Cost Per Click or Click-through Rate.

It is recommended to implement the Teads Pixel as early as possible before the launch of your Quality Traffic or Conversions campaign. Early implementation will benefit the performance of your campaign as the Teads Pixel has access to more data to build a profile of your website's visitors.

For optimal results, the best practice is to place the Teads Universal Pixel in the header of your website, and ensure it fires across all pages.

For more information and instructions on how to do this, refer to our documentation.

If you are unable to implement the Teads Pixel in the header of your website, it is also possible to implement the javascript code in the body of the page. However, in order to measure accurately, the pixel must be implemented on all pages across the site.

Note: if the Teads Pixel is only placed on the landing page of your campaign and not the full website, Teads Ad Manager will not be able to collect some site-centric metrics like average number of pages viewed per session, or visits to pages where the pixel is not implemented.

This implementation method is not supported, as Teads cannot set its first party cookie when the Teads Pixel is implemented within a Floodlight or through other containers or piggybacking methods.

Advertisers unable to implement the pixel via Google Tag Manager or directly into their website's code will not be able to optimize towards website outcomes, and their campaigns will be limited to Clicks or Branding objectives.

Yes. The Teads Pixel can be implemented alongside Google Analytics.

Note: GA's term Session is equivalent to what Teads Ad Manager refers to as Visits. Teads has also recently updated its definition of a Qualified Visit to align with the latest definition for an Engaged Session in GA4, which is 10 seconds visit or 2 page views.

Teads Ad Manager can also support advanced measurement in Analytics by adding dynamic macros with each click. For a list of supported URL macros, refer to this article here.

Discrepancies in visits/sessions measurement between your analytics platform and your campaign dashboard in Teads Ad Manager should be minimal (5-10% can be expected).

Larger discrepancies could be related to an implementation problem and should be investigated. For more information on troubleshooting, refer to this article here.

The Teads Pixel relies on 2 first party cookies that are saved in the users' browsers:

TFPAI: TFPAI stands for Teads First Party Auction ID. It facilitates the correlation between a user's click on an ad and their subsequent visit to a website. The Teads Click ID (AuctID) is transferred to the site through URL decoration, and its value is stored in a cookie. This cookie remains active for 30 days.

TFPSI: TFPSI stands for Teads First Party Session ID. It enables the correlation of all user events to create a session, regardless of whether the user arrives from a Teads ad or not. This cookie enhances the accuracy and reliability of measurements, assisting Teads in enhancing website session metrics such as qualified visits rate and pages viewed. It is auto-generated and remains active for 30 minutes, with the option to be renewed for an additional 30 minutes.

Cookies are the main mechanism in digital advertising to facilitate user behaviour tracking; for both targeting and measurement purposes.

First-party cookies refers to those created and stored by the website that the user is directly interacting with, while third-party cookies are generated by external websites, which typically happens when the user visits a site containing elements (like images or scripts) from these external sources.

There are 3 primary purposes for cookies:

The changes introduced by leading browsers like Safari and Firefox, which involve phasing out support for third-party cookies, means that the Teads Pixel can only rely on first-party cookies. This is the reason why it cannot be implemented through floodlights or other containers.

Additionally, Teads Ad Manager uses technology such as the Teads Click ID, which improves the number of deterministic signals available for the Teads Pixel for performance measurement in cookies-restrictive browsers.

Teads tracking technology provides access to the following information and technical specifications of the device:

Teads uses the aggregated data to report on and optimize the performance of campaigns.

Yes. Teads Pixel collects data points such as the IP address and device type in order to create a unique identifier for each user and household (i.e. devices on the same network). This enables tracking of online activities across different websites and devices for measurement, attribution, and optimization purposes.

Pursuant to the main privacy regulations in Europe (ePrivacy and GDPR) and in the US (CCPA), advertisers must place the Teads Pixel to be triggered post-consent. Users who visit the advertiser's website must be provided with appropriate information and choice mechanisms to opt-in or opt-out (depending on the applicable regulation), or to withdraw consent. This information should also include the descriptions of how data is collected, how that information is being used, if data is being collected by or shared with third parties, and where users can easily control their experience and exercise their rights.

Teads should also be listed as a partner on the website, with a link to Teads’ privacy policy (https://www.teads.com/privacy-policy/) and the following disclosure:

Teads will use tracking technologies to improve its product, and as part of the ad serving services operated with the advertiser to measure and optimize ad conversion, bounce rate, and time on site for the traffic that Teads is sending.

Teads Ad Manager uses technology to automatically detect pixels loading without user consent and blocks these domains from receiving signals and/or being used in campaigns.

If your website's domain has been blocked, please contact us via Intercom for additional support.

Every website using the Teads Pixel must integrate a CMP (Consent Management Platform) to secure user consent. Teads encourages its partners to adhere to IAB frameworks for technical interoperability between stakeholders, facilitating the transfer of proof of consent or opt-out.

Transparently identifying Teads as a vendor and providing clear information to users is crucial. Activation of the Teads Universal Pixel should occur only after obtaining valid consent in accordance with local regulations relevant to your users' jurisdiction.

Please ensure that your Website's Privacy Policy is updated in alignment with the details presented in the Teads Advertising Privacy Policy.

A Consent Management Platform (CMP) is a software tool or system used by website owners or operators to manage user consent regarding the collection and processing of personal data, particularly in compliance with data protection regulations such as the General Data Protection Regulation (GDPR) in the European Union or the California Consumer Privacy Act (CCPA) in the United States.

CMPs typically provide features such as consent collection, storage, documentation, and preference management. They allow website visitors to make informed choices about the use of their personal information by providing clear information about data processing activities and obtaining explicit consent where required. Additionally, CMPs often offer mechanisms for users to modify their consent preferences over time, and for website owners to demonstrate compliance with relevant data protection laws.

All data is sent exclusively to the Teads servers through a secured protocol (SSL/HTTPS), behind the main domain teads.tv. Specifically, the pixel script is delivered behind the domain p.teads.tv, communication with the script is done via the domain cm.teads.tv, and data collection is conducted through the domain t.teads.tv.

Additionally, Privacy Sandbox experiments are conducted using the domains fledge.teads.tv and cm.teads.tv.

To enable us to measure and optimize, websites that use content security policies must add the following rules:

Alternatively, allow default-src for https://*.teads.tv and 'unsafe-inline'.

The complete Teads Advertising Privacy Policy is available here: https://privacy-policy.teads.com/