How do you optimize campaigns with limited SKAN data? (2026)

SKAdNetwork gives you just enough data to be dangerous and not enough to be confident. After managing iOS campaigns through every SKAN iteration, the playbook for optimization under constrained signal has matured considerably. Here is how practitioners actually make decisions when conversion values arrive late, null, or not at all.

What is the core challenge of optimizing campaigns with limited SKAN data?

SKAN's privacy thresholds strip out 20-70% of conversion value data as null, according to Singular’s SKAN benchmarks report. You lose granular user-level attribution, delayed postbacks arrive 24-72 hours late, and crowd anonymity thresholds suppress low-volume ad set data entirely.

Key insight: Most SKAN campaigns lose more than half their conversion value data to null values and privacy thresholds.

• Null conversion values affect 40-70% of postbacks
• Crowd anonymity tiers gate data by volume
• Postbacks arrive 24-72 hours after install
• No user-level attribution exists in SKAN
• Low-volume ad sets lose data entirely

The fundamental constraint is not that SKAN data is inaccurate. It is that the data is incomplete by design. Apple's SKAdNetwork documentation enforces crowd anonymity tiers that determine how much data you receive based on install volume and privacy thresholds.

At the lowest tier, you get only the source app ID and no conversion value at all. According to AppsFlyer's 2024 analysis, roughly 40% of all SKAN postbacks arrive with null conversion values. For smaller campaigns or niche geos, that figure can exceed 70%.

The practical impact: you cannot tie a specific user to a specific ad, you cannot measure beyond a single postback window with confidence, and you cannot optimize toward downstream LTV events the way you did pre-ATT. Every strategy in this guide exists to reconstruct signal from these fragments.

For a deeper primer on how these mechanics work, see this breakdown of SKAdNetwork and its postback logic.

How has ATT compounded the SKAN data problem?

Apple's App Tracking Transparency framework reduced opt-in rates to roughly 25-30% according to industry tracking of ATT’s impact on mobile advertising. This means the opted-in cohort you can deterministically track is a small, self-selected minority that likely does not represent your full user base.

SKAN was designed to fill the gap for the 70-75% who opt out. But because SKAN itself strips data, you end up with a measurement gap on both sides: deterministic data from a biased minority, and aggregated-but-incomplete data from SKAN for the majority.

How do you use predictive modeling to compensate for missing SKAN conversion values?

Predictive models trained on your opted-in cohort (typically 25-30% of users per Adjust’s ATT benchmarks) can estimate LTV for the full install base. The key is mapping early funnel signals available within SKAN's timer window to downstream revenue events.

Key insight: Train predictive LTV models on opted-in users, then apply coefficients to SKAN cohorts for campaign-level optimization.

• Map D0 engagement signals to D30/D60 LTV
• Correct for opt-in user spending bias
• Validate predictions against SKAN cohort actuals
• Minimum 5,000 opted-in installs for stable models
• Update models monthly as user behavior shifts

The practical approach works in three stages. First, build a predictive model using your deterministic (opted-in) data where you have full event-level visibility. Second, validate that model against SKAN cohort-level outcomes to confirm it generalizes. Third, apply the model's coefficients to SKAN data to estimate campaign-level ROAS.

According to AppsFlyer’s performance benchmarks, apps that implemented predictive D0-D3 revenue models saw campaign-level ROAS estimates within 15-20% of actual values measured 30 days later. The most common architecture uses early engagement signals (session count, first purchase timing, feature usage) captured within SKAN's initial 24-hour conversion window.

One critical nuance: your opted-in users skew toward higher engagement and spend. According to data.ai's 2024 app intelligence report, opted-in users show 18-25% higher average revenue than opted-out users. Your model needs a bias correction factor to avoid systematically overestimating SKAN cohort value.

Most MMPs now offer built-in predictive modules. Adjust's Incrementality product, AppsFlyer's PredictSK, and Singular's SKAN Advanced Analytics all attempt this correction. The gap between their estimates and reality narrows as your install volume increases.

How do you run cohort analysis when SKAN strips user-level data?

Shift from user-level cohorts to campaign-level and time-based cohorts. Group installs by launch date, geo, and campaign ID, then measure blended backend metrics (revenue per install, trial starts) for each cohort.

According to RevenueCat’s State of Subscription Apps 2024, subscription apps using cohort-based SKAN analysis recovered 60-70% of their pre-ATT optimization capability.

Key insight: Campaign-date cohorts replace user-level cohorts as the primary optimization unit in SKAN environments.

• Group installs by campaign ID and date
• Need 200+ installs per cohort minimum
• Compare revenue-per-install across cohorts
• Hold spend stable for valid comparisons
• Track weekly cohort trends for fatigue signals

The mechanics are straightforward but require discipline. Create cohorts by grouping all installs from a specific campaign on a specific date. Then measure your backend KPIs (revenue, retention, trial conversion) for that cohort as a whole, not per user.

For example, if Campaign A generated 500 installs on January 15, track total revenue from those 500 installs at D7, D14, D30. Compare that cohort's revenue-per-install against Campaign B's cohort from the same date. This lets you make relative campaign quality decisions without user-level attribution.

The critical requirement is consistent spend levels. If Campaign A spent $5,000 on Monday and $500 on Tuesday, the Tuesday cohort is too small for reliable comparison. According to best practices for post-ATT measurement frameworks, you need at least 200-300 installs per cohort for statistically meaningful comparisons.

Time-based cohorts also help detect creative fatigue. When a campaign's weekly cohort revenue-per-install drops 15%+ versus the prior week at stable spend, that is a reliable fatigue signal even without user-level data.

How do you handle geo-level cohort differences?

Geo introduces massive variance. According to Liftoff's 2024 Mobile Ad Creative Index, CPI for casual games varies from $0.80 in Southeast Asia to $4.50 in the US. Blending geos into a single cohort masks performance.

Build separate cohorts per geo tier (Tier 1: US/UK/CA/AU, Tier 2: Western Europe, Tier 3: rest of world). Compare campaigns within the same geo tier only. Cross-geo comparisons should normalize by expected LTV per geo using your historical data.

What are creative-level proxy metrics and how do they replace conversion value data?

Creative-level proxies are upper-funnel platform metrics (IPM, CTR, watch-through rate, cost per engagement) that correlate with downstream outcomes you can no longer directly measure. Research from Solsten on psychology-driven creative optimization showed that improving IPM from 0.97 to 2.4 on Solitaire Klondike correlated directly with higher-quality installs.

Key insight: When you cannot measure downstream conversion, upstream creative metrics become your primary optimization lever.

• Map platform metrics to backend outcomes using opted-in data
• 3-second hold rate strongly predicts install quality
• Limit creative teams to 2 proxy KPIs maximum
• Update correlation maps quarterly
• IPM alone is insufficient; combine with engagement depth

The proxy metric approach requires building a correlation map between what you can measure (platform-side metrics) and what you want to measure (revenue, retention, trial starts). This is not guesswork. You build this map using your opted-in cohort where you have both platform metrics and backend outcomes.

Here is a practical example. Track IPM, CTR, and hold rate for every creative variant. Simultaneously measure D7 retention and trial conversion from your MMP's deterministic data. Run correlation analysis.

In subscription apps, we consistently see that creatives with 3-second hold rates above 45% produce trial-start rates 20-30% higher than creatives below that threshold, per industry patterns documented by Phiture’s Mobile Growth Stack.

Once you establish which proxy correlates with your target outcome, optimize toward that proxy in SKAN campaigns. This is imperfect but actionable. You are trading precision for speed.

The danger is over-indexing on a single proxy. Tactile Games’ CMO Gonzalo Fasanella described how Lily's Garden deliberately limited creative teams to only 2 KPIs to prevent analytics-driven bias from warping creative decisions. That restraint matters even more in SKAN environments where metrics are noisy.

How do MMPs handle probabilistic matching and what can you actually trust post-ATT?

MMPs use probabilistic (fingerprint-like) matching as a supplementary signal, but Apple's guidelines restrict its accuracy. According to privacy-first attribution standards, probabilistic methods now achieve roughly 50-70% match rates versus 90%+ in the deterministic era, per AppsFlyer's 2024 attribution accuracy report.

Key insight: Probabilistic matching supplements SKAN data but cannot replace it; use it for directional signals, not precise optimization.

• Match rates range from 40-85% depending on context
• Use for campaign-level trends, not ad-set decisions
• Cross-reference with SKAN data for validation
• Fraud risk is elevated with probabilistic methods
• Apple may further restrict these methods in 2026

Apple's crackdown on fingerprinting means probabilistic matching now operates in a gray area. MMPs like AppsFlyer, Adjust, and Singular use IP address, timestamp, and device model combinations to probabilistically match installs to clicks. The match confidence varies wildly by context.

High-confidence scenarios (same Wi-Fi network, install within 60 seconds of click) can exceed 85% accuracy. Low-confidence scenarios (cellular network, hours between click and install) drop below 40%. The aggregate accuracy of 50-70% means you should use probabilistic data for campaign-level trend analysis, not ad-set-level optimization.

One practical application: use probabilistic data to validate your SKAN cohort analysis. If SKAN says Campaign A outperforms Campaign B, and probabilistic data agrees, your confidence increases. If they disagree, investigate further before making budget moves.

Be aware that mobile ad fraud disproportionately exploits probabilistic matching. Fraudsters can generate fake click-to-install paths that match probabilistic criteria. Always cross-reference with SKAN data and backend metrics to catch discrepancies.

Need help scaling your mobile app growth? Talk to RocketShip HQ about how we apply these strategies for apps spending $50K+/month on UA.

Should you rely on probabilistic data for budget allocation?

Not as a primary signal. Use it as a tiebreaker. When SKAN data and cohort analysis both point in the same direction, allocate budget confidently. When signals conflict, probabilistic data can break the tie, but cap budget shifts at 15-20% based on probabilistic data alone.

According to post-ATT measurement framework best practices, the strongest approach triangulates three signals: SKAN postbacks, probabilistic matching, and backend cohort revenue. Two out of three agreement gives you actionable confidence.

How do web-to-app flows provide richer data than direct app install campaigns?

Web-to-app flows route users through a mobile web landing page before the App Store, allowing you to capture first-party data (email, ad click ID) before SKAN's privacy constraints kick in.

According to Adjust’s documentation on web-to-app journeys, advertisers using this approach see 30-50% more attributable conversion data than direct-to-store campaigns.

Key insight: Web-to-app flows let you collect first-party signals on your own domain before Apple's privacy framework strips them away.

• Capture click IDs on your own web domain
• Match installs using first-party data server-side
• Expect 20-40% higher CPI from added friction
• Best for high-LTV subscription and fintech apps
• Implement Meta Conversions API for server-side tracking

The architecture works like this: your ad sends users to a mobile web page you own. On that page, you capture the ad platform's click ID (fbclid, gclid, ttclid) and optionally collect an email address or other first-party identifier. Then you deep-link the user to the App Store.

When the user installs and opens the app, you match the stored click ID to the install using your own first-party data. This gives you deterministic attribution without relying on SKAN or probabilistic matching. The tradeoff: you add friction.

Conversion rates from web page to App Store drop 20-40% versus direct deep links, per Liftoff's 2024 benchmarks.

Subscription apps benefit most because the higher LTV justifies the conversion rate loss. A health and fitness app running web-to-app flows might see CPI rise from $3.50 to $5.00 but gain full attribution on 80%+ of installs instead of 30%. The net effect on optimized ROAS is often positive.

Meta's Aggregated Event Measurement (AEM) and Google's web conversion tracking both support this flow. Set up the Meta Conversions API on your landing page for server-side event tracking that survives browser-level privacy restrictions.

How should you handle null SKAN conversion values in optimization?

Null conversion values are not zero-value users. According to Singular's SKAN benchmarks, 40-60% of null-value installs actually generate revenue, often at rates only 10-15% below users with populated values. The key is redistributing null values proportionally rather than ignoring or zeroing them.

Key insight: Treating null conversion values as zero revenue systematically undervalues your best-performing campaigns.

• Never treat null conversion values as zero
• Use proportional redistribution as baseline method
• 40-60% of null installs generate actual revenue
• Predictive models improve null estimation accuracy
• Smallest campaigns suffer highest null rates

Apple returns null conversion values when privacy thresholds are not met, which means the campaign or ad set did not generate enough installs in the postback window. This is counterintuitive: your smallest, most targeted campaigns lose the most data.

The standard correction method is proportional redistribution. Take the distribution of non-null conversion values for a given campaign and apply that same distribution to the null installs. If 30% of non-null installs reached your highest conversion value tier, assume 30% of null installs did too.

This is imperfect but dramatically better than alternatives. Ignoring nulls means throwing away 40-60% of your data. Treating nulls as zero artificially depresses campaign ROAS, causing you to kill campaigns that are actually profitable.

A more sophisticated approach uses your predictive model (discussed earlier) to estimate the likely conversion value distribution of null installs based on the campaign's other characteristics: creative type, geo, time of day, platform. Some MMPs now offer this automatically.

Singular’s SKAN advanced analytics includes null value redistribution as a built-in feature.

What conversion value schema minimizes null impact?

Design your conversion value mapping to front-load the most important signal into the fewest bits. Instead of mapping 64 granular revenue buckets, use a simplified schema: 6 revenue tiers plus engagement flags.

According to Apple’s SKAN documentation, coarse conversion values (low/medium/high) still populate even at lower anonymity tiers where fine-grained values return null.

Prioritize the coarse value schema first. If a user hits your "high" coarse value tier, that single bit of information may be worth more than a null fine-grained value.

How do you structure creative testing when SKAN limits your feedback loop?

SKAN's delayed and incomplete data means creative tests need 3-5x more installs per variant than pre-ATT to reach statistical significance. According to industry testing standards documented by RocketShip HQ’s analysis of AI creative testing pitfalls, the hidden cost of increased creative output is proportionally larger test budgets.

Key insight: Each creative variant needs 3-5x more installs under SKAN to achieve the same statistical confidence as pre-ATT tests.

• 800-1,500 installs per variant for SKAN significance
• Pre-qualify concepts with proxy metrics first
• Separate creative themes into distinct ad sets
• Kill losers at 48 hours using platform metrics
• Validate winners after 5-7 days with SKAN data

Pre-ATT, you could test a creative variant with 200-300 installs and get a reliable read on D1 retention or trial rate. With SKAN, the combination of delayed postbacks, null conversion values, and aggregated data means you need 800-1,500 installs per variant for comparable confidence.

This fundamentally changes your testing velocity. If your daily budget supports 1,000 installs, you can test at most one or two new creatives per week instead of five or six. The implication: be ruthless about which concepts enter testing.

Pre-qualify creative concepts using proxy metrics (IPM, hold rate) before committing full SKAN test budgets.

Avoid the asset stuffing trap where all creative variants get dumped into one ad set. This prevents the algorithm from allocating sufficient impressions to each variant. Instead, separate creatives thematically into distinct ad sets, each with enough budget to generate the required install volume.

The testing cadence that works: run 2-3 new concepts per week in dedicated test ad sets with $1,500-3,000 minimum budget each. Use proxy metrics for the first 48 hours to kill obvious losers, then wait 5-7 days for SKAN data to validate winners.

How do lookalike audiences work with limited SKAN signal?

Lookalike audience quality has degraded significantly post-ATT because seed audience data is sparser. According to analysis of Meta lookalike audiences for mobile UA, lookalikes built from opted-in users only represent a biased subset, and Meta's own broad targeting often matches or outperforms narrow lookalikes on iOS.

Key insight: Broad targeting with strong creative differentiation increasingly outperforms narrow lookalikes on iOS due to SKAN signal loss.

• Meta Advantage+ often beats manual lookalikes on iOS
• Use first-party data (email lists) as seed audiences
• Web-to-app visitors make high-quality retargeting pools
• Lookalikes need 10K+ seed users for reliable performance
• Broad targeting works best paired with creative segmentation

The data tells a clear story. Meta's Advantage+ campaigns, which use broad targeting with algorithmic creative optimization, have shown 10-20% lower CPA than manually configured lookalike campaigns on iOS, per Meta's own 2024 performance benchmarks.

Why? Lookalikes depend on rich user event data to model similarity. With SKAN, Meta receives delayed, aggregated, and often null conversion signals. The model powering lookalikes simply has less to work with. Broad targeting gives the algorithm more room to find pockets of efficiency using its own first-party engagement data.

That said, lookalikes still have a role in specific scenarios. For high-value events with large seed audiences (10,000+ users), lookalikes can outperform broad targeting by 5-15% on CPA.

The key is using your first-party data, such as email lists or in-app purchaser lists, as seed audiences rather than MMP-derived event audiences.

One underused tactic: create web-based custom audiences from your web-to-app flow (discussed earlier). Users who visited your landing page but did not install form a high-intent retargeting and seed audience pool that is not subject to SKAN limitations.

Retargeting benchmark data shows web-engaged audiences convert at 2-3x the rate of cold traffic.

What does a practical SKAN-era measurement framework look like?

The strongest post-ATT measurement frameworks triangulate three independent signals: SKAN postback data, MMP probabilistic data, and backend revenue cohort analysis. According to post-ATT measurement framework guidance, campaigns where all three signals agree can be optimized with near pre-ATT confidence.

Key insight: Triangulating SKAN, probabilistic, and backend cohort data restores 70-80% of pre-ATT measurement confidence.

• Layer 1: SKAN postbacks with null redistribution
• Layer 2: MMP probabilistic matching for direction
• Layer 3: Backend server-side cohort revenue (ground truth)
• Layer 4: Geo-based incrementality holdout tests
• Two-of-three agreement gives actionable confidence

Here is the framework RocketShip HQ uses in practice. Layer 1 is SKAN postback data with null value redistribution, providing campaign-level conversion value estimates with a 24-72 hour delay. Layer 2 is MMP probabilistic matching, providing directional campaign-level attribution with 50-70% match confidence.

Layer 3 is backend cohort analysis: your own server-side revenue data grouped by install date and campaign. This is the ground truth layer. It tells you total revenue generated by all installs on a given day, regardless of attribution method.

Layer 4, which most teams skip, is incrementality testing. Run geo-based holdout tests where you pause spend in a matched market and measure the revenue delta.

According to Eric Seufert’s analysis on MobileDevMemo, incrementality testing is the only method that answers whether your ad spend actually caused conversions versus capturing organic demand.

The decision framework: when Layers 1 and 2 agree, act quickly. When they disagree, defer to Layer 3 backend data. When Layer 3 is ambiguous (similar campaigns, similar dates), invest in Layer 4 incrementality testing. This gives you the right tool for each uncertainty level.

How should you configure SKAN conversion value schemas in 2026?

The best-performing schemas in 2026 combine coarse and fine-grained values to maximize signal at every anonymity tier. According to Apple’s SKAN 4.0 documentation, you get up to 3 postback windows (0-2 days, 3-7 days, 8-35 days), but only the first window supports fine-grained 6-bit values.

Key insight: Prioritize revenue signal in the first postback window and engagement signal in the coarse-value second and third windows.

• First postback: revenue and monetization signal (fine-grained)
• Second postback: D3-D7 retention flag (coarse)
• Third postback: D8-D35 retention flag (coarse)
• Encode the highest-value question in the coarse tiers
• Audit and update schema every 90 days

Most apps make the mistake of trying to encode too much into the 6-bit (64 possible values) first postback. The smarter approach is to focus that first window on a single question: how much is this user likely to spend?

For subscription apps, a practical first-postback schema: values 0-3 map to engagement depth (sessions, features used), values 4-15 map to trial start timing, and values 16-63 map to subscription purchase and revenue tier.

This ensures that even if you only receive the coarse value (low/medium/high), you know whether the user subscribed.

The second and third postbacks in SKAN 4.0 only return coarse values (low, medium, high). Use these for retention signals. Second postback (days 3-7): did the user return after day 3? Third postback (days 8-35): did the user retain through week 2?

These binary retention flags are enormously valuable for predicting LTV even as coarse signals.

Update your schema quarterly. As your product changes, the early signals that predict LTV shift. A feature launch can change which D0 behavior correlates with D30 retention. Privacy-first attribution frameworks recommend schema audits every 90 days minimum.

How does Android's Privacy Sandbox affect SKAN-like optimization strategies?

Google's Privacy Sandbox for Android introduces the Attribution Reporting API, which shares structural similarities with SKAN (aggregated, delayed, privacy-threshold-gated data). According to Google's 2024 developer documentation, Android's API will support up to 20 event-level conversions per campaign versus SKAN's limit of 1-3 postbacks.

Key insight: Android Privacy Sandbox gives more conversion events than SKAN but still requires the same cohort-based optimization discipline.

• Android Attribution API allows 20 event-level reports
• GAID still available; build infrastructure now
• Port 70-80% of SKAN optimization methods to Android
• Topics API will degrade interest-based targeting
• Creative-driven targeting becomes essential cross-platform

Android marketers have a window of advantage. While Privacy Sandbox is rolling out gradually, the GAID (Google Advertising ID) remains available for most Android users. Use this window to build your cohort analysis infrastructure and predictive models before Android signal degrades.

The Attribution Reporting API's key difference from SKAN is the support for both event-level and aggregate reports. Event-level reports are limited (20 per campaign, with noise injected) but provide more granularity than SKAN's single conversion value. Aggregate reports are more complete but add noise and delay.

Practically, this means the strategies outlined in this guide (predictive modeling, cohort analysis, proxy metrics) apply to Privacy Sandbox with modifications. You will have more data points to feed models but still need the same triangulation approach.

Apps that build this infrastructure for iOS SKAN can port 70-80% of their methodology to Android with relatively modest adaptation.

One critical difference: Google's Topics API replaces interest-based targeting, which means the audience targeting degradation seen on iOS post-ATT will eventually hit Android too. Prepare by investing in creative-driven targeting now, where the creative itself acts as the targeting mechanism.

Optimizing with limited SKAN data is not about finding a single workaround. It is about building a layered system: predictive models for speed, cohort analysis for ground truth, proxy metrics for creative decisions, and web-to-app flows for richer signal.

Start by auditing your null conversion value rate, then implement the framework layer that addresses your biggest measurement gap first.

Frequently Asked Questions

How long should you wait before making budget decisions on SKAN data?

Wait at least 5-7 days for first postback data to accumulate and null values to stabilize, according to Singular's SKAN implementation guidelines. For subscription apps with longer conversion windows, extend to 10-14 days before making significant budget shifts.

Can you still run retargeting campaigns on iOS with SKAN limitations?

Yes, but effectiveness has dropped. According to AppsFlyer’s retargeting benchmarks, iOS retargeting conversion rates fell 38% post-ATT. Web-to-app retargeting pools and first-party email audiences remain the most reliable retargeting sources.

What minimum daily budget do you need for reliable SKAN optimization?

You need enough budget to hit Apple's crowd anonymity thresholds consistently. Industry patterns suggest a minimum of $500-1,000/day per campaign on Meta and $300-500/day on TikTok to consistently receive non-null conversion values, per Singular's SKAN benchmarks report.

Should you use SKAN 4.0's multiple postbacks or stick with a single postback?

Use all three postback windows if your app has a conversion cycle longer than 2 days. According to Apple’s SKAN 4.0 documentation, the second and third postbacks add 7-35 days of retention signal via coarse values, which is critical for subscription apps.

How do you detect ad fraud in SKAN campaigns without user-level data?

Focus on statistical anomalies at the campaign level: unusually high install volumes with near-zero conversion values, or geographic distributions that do not match targeting. According to AppsFlyer’s fraud report, SKAN fraud manifests as 15-25% inflated install counts from click injection attacks.

Does Apple Search Ads provide better data than SKAN for iOS campaigns?

Yes, significantly. Apple Search Ads uses its own attribution framework that provides deterministic, user-level attribution with no privacy thresholds, per Apple Search Ads documentation. Use ASA campaigns as a calibration benchmark for your SKAN data models.

How do emotional creative strategies interact with SKAN measurement limitations?

Emotional differentiation in creative becomes more valuable when measurement is constrained because strong emotional hooks improve IPM and reduce CPI, both directly measurable. Lily’s Garden achieved outsized performance by targeting sadness and anxiety emotions when 90% of competitors used only humor.

What tools or MMPs are best for SKAN optimization in 2026?

AppsFlyer PredictSK, Singular SKAN Advanced Analytics, and Adjust's Conversion Hub are the leading tools. According to AppsFlyer's 2024 Performance Index, apps using their PredictSK module achieved ROAS estimates within 15% of actuals. Choose based on which MMP your existing stack uses; switching cost is rarely justified.

Looking to scale your mobile app growth with performance creative that delivers results? Talk to RocketShip HQ to learn how our frameworks can work for your app.

Not ready yet? Get strategies and tips from the leading edge of mobile growth in a generative AI world: subscribe to our newsletter.

Related Reading

• Privacy-first attribution and measurement for mobile apps (comprehensive guide)
• AppsFlyer App Retargeting Report: Benchmarks and Post-ATT Strategies (2026)
• AppsFlyer Mobile Ad Fraud Report: Fraud Rates and Protection Benchmarks (2026)
• How Has ATT Changed Mobile Advertising? (2026)
• How to Use Lookalike Audiences for Mobile App UA on Meta