In this instruction you will read how to implement the Daisycon Conversion Pixel with Google Tag Manager (GTM). There are different scenarios for the implementation. Choose your scenario below and follow the steps.
Scenario 1:
You know how to use GTM and/or have used it before. There is a Data Layer available on the website and the order information is available as variables in GTM. Follow step 1.
Scenario 2:
You are not familiar with GTM, but there is a Data Layer available on the website. Follow step 1 and 3.
Scenario 3:
You are new to GTM and everything needs to be set-up. Follow step 1, 2 and 3.
Step 1 (add a new tag):
Go to Templates in the sidebar to start using our Tag Template in Google Tag Manager. You can find our Tag Template if you click on "Search Gallery". In this menu you can scroll to "Daisycon Conversion Pixel". If you click on this, Google Tag Manager gives you a summary about our Tag Template. Now add this to the workspace to start working with it.
After adding it to your workspace, our template will be available when adding a tag. Go to "Tags" and click on "New". In this screen you can find the Daisycon Conversion Pixel at the Custom part of the tag type list.
You can now enter values or add available Google Tag Manager variables in the form. If there are no variables available yet, read in step 3 about how to create these. It's possible to click on the question mark if you need extra information about a field.
Link to the Google Tag Manage gallery:
https://tagmanager.google.com/gallery/#/owners/DaisyconBV/templates/gtm-daisycon-conversion-pixel
Attention! It might happen that the implementation by means of the Daisycon Tag Template does not work properly. If this is the case, please use the following method:
Add a new custom HTML tag. Copy the conversion pixel from your Daisycon account: Settings -> Conversioncodes -> Daisycon pixel -> Shop type: Google Tag Manager. Enrich the conversion pixel with extra variables if necessary. Paste the complete conversion pixel as a HTML tag.
Important:
- Rename variables to variables that are already available in the Google Tag Manager workspace
- Remove variables that will not be used!
After adding the new Tag, you should add a trigger.
- Add a 'Trigger' to the tag.
- Trigger Type: Page View - DOM Ready
- Make sure the trigger fires at the 'Thank You' or 'Success' page. For example by adding a 'Page URL' => 'contains' => 'success'
It's also possible to add a trigger based on a (custom) event or any other action. More information about Google Tag Manager Triggers here.
Save the tag and the trigger and publish your edited workspace. After publishing, please contact your channel manager for testing the conversion pixel.
Step 2 (create a data layer):
To connect transaction information to Google Tag Manager (and the Daisycon conversion pixel) your website should contain a Data Layer. This Data Layer should be present on the 'Thank You' page or 'Success' page of your website. This Data Layer is the source of the data. If you look at the source code of this success page, the Data Layer could look like this:
<script>
dataLayer = [{
"transaction-id":"12345",
"description":"order from webshop",
"amount":"19.99",
"compensation-code":"12345 / abcdef";
}];
// This is just an example!
</script>
- Create a new Data Layer if necessary (more information about this)
- Follow all the steps from Step 1 if the variables already exist
- If the variables do not exist please create them following the example below
Step 3 (create variables):
Check if the mandatory variables are available in your GTM workspace. If not, add the missing variables. You can read here how to add additional variables to your GTM workspace.
|
variable |
example variable names |
mandatory |
description |
example |
|
ci |
campaign-id |
yes |
your Daisycon campaign-id. Ask your channel manager |
12345 |
|
ti |
transaction-id |
yes |
order number |
12345 |
|
pn |
product-name |
yes |
description for publisher |
order from webshop |
|
iv |
internal-value |
no |
description only for advertiser |
order from webshop |
|
a |
amount |
yes |
total amount excl. shipping cost |
19.99 |
|
r |
revenue |
yes |
total amount |
19.99 |
|
cc |
compensation-code |
highly recommended |
with this field we would be able to meassure different commission groups if required |
12345 / abcdef |
|
pr |
promotion-code |
highly recommended |
the promotional code used |
promo |
|
c |
country |
no |
country (ISO 3166-1, alpha 2) |
NL |
|
z |
zipcode |
no |
zipcode |
1314CH |
|
g |
gender |
no |
gender |
f |
|
b |
birth date |
no |
year of birth (yyyy) |
1984 |
|
cur |
currency |
no |
multicurrency support (ISO 4217) |
EUR |
|
sku |
sku |
no |
sku |
12345 / abcdef |
|
e1 |
extra1 |
no |
extra variables to enrich the conversion pixel |
12345 / abcdef |
|
e2 |
extra2 |
no |
extra variables to enrich the conversion pixel |
12345 / abcdef |
|
e3 |
extra3 |
no |
extra variables to enrich the conversion pixel |
12345 / abcdef |
|
e4 |
extra4 |
no |
extra variables to enrich the conversion pixel |
12345 / abcdef |
|
e5 |
extra5 |
no |
extra variables to enrich the conversion pixel |
12345 / abcdef |