Google Analytics 4 integration: How to set it up in Nimbata

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:

• An active GA4 property with a web data stream
• Your GA4 Measurement ID
• A GA4 Measurement Protocol API secret

The GA4 tracking tag (gtag or GTM) must already be installed on your website for session-based attribution to work.

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: When using dynamic number insertion (DNI), Nimbata can associate calls with the originating session. This allows you to view available session information (such as source/medium or campaign) for call events in GA4, similar to other event data.
• 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 GA4 by sending events via the Measurement Protocol when calls occur. These events are processed by GA4 and may take some time to appear in reports.

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, the GA4 Measurement Protocol API secret, is used by Nimbata to send events to GA4. 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.

Step 2. With these two properties in place, Nimbata can send call events to GA4. Next, choose a trigger to define which calls should be sent. The default trigger, 'After Every Call', sends all completed calls as events to GA4. If you want to filter which calls are sent (for example, only answered calls or first-time callers), you can create a custom trigger and apply it to the event.

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

[Optional] Step 3. For additional context, you may want to send extra parameters along with your events. Select the parameter you want to send (for example, Start Time) and assign a name for it. These parameters will be sent together with the event.

These parameters will appear as event parameters in GA4 and may need to be defined there before they can be used in reports.

[Optional] Step 4. Nimbata allows you to send multiple call events to your GA4 account, such as All Calls, Answered Calls, or First-time Callers. Each event should use a distinct trigger to avoid overlapping or duplicate data.

Video Version of the guide

🎉 That’s it! Your call events will appear in GA4 under Events or Conversions, depending on how they are configured and after GA4 has processed the data.

If events do not appear as expected, allow some time for GA4 processing and confirm that your Measurement ID and API secret are correctly configured.

Updated on: 06/02/2026