Skip to main content
Connect Invoca to Google Campaign Manager 360 to send call and Signal conversion data as Floodlight activities, attributing offline conversions to your online campaigns.
This is the second article in a series covering the Invoca for Google Campaign Manager integration: Integration Overview, Installation Guide (this article), Using Your Integration, and FAQs and Troubleshooting. Before you begin: You need a Campaign Manager 360 user profile with the “Insert offline conversions” permission, and Invoca account permission to manage integrations and credentials.

Step 1: Google Campaign Manager setup

  1. Identify the user profile you’ll use to connect Invoca with Campaign Manager. Make sure it has the Insert offline conversions permission — contact your Campaign Manager 360 administrator if it needs to be enabled.
  2. Find the Profile ID: log in to Campaign Manager, click the profile icon in the upper right, and copy the numeric identifier shown under the account name. You’ll need it in Step 2.
  3. If you want to track clicks on display and video ads, enable Enhanced Conversions — this appends a dclid parameter to landing page URLs.
  4. Identify the Invoca calls or Signals you want to send as Floodlight activities, and create a Floodlight activity for each. Copy the configuration ID (usually the CM360 Advertiser ID) and the Floodlight activity ID for each.

Step 2: Set up the integration in Invoca

  1. In the Invoca sidebar, click Integrations, then Manage Credentials.
  2. Click + New Credential, give it a friendly name, choose Google Campaign Manager from the dropdown, and click Authorize.
  3. In the authorization flow, enter the credentials of the user profile from Step 1, review the Google authorization prompt, and grant access.
  4. Go to Integrations > Manage Integrations and click the Google Campaign Manager tile. If it shows “Learn More” instead, contact your Invoca CSM (Customer Success Manager) or account manager to enable the integration.
  5. Enter a friendly name for your account, and the Profile ID you copied in Step 1.
  6. Select the OAuth credential you just created.

Create an Action

An Action is a Call or specific Signal to report. Three action types are available:
  • Send Call or Signal Activities (gclid only matching) — click-through performance from Google Ads and Search Ads 360.
  • Send Call or Signal Activities (gclid and dclid matching) — click-through performance from Google Ads, Search Ads 360, and Display & Video 360.
  • Send Call or Signal Activities (gclid, dclid, and matchId matching) — view-through and click-through performance across the same three products. This option requires your web development team to populate invoca_id as the match_id parameter in your Floodlight tags, using Invoca.Tools.readInvocaData('invoca_id'). See Google’s docs for iframe/image tags or the Google Tag depending on your Floodlight tag format.
For each Action:
  1. Enter a friendly name (include “Call” or the Signal name to distinguish Actions).
  2. Optionally filter by Profile or Campaign.
  3. Under Triggered By, choose All Calls or Signal (and select the specific Signal). Create separate Actions for more than one transaction type.
  4. Enter the Floodlight Configuration ID (Campaign Manager Advertiser ID) and Floodlight Activity ID from Step 1, matching your Triggered By selection.
  5. Enter a Default Value as a fallback revenue amount — a Signal’s own revenue value overrides this. Enter 0 if you don’t want a default.
  6. Enable Activate Enhanced Conversions for Leads if you want to include hashed phone numbers as an additional attribution identifier.
  7. Optionally add Custom Floodlight Variables to pass additional Invoca data: always enter dfareporting#customFloodlightVariable as the Customer Variable Kind, use the matching u key (for example, u46) as the Custom Variable Type, and enter a hard-coded value or Invoca substitution token as the Custom Variable Value.
  8. Optionally add Optional Conversion Fields for adUserDataConsent, limitAdTracking, childDirectedTreatment, or nonPersonalizedAd.
  9. Click Save. Repeat for each transaction type you want to report, using + New Action.

Step 3: Configure your Invoca Tag(s) to capture Google identifiers

  1. Click the gear icon, select Invoca Tags, and locate the Tag on your website.
  2. Open the Revision History tab and create a new draft, or continue an existing one.
  3. In the Marketing Data section, find and enable the Google Click ID (gclid) parameter.
  4. Find and enable the Display Click ID (dclid) parameter.
  5. Test your changes, then click Save & Go Live.
  6. If you have multiple Invoca Tags, publish the update to each.

Validate that events are reaching Google Campaign Manager

  1. In Invoca, click Integrations, then Manage Integrations.
  2. Click the Google Campaign Manager tile, then the name of the Action you created.
  3. Review the Delivery Details chart, showing successes (green) and errors (red) by day for the last 30 days. Click into the Delivery History tab and check the Response tab for individual requests — since Campaign Manager returns a 200 response even when there are processing errors, look for "hasFailures": true in the response body for clues.
  4. In CM360, uploaded conversions are typically processed and reportable within 24 hours. Run a Floodlight Impressions report to check — unlike other attribution reports, it returns both attributed and unattributed conversions by default, making it a quick way to confirm your conversions arrived.

Where to go next

Last modified on September 24, 2026