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

Google Analytics 4 Integration

This article assumes you have a working GA4 property and a web data stream configured. If you're unsure about your GA4 setup, we recommend reviewing Google’s GA4 documentation before proceeding: https://support.google.com/analytics/answer/9304153?hl=en

Nimbata’s Google Analytics 4 integration allows you to send call data as events directly to GA4, helping you understand which traffic sources, campaigns, and sessions drive phone leads. This guide covers how to connect Nimbata with GA4 to enable session-based call attribution and event tracking.

To do so follow the steps described below:

How to set up your Google Analytics 4 integration

Nimbata integrates with GA4 by sending events via the Measurement Protocol when calls occur. These events are processed by GA4 and may appear in reports with delay.The integration is configured at the project level, so make sure you are editing the correct project before proceeding.

Step 1. Go to Integrations > Google Analytics. The first thing you should do is to fill the GA4 API Key and the Measurement ID.

Note: Nimbata will display the "Your configuration is missing an API Key. Your configuration is missing an API Key" error message.

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.

Once inside the Data Streams, got to 'Web Stream Details'.

You will find the Measurement ID under the 'Stream Details' sub-menu. Copy and paste it into the Nimbata GA4 integration page. Next, you can grab your GA4 Measurement Protocol API secret, which is used by Nimbata to send events to GA4, in the 'Events' sub-menu by clicking the 'Measurement Protocol API secrets' tab.

Step 2. With these two properties in place, Nimbata can send call events to GA4. Next, select an Event to define which calls should be sent. You can create as many events to that trigger Nimbata to send data to Google Analytics 4 as you need by clicking on the 'Add Row' button.

Here is the full list of Events you can choose from:

Event Name	Event Description
Call Duration	The total length of the phone call in seconds, from connection to hangup.
Call Outcome	The final status of the call (e.g., Answered, Missed, Busy, or Voicemail).
Caller ID (formatted)	The phone number of the person calling, displayed in a readable format.
Configured Tracking Source	The marketing channel or campaign assigned to the tracking number (e.g., Google Ads).
Destination Number	The actual office or personal phone number where the call was routed and answered.
Destination Number (e164)	The answering phone number provided in the international standard format.
Destination Number (formatted)	The answering phone number displayed with standard regional formatting.
Destination Number Friendly Name	A custom label used to identify the receiving line (e.g., "Main Office").
Digits Pressed by Caller	Captures keypad inputs made by the caller, usually during an IVR menu.
Digits Pressed by Destination	Captures keypad inputs made by the person who answered the call.
Hangup Cause	The technical reason the call ended (e.g., "Normal Clearing" or "Abandoned").
Has Recording	A True/False indicator showing if an audio recording of the call was captured.
Has Transcription	A True/False indicator showing if the call audio was converted into a text transcript.
Has Voicemail	A True/False indicator showing if the caller reached and left a message.
IP Address	The network address of the caller, captured if the call started via a website click.
Project Name	The name of the specific account or sub-folder within your tracking platform.
Rating	A quality score (often 1–5 stars) assigned to the call by the receiver.
Recording was Stopped	Indicates if the call recording was manually paused (e.g., for privacy).
Start Time	The date and time the call began, usually recorded in UTC/GMT.
Start Time (Local Timezone)	The date and time the call began, adjusted to the local business timezone.
Tags	Custom labels applied to the call for filtering (e.g., "New Lead" or "Spam").
Talk Duration	The actual time spent speaking, excluding time spent on hold or in a menu.
Times Called	A counter showing how many times this specific caller has contacted you.
Tracking Number	The specific phone number the customer saw and dialed to reach you.
Tracking Number (e164)	The dialed tracking number in international standard format.
Tracking Number (formatted)	The dialed tracking number displayed with standard regional formatting.
Tracking Number Friendly Name	A custom internal name for the tracking number (e.g., "Website Header").
Unique Call ID	A specific alphanumeric string used to identify this individual call record.
Value	The monetary worth or conversion value assigned to the call.
Workflow Name	The name of the automated routing sequence or IVR path the call followed.

Step 3. Once you have entered the Measurement ID and GA4 Measurement Protocol API secret Nimbata will display the following message:

Click the 'Create new workflow' button for Nimbata to automatically create the Workflow that will tell it to send your Events to GA4:

Step 4. Go back to the GA4 integration page.

Nimbata will now display the following message,"This integration is running in 1 workflow: Google Analytics (running)", letting you know the integration is live:

Note: 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.

Note: 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 Event to avoid overlapping or duplicate data.

🎉 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: 05/03/2026

Was this article helpful?

Thank you!