Understanding the New iOS Landscape
Apple introduced App Tracking Transparency (ATT) in iOS 14 and refined the SKAdNetwork in subsequent releases. Users now choose whether apps can read the Identifier for Advertisers (IDFA). When permission is denied, the IDFA is unavailable and traditional cookie‑style attribution stops working. At the same time, SKAdNetwork provides aggregated conversion data that respects privacy but changes how marketers evaluate campaigns.
Key Differences Between IDFA Based Attribution and SKAdNetwork
IDFA based attribution supplies exact click‑through timestamps, device level granularity, and full funnel visibility. It works best for real‑time optimization but relies on user consent.
SKAdNetwork attribution delivers a post‑back after a conversion, includes a conversion value that can encode up to eight bits of information, and groups results into cohorts. The delay can be several hours to days, and the data is less granular, but it complies with Apple’s privacy rules.
Adapting Measurement Strategies
1. Redesign Conversion Value Mapping
Because SKAdNetwork only returns a single integer per conversion, marketers must decide how to encode meaningful signals. Common approaches include mapping high‑value actions to higher numbers, using time windows to indicate user lifetime value, and reserving specific values for repeat purchases. The mapping should be simple enough to decode in analytics while capturing the most business‑critical events.
2. Extend Attribution Windows
SKAdNetwork post‑backs can arrive up to 24 hours after install and may be delayed further by Apple’s privacy threshold. Adjust reporting dashboards to incorporate these windows, and avoid making optimization decisions on incomplete data.
3. Leverage Probabilistic Modeling
When direct attribution is limited, combine SKAdNetwork cohorts with first‑party signals such as in‑app events, CRM data, and cohort analysis. Statistical models can estimate the likely contribution of each campaign to revenue, providing a bridge between privacy‑safe data and performance insights.
4. Integrate Server‑Side Event Forwarding
Sending conversion events from your server to ad networks bypasses client‑side restrictions. Ensure the payload includes the SKAdNetwork conversion value and any additional metadata required for downstream modeling.
5. Diversify Media Mix
Relying solely on iOS paid acquisition becomes riskier under ATT. Allocate budget to channels less dependent on IDFA, such as search, display networks with contextual targeting, and owned media where you control the data pipeline.
Practical Workflow for a Campaign Launch
- Define business goals and select up to eight conversion events that matter most.
- Map each event to a numeric conversion value, reserving higher numbers for higher revenue actions.
- Implement server‑side forwarding of conversion values to the ad network’s endpoint.
- Configure SKAdNetwork settings in the app’s Info.plist, including the appropriate ad network identifiers.
- Launch the campaign, monitor SKAdNetwork post‑backs, and update conversion value mapping as product priorities shift.
- After the attribution window closes, combine cohort data with internal analytics to calculate cost per acquisition, return on ad spend, and lifetime value estimates.
Measuring Success Without IDFA
Success metrics now rely on a blend of aggregated SKAdNetwork data, first‑party analytics, and predictive models. Track cohort‑level ROAS, monitor changes in conversion value distribution, and use control groups to validate model assumptions. Over time, the model can be refined to reduce uncertainty and support budget allocation decisions.
Future Outlook
Apple continues to iterate on SKAdNetwork, adding more conversion value bits and reducing latency. Marketers should stay informed about each iOS release, regularly revisit their conversion value strategy, and experiment with hybrid attribution solutions that combine privacy‑safe signals with owned data.
Leave a Reply