Jet Interactive uses the information contained in your Google tracking cookie to assign a conversion to the correct Google Client ID and pass this through as an Event to your Google Analytics account.
If your Google tracking codes have not completed running by the time the Jet codes run, we will be unable to collect this information, and our attempt to post this information to GA will be rejected.
This is the most common reason for any data discrepancies between Jet reporting calls in Web Session Calls versus the Events that show in your Google account.
This can usually be fixed quite easily by ensuring that the Google tracking codes will run as a first priority, and Jet will run later, or last.
Prioritization in Google Tag Manager
If you have implemented your header code via Google Tag Manager, you can easily control tag firing prioritization in the Advanced Settings of a tag.
- Tag Firing Priority: Determines the order in which tags will be fired. The value can be a positive or negative integer, and tags with higher values will fire before those with lower values. (For example, a priority 3 tag will fire before a priority 1 or 2 tag.) Priority defaults to 0 if no value is specified. Tags will still fire asynchronously.
- Enable custom tag firing schedule: Specifies that the tag should fire during a specified timeframe.
Note: When selecting the checkbox to use a custom tag firing schedule, both a start and end date must be entered, and the end date and time must occur later than the start date and time.
- Only fire this tag in published containers: Prevents tags from firing in test environments (e.g., during previewing and debugging). When applicable, Tag Manager will tell you when the tag would have fired. For the most accurate testing, leave this option unchecked.
For more precise control, use Tag Sequencing to specify exactly which tags fire before and after a given tag.
In this case, you would fire the Jet tag after any Google Analytics tracking code.
Prioritization in source code
If you have implemented your header code via direct entry into your source code, this may be a more complex process.
As a general rule, your codes will usually load in the order they are added to the header code of your page.
This is why your Google Analytics tracking code is recommended by Google to be the first entry in your <head></head> tags, ensuring this will run as the very first code snippet.
This is also why Jet recommends placing our header code as the final entry in your <head></head> tags, to give your Google codes as much time as possible to run and complete before our code is activated.
To ensure your site is operating under the optimal design, please ensure your codes are laid out as above, with Google tracking code above the Jet code, ideally as the first entry in your head></head> tags, and Jet as the final code.
If you are using other ways to implement or prioritise your codes, you can utilise these programs to achieve the same result.
Please be advised, Jet is unable to directly support external programs and setup, so please ensure you have a thorough understanding of these tools before implementing them on your web page.