Pixel 2.0 Release: All You Need To Know

We have released new version of GLAMI Pixel. This article summarizes what it means and what you can do to fully benefit.

We are following the market trends

Our original GLAMI Pixel was built on 3rd party cookies. However, it is clear that the market is moving away from them. The biggest browsers are either already restricting 3rd party cookies (Safari) or planning to do so soon (Google Chrome). In the same time, we perceive as our duty to secure proper tracking of users in all of the major browsers. Only with that ability we are able to secure the best possible performance for our partners.

That is why we have introduced GLAMI Pixel 2.0 on April 22nd, our update tracking methodology that is built on 1st party cookies. This secures properly functioning tracking methodology in line with the current trends on the market.


How it affects you

This means that you can be sure that GLAMI Pixel will capture user traffic from all major internet browsers, and therefore your performance and campaigns will be optimized in the best possible way. However, we can secure this only if GLAMI Pixel is properly implemented on your eshop.


Actions you can take

Here is what you can do to make sure that your performance on GLAMI will not be affected. Please double-check that your GLAMI Pixel implementation is done completely in line with our Pixel Implementation Guide.

If you had GLAMI Pixel implemented perfectly already before the change (for previous version of Pixel), you don't need to change anything and GLAMI Pixel 2.0 will work for you as well. However, some aspects of the implementation were not critical for original Pixel, but are absolutely critical for Pixel 2.0.

These three requirements are most crucial:

  • 1) Implementation of Pixel event on EVERY landing page from GLAMI.
    • This event can be ViewContent event, PageView event or both
    • It is critical that at least some event is triggered, otherwise we might not be able to track the user traffic
    • By "landing page" we mean the first page where the user is redirected after leaving GLAMI to your e-shop. This should typically be the product landing page.
  • 2) Parameter GLAMI click id ("?gci=") is included into the url of EVERY landing page
    • Please make sure that your website or your tracking service are not blocking or deleting this parameter from the URL. Sometimes your affiliate program could cause this problem.
  • 3) GLAMI Pixel code should be implemented at the beginning of the html source code (before </head>), or via Google Tag Manager.
      • This assures that the code gets always loaded, even when user is quickly clicking on other pages on your eshop

    It is important that you make sure that your Pixel implementation is done in line with these requirements, otherwise it can happen that we are not able to track some part of user traffic on your eshop.

    One more step to secure best possible performance: GLAMI Audiences

    GLAMI Audiences is the latest result of our continuous effort to leverage data and show your products to the most relevant visitors of GLAMI. These two requirements will help you fully benefit from this feature:

    1. The ViewContent event contains valid ITEM IDs, and
    2. Item IDs in GLAMI Pixel are the same as ITEM IDs in your feed