Tracking Events with RMTrack()

Basic event call

The public loader exposes RMTrack(action, payload). The full runtime also provides window.RM.track(action_code, payload). Calls made before initialization are queued and drained when the tracker is ready.

Use normalized action codes such as registration, deposit, purchase, lead_submit, form_submit, or a customer-owned custom action created in Settings.

Payload guidance

Send useful fields such as user_id, amount, currency, email_domain, plan, product_id, campaign, or funnel step. RetentionMaster stores payload JSON with the event and can use mapped amount and currency paths for revenue-style reporting.

Avoid sending raw passwords, payment card data, or unnecessary personal data. Prefer stable identifiers and business context that improve analysis.

Retention asset context

Retention asset events such as popup_shown, popup_closed, popup_cta_click, popup_form_submit, and popup_click are enriched with retention asset identity when fired from a RetentionMaster overlay.