Eskimi Pixel Implementation via GTM

Integrating tracking pixels into your digital marketing campaigns is crucial for effective measurement and optimization. If you're using Eskimi DSP for your advertising needs, this manual article will guide you through the process of implementing the Eskimi DSP tracking pixels seamlessly using Google Tag Manager (GTM).

Follow the step-by-step instructions below to efficiently set up the Eskimi DSP tracking pixels through GTM and ensure accurate tracking and measurement of your advertising efforts.

It is important to note that when implementing pixels, testing should be conducted in collaboration with the Eskimi support team. This will ensure accurate data collection, and validate whether the pixel is properly integrated with your website.

Audience pixel implementation (automated version)

!Important - do not use it with conversion tracking until further notice

Eskimi DSP has been included in the Google Tag Manager's Community Template Gallery, streamlining the process of deploying the Eskimi DSP tracking pixel on client websites that utilise GTM.

• Access your GTM account, and on the top left side of the page select New Tag 
• Name the Tag according to the tag configuration and triggering
• Under Tag Configuration choose tag type - Discover more tag types in the Community Gallery
• Type Eskimi in the search bar and select Eskimi tracking pixel
• If this template is being added for the first time, click on Add to Workspace
• In the new pop-up window press Add
• Enter / paste tracking pixel ID and under Advanced Settings select Tag firing option - Once per page
• Under the Triggering section choose a default trigger - All Pages (Page View)
• Press Save to save the tag and Submit changes

Audience pixel implementation (manual version)

• Access your GTM account, and on the top left side of the page select New Tag 
• Name the Tag according to the tag configuration and triggering
• Under Tag Configuration choose tag type - Custom HTML and paste the Eskimi DSP base (audience) tracking code
• Under Advanced Settings select Tag firing option - Once per page 

• Under the Triggering section choose a default trigger - All Pages (Page View)
• Once the Tag Configuration and Triggering is added, press Save

Conversion pixel implementation

• In order to implement Eskimi conversion tracking pixel, press New Tag
• Name the tag according to the tag configuration and triggering
• Under Tag Configuration choose tag type - Custom HTML and paste conversion tracking code.
• Under Advanced Settings select Tag firing option - Once per page 

• To finalise Eskimi conversion pixel implementation, under the Triggering section choose an existing trigger for conversion or create a new one. In the example below you can see the most common trigger for tracking conversions with success/thank you page url.

Submit the changes

Once you have set up the necessary pixels and triggers, the last and most important step is to submit the changes. Without submitting them, the changes will not be applied to the actual environment of the site. To do this, go to the overview page and look for the "submit" button in the top right corner. Click on the "submit" button and follow the process until all the recent changes are published on your website. This submission ensures that the modifications you have made will take effect and be visible in the live environment of your site.

Tag Sequencing / Prioritisation

You can control tag firing prioritisation in the Advanced Settings of a tag. *This configuration is implemented on the page where the conversion pixel is deployed, ensuring that the "Tracking pixel" fires first before the "Conversion pixel" because the conversion pixel relies on the "esk" function described in the tracking pixel.*

• Tag Firing Priority: Determines the order in which tags will be fired. The value can be a positive or negative integer, and tags with higher values will fire before those with lower values. (For example, a priority 3 tag will fire before a priority 1 or 2 tag.) Priority defaults to 0 if no value is specified. Tags will still fire asynchronously.

In our case, we need to set the Eskimi tracking pixel priority to 2 and the conversion pixel priority to 1.

If other tags, such as analytics tags, are also used in the webpage setup, or if tag priority is utilised in other scenarios, "Tag sequencing" can be an alternative to "Tag firing prioritisation." This approach ensures that tags fire in a specific sequence, which can prevent conflicts when numerous tags are present on the same page or "Tag firing prioritisation" is used with other tags.

In our scenario, we can specify which tag should fire before or after a particular trigger. It's crucial to ensure that the "Tracking pixel" fires before the "Conversion pixel" or in other words - "Conversion pixel" fires after the "Tracking pixel".

OR

Here is a video that demonstrates the entire process without Tag Sequencing / Prioritisation.