What are the benefits of integrating Google Analytics and Mediahawk?

There are many benefits to integrating the Mediahawk software with Google Analytics. The main benefits are listed below:

  • Allows you to easily view which pages generate calls in Google Analytics.
  • Enables you to track every interaction with your campaigns and link phone calls to Google Analytics.
  • Mediahawk sends custom data about the phone call such as call length or service number back to Google Analytics within 5 minutes.
  • You can choose which dimensions & metrics you want to track in Google Analytics.
  • Match your phone call data alongside your online activity in Google Analytics reports.
  • Lets you customise the information you send to Google Analytics per number/campaign.



Key Facts:

  • Google Analytics integrates with all Mediahawk inbound products only.
  • Mediahawk sends data to Google within 5 minutes of the call being registered on the Mediahawk system, however Google can take up to 24 hours to update the information received, please wait 24 hours after set up to see if any data transfers.
  • Google imports data using the date it receives it, so if a call finishes at 23:59, Mediahawk sends it to Google at 1:05am (the next day). The call will be logged in Google under the next day and not the date of the call.
  • When setting a goal, ensure the destination drop down is: equals to.
  • Ensure the goal name matches what you have set up in Mediahawk, and that it begins with a forward slash (/) and ends in html.
  • Mediahawk sends all calls to Google analytics, however it’s only the in-visit Dynamic calls that get matched with the Google visitor ID.

What data is sent to Google Analytics?

Mediahawk sends this as standard to Google Analytics when an Goal is selected

For Dynamic calls, the following data is sent as a virtual page to GA

  • The Keyword that generated the call
  • Google Client ID (If available, if not Mediahawk generates a unique ID)
  • Campaign name, Medium and Source
  • Tag Parameters (If set in Mediahawk and GA)
  • Page Title (If defined)
  • Host Name
  • Referral Page
  • Page requested (Default virtual page – IE /Phonecalls.html)

For Dynamic calls, the following data sent as a virtual page to GA

  • Client ID (this is always a Mediahawk generated unique ID, not a GA ID)
  • Campaign name, Medium and Source
  • Host Name
  • Page requested (Default virtual page – IE /Phonecalls.html)

For Static calls, the following data sent as a virtual page to GA

  • Client ID (this is always a Mediahawk generated unique ID, not a GA ID)
  • Campaign name, Medium and Source
  • Page Title = Service Number
  • Host Name
  • Page requested (Default virtual page – IE /Phonecalls.html)

Mediahawk sends this as standard to Google Analytics when an Event is selected

All Event fields can be setup to select over 80 data point or a custom value.

For Dynamic calls, the following data is sent as an event to GA

  • The Keyword that generated the call
  • Google Client ID (If available, if not Mediahawk generates a unique ID)
  • Campaign name, Medium and Source
  • Tag Parameters (If set in Mediahawk and GA)
  • Page Title (If defined)
  • Host Name
  • Referral Page
  • Category: Campaign description
  • Action: Effective/Ineffective
  • Label: Effective/Ineffective

For Dynamic Post visit calls, the following data sent as an event to GA

  • Client ID (this is always a Mediahawk generated unique ID, not a GA ID)
  • Campaign name, Medium and Source
  • Host Name
  • Category: Campaign description
  • Action: Effective/Ineffective
  • Label: Effective/Ineffective

For Static calls, the following ata sent as an event to GA

  • Client ID (this is always a Mediahawk generated unique ID, not a GA ID)
  • Campaign name, Medium and Source
  • Page Title = Service Number
  • Host Name
  • Category: Service Number
  • Action: Effective/Ineffective
  • Label: Effective/Ineffective

Common Questions:

Q1          Why are there differences in my source data?

A1           Mediahawk relies on the source being set up on our system for it to recognise it as a source, if it’s not already set up then it will be classed as a referral. 


Q2          My conversions in Google Analytics don’t match Mediahawk

A2          If your call totals in Google Analytics are only matching your in-visit calls in Mediahawk, check if you have a filter that only includes traffic from your website e.g. www.yourwebsite.com. If this is the case post visit calls won’t be coming through, however to ensure they do, add your websites URL to the hostname field in your Mediahawk Google Analytics setup and this will ensure Google will import all calls.



Q3        Why is there a difference in sessions between Google and Mediahawk?

A3        Mediahawk and Google hold sessions open for different amount of time. If you were to leave a web page inactive for a length of time Google will hold this session open for 30 minutes however Mediahawk with leave it open for 1 hour. If you were to come back within that hour it would be counted as one session. 

More information on how Google classifies sessions can be found here: https://support.google.com/analytics/answer/2731565?hl=en



Q4    Are there differences in how Mediahawk and Google count visitors?

A4    Yes, there are a few reasons why this might happen;

  • The first is that Mediahawk counts visitors in a different way to Google counting sessions. e.g we will count each new click as a new visit where as they may link 2 x visits together from a short time period.
  • The second is that if someone is browsing and clicks on an ad and the page fails to load because the browser crashes or the user loses signal on a mobile device, Google will count the click but Mediahawk will never see the visit.
  • The third is that if a visitor bookmarks a page or sends it to someone else and the link is then clicked on, Google would recognise the GCLID and assign the direct visit to PPC where as Mediahawk would assign this as Direct Visit.