Forward events to Google Analytics

Track RightMessage questions, offers, and other interactions alongside your website activity in Google Analytics. This page lists the events RightMessage sends and what your website needs to receive them.

Turn forwarding on or off

Your page needs the RightMessage snippet and a configured Google Analytics installation with a callable gtag function. If your site loads Google Analytics only through Google Tag Manager, gtag may not exist. Turn on the Google Tag Manager app instead, which pushes test impressions to your data layer.

RightMessage doesn't install Google Analytics, choose a measurement ID, or ask for an analytics API key. Keep those settings in your Google installation.

Open Project settings (the gear at the bottom of the sidebar), then Integrations, and choose the Analytics tab. The Google Analytics switch controls forwarding. It starts off, and changes apply to your website after you publish.

Enlarge

Analytics tab of Integrations with switches for Google Analytics, Fathom Analytics, PostHog and Google Tag Manager, with Google Tag Manager onOriginalOriginal

Look up an event name

A/B test impressions use GA4's experiment event instead. See the next section.

Keep the plural event names as written. Your Google Analytics setup may depend on them. Other analytics services use different names.

RightMessage calls gtag('event', eventName, data). The interaction's data becomes the event parameters, with its original property names. Unlike PostHog, these names don't get an rm_ prefix. Available parameters depend on the event.

This integration doesn't send separate events for custom-field writes, tag changes, or contact identification. It also doesn't create Google Analytics key events, reports, or custom dimensions. Set those up in Google Analytics using the event names and parameters you see arriving.

A/B test impressions

Each time RightMessage counts a visitor in a version of a campaign A/B test, a campaign holdback, or a question, form, offer or flow split test, it sends:

gtag('event', 'experience_impression', {
  exp_variant_string: 'RM-cpn_5didDYbc-control',
  rm_experience_name: 'Pricing page campaign · Holdback',
  rm_variant_name: 'Held back'
});

exp_variant_string is RM-<experienceId>-<variantId>. GA4's experiment reporting reads this parameter, so these parameters keep their names as written. Register exp_variant_string as an event-scoped custom dimension to compare versions in GA4. Each test's Send to your analytics panel on the campaign's Testing tab lists every version's string.

Impressions go only to an enabled, published Google Analytics app. They aren't sent for an excluded browser, in previews or debugger sessions, or before cookie consent when the project waits for it. See analyze tests in GA4 and Google Tag Manager.

Check what arrives in Google Analytics

Answering a question on your website sends rm_answers when forwarding is enabled and gtag is available. Look for it in Google Analytics' debugging or realtime tools. Use your website for this check, rather than only the RightMessage editor preview.

For forms, check the subscription in your email platform too. A form-submission event doesn't confirm that the platform accepted it. Integration verification covers that check.

If an event doesn't arrive

RightMessage skips delivery when gtag is missing and catches delivery errors. There's no dashboard queue or replay control for missed events. Check publication, script order, consent settings, and browser blocking.

Turning the switch off and publishing stops future forwarding. It doesn't uninstall Google Analytics or remove stored events. For the names sent to other services, see Fathom, PostHog, or Google Tag Manager.