How to Track Calls as Goals in Google Analytics



Why Track Calls as Google Analytics Goals

To gain insight into the marketing that is converting best, it’s important to fully track the journey of a visitor from Ad to click to call to converted outcome.

How It Works

  • Visitor goes to your ad and clicks through to landing page
  • They hit a landing page with tracking template that includes data such as keyword & gclid and where they are presented with a dynamic tracking number
  • When they call the number
    • An event can be tracked that the call initiated
    • An event can be tracked that the call connected
    • An event can be tracked that the call converted (and optionally that did not)
  • In Google Analytics each event may be aligned to Goals
  • Completed Goals are configured to trigger conversions in Adwords

You now have insight into which Ads (and keywords) converted best.

Getting Set Up

Configure Retreaver

Create a campaign

Any campaign will work. Ensure conversion tracking is in place if you have call conversion criteria.

Add Parameter Mappers for Adwords’ Google Click ID and Keyword

You will need to add a gclid and keyword parameter mapper in Retreaver. Ensure your adwords also includes a parameter for gclid and keyword in your tracking template.

View our Parameter Mapping article for more information on pulling values from visitor URL's.

Parameter Mapping.png

Typically the value-track parameters to add to your tracking template are:


To enable auto-tagging of parameters to urls in adwords see: Tag Your AdWords Final URLs

Add Webhooks to the campaign to track Events back to Google Analytics.

View our webhooks article for more information on how to pass data to third parties from the Retreaver platform.

With Retreaver it’s possible to send multiple events for a single call to Google Analytics using Webhooks. For example:

Using the Webhook: Start: When a call Comes in

Using the Webhook: Answered: When a handler answers call

Using the Webhook: Conversion: If call converted

For each Webhook, assign parameters as follows (for all parameters available click here)tes

  • v = The Protocol version. The value should be '1'.
  • tidThe tracking ID / web property ID in "UA-XXXX-Y" format. Accessible using the [google_analytics_tracking_id] replacement token. For Mobile-Only engagements, you will need to hardcode this value instead using the Tracking ID of your media property.
  • cid = Client ID. Anonymously identifies a page view instance. Accessible using the [google_analytics_client_id] replacement token. For Mobile-Only engagements, you can use the [call_uuid] replacement token value instead to uniquely identify engagements.
  • t = Type. Use ‘event’.
  • ec = Event Category. We suggest using “Call” or “Calls”.
  • ea = Event Action. We suggest using an action aligned to the call status. I.e. Call+Started. Note the spaces must be escaped with a + or %20
  • el = Optional. Event Label. For use in Reporting
  • ev = Optional. Event Value. Must be an integer (Google limitation). This will track the value of the conversion from call to Google Analytics.

Optionally include:

  • gclid = Google Click ID. Needs to be passed to your landing page via the adwords tracking template. This is needed to match the ad conversion back to the ad.
  • cs = Source. This should align to your [source_id] or [affiliate_id]


Ultimately, use any event category, action and label you like. For simplicity, we’ve kept the category as “Call” and the action and label the same as each other.

For Events relating to conversions. The Webhook needs to also append &gclid=[gclid] at the end. This will be used to map conversions in Google Analytics to Adwords.

Test Fire Each Webhook

Either place a call through the campaign that will trigger each event. Or use the “Test Fire” button in Retreaver to send a call to Google Analytics. This will help you check that the events are being registered correctly.


Configure Google Analytics

Confirm Events Are In Google Analytics

Navigate to Behaviour > Events > Top Events in your Google Analytics. You should see the Event Category listed in the table. Add a Secondary Dimension for Event Action. This will show you the different types of events sent to Google Analytics from Retreaver.


Create Goals


Click on Admin then navigate to Goals under the View column:


Next, you will be asked to set up your first goal, or if you need to, click “New Goal”.

1. Select the Custom option for Goal Setup. Then Continue.


2. Next, give your goal a name and select Event as the Type. Then Continue.


3. Set the Category, Action and Label to match what you used in your Webhook, remembering to replace any escaped characters with their actual spaces or values. For example, “Call+Answered” in the Webhook becomes “Call Answered” in the goal details. Then click Save.


Your goals are now ready to go. Complete a few test calls to confirm you see the conversion information come through in the Goal view (Conversions > Goals > Overview).


For additional information check out the following links from Google


0 out of 0 found this helpful



Please sign in to leave a comment.