Review page analytics: the events you will see in your GA4/GTM/Clarity
If you connected your own GA4, GTM or Clarity in the review page editor ("Analytics" section), events with the names below will appear in your reports - here is each of them with an explanation, so you do not have to guess what it means
What it is and why
The customer's review page is a separate site (your own domain or ours, depending on the settings). When you enter your GA4/GTM/Clarity identifier in the dashboard, this page starts sending events to your account - the same one you use for the rest of your business
The event names are technical (in English, lowercase with underscores) - that is how GA4 will show them in a report. This is not a layout mistake or a forgotten translation: the name is the key by which the event is recognized in GA4 itself, and it cannot be changed for one account
No event carries the text of a review or complaint, or the customer's name or phone. Along with the event name come technical parameters: the rating, the platform, the code of the personal link (if the customer opened one) and a session identifier
The main customer path
These events describe the customer's path through the page itself - from opening the link to a review on the platform or a complaint in the form
| Event | What it means | When it fires |
|---|---|---|
| page_view | The review page was opened | The customer followed a link or a QR code |
| personal_link_expired | A page was shown for a personal link that is no longer active | The customer followed a personal link that was already used or turned off |
| rating_selected | A star rating was chosen | The customer tapped a number of stars |
| platform_redirect_clicked | The customer actually went to the review platform (Google or another) | Fires exactly once per page open, regardless of how the redirect happened |
| redirect_cta_clicked | A manual click on the button to go to the platform | The automatic redirect did not work (the browser blocked it), and the customer pressed the button themselves |
| conscious_cta_clicked | A click on the "Write a review on Google" button | The page is open in an app's built-in browser (Instagram, Threads and so on), where the app itself forbids the automatic redirect, or where the automatic redirect did not start after the text was copied |
| escape_skip | The instructions for leaving the app were shown right away, with no attempt at an automatic redirect | The page is open in iOS apps of the Meta family, where an automatic exit is deliberately not attempted |
| feedback_started | The customer started filling in the complaint form | The first text typed in the complaint field after a low rating (once) |
| feedback_submitted | The customer's complaint was sent successfully | The complaint form was accepted by the server |
| submit_error | Sending the complaint or contact failed | A network or server error while the form was being sent |
| platform_anyway_clicked | A click on the "I’d still like to leave a review on Google" link | A customer with a low rating decided to go to the platform after all instead of filling in the complaint |
| recovery_shown | The hold screen was shown (an offer to leave a contact for a callback) | It appeared right after the click on "I’d still like to leave a review on Google" |
| recovery_dismissed | The customer pressed "back" on the hold screen | A return to the complaint form without going to the platform |
| recovery_contact_left | The customer left a contact for a callback | A name and/or phone was sent from the hold screen |
| recovery_platform_continue | The customer went to the platform from the hold screen after all | Despite the hold, the customer chose to leave a review on the platform |
| social_click | A click on the business's social network icon | The customer tapped a link to Instagram/Facebook/etc. in the page footer |
Supporting events
These events describe the page's supporting screens: leaving an app's built-in browser (Instagram, Telegram and so on), from which Google does not open directly, the redirect modes with the customer's own text, and the Pochuto banner
| Event | What it means | When it fires |
|---|---|---|
| escape_overlay_shown | The "open in Safari" hint was shown (iOS) | The automatic exit did not work, or was not attempted at all (see escape_skip in the table above), and the page showed instructions |
| escape_fallback_shown | The fallback screen was shown (Android) | An attempt to open the link automatically in another browser did not take the customer off the page |
| copy_link_clicked | A click on the "Copy the link" button | The button is available on both screens above as the last way to leave the app manually |
| banner_click | A click on the "Powered by Pochuto" banner | The banner is shown only after the customer has already left a review or a contact |
| review_write_shown | The screen for writing your own text before the redirect was shown | The "Text first" or "Text and hint" redirect mode is on (the "Redirect to Google" section) |
| review_text_copied | An attempt to copy the customer's text to the clipboard (the result parameter shows whether it worked) | The customer pressed the button to go to the platform inside the text writing screen |
| review_animation_skipped | The animated hint did not play to the end | The customer pressed the redirect button before the animation finished (the "Text and hint" mode) |
These seven events go only to GA4/GTM/Clarity - they are not in the dashboard's own statistics (the "Statistics" section), because they are not tied to a specific review or request
A Microsoft Clarity detail
Clarity receives only the event name from the tables above, with no extra data (for example, what the rating or platform was) - unlike GA4 and GTM, where events arrive with the full set of parameters
Frequently asked questions
- Why are the event names in English?
- An event name is a technical identifier that GA4 shows unchanged in any account. Changing its language for one business is impossible - just as you cannot translate the name of a field in a database table
- Does Pochuto see these same events on its side?
- Partly. Some of the events above also go into Pochuto's own statistics (the "Statistics" section of the dashboard) for your business specifically - it is the same fact of an action, shown to you twice by different tools. But Pochuto never sees the data from your own GA4/GTM/Clarity account - it goes straight from the page to your service, bypassing our servers
- What if there are no events at all in my GA4?
- The most common cause is that the service ID is not entered in Profile or not turned on for the specific page. Check the "Analytics" section in the editor of the page you need - the dashboard will tell you which IDs are missing