> ## 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. # Google Campaign Manager: FAQs and Troubleshooting > Answers to common questions about the Invoca for Google Campaign Manager integration, including view-through impression fees, Safari ITP, and data discrepancies. **Applies to:** Google Campaign Manager integration **I use both Search Ads 360 and Campaign Manager — should Invoca integrate with both?** If you share Floodlight activities from Campaign Manager with your [Search Ads 360 account](https://support.google.com/searchads/answer/2458167), we recommend integrating with only one platform, so conversions uploaded to both aren't double-counted. If you want to track call conversions for both display and search, implement the Campaign Manager integration, but review [Search Ads 360's limitations](https://support.google.com/ds/answer/7384231) first. It's possible to integrate with both, but you'll need separate Floodlight activities for each. **Will I incur impression fees if I enable view-through tracking?** Yes — every time the 1x1 creative that writes the encrypted user ID to a first-party cookie is served, you're charged for that impression. We recommend conditional firing logic to only serve the creative when there's no `gclid` in the query string, no `gcm_uid` in the query string or first-party cookie, and only on the first page visit of a session. **Are there concerns around Safari Intelligent Tracking Prevention (ITP)?** Yes — ITP affects the view-through scenario in particular. Campaign Manager can't set its encrypted user ID when a display ad serves on a third-party site in Safari, so when a visitor navigates directly to your site, the 1x1 creative generates a new encrypted user ID that can't be matched to the earlier ad view. **Why is there a discrepancy between Invoca and Campaign Manager reporting?** Confirm the Invoca transaction actually captured a `gclid` or encrypted user ID — without one, Campaign Manager can't attribute the call or Signal to an ad interaction. Campaign Manager also requires that only one of the two values is sent per request; if you see both values on the same transaction in Invoca reports, troubleshoot your custom code to ensure only one is captured. Capturing an encrypted user ID also doesn't guarantee an ad interaction occurred within your Floodlight activity's attribution window — this is especially likely with Safari ITP. It can help to run a Campaign Manager report that includes unattributed conversions and compare totals to Invoca. **My transaction registered in Invoca, but I don't see it in Delivery History yet.** There's a 1-hour delay between a transaction appearing in Invoca and Invoca sending the data to Campaign Manager, to give Campaign Manager time to register the click IDs. **I captured both a `gclid` and `dclid` for a call, but only the `dclid` was sent — why?** Campaign Manager only accepts one of `gclid`, `dclid`, or match ID per conversion. Invoca prioritizes `dclid`; if that's blank, it falls back to `gclid`; if that's also blank, it falls back to the Invoca Unique ID as the match ID. If none of the three are present, the conversion isn't sent. **How can I see the data Invoca sends to Google?** Open an Action's Delivery History tab and expand a row to see the full JSON payload sent for that call or Signal. **How does Invoca send data to Google Campaign Manager?** Invoca uses the [Google Campaign Manager Conversions API](https://developers.google.com/doubleclick-advertisers/guides/conversions_upload). **Does Invoca support Enhanced Conversions for the Campaign Manager API?** Not currently, though it's under consideration. ## What each webhook field means | Field | Description | | :-------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------- | | `floodlightConfigurationId` | The Floodlight configuration ID for your Invoca data — usually the same as your Campaign Manager Advertiser ID | | `floodlightActivityId` | The Floodlight activity ID for the Activity matching this conversion | | `encryptedUserId` | A single encrypted user ID from the `%m` match macro, captured by the Invoca Tag | | `gclid` | A Google Click Identifier generated by Google Ads and captured by the Invoca Tag | | `value` | The value of the conversion | | `timestampMicros` | The conversion timestamp in Unix epoch microseconds (required) — uses the Signal occurred-at time, falling back to the call start time if nil | | `customVariables[].type` | The custom Floodlight variable type, mapping to `u[1-20]=` in the tags — for example, custom variable 82 maps to U82 | | `ordinal` | The conversion's ordinal, used to control de-duplication for same-user, same-day conversions (required) | | `encryptionEntityType` | The encryption entity type, matching your ad-serving or Data Transfer encryption configuration — typically `DCM_ADVERTISER` | | `encryptionEntityId` | The encryption entity ID for your Floodlight activity — the same as the Floodlight Configuration ID | **What timestamp is used for `timestampMicros`?** For both "Send Call or Signal Activities" and "Send Call or Signal Events" actions, Invoca first tries the Signal occurred-at time; if that's nil, it falls back to the transaction start time. ## Where to go next * [Google Campaign Manager: Integration Overview](/s/article/jhdcp92865-698) * [Installation Guide](/s/article/google-campaign-manager-installation-guide) * [Using Your Integration](/s/article/google-campaign-manager-using-integration)