...
- First party tracking domain used?
The tracking should be running on a sub domain of the shop. The name of the sub domain ideally should be a random string. Example:https://
qzxe
xcx23123.tmw.shopyourdomain.com
read more here: First-party Tracking Setup
- Is the tracking domain black listed (and hence easily blocked by ad blockers)?
You may check here, especially if the onpage tag is implemented:
https://trackingthetrackers.com/
You may also search for your domain here:
https://easylist.to/easylist/easyprivacy.txt
https://easylist.to/easylist/easylist.txt
About the conversion tag
- Is the conversion tag executed server side?
We do not recommend to execute the conversion tag executed in the browser
...
- , independent if you use a tag management system
...
- or not. We would expect a significant loss of data (15-25%)
...
- using a browser-side setup, and even more if you use a tag manger, since they are well known to ad-blocking software and browsers and can be easily blocked.
...
Execute the conversion tag
...
- server
...
- -side (and hence bypassing the browser)
...
- . You may use a server-side tagging solution (like server-side Google Tag Manager) if you execute the JavaScript part (ga.js) on a first-party domain (recommended by Google).
Read more: Configuring and implementing tracking
...
- tags server-to-server (S2S)
- Are click
...
- IDs transmitted (iclid)?
With every (bounce) click, Ingenious transmits a click id as parametericlid
. This iclid(s) should be stored by the shop (
...
- in a first party cookie, or attached to the sale/order) and transmitted in the conversion tag. Note that an order might have multiple click IDs assigned, because the user might have several independent interactions before the conversion.
read more: Working with the click ID - Is the session
...
- ID transmitted?
The session id should be transmitted in the conversion tag as well as in the onpage tag to increase tracking accuracy. What the session ID is relies on your specific system. Typically it’s a value which is consistent over several page-loads of the same user, sometimes even across browser-sessions.
read more: Conversion Tracking Implementation: Guide for shops - Is the customer
...
- ID transmitted?
Whenever a customer is logged in, the customer id (may be hashed) should be transmitted in the conversion tag (as well as in the onpage tag) to increase tracking accuracy as well as enable cross device tracking.
read more: Conversion Tracking Implementation: Guide for shops
Onpage tag
- Is the onpage tag implemented on all publicly accessible pages?
The onpage tag (using a first party domain) should be implemented on all public pages to detect incoming traffic.
read more: Working with Bounceless (SEO-friendly) tracking - Is all relevant data transmitted in the onpage tag?
Session id, customer id (may be hashed) are highly important to improve tracking accuracy. Product id for product pages is quite useful as well.
...