Back
 

Overview

 

Very often advertisers are working with several affiliate programs. Most will “require” their tags to be placed on Homepages, Landing Pages, Product Pages, and Conversion Pages. When you are working with 15 Affiliates this means you have 15 tags firing on all of these pages, irrelevant to whether or not they contributed to the current session. This is very bad for advertisers when they consider Conversion pages, where they are essentially giving all Affiliates information on the buying preferences AND monetary value of your customers, even if they didn’t participate in converting the customer. Since it would require custom development to only fire the appropriate Affiliate tag on the Conversion page based on the entry referrer, most marketers simply deal with the situation.

 

This exercise will walk you through some basic Extension Use Cases for TealiumDemo.com sandbox accounts. To complete this exercise you will need a sandbox provisioned for you by your Channel Enablement Manager, after which you’ll have access to Tealium IQ, as well as the URL to access the sandbox site.

 

 


 

Set Data + Persist Data Extensions

https://community.tealiumiq.com/t5/Developers/Persist-Data-Value-Extension/m-p/1075
https://community.tealiumiq.com/t5/Developers/Set-Data-Values-Extension/m-p/1611

 

Tealium IQ makes it very simple to correct for this scenario with our Persist Data extension coupled with Load Rules. We will create a new cookie called Inbound Referrer, where we will store the Referrer value on the first entry page of a visit. This is an implementation to a “Last Click” attribution model. We’ll create a Load Rule on the Checkout page that checks for specific values of this cookie to conditionally fire each Affiliate tag.

 

The first step is to create a Custom data source using our Set Data extension, taking the DOM Elements Referrer data source, and setting it to a new data source (remember to use the [+] button) on the right of the Set field to create a new data source. Create a new Source of referrer_value and your own Description and Alias, set the To field to Variable and in the next drop-down use referrer under the DOM Elements section at top. Create a condition of referrer  is populated.

 

image02.png

 

 

The reason we used the Set Data extension to create a new data source is because the Persist Data extension doesn’t allow mapping the DOM Elements data sources. Now that we have it, we can add another extension and chose Persist Data. You’ll set the extension as below:

 

  • Title – Original Referrer
  • Execution – Before Load Rules
  • Persist – Variable  Referrer Value
  • Duration – Session
  • Update – Keep First Value Set
  • Store in Cookie – Original Referrer 
  • click the [+] to create and a source of original_referrer

 

image03.png

 

 

Now we have a Cookie named original_referrer that will store the first referrer value seen on the visit. We’ll create a Load Rule that checks this value before firing the tag on the Confirmation page. We’ll create a rule for Commission Junction and for Google AdWords. Navigate to Load Rules, create a new Rule, and set with the following values:

 

  • Title – Commission Junction / Conversant Referrer
  • page_type  equals (ignore case)  checkout
  • AND Original Referrer  contains  cj.com
  • OR page_type  equals (ignore case)  checkout
  • AND Original Referrer  contains  conversant.com

 

image00.png

 

 

Now let’s create the rule for Google AdWords. Navigate to Load Rules, create a new Rule, and set with the following values (hint, you can duplicate the previous and change values):

 

  • Title – Original Referrer
  • page_type  equals (ignore case)  checkout
  • AND Original Referrer  contains  google.com
  • OR page_type  equals (ignore case)  checkout
  • AND Original Referrer  contains  conversant.com

 

image01.png

 

Now of course we need to create tags for these new rules. Follow the steps from previous exercises for adding tags and add a Conversant (Commission Junction) and Google AdWords Conversion tag, and set each to their appropriate Load Rule. Now they will only fire on the Checkout page AND the Original Referrer contains a referring domain matching the Affiliate.

 

 


 

Save and Publish

We’ve completed our second Marketing scenario. Let’s now Save and Publish to Dev/QA.