Back

Billing for iOS apps

In light of the changes introduced by Apple, we have adjusted our billing model to reflect the changes in how conversions and attribution are measured.

Together with the rest of AppsFlyer’s attribution models, SKAdNetwork poses a different challenge: SKAdNetwork attribution is user anonymous and therefore cannot be deduplicated from other attribution methods based on user-level identifiers. For the above scenario, AppsFlyer provides customers with two options for solutions:

  1. AppsFlyer’s Single Source Of Truth – a unique AppsFlyer solution for deterministically deduplicating users across SKAN and other AppsFlyer attribution methods.
  2. Side-by-side – a view of AppsFlyer attribution models alongside SKAN methods.

Invoicing

Customers using Single Source of Truth (SSOT)

If you are measuring iOS performance with the Single Source of Truth (SSOT) feature turned on, AppsFlyer will charge according to SSOT. Since the SSOT mechanism recognizes when SKAdNetwork installs have been predated by AppsFlyer attribution, there is a higher assurance that this billing model reflects your true iOS campaign activity. This model assures that you can never be charged twice for a single conversion.

Customers not using Single Source of Truth (side by side)

If you are not utilizing the SSOT feature, the following billing methodology will be used to ensure you are never charged twice for the same conversion:

Daily maximum [SKAdNetwork conversions | Privacy-Centric Attribution] per media source

AppsFlyer runs a side-by-side comparison of the number of daily conversions measured by SKAdNetwork and those measured by Privacy-Centric Attribution, per each media source. The higher of the two numbers is taken into account for billing. This ensures that customers are never charged twice for a conversion event.

To deliver the utmost transparency and clarity in how each billing cycle is calculated, you can download a conversion usage report. The links for download are available on the My Plan page in the AppsFlyer dashboard.

Frequently asked questions

Does this entirely replace my current billing plan?

No. This calculation clarifies how iOS conversions are measured for the sake of billing.

What about billing for my Android app?

Billing for Android is not affected by this change.

Will I see an increase in my bill?

It depends. We highly recommend choosing SSOT as it captures attribution from all methods without counting a user twice. This can potentially lead to higher conversions, you will notice, however, that SSOT will likely significantly decrease your eCPI and other cost metrics, providing balance to how your advertising dollars are spent post iOS 14.

What happens if some days the conversion events measured by SKAdNetwork are higher than those measured by Privacy-Centric Attribution, and some days it’s reversed?

The month’s billing will be based on a day-by-day calculation. For each day of the billing month, the higher of the two conversion measurements will be the one taken into account for billing.

What about deterministic, IDFA-based attribution?

Deterministically attributed conversions will be calculated as part of the Privacy-Centric Attribution conversions, for the sake of billing.

How are the costs for detected fraud calculated in the new billing methodology?

Real-time fraud protection in Privacy-Centric Attribution is automatically calculated and will not appear as part of your billing statement. Post-attribution fraud is deducted from the daily calculation amount, and the billing methodology either based on SSOT, or as follows (if you’re not using SSOT):

Daily maximum [SKAdNetwork conversions | Privacy-Centric Attribution] — Post-attribution (per media source)

Could I be charged twice for the same conversion?

No. In order to prevent duplication in measurement and in charging, AppsFlyer will only charge based on either Privacy-Centric Attribution or SKAdNetwork measurement, whichever of the two is higher for that day. It is actually likely that you may be undercharged compared to the number of actual conversions, as a precaution to ensure that no duplication occurs.

How is a day calculated?

The beginning and end of the day is based on the UTC timezone.

Can I see an example?

Here’s an example of a billing summary for May 1-4:

SSOT enabled

 

SSOT not enabled:

Can't find what you're looking for? Head over to the Help Center.