If you’re reading this article, chances are you’ve come across the need to send events from Binotel to Google Analytics 4 (GA4).
As of now, there are two ways to track Binotel events in GA4, depending on how the analytics code itself is implemented:
- Using Tag Manager tags;
- Automatically from the GA4 code (without Tag Manager).
Let’s go through each method step-by-step, starting with Tag Manager, since over 90% of websites use it.
We’ve covered how to set up event sending to Google Analytics 4 (GA4) before, but with Binotel, there are a few unique aspects to consider.
So, let’s break it down.
➊ Trigger
Add a custom event called “Binotel GetCall - Call requested”:
How does it work?
When an action takes place, an event is sent to GTM, triggering the event that fires off the tag and sends the event to Google Analytics 4. Then, you set up the tag.
➋ Tag
This is the actual handler for the action and its transfer to GA4. Name the action “GetCall”.
The event tag will look like this:
➌ Receiving Data in GA4
Within 24 hours, the new event will appear in the list of events, and from there, you can mark it as a conversion.
Similarly, you can create other events like:
👉 Binotel CallTracking — Call received via call tracking;
👉 Binotel Chat — Chat happened (successful chat).
If you have Google Analytics 4 and Binotel implemented without Tag Manager, the Binotel events will automatically appear in your GA4 event list and look like this:
Call Tracking
👉 binotel_ct_call_received — call received.
Callback
👉 binotel_gc_call_requested — call requested via GetCall.
Chat (new widget from Binotel)
👉 binotel_oc_chat_happened — user sent a message;
👉 binotel_oc_target_achievement — operator marked the chat as a target (we recommend marking this as a conversion);
👉 binotel_oc_contact_received — user left their contact info while the operator was offline.
This is usually enough to analyze the performance of your ad campaigns and other traffic sources.
Order a service