Google Ads Makes Customer Match More Precise With IP and Timestamp Data.

IP address and timestamp matching are now available in Customer Match. That means larger audiences, stronger signal, and better targeting from the first-party data you already have. Here’s what it means, what to do, and what to watch out for.

First-party data is supposed to be your competitive moat. The customer emails you collected, the phone numbers from lead forms, the mailing addresses from purchase history, this is the data that doesn’t disappear when a cookie deprecates or a platform changes its targeting rules. It’s yours. You earned it.

The problem most advertisers have quietly lived with: not much of it actually matches.

You upload a Customer Match list with 50,000 emails. Google matches maybe 30,000 ,some emails are old, some are personal addresses that don’t match the Gmail account a user browses with, some have typos from the original form submission. Your 50,000-record list becomes a 30,000-person audience. You paid to acquire 50,000 customers but you can only reach 60% of them with paid search and YouTube.

Google just changed that equation , on 25 September 2026, by adding two new matching identifiers to Customer Match: IP addresses and interaction timestamps.

This isn’t a minor platform update. For any advertiser who takes Customer Match seriously as a targeting and bidding signal, this is the most meaningful expansion of first-party data matching capabilities in years. Here’s the full breakdown of what changed, why it matters strategically, and exactly how to use it without stepping into the privacy compliance trap that comes with it.

---

What Actually Changed: The New Identifiers Explained

Customer Match works by taking first-party customer data like email addresses, phone numbers, mailing addresses, device IDs and matching it against Google’s signed-in user base to build targetable audiences across Search, YouTube, Gmail, and Display.

The match rate, the percentage of your uploaded records that Google can successfully link to a Google account determines the actual size and usefulness of the resulting audience. Historically, email address has been the most reliable identifier. Phone numbers and mailing addresses help but add friction. Device IDs are increasingly unreliable.

Google has now added two new identifiers to the matching process:

IP address. The IP address from which a user interacted with your website or app. Unlike email and phone, which must be hashed before upload (for privacy), IP addresses are uploaded unhashed. Google uses them to expand match coverage connecting Customer Match records to Google accounts that browse from the same IP addresses in ways that email alone can’t.

Interaction timestamp. The date and time of the user’s specific interaction with your business, a purchase, a form submission, a page view. Uploaded alongside the IP address, the timestamp helps Google identify the specific user session, reducing false matches from shared IP environments like offices or households.

Together, these two identifiers give Google’s matching system more signal to connect your customer records to Google users, which means more of your Customer Match list becomes a reachable audience.

One critical technical note: the file format for Customer Match uploads has expanded from six columns to eight. The new columns are “User IP address” and “User Interaction timestamp.” The column headers must use specific English-language naming as specified in Google’s updated documentation. If you’re using automated uploads or API-based Customer Match workflows, the file format change needs to be implemented in your pipeline before the new identifiers have any effect.

---

Why Match Rate Is the New Metric That Drives Downstream

Before the strategic implications, let’s be precise about why match rate matters so much because it’s the mechanism through which everything else flows.

A higher Customer match rate produces:

• Larger usable audiences – More of your customer records map to reachable Google users. A list that previously matched 55% now might match 68%, which at 100,000 records is 13,000 additional people you can now reach with targeted bids, creative, or exclusions.
• More reliable Smart Bidding signals. Smart Bidding uses Customer Match audiences as an input signal for value-based bidding. A larger, more complete audience gives the algorithm a more accurate picture of what high-value customers look like, which improves its ability to bid correctly for similar users in prospecting campaigns.
• More accurate exclusions. One of Customer Match’s most valuable use cases is excluding existing customers from acquisition campaigns so you don’t waste budget on people who’ve already converted. A low match rate means you’re excluding 55% of your customers and accidentally showing acquisition ads to the 45% who aren’t matching. Higher match rate means cleaner exclusion logic and less wasted acquisition spend.
• Stronger similar audiences. Google builds “similar segments” based on Customer Match lists expanding your targeting to users who share characteristics with your matched customers. A richer, larger matched audience produces better similar segments. A thin matched audience produces a similar segment that approximates your customer base poorly.

The IP address and timestamp addition directly improves the top of this chain match rate and the improvements cascade through every downstream use case.

---

The Five Strategic Uses of Customer Match (And How Each Gets Better With This Update)

Use 1: Bid Adjustment for High-Value Existing Customers

The most direct Customer Match use case: upload your customer list, create an audience, and apply a positive bid adjustment in Search campaigns for users on that list. When an existing customer searches for your category, you bid more aggressively, because you already know they’re worth more than an unknown prospect.

How the update improves it: Higher match rate means more of your existing customers are in the audience. Previously, the 40-45% of your customer list that didn’t match was being bid on at standard rates, no adjustment, no recognition of their existing relationship. IP and timestamp matching closes that gap. More customers get the bid treatment they deserve.

The implementation step: After implementing the new identifier columns in your upload file, compare your match rate before and after. The delta is the additional customers now covered by your bid adjustment. For accounts spending significant budget on branded and category terms, this delta has direct CPA and ROAS implications.

---

Use 2: Excluding Converters From Acquisition Campaigns

This is the use case most advertisers use Customer Match for and the one where low match rate causes the most invisible waste. Unmatched existing customers receive acquisition ads. They click at a higher-than-average rate (because they recognise your brand) and either don’t convert again (because they don’t need to) or convert in a way that artificially inflates your acquisition campaign’s numbers.

How the update improves it: Every additional customer that now matches via IP address or timestamp is a customer successfully excluded from acquisition campaigns. The budget previously wasted on retargeting existing customers through acquisition campaigns shifts to genuinely new prospects.

The implementation step: After the update, run a 30-day comparison of your acquisition campaign’s CPA before and after the expanded exclusion list is active. If the additional matched customers were clicking acquisition ads before, CPA should improve because you’re spending less budget on clicks from existing customers that weren’t converting.

---

Use 3: Re-engagement Campaigns for Lapsed Customers

Customer Match isn’t just for exclusion and bid adjustment. It’s a re-engagement channel. A list of customers who purchased 12+ months ago but haven’t returned is a segment you can actively target with win-back messaging, offers, and creative that speaks to their previous relationship with your brand.

How the update improves it: A timestamp-enriched Customer Match list can be segmented by regency of interaction. Customers who interacted six months ago go into one re-engagement segment. Customers who interacted two years ago go into another. The bid and creative strategy for each should be different recent lapsers respond to different messaging than long-lapsed customers.

The implementation step: When uploading re-engagement lists, include the interaction timestamp alongside the IP address. This lets you build multiple re-engagement audiences with different time windows and test whether regency of last interaction predicts re-engagement likelihood and it usually does.

---

Use 4: Lookalike Prospecting Through Similar Segments

Google builds similar segments from Customer Match lists audiences that share behavioral and demographic characteristics with your matched customers. These are your highest-quality prospecting audiences because they’re based on the actual characteristics of people who’ve already bought from you.

How the update improves it: Similar segments built on a 55% match rate audience are built on a partial picture of your customer base. The customers who weren’t matching may be systematically different from those who were, perhaps they’re older users with non-Gmail accounts, or they’re business purchasers with work emails, or they have different browsing habits. Your similar segment was missing those groups. Higher match rate means a more representative customer seed, which means a more accurate similar segment.

The implementation step: After expanding your match rate, rebuild your similar segments from the updated Customer Match audiences and run a controlled A/B test comparing the performance of similar segments built on old vs. new matched audiences. The difference in conversion rate should quantify the value of the match rate improvement.

---

Use 5: Audience Signals for Performance Max

Performance Max uses audience signals including Customer Match lists as input for its targeting decisions across all Google surfaces. Better Customer Match audiences mean better PMax targeting signals, which means the algorithm finds high-value prospects more efficiently from the start rather than spending budget on the learning phase.

How the update improves it: Every Customer Match audience used as a PMax signal gets more comprehensive with higher match rate. The algorithm sees a more complete picture of who your customers are. Its initial targeting is more accurate. The learning phase is shorter and less expensive.

The implementation step: After expanding Customer Match match rate, review your PMax audience signal configuration and ensure your updated Customer Match lists are included. If you haven’t been using Customer Match as a PMax signal, this is the moment to add it and the expanded match rate makes it significantly more valuable than it was.

---

The Privacy Compliance Conversation You Can’t Skip

Here’s where most coverage of this update stops too soon. The match rate improvement and strategic upside are real but they come with compliance requirements that need to be handled before the feature is switched on, not after.

The unhashed upload requirement is the biggest operational change. Email addresses and phone numbers in Customer Match must be SHA-256 hashed before upload. IP addresses and timestamps must be uploaded unhashed. This means your data pipeline needs to handle two different treatments for different identifier types in the same upload file. If you’re using an automated Customer Match upload workflow, this needs to be built into the pipeline correctly partial hashing or full hashing of unhashed fields will break the matching.

The geographic exclusion is non-negotiable. IP address and timestamp matching is explicitly unavailable for users in the European Economic Area, the United Kingdom, and Switzerland. This isn’t a preference setting, it’s a compliance boundary. Before enabling the new identifiers, your upload workflow needs to filter out any customer records associated with EEA, UK, or Swiss locations. Uploading those records with IP addresses in scope is a compliance violation, not just a platform error.

Consent and disclosure requirements apply. Google’s updated documentation specifies that data collection practices must include appropriate disclosures and consent for the use of IP addresses in advertising matching. If your privacy policy and cookie consent framework don’t currently cover IP address use for ad targeting purposes, they need to be updated before you begin collecting this data for Customer Match uploads. This is a legal question as much as a marketing one, loop in your legal or compliance team before implementation.

The language shift in Google’s documentation is worth noting. Google has quietly changed language across several Customer Match help pages, now describing customer information as data advertisers “collected” rather than data they “shared.” This shift signals a tightening of Google’s own positioning around first-party data responsibility, the advertiser is responsible for collection practices, consent, and appropriate use. The platform is the mechanism, not the compliance backstop.

---

The Implementation Checklist: What to Do Before Your Next Upload

If you want to capture the match rate improvements from the new identifiers, here’s the exact sequence to follow:

Step 1: Audit your data collection infrastructure. Confirm that your website and app capture IP addresses at the point of user interaction and store them alongside the interaction timestamp. If they don’t, this is a development task that needs to be completed before any Customer Match workflow changes make sense.

Step 2: Review your privacy policy and consent framework. Confirm that your privacy policy covers IP address collection and use for advertising matching purposes. If it doesn’t, update it. Confirm your consent framework reflects this use. For any customers whose data was collected under frameworks that didn’t include this disclosure, those records should not be included in IP-address-enriched uploads until re-consent is obtained.

Step 3: Build your geographic filtering logic. Add filtering to exclude all records associated with EEA, UK, and Swiss locations from any upload that includes IP address and timestamp columns. Automate this filtering so it can’t be accidentally bypassed in future uploads.

Step 4: Update your Customer Match upload file format. The new eight-column format adds “User IP address” and “User Interaction timestamp” to the existing six-column structure. Update your upload template and any automated pipelines to use the exact English-language column headers specified in Google’s updated documentation.

Step 5: Run a test upload with a small segment first. Before running the new format against your full customer database, upload a small test segment and check the resulting match rate against the same segment’s historical match rate. The improvement should be visible in audience statistics within 24-48 hours.

Step 6: Monitor and document the match rate delta. After full implementation, track match rate by list across a 30-day window. Document the improvement. This becomes the business case for maintaining clean, comprehensive first-party data collection because you can now quantify what each additional percentage point of match rate is worth in audience reach and downstream campaign performance.

---

The First-Party Data Principle This Update Reinforces

Zoom out from the specific identifiers and the implementation steps and the principle underneath this update is clear: the quality and completeness of your first-party data is now a direct competitive variable in your Google Ads performance.

Two advertisers in the same category with similar budgets and similar strategies will get different results from Customer Match based purely on the richness of their first-party data. The advertiser with 70% match rate reaches 70% of their customer base with precision targeting. The advertiser with 45% match rate reaches 45%. That gap compounds across bid adjustments, exclusions, re-engagement campaigns, similar segments, and PMax signals.

Every investment in first-party data quality, clean collection infrastructure, appropriate consent frameworks, comprehensive CRM enrichment, regular data hygiene now has a more direct and measurable line to paid media performance than it did before this update.

The brands treating Customer Match as an afterthought are competing at a systematic disadvantage against the ones that have built first-party data collection into their marketing infrastructure as a strategic priority. This update widens that gap.

---

The Bottom Line

Google’s addition of IP address and timestamp matching to Customer Match is a genuine improvement to first-party data utility in Google Ads. For advertisers who implement it correctly with the right data collection infrastructure, appropriate consent practices, and geographic filtering in place and the match rate improvement feeds directly into better audience reach, more accurate exclusions, stronger Smart Bidding signals, and higher-quality similar segments.

The compliance requirements are real and non-negotiable. The EEA, UK, and Switzerland exclusion is a legal boundary, not a targeting choice. The unhashed upload requirement changes data pipeline handling. The consent and disclosure requirements need to be in place before collection starts.

Get the compliance framework right first. Then implement the expanded identifier columns. Then watch your match rate improve and trace that improvement through every downstream audience and campaign that depends on it.

First-party data has always been theoretically valuable. Google just made it more operationally powerful. The question is whether your infrastructure is set up to capture that power while competitors are already running with match rates.

---

If You liked our content or found it helpful, Comment Below! Or Just Share your valuable reviews here.