Once you have followed the steps to create and install the Teads Pixel, the final step of the pixel configuration process is to set up the conversion events that are relevant to your brand.
A predefined list of standard events for tracking is available within every pixel in Events Manager, with each event offering URL Based and Code Based triggering options. The Events Manager will also give you overall statistics on your pixel and your created conversions.
Follow these steps to set up a conversion event:
1. Click on the Events button of your pixel in Events Manager.
2. A new panel will appear, listing all the available event types. To start configuring an event, click on the appropriate event type, e.g. Add to Cart or Purchase.
3. There will be two options for conversion creation:
Code-based events:
Code-based events:
This consists of firing the event by directly incorporating a piece of code onto the website. This code is designed to trigger the specific event when it occurs.
Follow the instructions below to do this:
Copy the code snippet from the Code Based Event tab.
Configure the code snippet to load whenever the specific event occurs on your website. You can do this by using a tag management solution like Google Tag Manager or by adding the code directly to your website's code.
Refer to the steps below to implement the pixel via Google Tag Manager (recommended):
Open GTM and select the Workspace associated with your website.
Click Add a new Tag.
Select Tag Configuration.
Click on Discover more tag types in the Community Template Gallery.
Search for 'Teads' and select the tag named Teads Advertiser Pixel.
Click the Add to Workspace button to add the tag template to your Workspace.
Select Tags from the menu and click New.
In Tag Configuration, select Teads Advertiser Pixel.
Enter your Pixel ID from the Events Manager section in Teads Ad Manager into the Teads Identifier input on Google Tag Manager.
Select the Event based pixel option within the Teads Advertiser Pixel template, and enter the name of the standard event in the field provided.
You can also add event metadata for more advanced tracking. For more information, refer to our Event Metadata documentation.
Select the most appropriate trigger to fire your conversion event.
If you prefer to implement the event code directly into the HTML of your site, please follow the steps below:
Implement the event code in the <head> section of the page where the conversion event takes place in the website (e.g. product pages, purchase confirmation page).
Ensure that the event code is properly formatted. There should be no spaces in the conversion type value. For example, "AddToCart" should be used instead of "Add To Cart".
When using event metadata (recommended), it is possible to add name, price, and currency values for more advanced event tracking. The 'name' value can use any text with no special formatting required. Note that metadata values must be populated dynamically. For more information, refer to our Event Metadata documentation.
You must ensure that the conversion tag script is only triggered when the conversion point is reached. It is possible to fire the tag based on a variety of triggers including (but not limited to):
Visiting a specific URL: If the code will be triggered by a URL (e.g. order confirmation page), it is strongly recommended that it be implemented in the backend of the website and triggered via the server.
A click on a specific element: This will require implementing additional javascript based on your website's structure. Refer to the step by step guide here.
Viewing a specific element: This will require implementing additional javascript based on your website's structure. Refer to the step by step guide here.
URL-based events
URL-based events
This option does not require any additional code integration on the website. Instead, it involves setting a URL as the trigger for the event, such as the URL of a purchase confirmation page. To use this option, click on the URL Based Event tab.
In this section, you have the ability to add a new URL (using the "equals" condition) or a keyword (using the "contains" condition). Whenever our pixel is called on a page, the event will be tracked accordingly.
To add a keyword in the URL, use 'URL Contains' (recommended):
This is recommended as website domains differ from one country to another.
For example,
US version of the domain: www.teads-advertiser.com/cart
FR version of the domain: www.teads-advertiser.fr/cart
IT version of the domain: www.teads-advertiser.it/cart
etc.
To map the Add to Cart event across multiple domains, add the keyword "cart" to create a single event that covers all the domains.
To add a full URL, use 'URL Starts with':
After you have added the URL, click on "Check Activity" button to ensure proper functionality. This action opens a new browser tab containing the entered URL to verify if our pixel is correctly firing on that page. If the pixel is successfully triggered, a green light will be displayed, and the "Save" button will become accessible, allowing you to proceed with saving the configuration.
In the event of a failed URL check, it can be attributed to either the pixel not being installed correctly or your website not responding within the specified timeout period. Note that a failed URL check does not prevent you from saving the URL configuration, so we recommend re-checking again at a later time to ensure that the URL displays a green light and shows activity.
Note: Adding a Conversion Name from the 'More Options' section during event creation is not mandatory but strongly recommended. Using conversion names will allow users to report separately on URLs or keywords configured under the same event category.
For instructions on how to add a Conversion name to a code-based event, as well as more advanced event configuration options, refer to our Event Metadata documentation.