Skip to main content
All CollectionsStatistics
What information can be founded in GA4 reports?
What information can be founded in GA4 reports?

To better understand the statistics in GA4, you will find more details in this article about the information sent by poool

Flore Bayle avatar
Written by Flore Bayle
Updated over a week ago

Thanks to the native connectors poool x gtm and poool x gtag, you can analyze the performance of your walls in GA4. For this, we invite you to create a "poool" exploration in GA4 to bring up relevant information.

We share more details in this article to help you understand everything visible in your explorations.

Event_category

Simply put, this data will be associated with poool. Useful for filtering your events.

Event_action

In this category, you will find the name of the event sent. This corresponds to different types of displays or user interactions with the wall.

  • identity-available: triggered when a user visits the page with the poool tag.

  • paywall-seen: paywall seen by the user (when it becomes visible in the browser).

  • ready: paywall displayed and loaded on the page.

  • release: when the action unlocks the current article.

  • click: click on a wall button.

  • register: triggered when the user registers for the newsletter from the newsletter widget or the Discovery Pass widget.

  • formSubmit: triggered when the user registers via a form widget.

  • error: API error. In this case, the default action you have configured is called.

💡 Note: You may notice the "widget-seen" information in your statistics. This is an event sent by poool in our old nomenclature. We recommend considering the "paywall-seen" information, which is the most recent.

Here is an example of an Analytics view that includes event_category and event_action.

Here's an example of an Analytics view that includes event_category and event_action

Event_label

Details of the information sent in the event_label.

In the "event_label", several pieces of information appear in this form:

[Context] - [Segment] - [Scenario] - [Widget] - [Action Button] - ID button

More specifically, this corresponds to all the settings you have made in the Dashboard:

  • [Context]: context name.

  • [Segment]: user segment.

  • [Scenario]: scenario name given in the Dashboard.

  • [Widget]: widget name.

  • [Action Button]: in case you use a dynamic action/link, you will have its details.

  • [ID button]: button ID in case of a custom button.

💡 We recommend keeping this nomenclature in mind when naming elements in the Dashboard. This will allow you to easily read your results in GA4.

Here is an example of the information you find in the "event_label":

Specificities of action buttons

🔎 A little focus on action buttons. At the end of the label information, you will find details depending on the accomplished action.

If you choose a dynamic action (action or link), several elements appear:

  • subscribe_link: click on the subscription button.

  • login: click on the login button.

  • link_button: click on a "discovery URL" widget button.

  • no_thanks: click on the alternative.

If you choose a custom button in your appearance:

  • custom_button + button ID: click on a custom button. The button ID will help you understand and isolate the button type.

Going further in the analysis

Thanks to the collected information, you can cross it with other statistics in GA4 and thus push your analysis further.

For example, we think of (these pieces of information should be adapted according to your GA configuration):

  • Page_location: to cross the performance of the wall with the viewed page.

  • Conversion: to understand the user journey up to subscription.

Our team is at your disposal to help you understand the reports and deepen your analyses. Feel free to contact us via chat or at support@poool.fr.

Did this answer your question?