This happens when a domain running the Invoca Tag has only Google Analytics 4 deployed, but the Tag is still set to read g_cid from a Universal Analytics property.Applies to: Customers capturing
g_cid attribution in their reporting, customers integrated with Google Analytics using options.integrations.googleAnalytics = true in their custom code block, customers relying on Google Tag Manager to handle tagging for both Invoca and Google Analytics
Symptoms
g_cidattribution shows asnot_found.- If a single Invoca Tag is deployed across multiple domains,
g_cidmay be captured correctly on some domains but shownot_foundon others.
Cause
The Invoca Tag expectsg_cid to come from the Google Universal Analytics property ID. If a domain runs only Google Analytics 4 with no Universal Analytics deployed, that property ID isn’t present, so g_cid attribution fails on that domain — even when other domains using the same Tag have both properties deployed and work correctly.
Resolution
- Open the Invoca Tag and create a new draft.
- For the
g_cidMarketing Data Field, update Data Source Type to JavaScript Data Layer and Data Source Name togaGlobal.vid. - Click Save & Go Live to publish the change.