...
Try to avoid that your tracking domain is listed in ad and private blocking lists
You may check here:
- https://trackingthetrackers.com/
- You may also search for your domain here:
https://easylist.to/easylist/easyprivacy.txt
https://easylist.to/easylist/easylist.txt
...
Execute the conversion tag on the server side
We do not recommend to execute the conversion tag 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)
Track cookieless using click IDs (iclid)?
With every redirect click, Ingenious transmits a click id as parameter iclid (Ingenious Click Id). This iclid(s) should be stored on the advertiser-side in the user-session (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.
Track cookieless using external click IDs (i.e. gclid, fbclid)?
If you use a system which generates it’s own click IDs, or use advertising system which generate their own click IDs (like Google Ads), you can use these IDs in the conversion tag.
Read more: Working with the click ID
Use Session IDs
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
Attach the Customer ID
Whenever a customer is logged in, the customer id (may be hashed) should be transmitted in the on-page and conversion tag to increase tracking accuracy as well as enable cross device tracking.
Read more: Conversion Tracking Implementation: Guide for shops
...
Send extended data for attribution in the onpage tag
Extend your onpage tag data with Customer id (may be hashed) and Session IDs to improve tracking accuracy.
Consent Management
Support TCF 2.0
In order to transmit and receive consent, the framework TCF 2.0 can be used.
read more here: IAB Transparency & Consent Framework v2.0
...