Adback ties paid clicks to installs and to the trials and subscriptions that follow, then reports it all by campaign — and returns the same signal to the ad platform as server events, so you can optimize against subscription events instead of installs alone.
Links from redirect templates · Provider responses visible per event
How it works
Once the SDK is in the app, everything below is yours to run from the console — creating links, launching campaigns, and reading the results.
Campaign lifecycle
Create a link from a redirect template
campaign parameters captured at the click
Put the link behind your ads
Meta, TikTok, or Google campaigns
Adback matches installs to paid clicks
each install credits its source campaign
Trials and revenue join the campaign
from RevenueCat, Superwall, or custom events
Server postbacks return the signal
accepted or rejected, shown per event
Use cases
Attribution you can act on: reports that break down the way your ad account does, and a delivery view that shows whether the platform accepted each event.
Postbacks carry trials and subscriptions, so campaign optimization can target the events your revenue depends on — TikTok first, Meta and Google next.
Each click carries the parameters your template captures, so reports break down by the same campaigns you manage in the ad account.
Every postback shows its provider response — accepted or rejected — so you know the signal arrived before you judge the campaign.
A single link routes each click by country and language to the right App Store or Play Store destination.
More solutions
Start free. After the SDK is added once, links, campaigns, and reporting are all self-serve from the console.