In this article, we will look at creating a goal for transitions from Messengers. We will describe in detail the process of setting up conversions for messengers, as well as parameters and features of data transmission when accessing a messenger.
Setting up data transmission for messenger communications
To set up data transmission for messenger communications, you first need to activate the corresponding function in the GA4 integration settings section. To do this, go to "App Marketplace" -> "Settings"
In the GA4 integration settings, activate the parameter by checking the corresponding checkbox "Appeals to Messengers" and save the changes:
Important! For this function to work, at least one messenger integration must be activated in the project.
After activating the checkbox, a corresponding Webhook will be automatically created to transfer data to GA4.
To view the parameters and edit the data being transmitted, in your personal account go to the "Integration" section, then to the "Webhooks" page. The page contains a table of active and configured project integrations. We are interested in the one named "Google Analytics 4 messengers" - click on the edit icon:
The Webhook for the Ringostat_messengers event is automatically created for the "Start of dialogue in messenger" event. That is, we track not the number of clicks on the messenger icon on the site, but the number of actual appeals and started chats.
Now let's look at the default parameters that are created for transmission to GA4.
Parameter "name".
The "name" parameter has the value "Ringostat Messangers" by default, but can be renamed upon request.Parameter "data_source".
The "data_source" parameter has the value "Ringostat" by default, but can be renamed upon request.Parameter "messenger".
The "messenger" parameter transmits the name of the messenger the client is accessing.Parameter "username".
The "username" parameter transmits the name and nickname to GA4 from the messenger. For example, for Telegram: (Mykola Basmovych, @nikola22).Parameter "browser".
The "browser" parameter transmits the browser name and version to GA4.
This file describes all parameters that can be transmitted by the "Open/close dialogue" event
After performing all the actions described above, you can immediately check the integration in the GA4 "Realtime Reports" section
IMPORTANT!
From the moment the integration is enabled, events from Ringostat will be automatically transmitted to Google Analytics.
Google Analytics itself displays event data with a 24-hour delay. That is, if there was an appeal, it will appear in Google Analytics reports after 24 hours.
Setting up audience for different messengers
Go to the "Admin" => "Audiences" section
And click the "New Audience" button:
Select "Create a custom audience":
Specify the name "Telegram_Messenger" (without spaces, using underscore). After that, configure the condition:
select the "Ringostat_messengers" event:
to set the audience condition, specify the custom parameter of our event "messenger":
for the condition, select "contains" and specify the value — the messenger for which you want to create an audience: "telegram", "viber" or other.
Then accept the settings.
After specifying the condition, indicate "Audience Trigger".
With the name "Telegram_Messenger" (the activator should not have spaces).
We recommend using the same names for "Activator", "Audience" and "Conversion" (not using spaces, as this is not provided for "Audience") to avoid errors in the setup.
After that, save the audience.
As a result, you will see an estimated count of users within this audience:
Google Analytics does not count users for events that were transmitted earlier. The conversion will include those events that will be recorded after completing the setup.
Creating a conversion
Go to the "Admin" => "Key Events" section. Click the "New conversion event" button
Specify the same conversion name as in the audience activator — "Telegram_Messenger" or "Ringostat_messengers" - if you didn't create a special audience before, and save:
The event conversion is automatically created as active.
You can check the conversion operation the next day.