How to Choose a Consent Management Platform for Your Mobile Game: Google's 2026 TCF Requirements, UMP vs. Third-Party CMPs, Consent Rates and Ad Revenue, RFP Questions, and an Implementation and QA Plan
A consent management platform (CMP) is the tool that tells a player, on first launch, what their personal data will be used for, then stores the player's choices as a standardized signal and passes it to the ad SDKs and measurement SDKs in the game. On the surface it is a single pop-up. In practice it is the gate that decides how much of your European ad inventory can be sold as personalized, and how much of your UA conversion data ever makes it back to the networks you buy from.
That gate is not optional. Since January 16, 2024, Google has required publishers using AdMob, Ad Manager, or AdSense to work with a Google-certified CMP integrated with IAB Europe's Transparency and Consent Framework (TCF) in order to serve personalized ads to users in the European Economic Area (EEA) and the UK, and it extended the same requirement to Switzerland on July 31, 2024. As of November 2026, two more dates sit on top of that: TCF v2.3 is mandatory for consent strings generated on or after March 1, 2026, and the deadline for TCF v2.4 in mobile app environments is February 23, 2027.
This guide lays out how a game studio that earns ad revenue or runs UA in Europe should choose a CMP: the difference between Google's UMP SDK and third-party CMPs, what consent rates do to ad revenue and measurement, pricing models, an evaluation checklist and RFP questions, and an implementation and QA plan. How to rebuild a UA strategy without third-party data is covered in Privacy-First UA: How to Build a Strategy That Works Without Third-Party Data. This piece focuses on the purchase decision behind the consent infrastructure that makes that strategy work. It is not legal advice; final wording and the choice of legal bases should be settled with in-house counsel or outside advisors.
Why is a CMP mandatory for games that serve ads in the EEA, UK, and Switzerland?
To serve personalized Google ads to users in the EEA, the UK, and Switzerland, a Google-certified CMP integrated with the TCF has to generate the consent string (TC String); traffic without one can only be sold as non-personalized or limited ads. A game with no CMP, or a misconfigured one, ends up selling a large share of its European traffic at lower prices.
According to Google's help documentation, the requirement took effect on January 16, 2024 for the EEA and UK and on July 31, 2024 for Switzerland. Google updates its certified list weekly, and as of November 2026 it includes more than 100 CMPs. Google is also explicit that certification is assessed against criteria focused on TCF integration, and that it does not check CMPs for full compliance with the TCF or with privacy law. Using a certified CMP does not mean the legal work is done, and that is worth stating before any purchase.
The TCF itself keeps moving. These are the dates a game studio needs to know as of November 2026.
Date | What happened | What it means for a game studio |
|---|---|---|
January 16, 2024 | Google-certified TCF CMP required for personalized ads in the EEA and UK | Requests without a certified CMP are sold only as non-personalized or limited ads |
July 31, 2024 | Same requirement extended to Switzerland | Swiss traffic follows the same rules |
June 19, 2025 | IAB Europe releases TCF v2.3 | The disclosedVendors segment becomes mandatory |
March 1, 2026 | Consent strings generated from this date must follow v2.3 | A missing segment, or one that omits Google (vendor ID 755), triggers Google error 1.4 and may fall back to limited ads; strings created earlier remain valid |
July 23, 2026 | TCF technical specifications v2.4 and Policies v5.0.b published | Standard explanatory text and illustrations for Features, a renamed Special Feature 2, policy changes on multi-device consent |
October 23, 2026 | Deadline for v2.4 in web environments | Already applies if you run a web shop or web payment pages |
February 23, 2027 | Deadline for v2.4 in mobile app and CTV environments | App CMP SDK updates and your game update must be live before this date |
The last row is the most operational one. A web CMP can be updated by swapping a script on the server, but an app CMP is updated only when the vendor ships a new SDK, the studio ships a build containing it, and players install the update. If you are choosing a CMP in November 2026, "when will your v2.4-ready SDK ship?" is a mandatory RFP question. During the v2.3 transition, IAB Europe advised that CMPs should not need to resurface the consent UI purely because of that change. Confirm with each vendor whether v2.4 requires renewed consent and, if so, when and for which users it will ask again.
How do consent rates affect ad revenue and UA measurement?
Ad requests from users who have not consented are sold without personal data, which lowers prices, and conversions sent without a consent signal cannot be used for user-level measurement and optimization. A CMP therefore shapes results on both the revenue side and the UA side.
Start with revenue. Google's documentation describes limited ads as disabling the collection, sharing, and use of personal data for ad personalization while using only what is needed to deliver the ad. With limited ads, personalization and remarketing are off, and so are frequency capping, conversion tracking, and unique reach measurement. AdMob Campaigns do not serve on limited ad requests, and programmatic demand participates only when programmatic limited ads is turned on. With less demand competing, the same impression sells for less.
Academic research gives a useful reference point for how much less. A study by Laub, Miller, and Skiera analyzed 218 million ad impressions from 10,526 publishers (apps) in EU and US mobile in-app traffic in 2023 and found that impression prices were on average 23% lower when user tracking was not available. The CMP vendor Usercentrics reports that across its customer base, the average opt-in rate in apps is 80%, top performers reach 90% or more, and unoptimized implementations fall as low as 64%. These are vendor-reported figures from its own customers and should be read as directional, but the fact that implementation quality alone can open a gap of more than 20 percentage points on the same European traffic is meaningful for the decision.
A simple calculation helps calibrate this. If the consent rate rises from 64% to 80%, the share of European ad requests that can be sold as personalized rises from 64 to 80 per 100. If non-consented impressions sell at a 23% discount, then indexing the consented price at 100, the average price is 91.7 at a 64% consent rate and 95.4 at 80%, a difference of about 4% in European ad revenue. For a game earning $100,000 a month in European ad revenue, that is several thousand dollars a month. The real difference depends on genre, ad format, and mediation setup, so treat this as a starting point for estimating the value of a CMP switch or a consent screen redesign. Price levels by region and format are covered in What Are 1,000 Ad Impressions Worth? 2026 Mobile Game eCPM Benchmarks by Format, Region, and OS, and the Q4 Price Window.
The UA side is affected more quietly. Google Ads instructs advertisers who send app conversions through app attribution partners (AAPs), the MMPs Google has certified, to capture the consent status of EEA users before sending those conversions. For conversions passed without user-level consent, Google says it may use gbraid for non-user-level measurement. The same Google Ads page lists, for each MMP, the minimum SDK version needed to pass consent and the method for delaying SDK start until consent is captured. If your game uses Firebase, the consent mode v2 values ad_user_data and ad_personalization have to be updated to match the CMP result. In short, choosing a CMP is not a pop-up design decision; it is the design of a data flow in which the signal the CMP creates reaches your MMP SDK, Firebase, and ad SDKs in the right order. How MMPs match installs, and why every network reports a different number, is covered in Why Every Dashboard Shows a Different Install Count: A Game Marketer's Guide to Mobile Attribution in 2026.
How does Google's UMP SDK differ from a third-party CMP?
Google's User Messaging Platform (UMP) SDK is Google's free CMP, configured in the Privacy & messaging section of AdMob and Ad Manager and displayed inside the app, while third-party CMPs are paid tools that manage multiple platforms and regulations from one place and offer deeper consent analytics, experimentation, and design control. A single title that monetizes mainly through Google's stack is often well served by UMP; studios with many titles, games spanning web, PC, and mobile, or a goal of actively managing consent rates are the ones that should evaluate third-party CMPs.
Google's developer documentation is clear on how UMP works. On every app launch, call requestConsentInfoUpdate() to check whether consent is needed, call loadAndShowConsentFormIfRequired() to show the form when required, and request ads only when canRequestAds() returns true. A privacy options entry point must also be visible, for example in the settings screen, so players can change their choices later. Google stresses that the app should refresh consent status on every launch rather than relying on cached consent data. UMP also supports writing the GPP signal for US state privacy laws.
Criterion | Google UMP SDK | Third-party CMP (typical) |
|---|---|---|
Cost | No separate fee, used within your AdMob or Ad Manager account | Subscription based on usage such as daily active users, monthly unique visitors, or sessions; enterprise tiers quoted |
Google certification and TCF | Google-certified; Google's messages support TCF v2.3 | Most are on Google's certified list, but check each one |
Platforms | Apps using the Google Mobile Ads SDK (Android, iOS, Unity, Flutter, and others) | Often manages apps, web, CTV, and PC from one account |
Regulations | European regulations messages, US state regulations messages (writes GPP) | Templates for GDPR, US state laws, and other regions; multilingual management |
Design control | Configured within Google's message templates | Wider control over layout, copy, and branding (within TCF policy) |
Consent analytics and testing | Basic reporting | Often offers consent rates by screen and A/B testing |
Non-Google ad partners | Supported through the TCF and Google's Additional Consent (AC) specification | TCF and AC support, with vendor list management tools |
Measurement SDK integration | The studio passes consent results to its MMP and Firebase | Some vendors provide MMP and Firebase consent integrations at the SDK level |
The third-party column varies by vendor and should be read only as typical features. The decision comes down to three questions, not a count of features. First, does most of your ad revenue come through Google mediation? If so, UMP meets the requirements with the least integration work. Second, is your European traffic large enough that one or two points of consent rate make a meaningful revenue difference? If so, the subscription for a CMP with screen testing and analytics can pay for itself. Third, do the same players give consent repeatedly on mobile, PC, and web? Now that TCF v2.4 policies address multi-device consent, studios running multiple platforms should check each vendor's plans here separately.
If you also ship an iOS build, keep one more distinction in mind. Apple's App Tracking Transparency (ATT) prompt is a system dialog separate from GDPR consent, and a CMP does not replace it. The order and wording of the two screens affect both user experience and both consent rates, so check how each CMP handles sequencing with ATT during the demo.
Can a CMP handle US state privacy laws, GPP, and age signals too?
Unlike Europe, the US model centers less on prior consent and more on opt-outs from the sale or sharing of data and from targeted advertising, and the standard for carrying those opt-out signals through the ad ecosystem is IAB Tech Lab's Global Privacy Platform (GPP). As of November 2026, a capable CMP should generate GPP signals for the US alongside TCF signals for the EEA.
According to IAB Tech Lab, GPP is a protocol that carries a US National string, a number of US state strings, IAB Europe's TCF, and IAB Canada's TCF in a single container. The Google Mobile Ads SDK reads GPP signals that a CMP or custom messaging has written to local storage, and for studios not using GPP it also supports setting the restricted data processing (RDP) parameter directly. Comprehensive state privacy laws in the US keep multiplying each year, so rather than tracking the list yourself, it is more realistic to review a source such as the IAPP US State Privacy Legislation Tracker with counsel on a regular cadence, and to ask CMP vendors how quickly they update GPP sections and message templates when a new state law takes effect.
Children and age signals deserve only a short section here, but not a light one. The FTC's amended COPPA Rule took effect on June 23, 2025, with a compliance date of April 22, 2026 for most provisions. Under the amended rule, operators of child-directed services must obtain separate verifiable parental consent before disclosing children's personal information to third parties, including for targeted advertising. A CMP connects to this in two ways. The first is branching the consent flow itself by age. Google's documentation says that when an app using UMP tags requests from under-age users with TFUA, UMP does not request consent, and that configuring this for COPPA and related regulations is the developer's responsibility. The second is where the age signal comes from. On July 29, 2026, Google announced it is expanding the Play Age Signals API to developers globally. The API returns an age range rather than a birth date; it launched first in Brazil and is expanding to Australia and Canada and then to all markets later in the year. The core of implementation is making sure your age gate, platform age signals, CMP flow, and the child-directed settings in your ad SDKs do not contradict each other.
How is CMP pricing structured, and what should you evaluate?
App CMP pricing is mostly a subscription based on usage (daily active users, monthly unique visitors, or sessions), with public prices only for smaller tiers and quotes for larger ones; Google's UMP has no separate fee. The right comparison is therefore not the monthly subscription but the annual total with every feature you need turned on at your traffic level, set against the European ad revenue that spend protects or recovers.
As one public example, as of November 2026 Usercentrics lists its app CMP Advanced plan at €49 per month billed annually for up to 500,000 daily active users (averaged across all apps), with a quoted Premium plan above 500,000, and no limit on the number of apps or configurations. Many other major CMPs do not publish prices and sell only on quotes. Because billing units differ by vendor (DAU, monthly unique visitors, sessions), the same game can price out very differently; put your DAU, MAU, monthly sessions, and number of platforms in the RFP so every vendor quotes on the same basis.
After price comes evaluation. From a game studio's perspective, this order works in practice.
Criterion | Why it matters | How to check |
|---|---|---|
Google certification and TCF version | Without certification or a correctly formatted string, European requests fall back to limited ads | Listing on Google's certified CMP list, v2.3 disclosedVendors support, release date of the v2.4 app SDK (against the February 23, 2027 deadline) |
Ad partner coverage | Every ad network in your mediation stack needs to receive the consent signal | Handling of TCF-registered and non-registered vendors (Google AC specification), Google (ID 755) included by default |
Measurement integration | If consent results do not reach your MMP and Firebase, UA optimization signals break | Delayed MMP SDK start integration, consent mode v2 mapping, sample integration code |
Multiple regulations | Europe and the US use different signal systems | GPP generation (US National and state sections), region detection, update cadence for new state laws |
Age and child flows | Children must not see the adult consent flow | Age gate integration, passing child tags such as TFUA, support for platform age signals |
Performance and stability | The consent screen sits on the critical path of first launch | SDK size, delay to first screen, offline and network-failure behavior, incident history |
Screen control and localization | A screen that clashes with the game's tone increases drop-off and refusals | Game engine support (such as Unity), languages, design freedom within TCF policy |
Analytics and testing | You cannot manage consent rates without measuring them | Consent rate reports by region, screen, and version; A/B testing support |
Consent records and audit | You need evidence for regulator inquiries or disputes | Retention period for consent logs, export, data storage region |
Pricing structure | Costs can rise non-linearly with traffic | Billing unit, overage pricing, extra cost per app or platform, contract term |
The first three rows are knockout criteria and the rest are comparison criteria. If a vendor falls short on Google certification, mediation partner coverage, or measurement integration, it is better to drop it even if its price and design are attractive. Normalizing the scorecard the same way you would for an ad network speeds up later decisions; for the format, see the evaluation table in How to Choose a Mobile Advertising Platform for Your Game in 2026: Evaluation Criteria, RFP Questions, and Pilot Design.
What questions belong in a CMP RFP?
The point of a CMP RFP is not to confirm "do you support the TCF?" but to get, in a comparable format, how consent signals are created and how far they travel in your ad stack, your measurement stack, and your operating regions. Questions should be written as "how, when, and on which plan."
Area | Example RFP questions |
|---|---|
Certification and versions | Are you on Google's certified CMP list? Which app SDK version supports the TCF v2.3 disclosedVendors segment, and when will a v2.4-ready SDK ship? Will the move to v2.4 require renewed consent from existing users? |
Ad partners | For each partner in our mediation list, is the signal passed via a TCF vendor ID or the AC specification? What triggers renewed consent when the vendor list changes? |
Measurement | Do you have sample integrations that pass consent results to MMP SDK start and Firebase consent mode values? How are consent changes reflected in measurement SDKs? |
US and other regions | Which GPP sections do you generate? How do you determine user region? How long does it take to update templates when a new state law takes effect? |
Age | Can the consent flow branch on the result of an age gate? Do you support passing child-directed tags to ad SDKs? |
Platforms | Do you officially support the engine we use, such as Unity? Can mobile, PC, and web consent be managed in one account? |
Performance | What is the SDK size and the average delay to first display? What is the default behavior on network failure? |
Analytics and testing | Do you report consent rates by region, screen, and app version? Which plan includes A/B testing? |
Records and data | How long are consent logs retained, and in what format can they be exported? In which region is data stored? |
Pricing | What is the billing unit, and what is the annual total with all required features at our DAU, MAU, and session volume? What are overage rates and contract terms? |
Support | Will you help diagnose Google error codes (for example 1.4, 2.x, 10.1) when they appear in reports? Can you support our time zone? |
Once responses arrive, fix the rows in your own terminology and transcribe each vendor's answer as "included / higher plan / add-on / not supported." Get the v2.4 timeline as a specific date. With a February 23, 2027 deadline, once you factor in your game update cycle and store review times, the real margin is shorter than it looks.
How should you run CMP implementation and QA, and how far can you manage consent rates?
The core of CMP implementation is fixing the order "check consent, then initialize ad SDKs, then start measurement SDKs" in code, and verifying with test devices and Google's reports that the right signals actually go out in each region. Managing consent rates comes after that, and it means improving clarity and timing within what the rules allow, not steering players toward "accept."
Phase | Duration (example) | Tasks | Exit criteria (example) |
|---|---|---|---|
Design | 1 to 2 weeks | Document ad and measurement SDK initialization order, reconcile mediation partners and MMP against the CMP vendor list, decide where the age gate sits, draft copy for legal review | Signal path for every partner documented |
Build | 2 to 3 weeks | Integrate CMP SDK, refresh consent status on every launch, block ad requests before consent, connect MMP and Firebase consent, add a privacy options entry point to settings | No ad or measurement requests leave the device before consent |
QA | 1 to 2 weeks | Use debug geography to reproduce the EEA, UK, Switzerland, regulated US states, and unregulated regions; check TC and GPP strings for accept, reject, partial choice, and later change; check the under-age scenario | Signals match expected values in every scenario |
Staged rollout | 2 to 4 weeks | Release to selected countries and a share of users, check error codes and limited-ad share in Google's Privacy & messaging reports, compare European eCPM and fill rate | Error codes below a pre-set threshold; any drop in European ad revenue is explainable |
Operations | Ongoing | Monthly review of consent rates and error codes, respond to vendor list and TCF version changes, reflect new state laws and age rules | Quarterly review log maintained |
The scenario most often missed in QA is "reject." Everyone tests the accept path, but you need to verify separately that rejected users still receive limited ads correctly, that the MMP behaves properly without consent, and that switching to consent later in settings updates signals immediately. Among Google's error codes, 1.2 (no Purpose 1 consent in the EEA, UK, or Switzerland), 1.4 (disclosedVendors segment missing or malformed), and 10.1 (a request from a GDPR region with no TCF signals) point directly at implementation problems, so check them daily for the first few weeks after launch.
Managing consent rates starts with being clear about the rules. The GDPR defines consent as a freely given, specific, informed, and unambiguous indication of wishes by a clear affirmative action (Article 4(11)), and requires that withdrawing consent be as easy as giving it (Article 7(3)). In the Planet49 judgment (C-673/17), the Court of Justice of the EU held that a pre-ticked checkbox does not constitute valid consent. Hiding the reject button, making only "accept" stand out, or blocking gameplay for players who refuse does not raise your consent rate so much as raise the risk that the consent you collect is invalid.
There is still plenty you can do within the rules. First, timing: rather than showing the form on top of the first loading screen, show it at a stable moment that fits the game's tone, while making sure it completes before any ad request. Second, wording: explaining in plain, local language that ads are what keep the game free makes it easier for players to understand what they are agreeing to. Third, consistency: give accept and reject buttons equal size and placement, and let players change their choice at any time in settings, which builds trust. Fourth, measurement: log consent rates by region and screen version, and change one thing at a time with an A/B test. Most of the data involved here is first-party data that players create inside the game, and building the ability to make operating decisions from in-game behavior data, even when consent rates are not perfect, pays off over the long run. The Android-side shift away from identifier dependence is covered in Privacy Sandbox Is Gone. What That Actually Means for Android Game Marketing.
The same logic applies when choosing UA channels: the consent environment is part of the evaluation. Playio is an Android-based community of 5 million gamers who love games, and it connects games with players whose tastes fit, based on the genre preferences, play history, and in-game behavior data that players generate inside the platform. Because it relies on in-platform engagement data rather than matching external identifiers, the way campaigns run does not shift much as consent signals thin out. The default pricing model is CPI, CPE based on in-game actions such as tutorial completion, level milestones, or playtime goals is also supported, and results are verified through the tracking links and postbacks of the MMP the studio already uses. If a CMP rollout or switch has you re-examining your measurement setup, share one in-game event you would use as the success metric and your target countries, and we can review a small test campaign built around that benchmark together.
More details are available here. (https://playioadsen.oopy.io/bizdeck)
Key takeaways
Serving personalized Google ads in the EEA, UK, and Switzerland requires a Google-certified CMP integrated with the TCF (EEA and UK since January 16, 2024; Switzerland since July 31, 2024); traffic without one is sold only as non-personalized or limited ads. As of November 2026, TCF v2.3 is in force (disclosedVendors mandatory for strings generated on or after March 1, 2026), and the v2.4 deadline for mobile apps is February 23, 2027. Research shows in-app impressions without user tracking sold for 23% less on average, and vendor data shows app consent rates ranging from 64% to over 90% depending on implementation quality. Consent signals must reach not just ad SDKs but also your MMP and Firebase consent mode to keep UA measurement and optimization working. A single title built on Google's stack can start with the free UMP SDK, while studios with multiple titles, multiple platforms, or a need for consent testing should compare third-party CMPs on annual total cost. Use Google certification and TCF version, mediation partner coverage, and measurement integration as knockout criteria, and US GPP, age flows, performance, analytics, records, and pricing as comparison criteria. Implement by fixing the order of consent check, then ad and measurement SDK start; QA the reject scenarios and Google error codes; and roll out in stages. Manage consent rates through timing, wording, equal choices, and testing, not by hiding the option to refuse.
For inquiries about Playio's advertising solutions, reach out at: [email protected]
Sources (for data verification; whether to display them at publication to be decided in review):
Google AdMob Help, Tips on using a CMP with Google publisher products / Google certified CMP requirement (Google-certified CMP integrated with the TCF required for personalized ads from January 16, 2024 in the EEA and UK and July 31, 2024 in Switzerland; non-certified CMP traffic gets non-personalized or limited ads; certified list updated weekly; Google does not check CMPs for full TCF or privacy law compliance; Additional Consent specification supports non-TCF partners; UMP publishers tag under-age requests with TFUA): https://support.google.com/admob/answer/13554116?hl=en
Google AdMob Help, Troubleshooting IAB EU TCF v2.3 implementation (v2.3 mandatory for TC strings generated on or after March 1, 2026; error 1.2 no Purpose 1 consent, 1.4 disclosedVendors missing or omits Google ID 755, 9.1 non-certified CMP gets non-personalized ads, 10.1 GDPR-region request without TCF signals; Google attempts limited ads for many errors): https://support.google.com/admob/answer/9999955?hl=en
Google AdMob Help, Limited ads (personalization disabled; frequency capping, conversion tracking, unique reach measurement disabled; AdMob Campaigns do not serve on limited ad signals; programmatic demand only with programmatic limited ads on): https://support.google.com/admob/answer/10105530?hl=en
IAB Europe, All you need to know about the transition to TCF v2.3, 2025-12-15 (v2.3 released June 19, 2025; transition ends February 28, 2026; strings without disclosedVendors invalid afterward; no need to resurface UI for this change alone): https://iabeurope.eu/all-you-need-to-know-about-the-transition-to-tcf-v2-3/
IAB Europe, TCF Policies v5.0.b and Specifications v2.4: confirmation of the timeline, 2026-07-16 (Specifications v2.4 and GVL published July 23, 2026; deadlines October 23, 2026 for web and February 23, 2027 for mobile apps and CTV; standard texts and illustrations for Features, renamed Special Feature 2): https://iabeurope.eu/wp-content/uploads/TCF_V-CMP_comms_TCFpoliciesV5.0.bAndSpecificationsV2.4ConfirmationOf-theTimeline_160726_IABEurope.pdf
IAB Europe, TCF Policies v5.0.b, 2026-05-29 (policy changes on multi-device consent, presentation of Features, Special Feature 2): https://iabeurope.eu/wp-content/uploads/TCF-Policies-TransparencyConsentFramework_Policies_Version-2026-05-29.5.0.b.docx.pdf
Google for Developers, AdMob Android: Get started with the UMP SDK (requestConsentInfoUpdate on every launch, loadAndShowConsentFormIfRequired, canRequestAds, required privacy options entry point, do not rely on cached consent data): https://developers.google.com/admob/android/privacy
Google for Developers, AdMob Android: U.S. states privacy laws compliance (GPP support, UMP SDK writes the GPP signal, RDP parameter gad_rdp): https://developers.google.com/admob/android/privacy/us-states
Google Ads Help, App attribution partners (capture EEA user consent before sending app conversions to an AAP; conversions without user-level consent may be measured at non-user level via gbraid; minimum SDK versions and delayed SDK start per MMP): https://support.google.com/google-ads/answer/12961402?hl=en
Google Tag Platform, Consent mode for apps (Firebase consent mode; analytics_storage, ad_storage, ad_user_data, ad_personalization; eu_consent_policy setting): https://developers.google.com/tag-platform/security/guides/app-consent
IAB Tech Lab, Global Privacy Platform (protocol carrying US National and state strings, IAB Europe TCF, and IAB Canada TCF): https://iabtechlab.com/gpp/
IAPP, US State Privacy Legislation Tracker (tracker of comprehensive US state privacy laws): https://iapp.org/resources/article/us-state-privacy-legislation-tracker
Laub, Miller, Skiera, The Economic Value of User Tracking for Publishers, arXiv 2303.10906 (revised April 2024; Study 2 covers EU and US mobile in-app traffic in 2023, 10,526 publishers (apps), 218 million impressions; average impression price 23% lower without tracking): https://arxiv.org/abs/2303.10906
Usercentrics, Consent & Revenue: Mobile Apps Report (average app opt-in rate 80% across its CMP customer base, top performers 90%+, unoptimized implementations as low as 64%; 2025 data; vendor source): https://usercentrics.com/resources/consent-revenue-mobile-apps-report/
Usercentrics, Pricing (app CMP Advanced €49 per month billed annually up to 500K average DAU across apps; Premium quoted above 500K; unlimited apps and configurations; 30-day free trial; Google-certified CMP): https://usercentrics.com/pricing/
FTC, 16 CFR Part 312: COPPA Final Rule Amendments (published April 22, 2025; effective June 23, 2025; compliance date April 22, 2026 for most provisions): https://www.ftc.gov/legal-library/browse/federal-register-notices/16-cfr-part-312-coppa-final-rule-amendments
FTC, Children's Online Privacy Protection Rule: A Six-Step Compliance Plan for Your Business (separate verifiable parental consent for third-party disclosures): https://www.ftc.gov/business-guidance/resources/childrens-online-privacy-protection-rule-six-step-compliance-plan-your-business
Android Developers Blog, Google Play Age Signals API, 2026-07-29 (age range signals, shared at parents' choice; available in Brazil, Australia and Canada by mid-August, all markets later in the year): https://android-developers.googleblog.com/2026/07/google-play-age-signals-api-safer-experiences.html
EUR-Lex, Regulation (EU) 2016/679 (GDPR) (Article 4(11) definition of consent; Article 7(3) withdrawal as easy as giving consent): https://eur-lex.europa.eu/eli/reg/2016/679/oj
CURIA, Case C-673/17 Planet49 (pre-ticked checkbox is not valid consent): https://curia.europa.eu/juris/liste.jsf?num=C-673/17
Own calculation: average European ad price index at 64% and 80% consent assuming a 23% discount on non-consented impressions (91.7 vs 95.4, about 4% relative); phase durations and exit criteria (examples): illustrative calculation