Rimo Integration - Everflow Helpdesk

Rimo is a telehealth platform with a built-in Everflow integration that tracks the full visitor journey — from the moment someone lands on the Rimo intake funnel through treatment creation, approval, and recurring orders. This guide walks through setup so you can attribute partner traffic to every stage of the funnel using a mix of client-side and server-side events.

How tracking works in Rimo

Rimo supports two attribution modes that work together: a JavaScript SDK for in-browser events and server postbacks for server-confirmed milestones. Most networks enable both and split the funnel between them.

💻Client-side

JavaScript SDK

Visitor lands on your landing page and the cross-subdomain click script fires EF.click() and stores the click cookie.

Visitor redirects from your landing page to the Rimo intake form.

Rimo fires events in the browser as the visitor moves through the funnel.

Best for: tracking in-browser events — Teleform Started, Screen Viewed, Checkout Started.

🔒Server-side

Server Postbacks

Rimo's backend fires postbacks when a status has changed.

Click attribution comes from extracting the Transaction ID cookie and injecting it into the server postback.

Server-only events (Treatment Approved, First Order, Recurring) fire reliably regardless of browser state.

Best for: revenue-bearing events that occur post-browser.

Pro-Tip: split your funnel by reliability needs

Use client-side for tracking in-browser events (Teleform Started, Checkout Started). Use server-side for tracking events that occur after the user has left the browser (Treatment Approved, First Order, Recurring Order).

Before you start

A live Rimo account with admin access to Settings → Apps.

Your Everflow tracking domain (the URL you serve main.js from). Find it under Control Center → Tracking Domains.

Your Network ID (NID). Located at Control Center → Platform Configuration → General.

The Advertiser/Brand ID for the Rimo brand inside your Everflow account. You'll pass this as the aid parameter on every event.

Any Advertiser Event IDs you want to map to non-base conversions. Leave the adv_event_id parameter empty for the base conversion.

Setup walkthrough

Place the cross-subdomain click script on your landing page

On the page that redirects visitors to the Rimo intake funnel, drop the script below. The tld option ensures the click cookie is shared across subdomains, so attribution survives the hop from your landing page to the Rimo-hosted form.

Cross-subdomain click script

<script type="text/javascript"
        src="https://www.TRACKING_DOMAIN.com/scripts/main.js"></script>
<script type="text/javascript">
EF.configure({
  tld: 'ROOT_DOMAIN.com'
});
EF.click({
  offer_id: EF.urlParameter('oid'),
  affiliate_id: EF.urlParameter('affid'),
  source_id: EF.urlParameter('source_id'),
  sub1: EF.urlParameter('sub1'),
  sub2: EF.urlParameter('sub2'),
  sub3: EF.urlParameter('sub3'),
  sub4: EF.urlParameter('sub4'),
  sub5: EF.urlParameter('sub5'),
  uid: EF.urlParameter('uid'),
  transaction_id: EF.urlParameter('_ef_transaction_id')
});
</script>

Replace TRACKING_DOMAIN with your Everflow tracking domain and ROOT_DOMAIN.com with the root domain shared by your landing page and Rimo subdomain.

Install the Everflow integration in Rimo

Inside Rimo, go to Settings → Apps → App Store → Everflow and click Install.

Rimo App Store with the Everflow integration page open and the Install button highlighted

Configure the tracking domain

In the integration settings, paste your Everflow tracking domain without the https:// prefix. Example: www.serve-eflow-test.com.

Rimo Everflow integration settings with the Tracking Domain field populated

Pick your tracking modes and add your NID

Toggle the modes you want to use:

Client-Side Tracking — events fire directly from the visitor's browser via the Everflow JS SDK.

Server-Side Tracking — Rimo's backend posts to your tracking domain. Requires your NID (Network ID).

Send Coupon Code — opt-in toggle that adds a coupon_code parameter to every server postback.

Everflow Control Center General settings showing where to find your Network ID (NID)

Find your NID at Control Center → Platform Configuration → General.

Server-side tracking toggles in Rimo with the Send Coupon Code option visible

Wire up client-side events

For each browser-side event you want to track, set:

aid — the Advertiser/Brand ID for Rimo in your Everflow instance.

adv_event_id — the Advertiser Event ID. Leave empty for the base conversion.

Rimo client-side event configuration showing aid and adv_event_id fields

Wire up server-side events

Server postbacks accept a few additional fields:

aid — the Advertiser/Brand ID (same as client-side).

order_id — choose between Treatment ID (same value across every order in a treatment) or Order Number (unique per order). Order Number is recommended for clean dedupe.

adv_event_id — same rule as client-side.

amount — auto-populated for Treatment Created, First Order, and Recurring Order.

Rimo server-side event configuration with aid, order_id source, and event mapping

Supported events

Client-side (JavaScript SDK)

Event

When it fires

Teleform Started

Visitor begins the questionnaire.

Screen Viewed

Visitor lands on a step in the funnel.

Screen Completed

Visitor advances past a step.

Form Progress

Granular progress signal during a single screen.

Lead Created

Contact info captured.

Disqualified

Visitor failed eligibility.

Checkout Started

Visitor begins the checkout flow.

Offering Viewed

Visitor sees a treatment plan.

Offering Selected

Visitor picks a plan.

Treatment Created

Visitor completes checkout (not yet provider-approved).

Server-side (Server Postbacks)

Event

When it fires

Treatment Created

Treatment record exists. Not yet approved.

Treatment Approved

Provider has approved the treatment.

First Order

Initial order is approved and created.

Recurring Order

Every subsequent recurring shipment after the first.

Recommended event mapping

Most networks don't need every event. Start with this minimum mapping and add the rest only when a specific use case calls for it.

Client-side (recommended minimum)

Teleform Started — top-of-funnel signal. Lets you see whether traffic is actually engaging.

Checkout Started — intent signal. Useful for partners optimizing toward purchase intent.

Treatment Created — not-yet-approved checkout completion. Pairs with the server-side First Order to compare projected vs approved volume.

Server-side (recommended minimum)

First Order — pay out partners on approved orders, not on Treatment Created. Filters out anyone who never gets approved by a provider.

Recurring Order — track and (optionally) pay on every subscription renewal as its own event.

Template variables for event payloads

Already mapped

{{ orderAmount }} — auto-populated as amount on server events.

{{ couponCode }} — auto-populated as coupon_code when the Send Coupon Code toggle is on (step 4c).

{{ orderNumber }} — auto-populated as order_id if Order Number is selected as the source.

Optional — available for adv1-adv5

Pass any of the variables below as adv1–adv5 to enrich your reporting:

{{ treatmentId }}

{{ email }}

{{ phoneNumber }}

{{ offeringCode }}

{{ offeringId }}

{{ billingPlanId }}

{{ customerId }}

{{ storeId }}

Per the Parameters & Macros guide, adv1–adv5 are mapped to standard reporting columns by default.

Troubleshooting

Clicks aren't attributing across the redirect to Rimo

Double-check the tld value in the click script. It must be the root domain shared by your landing page and the Rimo intake form (e.g. if your landing is get.example.com and Rimo is at app.example.com, set tld: 'example.com'). If they're on completely different root domains, cross-subdomain cookies won't apply and you'll need to pass the transaction ID through URL parameters instead.

Server postbacks aren't showing up in Everflow

Verify three things: (1) the tracking domain in step 3 is correct and reachable, (2) the NID in step 4 matches your Network ID, (3) the Advertiser/Brand ID (aid) in steps 5-6 maps to a real advertiser in your Everflow instance. Use Everflow's Postback Validator if you want to confirm the request is shaped correctly.

Duplicate conversions on Treatment Created and First Order

That's expected if you map both as the same event in Everflow. Use distinct Advertiser Event IDs (adv_event_id) so they show up as separate events. Treatment Created represents intent (checkout completed); First Order represents revenue (provider-approved). Most networks pay only on First Order.

Recurring orders aren't firing

The Recurring Order event fires only on subsequent shipments after a First Order has been approved and created. It will not fire on the initial purchase — that's First Order's job. If you're testing with a fresh customer, you'll need to wait for a real renewal cycle to verify.

I want a parameter that isn't in the template variable list

The variables Rimo exposes are listed above. To pass anything custom, contact your Rimo account team — they can extend the template variable set on their side. Pass any new variable through adv1–adv5 for reporting.

Overview