> ## Documentation Index
> Fetch the complete documentation index at: https://docs.invoca.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Why Does Google Client ID (g_cid) Attribution Show as Not Found?

> 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_cid` attribution shows as `not_found`.
* If a single Invoca Tag is deployed across multiple domains, `g_cid` may be captured correctly on some domains but show `not_found` on others.

## Cause

The Invoca Tag expects `g_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

1. Open the Invoca Tag and create a new draft.
2. For the `g_cid` Marketing Data Field, update Data Source Type to **JavaScript Data Layer** and Data Source Name to `gaGlobal.vid`.
3. Click **Save & Go Live** to publish the change.

## Where to go next

* [Google Analytics 4.0 (GA4): Integration Overview](/s/article/jhdcp92865-585)