RevenueCat revenue,
joined to the ad that earned it.
RevenueCat stays exactly what it is today: your billing source of truth. Adback adds the missing link. Every purchase, renewal, refund, and trial conversion joins back to the paid click that produced it, and eligible events flow on to the ad network.
One setAttributes call in-app · One webhook in RevenueCat
How the join works
From receipt to campaign report
No SDK purchase tracking, no double bookkeeping. The app hands off attribution once; everything else happens server-to-server.
Your app hands off attribution
After the SDK resolves the install, getAttributionParams returns flat string attributes: adback_id, source, campaign, creative, and more. One setAttributes call passes them to RevenueCat.
Adback.getAttributionParams() → Purchases.shared.setAttributes(...)
RevenueCat sends billing events by webhook
Purchases, renewals, refunds, cancellations, and trial conversions arrive at Adback's webhook endpoint for your app. The webhook secret is verified before anything is processed.
purchases · renewals · refunds · trial conversions
Adback joins revenue to the click
Each event is matched back to the attributed install via adback_id and deduplicated on store transaction identifiers. Campaign, ad group, and creative reporting now reflects real billing outcomes.
joined on adback_id / install_id · transaction-level dedupe
Eligible events post back to the network
Revenue events that pass your mapping rules are forwarded server-side to the connected ad network (TikTok Events API today) with value and currency, so the optimizer learns from subscribers, not just installs.
mapped events only · accepted / rejected responses recorded
if let attributes = await Adback.getAttributionParams() {
Purchases.shared.setAttributes(attributes)
}Setup
Four steps, about fifteen minutes
Everything you need lives in the Adback console: the webhook URL, the secret, and the trace view to verify.
Connect RevenueCat in the Adback console
Open your app's integrations screen and add RevenueCat. The console generates the webhook URL and secret for this app.
Add the webhook in RevenueCat
In your RevenueCat project's integration settings, create a webhook, paste the Adback webhook URL, and set the authorization header to the secret from the console.
Hand off attribution in your app
After Adback.configure, pass the attribution parameters to RevenueCat with setAttributes so webhook events can be joined to the paid click.
Verify with a sandbox purchase
Trigger a test purchase and confirm the revenue event appears in the Adback trace view, joined to the expected install and campaign.
Data boundaries
What Adback does with RevenueCat data
The integration is scoped to attribution. Adback is not a billing dashboard and does not manage your RevenueCat account.
What happens
- The webhook secret is verified before any event is processed
- Events join to installs via adback_id and dedupe on store transaction identifiers
- Revenue amounts and currency feed campaign, ad group, and creative reporting
- Only mapped, eligible revenue events are forwarded to ad networks
- Every webhook and postback attempt is visible as a trace row
What never happens
- Adback never asks the mobile SDK for purchases or receipts
- RevenueCat API keys are not required. The webhook and secret are enough
- Raw webhook payloads are not echoed into logs or error responses
- Subscriber PII is not forwarded to networks unhashed
- No writes back into your RevenueCat project
Your subscriptions already
know which ads work.
Connect RevenueCat and find out. Free to start, no credit card.