Skip to main content
All CollectionsTeads Universal PixelGet Started
Create and Track Conversion Events
Create and Track Conversion Events

Learn how to set up conversion event tracking to measure the website actions that are important to your brand

Updated over 6 months ago

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.

Each Teads Pixel in TAM Events Manager allows you to track 8 types of conversion events, each of which can use either URL-based or code-based triggers. The Events Manager also provides detailed statistics on your pixel and created events.To view these statistics, select View Pixel Activity from the pixel options menu.

Follow the steps below to set up a conversion event:

1. Select the Setup Events button of your pixel in Events Manager.

2. A new panel listing all the available event types will appear. To start creating an event, click on New Event on the right side of the event type you wish to configure, e.g. Add to Cart, Purchase, etc.

3. There will be two options for creating conversions to choose from:

Code based & GTM events:

This is the recommended method of event configuration, and consists of directly incorporating a piece of code onto your website, which will be triggered when the specific event occurs (e.g. Purchase, Search, Complete Registrations, etc).

There are two methods available to trigger code-based events:

  1. Using the Teads Advertiser Pixel template in Google Tag Manager (recommended), or

  2. Manually configuring the code snippet within the code of your website to load whenever the specific event occurs.

Refer to the steps below to implement the pixel via Google Tag Manager (recommended):

  1. Open GTM and select the Workspace associated with your website.

  2. Click Add a new Tag.

  3. Select Tag Configuration.

  4. Click on Discover more tag types in the Community Template Gallery.

  5. Search for 'Teads' and select the tag named Teads Advertiser Pixel.

  6. Click the Add to Workspace button to add the tag template to your Workspace.

  7. Select Tags from the menu and click New.

  8. In Tag Configuration, select Teads Advertiser Pixel.

  9. Enter your Pixel ID from the Events Manager section in Teads Ad Manager into the Teads Identifier input on Google Tag Manager.

  10. Select the Event based pixel option within the Teads Advertiser Pixel template, and enter the name of the standard event in the field provided.

  11. You can also add event metadata for more advanced tracking. For more information, refer to our Event Metadata documentation.

  12. 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, follow the steps below:

  1. Copy the code snippet from the Code Based section.

  2. 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).

  3. 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".

  4. 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.

  5. 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):

    1. Visiting a specific URL: If the code will be triggered by a URL (e.g. order confirmation page), it is strongly recommended that it is implemented in the backend of the website and triggered via the server.

    2. 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.

    3. 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 or Keyword 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, start by clicking on the URL or Keyword based tab in the events configuration screen.

  1. Click on Add URL Or Keyword. You may use a full URL (using the "Starts with" condition) or a keyword (using the "Contains" condition). Whenever our pixel is called on a page, the event will be tracked accordingly.

  2. To add a keyword in the URL, use 'URL Contains' (recommended):

  3. 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.

  4. The Metadata section includes the option to give your conversion event a specific name, which is strongly recommended to allow differentiation between events configured under the same event type.

Note: Adding a Conversion Name from the 'Metadata' 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 and GTM events, as well as more advanced event configuration options, refer to the Event Metadata documentation.

Did this answer your question?