BoonAds Get in touch

The tracking and checks behind every campaign.

We work inside your attribution platform, pass every click through server-side tracking, and screen each conversion before it reaches your invoice.

How a conversion travels.

The same four steps for an install, a purchase or a lead.

  1. A click gets an ID

    Every ad click carries a unique click ID plus the source and sub-ID it came from.

  2. Your platform attributes it

    Your attribution platform or form records the install, event or lead and matches it to that click.

  3. A postback fires

    The conversion is sent back to us server to server, with the click ID and event name.

  4. We validate and report

    Checks run, the conversion is accepted or rejected, and it appears in reporting by source.

What we plug into.

No new software for your team to learn. We connect to what you already use.

Attribution platforms

AppsFlyer, Adjust, Branch, Singular, Kochava and any platform that supports ad-partner postbacks.

Server-side tracking

Click IDs, sub-IDs and payouts passed in tracking links and returned by postback. No pixels needed for app campaigns.

https://track.example/postback?click_id={click_id}&event={event_name}

Lead delivery

Leads posted to your CRM or API in real time, or sent by email, with the consent text and timestamp attached to each one.

Reporting

Conversions, rejections and spend by source and sub-ID, matched to your platform's numbers before every invoice.

Four checks run on every campaign.

When one trips, the conversion is rejected and the source is paused while we investigate.

Click-to-install timing

Installs that land impossibly fast, or long after a burst of clicks, point to click injection or click spamming.

when click_to_install is too short then reject, pause source

Network signals

Traffic from data-centre IP ranges, proxies or known bad networks is flagged before it reaches your report.

when ip in data_centre_range then reject

Device patterns

Clusters of identical device models, OS versions or settings from one source are a sign of install farms or emulators.

when device_share for one model is abnormal then review source

Post-install quality

Installs that never open again or never reach a key event are reviewed with you, and the source is cut if it keeps happening.

on advertiser_reject then reverse, claw back

See how your tracking holds up.

Send us your app or offer and we will check your events and postback setup before you spend anything.