The success of your campaign's performance depends heavily on the implementation of the Yieldr pixel, your Yieldr Ads Tag, which needs to be placed either in the source code of your website or in your tag management system. The main purposes of the Tag is to track visitor data so we can find back these visitors on other websites (where your advertisement is being served) and show them the products we know they are interested in.
Our tag contains several scripts from third parties that help us track your visitors’ interests and preferences (up to a certain non PII level). For more information on our policies on privacy and data collection feel free to contact us.

What our Tag does in a nutshell

  1. If a user visits your website for the first time since our tag was placed, the tag will create a cookie file[1] that is hosted on the user’s computer. This cookie contains a unique ID, which Yieldr uses to find the user and store data about this user in its database. The stored information can be for example a product ID, a category name or a country that was looked at by the visitor on your website.
  2. When that same user then visits a different website, where your advertisement is being served (i.e. a publisher website), our script contained in your creative will check if there is a cookie file on the user’s computer.
  3. If a cookie is found that matches with the XML-file attached to the creative, the creative will automatically show a product from the XML-file corresponding with the user’s interests.

If no cookie is found, either a pre-set or a random product from the XML-file will be shown to the visitor.
The Tag can be implemented either directly in the websites source code, or (preferably) within a tag management system. It is very important that the Tag scripts are placed within the page without any alterations to the code (except alterations to set the variables inside the tag).

IMPORTANT NOTICES

  • The values passed through in the parameters should be encoded in UTF-8. If the values are not encoded in this way, it will cause the Yieldr Tag to malfunction. 
  • The Tag should be implemented on every page of the website and in every language version. The Tag may contain one or more parameters that have to be filled dynamically with data from the viewed page. Some of these parameters will be used for retargeting, others are solely for reporting purposes.
  • The parameters in the Tag should be filled dynamically, so they contain the available data from the page being viewed. When an ajax request is done, the advertiser custom data script should change accordingly. When the data is not available at a certain page it can be left empty. For example:
yldr.set("returndate", "");

Please note: Use a dot symbol '.' to define decimals. Use a semicolon ';' to separate multiple values when necessary.

Follow the 5 steps below for a correct implementation:

  1. Copy the Tag script you have configured
  2. Add the Tag script to your website's HTML, preferably by putting it into your tag management system (TMS). When you don't have a TMS you can implement it directly in the source code of your website.
  3. Make sure that all parameters you have configured in the first step are being filled with the right data.
  4. Test the implementation by using the Yieldr Tag Inspector
  5. Start creating cases.

[1] A cookie is a piece of text stored on a user's computer by their web browser. A cookie can be used for authentication, storing site preferences, shopping cart contents, it can be the identifier for a server-based session, or anything else that can be accomplished through storing text data.

Did this answer your question?