AAdback Docs

Getting started

Welcome to Adback

Adback connects paid ad clicks, app installs, subscription revenue, and provider postbacks without forcing teams to build a web funnel.

Mobile SDK overviewInstall the Adback SDK, resolve attribution, send app events, and hand off campaign params.SKAN and AdAttributionKitUnderstand how Adback fits alongside SKAN, AdAttributionKit, and Apple AdServices.Signal linksCreate provider-ready ad links that capture campaign macros and redirect to approved store destinations.IntegrationsConnect ad networks, subscription platforms, and Apple Ads reporting to Adback.

What is Adback?

Adback is a lightweight attribution and postback platform for subscription app developers. It helps teams run paid social and search campaigns that redirect users to the App Store or Play Store while keeping enough signal to measure revenue and optimize campaigns.

The core loop is simple: create a signal link, install the SDK, connect subscription revenue, then send mapped events back to ad networks.

  • Signal links capture campaign, ad, creative, keyword, and click context.
  • The SDK resolves installs and exposes attribution params to RevenueCat, Superwall, or your own paywall logic.
  • Revenue integrations join subscription outcomes back to campaigns.
  • Postback workers send mapped, privacy-aware server events to providers.

Start here

For a first production integration, use the iOS SDK guide, create one paid-ad link, and connect either RevenueCat or Superwall before scaling provider postbacks.

  1. Create an app in the Adback console.
  2. Copy the production SDK key from the SDK screen.
  3. Install the iOS SDK and call configure on app startup.
  4. Pass attribution params into RevenueCat, Superwall, or your own backend.
  5. Use an Adback link in one Meta, TikTok, Google, or Apple Ads campaign.
  6. Verify click, install, revenue, and postback trace rows in the console.

Current MVP boundaries

Adback is intentionally focused on the signal path that small subscription teams need first. It is not a general product analytics SDK and it is not a generic short-link platform.

  • SDK revenue capture is not exposed in the MVP. Use RevenueCat, Superwall, App Store Server Notifications, or backend webhooks as the billing source of truth.
  • SKAN and AdAttributionKit reporting are not part of the MVP reporting surface.
  • The public SDK packages are binary/customer install packages. Private matching logic stays on api.adback.app.
  • adback.link is a shared resolver for many apps and links, not one Worker project per tracking link.