Help:Editing

From Wiki

(Difference between revisions)
Jump to: navigation, search
Alex Searle (Talk | contribs)
Mirjam Eden (Talk | contribs)
(Blanked the page)
 
Line 1: Line 1:
-
= [[GTM Setup Via Custom Code]] =
 
-
[[File:GTM Logo.PNG]]
 
-
 
-
== About this Guide ==
 
-
This guide was produced as an example of the steps that could potentially be followed to implement custom tags for the Awin tracking code into Google Tag Manager and as a method of demoing such an implementation. The variables, triggers and tags also do not reflect a finished implementation.
 
-
 
-
Awin will not claim any responsibility for programs that suffer as a result of the use of Google Tag Manager and does not claim to be able to provide full support for the platform.
 
-
 
-
Extra assistance may be found on the Google Tag Manager Community Pages
 
-
 
-
== Accounts ==
 
-
In order to access Google Tag Manager, you must create a Google account. This can be done from the Google search page. Once you have this account, you must then navigate to the Google Tag Manager Login page and click “sign in”.
 
-
 
-
Once signed in, you will be directed to the “Get Started” page where you will create your first Google Tag Manager account. Next you will be prompted to set up a Container for this new account. So far we have created two accounts: 1. Google Account; 2. Google Tag Manager Account. In the below example, the Account Name is ‘Awin’ for demonstration purposes. Please set this to your desired account name.
 
-
 
-
[[File:Add_a_new_account.PNG]]
 
-
 
-
== Container ==
 
-
A Container holds your Google Tag Manager implementations together. Multiple containers can be created in a single Google Tag Manager account.
 
-
 
-
[[File:ContainerCreator.PNG]]
 
-
 
-
'''Container Name'''
 
-
Apply an appropriate name for the container.
 
-
 
-
'''Where to use Container'''
 
-
We will be conducting a web page implementation.
 
-
 
-
== Implementing the Container Code ==
 
-
In the next screen you will be asked to accept the terms and conditions and then you’ll be supplied with the container tag code. This code needs to be implemented on every page of the website (including the confirmation page) as close to the opening <head> tag as possible [2]. You can copy this code now and place it on your site or you can continue and add it later.
 
-
 
-
[[File:InstallGoogleTagManager.PNG]]
 
-
 
-
[[File:GTMContainerCode.PNG]]
 
-
 
-
 
-
== Variables ==
 
-
 
-
[[File:VariableIcon.jpg]]
 
-
 
-
Variables are populated inside of Google Tag Manager via code added on the confirmation page. By clicking on the “Variables” button, you will see that some variables are already created by default but you will need to create new variables for this implementation.
 
-
 
-
Click the “new” – “User defined variables” button to get started.
 
-
 
-
You will be asked to choose the type of variable, select ‘data layer variable’ from the list:
 
-
 
-
[[File:ChooseVariableType.PNG]]
 
-
 
-
Enter the data layer variable name and click ‘save’:
 
-
 
-
[[File:VariableConfiguration.PNG]]
 
-
 
-
If not done already, you will then be prompted to name your variable, please name the variable in accordance with the table on the next page and click the “Save” button.
 
-
 
-
[[File:RenameVariable.PNG]]
 
-
 
-
Repeat this process with the information from the table on the next page.
 
-
 
-
[[File:VariablesTable.PNG]]
 
-
 
-
[[File:VariableTab;eWarning.PNG]]
 
-
 
-
On completion you should see the same values in your variables table as below:
 
-
[[File:UserDefinedVariables.PNG]]
 
-
 
-
== Triggers ==
 
-
 
-
[[File:Trigger.jpg]]
 
-
 
-
Select the ‘Triggers’ column in the left hand menu bar
 
-
 
-
[[File:TriggersMenu.PNG]]
 
-
 
-
The rules created here can be used to trigger the firing of the Tags stored in Tag Manager. Click the “NEW” button to get started. Then select the Trigger Configuration box; select ‘Window Loaded’ and click continue.
 
-
 
-
[[File:ChooseTriggerType.PNG]]
 
-
 
-
Leave the trigger type as ‘Page View – Window Loaded’. Click ‘continue’ and select ‘Some page Views’.
 
-
 
-
The trigger being created will fire the tracking tags whenever a user reaches the sale confirmation page. To do this set “Page URL”, “contains” and “checkout/success” (select the appropriate page name from your site).
 
-
 
-
[[File:TriggerConfiguration.PNG]]
 
-
 
-
Click ‘save’ and you will be asked to rename the trigger, here add an appropriate trigger name e.g. ‘awinTrigger’.
 
-
 
-
[[File:RenameTrigger.PNG]]
 
-
 
-
Click ‘save’ and now you should have the variables and triggers in place.
 
-
 
-
Please note: You may already have triggers that allow tags to fire on the confirmation page. If that is the case then you don’t need to create new trigger and can just use the ones you already have created
 
-
 
-
== Tags ==
 
-
 
-
[[File:Tags.jpg]]
 
-
 
-
Tags are snippets of any code a user may want to fire based on certain conditions. In this case, it is the Awin Tracking Code.
 
-
 
-
The Awin Google Tag Manager plugin allows you to enter the variables names without messing with any code. (Please click here for guide). However, a custom HTML setup will be needed for more complex features (e.g. Product Level Tracking).This guide will allow you to create custom tags for Awin tracking and will also enable you to set up ‘Product Level Tracking’ if desired.
 
-
 
-
== Conversion Tag ==
 
-
 
-
Select the ‘Tags’ column in the left hand menu bar
 
-
 
-
[[File:TagsMenu.PNG]]
 
-
 
-
Click the ‘NEW’ button and you will now have the opportunity to create a new tag
 
-
 
-
[[File:NewTags.PNG]]
 
-
 
-
Click the ‘Tag Configuration’ box and select ‘Custom HTML’ as the tag type. This will allow you to set up the conversion part of the tracking code.
 
-
 
-
[[File:ChoseTagType.PNG]]
 
-
 
-
Now paste the code provided by your tech contact.
 
-
[[File:CustomHTML.PNG]]
 
-
(Please replace all instances of XXXX with your unique advertiser ID.)
 
-
 
-
We will need to add a trigger to define when the tag should fire. We only want this tag to fire on the confirmation page so select the trigger you made earlier. Click the box named ‘Triggering’.
 
-
 
-
[[File:Triggering.PNG]]
 
-
 
-
Select the “awinTrigger”
 
-
[[File:AwinTrigger.PNG]]
 
-
 
-
When finished, click ‘SAVE’. You will then be asked to rename the Tag, give it a meaningful name e.g. awinConversionTag.
 
-
 
-
[[File:RenameTag.PNG]]
 
-
 
-
== MasterTag (Journey Tag) ==
 
-
 
-
The MasterTag (Journey Tag) needs to be set up to fire on all pages except the confirmation page. Click ‘New’ and select “Awin Journey”.
 
-
 
-
Enter your assigned merchant ID.
 
-
 
-
[[File:MasterTag.PNG]]
 
-
 
-
The journey tag must be globally triggered once on all pages. This can be achieved by adding a new trigger. To add this trigger, click the box named ‘Triggering’. Now select the ‘All Pages’ trigger.
 
-
 
-
[[File:AllPagesTrigger.PNG]]
 
-
 
-
It is necessary to add an exception rule to prevent the Journey tag from being triggered on the confirmation page. This is because the Journey Tag is already included at the bottom of the Custom HTML code snippet so that it is set to fire on the confirmation page.
 
-
 
-
To add an exception for the journey tag not to appear on the confirmation page so you will need to select the “awinTrigger” set up previously.
 
-
 
-
To do this, click the “ADD EXCEPTION” button and select the “awinTrigger”
 
-
 
-
[[File:AwinTrigger1.PNG]]
 
-
 
-
Save the Tag and name it ‘awinJourneyTag’
 
-
 
-
[[File:RenameTag1.PNG]]
 
-
 
-
You should now have the Tags listed in the Tags table with the correct firing triggers.
 
-
 
-
[[File:DualAwinTags.PNG]]
 

Current revision as of 11:19, 23 September 2019

Privacy

Due to new European legislation regarding how websites store information about you, AWIN is updating its privacy policy. You can see the new version of our policy here. If you would like to see the information we capture on this website, please click here for further details. In order to accept cookies on this site please click the 'I ACCEPT' button