Google Customer Match Data Manager Migration: 4 Steps for PWA Advertisers in 2026

→ Want to bypass Google Play entirely? See how ROiBest PWA works — no submission, no cut, 1.2x installs.

Google Customer Match Is Moving to Data Manager — What Advertisers Need to Know in 2026

If you run Google Ads campaigns that rely on Customer Match audiences, the migration to Data Manager API is no longer optional. Google has been steadily deprecating legacy Customer Match upload methods throughout 2025 and into 2026, and the window for a smooth transition is closing fast.

For advertisers running PWA install campaigns through UAC or Performance Max, this shift carries extra weight. PWA-based distribution channels generate first-party data — email captures at install, push notification opt-ins, direct engagement signals — that feeds directly into Customer Match audiences. If your data pipeline breaks during this migration, your best-performing audience segments go dark.

This guide walks through exactly what is changing, the 4-step migration process, and why teams distributing apps via PWA have a structural advantage in the new Customer Match ecosystem.

What Is Changing with Customer Match and Data Manager

Google Ads audience targeting with first-party data

Google Customer Match has been a cornerstone of first-party data targeting since its launch. Advertisers upload hashed customer lists — emails, phone numbers, mailing addresses — and Google matches them against signed-in users across Search, YouTube, Gmail, and Display.

The change in 2026 is architectural. Google is consolidating all first-party data operations under the Data Manager framework within Google Ads. This means:

Legacy API endpoints for Customer Match list uploads are being deprecated. The older AdWords API methods and even some Google Ads API v14 endpoints are scheduled for sunset.
Data Manager becomes the single interface for connecting, transforming, and activating first-party data — whether that data comes from a CRM, a website, or a PWA.
Audience refresh cadence is now tied to Data Manager connectors. Instead of manual batch uploads, Google is pushing advertisers toward automated, scheduled data syncs through Data Manager’s connector framework.
Match rates are expected to improve because Data Manager applies enhanced matching logic, including support for multiple identifiers per user record.

According to Google’s own advertiser communications, accounts that migrated to Data Manager during the 2025 beta saw an average 15-20% improvement in match rates compared to legacy CSV uploads. That translates directly into larger addressable audiences and lower CPAs for campaigns targeting Customer Match segments.

For teams running Google Ads PWA install campaigns, this migration is particularly relevant. PWA install flows capture verified email addresses and push notification permissions at the moment of engagement — data that is inherently cleaner and more complete than what you get from fragmented app store install funnels.

The 4-Step Migration Process for Google Ads Advertisers

Whether you manage a single account or an MCC with dozens of sub-accounts, the migration follows four stages. Rushing through any of them creates risk — broken audiences, lost match coverage, or compliance gaps that could trigger account-level issues.

Step 1: Audit Your Current Customer Match Data Sources

Before touching Data Manager, you need a complete inventory of how first-party data currently flows into your Google Ads account.

Map every Customer Match list you are actively using. For each list, document:

The data source (CRM export, website form, PWA install event, offline conversion import)
The upload method (manual CSV, Google Ads API, third-party connector like Zapier or Segment)
The refresh frequency (daily, weekly, ad-hoc)
The identifier types included (email, phone, address, mobile device ID)

Pay special attention to lists that are connected to active campaigns. Google’s migration documentation warns that lists uploaded via deprecated endpoints will stop refreshing once the legacy methods are fully sunset — meaning your audience shrinks with every passing day as users churn out of the match pool.

Teams using PWA distribution should audit their install-event data pipeline separately. PWA installs typically capture email at the point of install (since there is no app store intermediary handling the account), giving you a direct, consented first-party identifier. Confirm that this data is flowing into your Customer Match lists and note the current upload mechanism.

Step 2: Set Up Data Manager Connectors

Data Manager lives inside the Google Ads interface under Tools > Data Manager. The setup process involves creating connectors — integrations that pull data from your sources into Google’s system.

Google supports native connectors for major platforms (Salesforce, HubSpot, Shopify, BigQuery, Google Sheets, and more). For custom data sources — including PWA backend databases — you will use the Google Ads API Data Manager endpoints or connect through a middleware like Google Cloud Dataflow.

Key decisions at this stage:

Choose your sync frequency. Data Manager supports real-time, daily, and weekly sync options depending on the connector type. For PWA install campaigns where users convert quickly, daily or real-time sync prevents audience staleness.
Configure enhanced matching. Data Manager allows you to map multiple identifiers per user record. If your PWA captures both email and phone number at install, map both fields — this can push match rates above 60%, compared to the 30-45% typical of email-only uploads.
Set consent flags correctly. Under Google’s updated consent framework (aligned with DMA requirements in the EU and evolving US state privacy laws), each data record must carry a consent signal. PWA install flows have an advantage here: you control the consent UX entirely, with no app store intermediary obscuring the consent chain.

Google’s internal data shows that advertisers using Data Manager connectors with enhanced matching see match rates averaging 52%, versus 38% for single-identifier legacy uploads. That 14-point gap represents a significant expansion of your targetable audience.

Step 3: Run Parallel Audiences During the Transition

Do not cut over from legacy uploads to Data Manager in a single move. Instead, run both systems in parallel for at least 2-4 weeks.

Create new Customer Match audiences powered by Data Manager connectors alongside your existing legacy-uploaded lists. Apply both audience types to your campaigns as observation audiences first, then compare:

Audience size (Data Manager lists should be equal or larger due to improved matching)
Match rate reported in the audience manager
Campaign performance metrics (CTR, conversion rate, CPA) when targeting each audience

This parallel period also serves as a safety net. If something is misconfigured in your Data Manager connector — wrong field mapping, broken consent flags, sync failures — your legacy audiences continue to serve while you troubleshoot.

For Google Ads PWA install campaigns running in 2026, the parallel testing phase is especially valuable. PWA install audiences tend to be high-intent (these users actively chose to install without an app store nudge), so even small improvements in match coverage can meaningfully move campaign ROAS.

Step 4: Deprecate Legacy Uploads and Optimize

Once you have confirmed that Data Manager audiences match or exceed your legacy list performance, sunset the old upload methods.

Disable or archive legacy Customer Match lists that are now replicated in Data Manager.
Update any automated scripts or third-party integrations that were pushing data via deprecated API endpoints.
Set up monitoring for Data Manager sync health — Google provides sync status dashboards and error logs within Data Manager. Build alerts for sync failures so you catch issues before your audiences go stale.
Review audience refresh cadence quarterly. As your PWA user base grows, you may need to move from daily to more frequent syncs to keep Customer Match audiences current.

Advertisers who completed this migration during early 2025 reported that the full process — from audit to legacy deprecation — took 3-6 weeks for single accounts and 8-12 weeks for large MCCs. Do not wait until the legacy endpoints are fully shut off to begin.

Why PWA First-Party Data Strengthens Customer Match Audiences

The migration to Data Manager is a technical necessity, but it also highlights a strategic reality: the quality of your first-party data determines the ceiling of your Customer Match performance.

PWA distribution creates structurally cleaner first-party data compared to traditional app store installs, for several reasons:

Direct Email Capture at Install

When a user installs a PWA, the install flow is controlled entirely by the advertiser. There is no Google Play account layer sitting between you and the user. This means you can capture a verified email address — the primary Customer Match identifier — at the exact moment of highest intent.

App store installs, by contrast, route through Google Play’s account system. The user’s Play Store email may differ from their primary email, and you often do not capture it directly until the user registers inside your app — a step that many users skip or delay.

Push Notification Opt-In as a Consent Signal

PWA push notification permission is a clear, browser-mediated consent event. When a user grants push permission, you have an explicit, timestamped consent signal that satisfies Google’s enhanced consent requirements for Customer Match.

This is important because Data Manager now requires consent metadata alongside user identifiers. PWA installs produce this consent trail natively, whereas app installs often require additional in-app consent flows that introduce friction and reduce opt-in rates.

Industry benchmarks suggest that PWA push opt-in rates range from 40-60%, compared to native app notification opt-in rates of 35-50% (post-iOS ATT, Android 13+ changes). That higher opt-in rate means a larger share of your PWA users can be included in Customer Match with full consent compliance.

No Platform-Mediated Data Loss

With app store distribution, several data friction points exist: the Play Store handles the install attribution, the install referrer may be stripped or delayed, and the user’s identity is mediated by Google Play Services. Each of these layers can introduce data loss or latency.

PWA installs remove these intermediaries. The install event fires directly in your analytics, the user’s identity is captured by your own authentication system, and there is no platform taking a data toll between your ads and your audience lists.

For advertisers spending significant budget on cross-platform campaigns including Google Ads and other channels, this data cleanliness compounds. The same first-party identifiers captured via PWA can feed Customer Match on Google, Custom Audiences on Meta, and email marketing systems — creating a unified first-party data asset.

Practical Steps for Google Ads PWA Campaign Teams

If you are running or planning PWA install campaigns through Google Ads (UAC or Performance Max), here is how to align your Customer Match strategy with the Data Manager migration:

1. Instrument Your PWA Install Funnel for Customer Match

Ensure your PWA captures the identifiers that Data Manager needs at the right moments:

Email capture at install or first session (required for Customer Match)
Phone number if applicable to your business (improves match rate by 10-15% when combined with email)
Push notification consent with timestamp (feeds into consent metadata for Data Manager)

Store these identifiers in a structured format that your Data Manager connector can ingest — typically a database table or BigQuery dataset with columns for each identifier type plus consent flags.

2. Build a Dedicated Data Manager Connector for PWA Data

If your PWA backend stores user data in BigQuery (common for teams using Firebase or Google Analytics 4), use Data Manager’s native BigQuery connector. This eliminates the need for intermediate exports and supports automated, scheduled syncs.

For other backend architectures, use the Google Ads API Data Manager endpoints to push data programmatically, or route through Google Sheets as a lightweight connector option for smaller-scale operations.

3. Segment Your PWA Audiences in Customer Match

Do not dump all PWA users into a single Customer Match list. Segment by:

Install recency (users who installed in the last 7/30/90 days)
Engagement level (users who opted into push vs. those who did not)
Conversion status (users who completed a target action vs. install-only users)

These segments allow you to build differentiated bidding strategies — bidding higher for lookalikes of your most engaged PWA users, and using exclusion lists to avoid spending on users who already converted.

4. Monitor Match Rates and Optimize Iteratively

After connecting your PWA data through Data Manager, check your match rates weekly for the first month. If match rates are below 40%, investigate:

Are email addresses being captured in a clean, un-hashed format before hashing for upload?
Are you including secondary identifiers (phone, address) where available?
Is the consent metadata properly formatted per Google’s specifications?

Teams that optimize their PWA data pipeline for Customer Match typically see match rates stabilize in the 50-65% range — significantly above the platform average of 38-45% — because PWA captures tend to use primary, actively-used email addresses rather than throwaway accounts.

Timeline and What Happens If You Do Not Migrate

Google has not published a hard cutoff date for all legacy Customer Match upload methods, but the trajectory is clear:

Q1 2026: Several older API versions (v14 and below) lost Customer Match upload support.
Q2-Q3 2026: Data Manager is positioned as the primary interface, with legacy methods receiving no further updates or support.
Late 2026 and beyond: Full deprecation of legacy upload paths is expected, with Data Manager as the sole method.

Advertisers who delay risk sudden audience list attrition — your Customer Match lists stop refreshing, audience sizes shrink, and campaigns relying on these audiences see performance degrade seemingly overnight.

The migration itself is not technically difficult, but it requires careful planning and testing. Start now, run parallel audiences, and confirm everything works before the legacy safety net disappears.

Key Takeaways

Customer Match is migrating to Data Manager API — legacy upload methods are being deprecated throughout 2026.
The 4-step process (audit, set up connectors, run parallel, deprecate legacy) takes 3-12 weeks depending on account complexity.
Data Manager improves match rates by 15-20% on average through enhanced matching and multi-identifier support.
PWA distribution generates cleaner first-party data for Customer Match — direct email capture, native consent signals, and no platform-mediated data loss.
PWA-sourced Customer Match audiences typically achieve 50-65% match rates, well above the 38-45% platform average.
Do not wait — start the migration now to avoid performance disruption when legacy endpoints are fully sunset.

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.

→ Get Started Free