Articles on: Integrations

Google Analytics 4

Google Analytics 4 Integration



The Google Analytics – Nimbata integration allows you to send call data as events directly to your Google Analytics account and mark them as conversions. Before you begin you need to have an active GA4 Property setup and have the gtag installed on your website. Additionally, you will need to find your GA4 measurement ID and create your GA4 API secret.

Things you can do when using Google Analytics with Nimbata include:

⚡️ Send call data as events: The Google Analytics + Nimbata integration allows you to send call data as events, directly to your Google Analytics account and mark them as conversions.
⚡️ View call data in Google Analytics: Nimbata provides session-level attribution (source, campaign, or keyword) for call conversions using dynamic number insertion (DNI). You can view session information about the call, such as keyword, campaign, source/medium, and other session-based info, just like you do with clicks
⚡️ Analyze call data in dashboards: Include call data information to the reports you create in Google Analytics and view the sessions that drove calls at source/medium/campaign level.


(If you prefer visual guidance, feel free to scroll down for our video guide. It provides a hands-on walkthrough to make the process even more straightforward.)


Set up the GA4 Integration



Nimbata integrates with your Google Analytics account, by sending an event each time a call is placed under your account. This type of integration allows you to view session information about the call, such as keyword, campaign, source / medium and other session based info, just like you do with clicks.

The integration is performed on a brand level, so before continuing, make sure you are performing edits for the desired brand.

Step 1. Go to Integrations > Google Analytics. The first thing you should do is to fill the GA4 API Key and the Measurement ID. These are placed in your GA4 Account under Admin > Data collection and modification > Data Streams as below. If you haven't created a data stream you should create one.



The first property, GA4 API Key which serves as the communication linker between GA4 and Nimbata, you'll find it under Measurement Protocol API secrets. Just grab the key and seamlessly paste it onto your Nimbata Screen. Moving on to the second property, the Measurement ID can be found within Stream Details. Similar to the API Key, effortlessly grab the Measurement ID and paste it onto your Nimbata Screen as well.





Step2. With these two properties, Nimbata has everything you'll need to send back events as Calls. Now, let's delve into setting up your events. First and foremost, pinpoint your trigger. Opt for the pre-defined one: "After Every Call". By doing so, Nimbata seamlessly sends all your calls as events to GA4. If you wish to tweak this and selectively filter your calls before they are sent back to GA4, consider creating a new trigger. For instance, if you want to send only answered calls from first-time callers as events, create a trigger tailored to this criterion and position it under your GA4 event. Here's an example of what the trigger might look like:



This way, you can fine-tune your event setup to precisely align with your preferences and objectives.


[Optional] Step 3. For a better understanding of your data, you can might want to send additional parameters that will be sent back along with your events. For example in case you want to send "start time" as additional information, you should select the "Start Time" option from the dropdown list and give your new parameter a name. For example:




[Optional] Step 4. Nimbata lets you send different call events to your GA4 Account, like All Calls, Answered Calls, First-time Callers, and any other event you wish to track. If you want to send multiple events just click "Add Event" and follow the steps 1-3. Make sure to use different triggers for each event!


Video Version of the guide







🎉 That's it! You will find all your events on GA4 under Data Display > Events or Conversions based on your configuration.

Updated on: 08/07/2024

Was this article helpful?

Share your feedback

Cancel

Thank you!