Forward events to Fathom
You'll find the Fathom event names for your RightMessage questions, offers, and forms, plus what your website needs to send them.
Updated
View as MarkdownSee which RightMessage questions and offers visitors interact with in Fathom Analytics. RightMessage sends four types of interaction to the Fathom library already running on your page.
Turn forwarding on or off
Your page needs the RightMessage snippet and an initialized Fathom library with a callable fathom.trackEvent function. RightMessage doesn't install Fathom's script or set up a Fathom account for you.
Open Integrations, then Other integrations, to find Fathom Analytics. Enable turns forwarding on, and Disable turns it off. Both changes need to be published before they affect your website. Forwarding starts off.
Look up an event name
| If you want to track… | Fathom event name |
|---|---|
| Question displayed | rm_question_exposure:<questionId> |
| Offer displayed | rm_offer_exposure:<offerId> |
| Form submitted | rm_offer_conversion:<offerId> |
| Question answered | rm_answer:<questionId> |
Replace the part in angle brackets with the question or offer's ID, not its visible title. For example, a WorkForge (opens in a new tab) question with the illustrative ID raq_workstyle sends rm_answer:raq_workstyle when someone answers it.
Each event has a name but no properties object. RightMessage doesn't send the answer text as a Fathom property. Each question or offer has its own ID, so it produces separate event names.
RightMessage doesn't forward campaign exposure, campaign conversion, widget dismissal, split-test assignment, field writes, or tag changes to Fathom. Fathom receives fewer event types than PostHog.
Check what arrives in Fathom
Display and answer a question on your website, then look for both events in Fathom's event reporting. Each name includes that question's ID. A form submission uses the offer-conversion event name, even though the visitor submitted a form.
Forwarding needs to be published, and Fathom's library needs to be running. Consent settings and browser script blocking can also stop delivery.
If the Fathom global or its trackEvent function is missing, RightMessage skips the event. It catches delivery errors, and there's no dashboard queue or replay control for missed events. Disabling forwarding leaves Fathom's script and previously collected events in place.