Skip to content
Apply
Who it’s for / AppsIn buildApp events, consent and App Store payments run in the hub as an optional module.

Count the store clicks Meta missed.

Clickfall for apps: store clicks from your website counted on your own domain, App Store payments from Apple, and leads sent to Meta for consenting visitors.

Illustrative
DayClickfall countedPlatform reported
Mon42
Tue63
Wed31
Thu63

Gap tracked daily, per campaign

The problem

Your ads send people to the App Store.

The platform sees some of them. Your backend sees more.

19App Store button clicks Clickfall counted, against 9 that Meta reported. Clicks, not downloads or installs.Source · One of our own sites, Sept 2026
How Clickfall does it

Three steps.

01Count the store clicksEvery App Store and Google Play button, on your own domain.
02Connect the appApp events and App Store payments, behind the app’s own consent.
03Send the true nameA store click goes to Meta as a lead, not a download.
What it's worth

Ads that find people who install, not people who click.

FAQ

Asked about apps.

Why not call a store click a download?

Because it isn’t one. If clicks are sent as downloads, the platform learns to find people who click and don’t install.

Does it read App Store payments?

Yes: the hub takes Apple’s server notifications into the customer ledger, as an optional module.

What about the app’s own events?

The app sends them with its own token, and only after the user’s consent in the app.

This explains the law in plain English. It isn't legal advice.