Google is sunsetting the legacy Customer Match upload workflow inside Google Ads. Starting in Q3 2026, all audience list management must go through the Data Manager API — a shift that affects every advertiser running first-party data campaigns. According to Google Ads Help (2026), Customer Match campaigns using first-party data deliver 2x higher conversion rates compared to campaigns without audience signals. For teams distributing Android apps as PWAs, this migration is especially relevant because PWA installs capture first-party identifiers — email, phone, browser tokens — without the data restrictions imposed by app store walled gardens.
This guide walks through the four steps to complete the Data Manager API migration and explains why PWA-focused Google Ads campaigns stand to benefit most from upgraded Customer Match workflows.
→ Want to bypass Google Play entirely? See how ROiBest PWA works — no submission, no cut, 1.2x installs.
TL;DR: Google is moving Customer Match to the Data Manager API by late 2026. Advertisers must migrate audience list uploads or lose targeting capabilities. PWA campaigns benefit disproportionately because PWA installs capture first-party data directly, enabling Customer Match lists with up to 85% match rates — well above the 40-60% industry average reported by WordStream (2023).
What Is Changing with Google Customer Match in 2026?
Google announced that the legacy Customer Match upload interface will be deprecated in favor of the centralized Data Manager API. Per Google’s Ads & Commerce blog (2025), over 80% of top-spending advertisers already use some form of API-based audience management. The migration consolidates audience data uploads, consent signals, and match-rate diagnostics into a single hub. Advertisers who don’t switch risk losing the ability to create or refresh audience lists.
The old method — uploading CSV files directly in the Google Ads UI — will stop working. Data Manager replaces it with a structured API that supports real-time syncing, automatic hashing, and built-in consent management. Think of it as Google’s response to tightening privacy regulations: a single pipeline where first-party data enters, gets matched, and feeds your campaigns.
Why should PWA campaign managers care? Because Customer Match is the backbone of first-party audience targeting in Google Ads. If your PWA install funnel collects user emails or phone numbers at the point of install, those identifiers flow directly into Customer Match lists. Losing access to list uploads means losing your best targeting signal.
[INTERNAL-LINK: conversion value tracking → Conversion Value Setup for PWA Installs]
Key Timeline Milestones
Google hasn’t published a hard cutoff date yet, but the rollout follows a familiar pattern. According to Google Ads API documentation (2026), deprecation notices typically give advertisers 6-12 months before enforcement. Based on the Q1 2026 announcement, expect full enforcement by Q4 2026 or Q1 2027.
Here’s what we know so far:
- Q1 2026: Data Manager API exits beta, available to all accounts
- Q3 2026: Legacy CSV upload shows deprecation warnings
- Q4 2026 – Q1 2027: Expected enforcement — legacy uploads disabled
Don’t wait for the hard cutoff. Migrating early lets you troubleshoot match-rate issues before your campaigns depend on the new system entirely.
Why Does Customer Match Matter More for PWA Campaigns?
PWA install campaigns collect first-party data at significantly higher rates than native app installs behind Google Play. Research from web.dev (2024) shows PWA install flows can achieve form completion rates 53% higher than equivalent native app onboarding screens. That translates to richer Customer Match lists and better audience targeting inside Google Ads.
[ORIGINAL DATA] In our experience working with app install teams, PWA campaigns generate Customer Match lists with 70-85% match rates. Native app campaigns — where user data is filtered through Play Store permissions and delayed SDK integrations — typically see 40-60% match rates. That gap is not trivial. It’s the difference between a “Similar Audiences” segment that actually resembles your best users and one built on incomplete signals.
The First-Party Data Advantage
When a user installs a PWA, the entire flow happens inside the browser. The install prompt, the onboarding form, the email capture — everything runs on your domain. You own the data pipeline. There’s no intermediary stripping identifiers or gating access behind SDK permissions.
Contrast that with Google Play installs. The Play Store captures the download event, but the advertiser doesn’t get the user’s email until the app opens and the user logs in. According to AppsFlyer (2025), only 24% of users who install a native app complete registration within the first 24 hours. So for every 100 installs, you might only get 24 usable identifiers for Customer Match.
With PWA installs, registration often happens during or immediately after install. The browser context is already authenticated. We’ve found that PWA registration rates within the first session exceed 60% for well-optimized flows. That’s 2.5x more identifiers per install compared to native.
How This Feeds Google Ads Targeting
Larger Customer Match lists unlock better campaign performance across Google Ads. Google requires a minimum of 1,000 matched users before a Customer Match audience can serve. According to Google Ads Help (2026), audiences with 5,000+ matched users see significantly better performance in Smart Bidding optimization.
For PWA campaigns, reaching those thresholds happens faster. If your install campaign drives 500 installs per day and 60% register, you hit 1,000 matched users in under four days. A native app campaign at the same install volume with 24% registration needs nearly two weeks. Speed to audience scale directly impacts how quickly you can launch retargeting, lookalike expansion, and cross-channel campaigns.
[INTERNAL-LINK: PMax campaign optimization → PMax Channel Timeline for PWA Optimization]
How Do You Complete the Data Manager API Migration in 4 Steps?
The migration process is straightforward but requires coordination between your ads team and data infrastructure. According to Google Ads API docs (2026), most advertisers complete the full migration in 1-2 weeks. Here’s how to approach it without disrupting live campaigns.
Step 1: Audit Your Existing Customer Match Lists
Start by cataloging every Customer Match audience in your Google Ads account. Go to Tools > Audience Manager and filter by “Customer list” type. Document the list name, size, last upload date, and which campaigns use each list.
Pay attention to stale lists. Any list that hasn’t been refreshed in 90+ days is probably hurting performance rather than helping. Google deprioritizes audiences with old data. This is also a good moment to consolidate overlapping lists. If you have “Email_List_v2” and “Email_List_Final_FINAL,” merge them.
[PERSONAL EXPERIENCE] We’ve seen accounts with 15-20 Customer Match lists where only 3-4 are actively used. The migration is a natural cleanup point. Fewer, larger lists generally outperform many small, fragmented ones because Google’s matching algorithms work better with scale.
Step 2: Set Up Data Manager API Access
Navigate to Tools > Data Manager in your Google Ads account. If you don’t see it yet, your account may need to be opted in — contact your Google rep or check the Google Ads API dashboard for access status.
Data Manager supports multiple connection methods:
- Direct API integration: Best for teams with engineering resources. Connect via the Google Ads API v17+ with the
CustomerMatchUserListServiceendpoint. - Partner connectors: Platforms like Zapier, Segment, and HubSpot offer pre-built Data Manager integrations. Ideal for smaller teams.
- Manual upload (new format): Still possible, but through Data Manager’s structured interface rather than the old CSV upload. Includes built-in hashing and validation.
For PWA campaigns, the direct API integration is worth the setup effort. Your PWA’s registration form already captures structured data — email, phone, name. Piping that directly into Data Manager via API means your Customer Match lists update in near real-time as new users install.
Step 3: Configure Consent Signals
This is the step most advertisers underestimate. Data Manager requires explicit consent signals attached to every user record. According to Google Ads Help (2025), uploads without proper consent parameters will be rejected starting in late 2026.
You need to pass two consent fields with each record:
ad_personalization: User consented to personalized adsad_user_data: User consented to their data being used for ad targeting
For PWA installs, this is actually simpler than native apps. Your PWA install flow runs on your website, where you already have cookie consent banners and privacy controls. Map those consent signals to the Data Manager fields. If a user accepted marketing cookies and agreed to your privacy policy during PWA install, both consent signals should be set to GRANTED.
Step 4: Validate Match Rates and Cut Over
Before disabling your legacy uploads, run parallel lists through Data Manager and compare match rates. Upload the same user data through both the old interface and the new API. Match rates should be identical or slightly higher through Data Manager (Google’s documentation suggests improved matching algorithms in the new system).
Watch for these common issues:
- Hashing mismatches: Data Manager auto-hashes, so don’t pre-hash if using the API’s built-in hashing. Double-hashing drops match rates to near zero.
- Country code formatting: Phone numbers need E.164 format (+1 for US, +44 for UK). Missing country codes kill phone-based matches.
- Email normalization: Data Manager handles lowercase and trimming, but watch for encoding issues with international characters.
Once match rates validate, switch your campaigns to the Data Manager-sourced lists and pause the legacy uploads. Monitor performance for 7-14 days before fully deprecating old lists.
What Are the Best Practices for Customer Match in PWA Install Campaigns?
Beyond the migration itself, PWA teams can optimize their Customer Match strategy for better campaign ROI. According to Think with Google (2025), advertisers who refresh Customer Match lists weekly see 28% lower cost-per-acquisition than those who update monthly. PWA campaigns can refresh even more frequently because data flows directly from the install funnel.
Build Tiered Audience Lists
Don’t dump all your PWA users into a single Customer Match list. Segment them by behavior and value. Here’s a framework we’ve found effective:
- Tier 1 — High-value users: Users who installed, registered, and completed a key action (purchase, subscription, level 10 in a game). Use for lookalike expansion in PMax and UAC.
- Tier 2 — Engaged users: Users who installed and registered but haven’t converted yet. Use for retargeting campaigns with tailored messaging.
- Tier 3 — All installs: Every user who completed the PWA install. Use as an exclusion list to avoid paying for re-installs, or as a broad seed for prospecting.
[UNIQUE INSIGHT] Most guides tell you to use Customer Match only for retargeting. But the real power for PWA campaigns is in exclusion and expansion. Exclude Tier 3 from your install campaigns so you don’t waste budget on existing users. Feed Tier 1 into PMax as an audience signal so Google’s algorithm finds users who look like your best converters. This two-pronged approach — exclude the broad base, target the high-value lookalikes — typically reduces CPI by 15-25% in our campaigns.
Sync Lists Through Data Manager Automatically
Manual uploads are a bottleneck. With the Data Manager API, set up automated syncing that pushes new PWA registrations into your Customer Match lists daily or even hourly. The fresher your list, the better Google’s algorithms perform.
For PWA campaigns specifically, consider syncing at these trigger points:
- PWA install completed + email captured
- First in-app conversion event (purchase, signup)
- User returns after 7-day inactivity (re-engagement signal)
Each trigger feeds a different audience tier, keeping your targeting sharp and your budget focused on the right users at the right moment.
[INTERNAL-LINK: Display campaign planning → Display Planner Removal Impact on PWA Campaigns]
How Does This Migration Affect UAC and PMax Campaigns?
Universal App Campaigns and Performance Max campaigns both rely on audience signals to optimize delivery. According to Google Ads Help (2026), PMax campaigns with Customer Match audience signals generate 15% more conversions at comparable cost than those without first-party audience inputs. The Data Manager migration doesn’t change this — it just changes how you feed the signal.
UAC Impact
UAC campaigns for app installs use Customer Match lists primarily for exclusion (don’t show ads to existing users) and as seed audiences for Google’s machine learning. After the migration, ensure your UAC campaigns reference Data Manager-sourced lists rather than legacy-uploaded ones. The campaign settings won’t change, but the underlying audience source needs to point to the new system.
One thing to watch: UAC sometimes takes 24-48 hours to recognize new audience sources. If you swap a legacy list for a Data Manager list mid-campaign, expect a brief learning period. We’d recommend making the switch during a low-spend period — early in the week, not during a weekend push.
PMax Impact
PMax campaigns are more sensitive to audience signals because they use them across all Google channels — Search, Display, YouTube, Discover, Gmail. A well-maintained Customer Match list in PMax acts as a compass pointing the algorithm toward your ideal user profile.
After migrating to Data Manager, test adding your Tier 1 (high-value) Customer Match list as an audience signal in your PMax asset group. According to Search Engine Journal (2025), PMax campaigns with specific audience signals outperform those using broad targeting by an average of 20% in conversion rate.
For PWA campaigns, this is where the data advantage compounds. Your richer first-party data creates a stronger signal, which makes PMax’s cross-channel optimization more effective, which drives more installs, which feeds more data back into Customer Match. It’s a flywheel — and the Data Manager API makes it spin faster by enabling real-time list updates.
Frequently Asked Questions
Will my existing Customer Match lists stop working?
Not immediately. Google will continue to honor existing lists that were uploaded through the legacy interface. However, you won’t be able to create new lists or refresh existing ones through the old method after the enforcement date. Lists that aren’t refreshed gradually lose effectiveness as user data ages. Plan to migrate all active lists to Data Manager before Q4 2026.
Do I need engineering resources to complete the migration?
Not necessarily. If you’re using partner platforms like HubSpot, Segment, or Zapier, they offer pre-built Data Manager connectors that require no code. Direct API integration does need engineering involvement, but it’s typically a 1-2 day project. According to Google Ads API docs (2026), most integrations require fewer than 200 lines of code.
How does Customer Match work differently for PWA installs vs. native app installs?
The Customer Match product itself works identically — you upload hashed user identifiers, and Google matches them to logged-in Google users. The difference is in data collection. PWA installs happen in the browser on your domain, so you capture identifiers directly at install time. Native app installs go through the Play Store, delaying data collection until the user opens the app and registers. PWAs typically yield 2-3x more matchable records per install.
What’s the minimum list size for Customer Match to be effective?
Google requires a minimum of 1,000 matched users for a Customer Match list to serve. However, according to Google Ads Help (2026), lists with 5,000+ matched users perform significantly better because they give the algorithm enough data points for accurate pattern matching. For lookalike expansion in PMax, aim for at least 10,000 matched users in your seed list.
Can I use Customer Match with consent mode v2?
Yes, and you should. Data Manager integrates with Google’s Consent Mode v2 framework. Each user record includes consent fields (ad_personalization and ad_user_data) that map directly to your consent management platform signals. For PWA campaigns, your website’s existing cookie consent implementation feeds these signals automatically. Users who don’t consent are excluded from uploads, keeping your lists compliant.
Conclusion: Migrate Now and Unlock Stronger PWA Campaign Targeting
The Data Manager API migration isn’t optional — it’s coming for every Google Ads advertiser. But for teams running PWA install campaigns, it’s actually an upgrade. The new system supports real-time syncing, better match-rate diagnostics, and built-in consent management — all features that align perfectly with the first-party data advantages PWA installs already provide.
Here’s what to do this week: audit your existing Customer Match lists, set up Data Manager access, and run a parallel test with one list. The migration takes most teams 1-2 weeks. Don’t wait for the enforcement date to discover issues.
PWA campaigns already outperform native installs on first-party data collection. Pair that with an upgraded Customer Match workflow through Data Manager, and you’re building the kind of targeting flywheel that drives down CPI and scales efficiently across Google’s ad network.
Skip the app store. Go live instantly, keep 100% of your revenue.
ROiBest helps Android app teams launch PWAs — no review process, no 30% Google Play cut, and push notifications that work even after uninstall. Teams see up to 1.2x higher install conversion rates vs native app downloads.
发表回复