AAdback Docs

Campaigns

Enhanced app campaigns

Enhanced app campaigns send users through fast ad links to the store while Adback preserves click context, matches installs, and sends better conversion signals back to providers.

How it works

The advertised app uses an Adback link in paid ads. The user is redirected to the app store, then the SDK resolves the install on first open.

  1. User clicks a Meta, TikTok, Google, or Apple Ads ad.
  2. adback.link captures click context and redirects to the approved store destination.
  3. The user installs and opens the app.
  4. The SDK resolves install attribution against recent click candidates.
  5. RevenueCat, Superwall, or backend revenue events join to the Adback attribution identity.
  6. Mapped provider postbacks send eligible signals back to ad networks.

Why use it

For subscription apps, the useful optimization signal is not just install volume. It is trial, purchase, renewal, refund, and payback quality by campaign and creative.

  • No web checkout or funnel is required for the MVP path.
  • Campaign, ad, creative, keyword, and click context can survive the store redirect.
  • Server revenue integrations are the source of truth for billing outcomes.
  • Trace rows make setup failures visible instead of leaving teams with black-box attribution.

Launch checklist

Start with one campaign before rolling Adback links across all paid traffic.

  1. Install and configure the SDK in a production build.
  2. Connect RevenueCat, Superwall, or backend revenue webhooks.
  3. Create one signal link for the app and network.
  4. Paste the provider-specific URL template into the ad platform.
  5. Run a small campaign and verify click, install, event, revenue, and postback traces.
  6. Expand once the trace is clean.