How to Track Calls as Goals in Google Analytics

Follow

Overview

Tracking 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. Retreaver webhooks are capable of triggering various Google Analytics events, which can be used to create customized reports inside of the Google Analytics platform using data gathered from Retreaver call engagements.

 

Brief Overview of the Google Analytics Integration:

  1. Visitor goes to your ad and clicks through to your landing page.
  2. They hit a landing page with a tracking template that is configured to provide URL parameters using data such as search keywords & google click ids.
  3. When the lead calls the displayed Retreaver tracking number, an event can be triggered to track whether or not the call was initiated, connected or converted.
  4. Inside of Google Analytics, each event is associated with a Goal.
  5. Completed Goals can then be configured to trigger conversions in Google Ads

This process will offer you an insight into which Ads (and keywords) converted best.


 

Integrating with Google Analytics using Retreaver

 

Getting Started: Configuring Retreaver Parameter Mappers

Getting Started: Configuring Retreaver Parameter Mappers

To get started, you will need to configure your Retreaver campaign to scan for the Google click ID and keyword presented in the URL parameters that your landing page will provide.

Head into your Campaign overview page -> Retreaver JS Settings -> Parameter Mappers to edit your campaign parameter mapping settings.

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

Parameter Mapping.png 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.

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

?utm_source=adwords&glcid={gclid}&keyword={keyword}

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

Creating Campaign Webhooks to track Events back to Google Analytics

Creating Campaign Webhooks to track Events back to Google Analytics

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

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

For example:

Using the Webhook: Start: When a call Comes in

https://www.google-analytics.com/collect?v=1&tid=UA-XXXXXXXXX-X&cid=YYYY&t=event&ec=Call&ea=Call+Started&el=Call+Started

 


Using the Webhook: Answered: When a handler answers call

https://www.google-analytics.com/collect?v=1&tid=UA-XXXXXXXXX-X&cid=YYYY&t=event&ec=Call&ea=Call+Answered&el=Call+Answered

 


Using the Webhook: Conversion: If call converted

https://www.google-analytics.com/collect?v=1&tid=UA-XXXXXXXXX-X&cid=YYYY&t=event&ec=Call&ea=Call+Converted&el=Call+Converted&e=##

 

Google Analytics Webhook Parameters

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

For more information about replacement tokens, view our How to use Tags and operators guide.

  • 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 custom Reporting.
  • ev = Optional. Event Value. Must be an integer (Google limitation). This will track the value of the conversion from the call into Google Analytics. We recommend using a [revenue] replacement token.
  • gclid = Optional. 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. Place into the webhook using a [gclid] replacement token.
  • cs =Optional. Source. This should align to your [source_id] or [affiliate_id] values. 

 

Google_Analytics.pngExamples of Google Analytics Webhooks placed on the Retreaver campaign level.

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.

Testing & Viewing Events on Google Analytics

Testing & Viewing Events on Google Analytics

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.

Test-Fire.png


Navigate to Behaviour -> Events > Top Events in your Google Analytics, then Add a Secondary Dimension for Event Action. This table will now show you the different types of events that were sent to Google Analytics from Retreaver.

Events-in-Analytics.png
Creating Goals inside of Google Analytics

Creating Goals inside of Google Analytics

Navigate to the Admin page, then head to Goals under the View column:

new-goals.png

 

If this is your first created goal, you will be asked to set up your first goal, otherwise click on the “New Goal” button instead - then follow along with steps below: 

1. Select the Custom option for Goal Setup, then press continue.

goals-step-one.png


2. Next, give your goal a name and select the Event as the Type of Goal, then press continue.

goals-step-2.png


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.

goals-step-3.png



Your goals are now ready to go!

Complete a few test calls to confirm that you see the conversion information in the Goal view page successfully: Navigate to the overview page from: Conversions > Goals > Overview.

goals-in-analytics.png



For additional information check out the following links from Google

 

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.