RevenueCat

Attribute RevenueCat in-app purchases and subscriptions to the traffic that earned them.

Realific listens for RevenueCat webhooks. You add one webhook in RevenueCat that points at Realific, and paste its signing secret into Settings → Revenue → RevenueCat.

Set up the webhook

Where: app.revenuecat.com → your project → Integrations → Webhooks

1. Open app.revenuecat.com and pick your project.
2. In the left menu, open Integrations → Webhooks and click “Add new configuration”.
3. Name: Realific. Webhook URL: paste https://api.realific.app/webhooks/revenuecat/YOUR_SITE_ID
4. Environment: Production. Events: All events.
5. Turn on “HMAC webhook signing” and copy the signing secret. (No HMAC? Set “Authorization header value” to a long random string and use that instead.)
6. Save, then paste the secret into Realific (Settings → Revenue).

Your exact webhook URL, with your site id filled in, is on the provider card in Settings → Revenue.

Events

• All events (Realific uses purchases, renewals and refunds)

Where the secret is

Integrations → Webhooks → your configuration → HMAC signing secret (or the Authorization header value you set).

Realific stores the secret encrypted (AES-GCM) and never shows it again. To rotate it, paste the new one and click Update secret.

Link payments to visitors

Purchases are matched by RevenueCat’s app_user_id, so pass the same user id to realific.identify() on your site. You can also set a subscriber attribute realific_visitor_id.

// On your site, after sign-in
realific.identify(user.id, { email: user.email });

// In the app: the same id
Purchases.logIn(user.id);

In the browser, the visitor id is the _rf_vid cookie, also available as window.realific.v. Without it, Realific matches the customer email against users identified with realific.identify() in the last 30 days.

Check it works

Make a test purchase (or use RevenueCat’s “send test event”), then open Revenue in Realific. The provider card shows “Last payment received” once the first event arrives.