App Tracking Transparency Opt-In Rate
Leveraging context to increase app tracking transparency opt-in rate.
The challenge with app tracking
Ever since Apple introduced App Tracking Transparency in 2021, apps relying on ad-revenue have struggled to show the ATT prompt at the right time, reducing their likelihood of an opt-in. Without an ATT opt-in by the user, it has become difficult to do proper ad attribution, and targeted ads, therefore reducing your app’s revenue.
Most apps decided to just prompt the user immediately, thinking that the total number of opt-ins will be higher using this approach. And while that may be true, our data shows that it’s more important to have a higher opt-in rate for active users you keep for a longer time, than just looking at the plain metrics of total number of opt-ins.
What is real-world context?
ContextSDK is a unique, new technology that detects the user’s real-world context to improve your app’s performance. We leverage on-device sensors, and execute on-device machine learning models to improve over time.
Currently, your app behaves the same way, no matter if the person carries their suitcase from the airport trying to grab a taxi while using their phone with the other hand, vs. the person being relaxed on the couch at home, together with their partner.
Leverage the user’s real-world context to maximize the ATT opt-in rate
ContextSDK is a new, unique technology leveraging the latest on-device sensors to find the perfect moment to ask your users for an opt-in. Using on-device Machine Learning execution, all decisions on when to show the prompt happen directly on-device, and require only 2 seconds of your app being in the foreground.
Focus on LTV instead of short-term gains
Ever since Apple introduced App Tracking Transparency in 2021, apps relying on ad-revenue have struggled to show the ATT prompt at the right time, reducing their likelihood of an opt-in. Without an ATT opt-in by the user, it has become difficult to do proper ad attribution, and targeted ads, therefore reducing your app’s revenue.
Be more tactical on when to ask your user, reduce churn, and drive those LTV metrics up.
Effortless integration
Replace your ATTTrackingManager with ContextManager, and you’re good to go:
Before ContextSDK
After ContextSDK
Step 1
Calibration mode
During this time, ContextSDK will calibrate its more than 180 context signals on your user-base and app. Each app is truly unique, and it’s critical to have a highly customized custom-model that will achieve the best results for your app.
While ContextSDK calibrates its signals, your app’s behavior won’t change.
Step 2
Start leveraging ContextSDK
Depending on your app’s size, after a few days or weeks, we’ll provide you with a custom ContextSDK binary including your own model. Just replace requestATTrackingAuthorizationForCalibration with requestATTrackingAuthorizationIfGoodMoment to let ContextSDK do its magic.
From that moment on, we will automatically fine-tune and optimize your machine learning model further, as we gather more data.
No PII, ever
We pride ourselves in being extremely privacy-focused, never using or storing any kind of Personally Identifiable Information, and never identifying a user, or device.
This allows for an easy integration, and makes your legal team happy.
For larger customers, we also offer on-premise solutions, leveraging your existing infrastructure.
An increase in ATT opt-ins = more revenue
Based on our experience with large players in the market: an increase of 10% ATT opt-in can increase their revenue by 5-7%.
It is clear that app developers usually don’t spend enough time optimizing this crucial aspect of their app. We want to change that.
Minimal footprint on your app
At ContextSDK, we've obsessed over efficiency, ensuring that our solution demands as little as necessary from your iOS app's resources. We've fine-tuned our technology, so it uses a minimal load on both battery and CPU on your user’s devices.
Risk-free rollout
ContextSDK is battle-tested and ready to handle your scale, currently processing more than 40m events per day.
During the calibration phase, we will keep triggering the ATT prompt during the first app launch, therefore not impacting or changing your app’s functionality in any way.
Once you switch over to your custom model, we recommend running your own A/B test to see the revenue impact ContextSDK has. Additionally, we’ll be able to provide you further insights into its performance.
You only have one shot
You can only trigger the ATT system prompt a single time. Don’t waste it.
Coming up with rules on when to best show the prompt is extremely difficult, time-consuming and requires a ton of data. We’ve spent the last 1.5 years building this technology, and have Billions of events already processed, so we can offer you this drop-in product today.