Skip to main content
Answers to common questions about the Invoca for Google Analytics 4 (GA4) integration, including multi-property setups, data field mapping, and troubleshooting missing events.
Applies to: Google Analytics 4 (GA4)

​
Can I pass traffic parameters (utm_source, utm_medium, etc.) with the Event to Measurement Protocol 4?

Not yet — GA4 doesn’t currently support this in its parameter reference. To get marketing source/medium/content/term insights, create Custom Dimensions to pass that information, or capture and pass the session_id (which only associates Events with a session if reported within 3 days).

​
I have many GA4 Properties — how do I integrate?

If each GA4 Property maps to a specific Invoca Profile or Campaign, set up Actions to filter by Profile (Network-level Actions) or Campaign (Profile-level Actions). If your call data doesn’t segment that cleanly, use a more advanced setup with Lookup Tables: create Marketing Data fields for the Measurement ID and API Token, then build a 3-column Lookup Table — a key Invoca already tracks (like Destination Phone Number), the Measurement ID, and the API Token. Your API Token will be visible in Invoca reports with this approach, so it’s only recommended when there’s no other way to segment data to the correct property.

​
Can I pass calls or Signals from “static” Invoca promo numbers, where there’s no Google Analytics Client ID?

Yes — check Include events from “static” and “overflow” numbers in the Action setup, even though GA4 is primarily built to track app and website traffic.

​
Can I create “Goals” in GA4 based on Invoca Events, like in Universal Analytics?

GA4 replaced Goals with marking an Event as a Conversion. See Google’s Conversions in GA4 for more.

​
Can I create audiences based on Invoca Events?

Yes — see Google’s Create an audience, including how to share audiences with linked advertising products.

​
Does Invoca pass value and currency for Invoca Events?

Yes. If you don’t see it, pause and resume the Action to start passing that data. Invoca passes the Revenue field as the value; currency defaults to USD unless you enter your own 3-letter ISO 4217 code in the Action setup.

​
What fields does Invoca pass by default?

The Google Analytics Client ID (or transaction ID for “static”/“overflow” number events), the Invoca Revenue field as the value, currency, and a Unix-microsecond timestamp. To pass additional data — for Custom Dimensions or Metrics — use the Custom Parameters section of the Action setup, after creating the corresponding dimension/metric in GA4 first.

​
Where can I view Invoca Events?

Anywhere you already view Events/Conversions in GA4 reporting.

​
How can I see the data Invoca sends to GA4?

Open an Action’s Delivery History tab to see exactly what was sent for each call or Signal, or review GA4’s Realtime reports and drill into Event details.

​
How does Invoca send data to GA4?

Invoca uses the GA4 Measurement Protocol endpoint.

​
I’m not seeing data in GA4 — what could be wrong?

Confirm event names and custom dimension names match exactly between GA4 and the Invoca Action, and double-check your Measurement ID and API Secret. Only GA4 Realtime reports update instantly — other reports typically populate within 8 hours.

​
Does GA4 have tools to explore available parameters?

Yes — the GA4 Event Builder lets you explore and validate parameters.

​
I’m only seeing 204 status codes — is that expected?

Yes — GA4 doesn’t validate events in real time and returns a 204 status for every request it receives.

​
Can I backfill data via Invoca or directly in GA4?

No, this isn’t possible.

​
How long does it take for events to show up in GA4?

Around 24 hours.

​
What’s an acceptable margin of difference between Invoca and GA4 event counts?

A discrepancy of 10-15 events generally isn’t worth investigating, since Invoca and GA4 are different systems. At least seven days — anything shorter is too short a window for accurate comparison.

​
Where to go next

Last modified on September 24, 2026