Integrations

Adback integrations join campaign clicks, SDK installs, server revenue, and provider postbacks into one debuggable signal path.

Ad networks

Ad network integrations use saved credentials, mapped events, and signal links. SDK events do not automatically become provider postbacks; they must pass customer mapping, attribution, dedupe, and provider eligibility rules.

Meta Ads uses Conversion API credentials and event postback mappings.
TikTok and Google follow the same server-postback model as they are added.
Apple Ads uses read-only reporting sync and optional AdServices install attribution.
Provider tokens are encrypted and never collected by the mobile SDK.

Subscription platforms

Use server-side subscription platforms as the billing source of truth. The SDK only hands off attribution params.

RevenueCat attributes receive Adback params from getAttributionParams.
Superwall user attributes can receive the same params for paywall targeting.
Revenue webhooks carry purchases, renewals, refunds, trials, and subscription lifecycle events back to Adback.
The backend joins revenue to adback_id, install_id, customer aliases, and provider attribution records.

Postback rules

Postbacks are deliberate outputs, not a firehose.

Events must be mapped by the customer or default provider config.
Revenue postbacks should come from server revenue sources, not SDK purchase events.
User match data is normalized and hashed server-side before provider delivery.
Provider request IDs, acceptance state, retries, and redacted payload summaries belong in trace/debug views.