WARNING! It’s assumed you have an in-depth understanding of clientside, serverside tracking with deduplication.
IMPORTANT! With this setup, you will need to add a ‘dummy’ node to the start of your decision tree. This can ADD latency because Node 1 has to load, fire GTM and fire pixels etc so please be sure to test FIRST before driving live traffic. This dummy ‘Node 1’ contains a script that waits for GTM and the various pixels to fire. The reason is to ensure you grab the various values required for serverside tracking when can only be attained from the various pixels. Example: Facebook serverside tracking requires FBC and FBP values for perfect deduplication.
This setup explained here assumes you are using the LeadsHook provided GTM container. If are NOT using LeadsHook GTM container then can still learn why and how this setup works — unfortunately you will have to do a lot of custom scripting to make it work.
Video 1: Understanding First Node Clientside & Serverside Deduplication
Video 2: Confirmimg Your Clientside & Serverside Deduplication is Working
Resources
Download Sample Google Tag Manager
Download Sample Decision Tree (Import .zip into LeadsHook)
Download Node 1 Script (Unzip to view script in text file. This is ALSO available in the decision tree download above)
