Skip to content
Adrythm

How-to

Send tracked calls to GA4 without double counting in Google Ads

Updated October 11, 2026

25 minutes, then a day to confirm

Connect your call tracking tool to GA4 so each call arrives as an event, turn on its duplicate-event setting, and mark the call event as a key event. Do not create a Google Ads conversion from it when calls already reach Google Ads another way: the same call could count twice, in bidding too if it is Primary.

Before you start

  • Editor access or above on the GA4 property, which Google requires to mark an existing event as a key event.
  • A GA4 web data stream. CallTrackingMetrics, for one, supports only a web data stream.
  • A list of how calls reach Google Ads today: the call tracking tool's own integration, Google's calls from ads, or Google's calls from website visits.

Connect the call tracking tool to GA4

On a CallTrackingMetrics non-agency plan, the connection starts with Sign in with Google in the GA4 integration settings.

  1. Open the GA4 integration settings, click Sign in with Google and choose the Google account that can reach your GA4 property.
  2. Choose your GA4 Account, GA4 Property and GA4 Data Stream, one of each. The tool uses the stream's API secret if one exists and creates one if not.
  3. Turn on Send GA4 events after each activity and Send conversion events. Send events when no GA4 session data is available (offline sources) sends calls that have no GA4 session to match, such as calls to numbers used offline. CallTrackingMetrics' own setup turns it on; leave it off only if GA4 should hold session-matched calls alone.
  4. Turn on the setting that prevents duplicate events from being sent from a single activity.
  5. Preview the event format and write down the event name it shows, such as CTM_Activity for a first-time inbound caller, then save.

On a CallTrackingMetrics agency plan the path differs: go to Integrations, Google Analytics 4, Settings, link a Google Analytics user, click New Data Stream Link, assign the account and save. The duplicate toggle there reads Prevent duplicate events from being sent from a single activity to the same Data Stream.

Mark the call event as a key event

A key event is a GA4 label, and turning it into a Google Ads conversion is a separate step that this page leaves out on purpose.

  1. Make one test call to a tracking number from a visit to your site, so GA4 receives the event.
  2. In GA4, open Admin, and under Data display click Events.
  3. Find the call event in the Recent events tab and click the star icon next to it.

Google says a new key event can take up to 24 hours to show in standard reports, while Realtime updates within a few minutes.

Keep the call event out of Google Ads bidding

When calls already reach Google Ads from the call tracking tool or from Google's own call actions, the GA4 call event should not become a second Google Ads conversion for the same calls.

  1. In GA4, when you open Advertising, then Tools, Conversion management to create Google Ads conversions, or import GA4 events from the Google Ads side, leave the call event unselected.
  2. In Google Ads, open Campaigns, add the All conv. column and pick a date range long enough to include calls. Click the segment icon and choose Conversions, then Conversion source: rows with Google Analytics as the source come from GA4. Segment by Conversions, then Conversion action to check whether one of them is your call event.
  3. If it is, go to Summary in the Conversions drop-down of the Goals menu, click Edit goal on its goal, set it to Secondary (observe only) under Conversion action optimization, and click Save.
  4. Do not rely on the default. Google says conversions created from GA4 start as Secondary, but one of its pages also ties that to the account already having goals from an Analytics property, and the default may not hold for an action imported from the Google Ads side. Either way it can be switched to Primary in Google Ads.
  5. Check custom goals too. Google says actions in a custom goal are used for bidding regardless of whether they are set as primary or secondary. If a custom goal includes the GA4 call action, remove it from that goal.

Check it worked

After a test call, the call event should appear in GA4's Realtime report within a few minutes, and in standard reports as a key event within 24 hours.

In Google Ads, Goals, Conversions, Summary should show each call counted by only one Primary action, and no action from Google Analytics counting calls. If two routes carry the same calls, keep one Primary and set the other to Secondary. After a week, the Conversions column segmented by Conversion action should show call conversions close to the ad calls in your call log, not twice that.

When importing the GA4 call event is the right choice

If nothing else sends calls to Google Ads, no call tracking integration and no Google call action, the GA4 call event can be the one route, and importing it does not double anything. A call tracking tool's own Google Ads integration is still the more direct route where it exists. That is a judgment, not Google's rule.

Still have a question this page did not answer?

Ask it on a call. Thirty minutes, a straight answer, and no follow-up sequence if you decide not to work with us.