Google Ads Now Matches Customers by IP Address: What Ecommerce Brands Must Do Before October

On September 25, 2026, Google Ads announced that Customer Match now accepts IP addresses and interaction timestamps as new matching signals. For ecommerce brands running retargeting and exclusion campaigns, this expands your Customer Match audience coverage to site visitors who never submitted a form, and Google's own research shows brands that strengthen first-party data connections in the platform see up to a 26% uplift in incremental ROAS.

What Does Google Customer Match's New IP Address Matching Mean for Your Campaigns?

Customer Match audiences now have a new data source: IP addresses paired with interaction timestamps. When you upload these records to Google's Data Manager, Google matches those IPs to accounts in its ecosystem and adds them to your Customer Match lists. Retargeting audiences get larger, exclusion lists get more complete, and your lookalike seed pools grow, without requiring new email captures or lead forms.

What Is IP Address Matching and How Is It Different from Email Targeting?

Before this update, Customer Match accepted five signal types: hashed email addresses, hashed phone numbers, hashed first and last names, postal addresses, and mobile device IDs. All of those required direct contact from your customer, either a form fill, a purchase, or a newsletter signup. IP address matching is different: it captures every session your server logs, regardless of whether that visitor ever gave you their contact information.

There is a key technical distinction. Every other Customer Match signal type must be hashed before upload to protect privacy. IP addresses and timestamps are uploaded in plaintext, unhashed format, because the matching logic Google applies to IP signals works differently from email or phone matching. Google processes these directly through Data Manager and uses them only for audience creation, not for building broader interest profiles or sharing with third parties.

Timestamps must accompany every IP address upload. You cannot submit timestamps alone. If you upload an IP address without a timestamp, Google defaults to matching the most recently known user associated with that IP, which can be inaccurate for shared networks, households, or office connections. Include both the initial interaction timestamp and the most recent one for highest accuracy.

For context on how this fits into Google's broader measurement and data push throughout 2026, see our full Google Ads 2026 update tracker.

Which Ecommerce Brands Will Benefit Most from IP Address Customer Match?

Brands primarily selling to US, Canadian, Australian, or other non-EEA audiences will see the most immediate impact. IP address matching is not available for users located in the European Economic Area, the United Kingdom, or Switzerland. Google requires advertisers to exclude these regions from IP address uploads as a policy requirement, not just a recommendation. Brands with significant EU or UK traffic need to segment their upload lists by geography before submitting.

Within non-EEA markets, the brands most positioned to benefit are those with high browse-to-submit ratios: product pages or collections that see a lot of traffic but generate relatively few form fills or add-to-cart events. Every session you log on those pages already carries an IP address and timestamp. Turning those into Customer Match records creates retargeting audiences from visitors who your current email-based lists miss entirely.

Brands already using Google's AI Max search campaigns will benefit further, since larger Customer Match pools feed into AI Max's audience expansion and search term coverage signals.

What Are the Data Requirements and Geographic Restrictions for IP Matching?

The upload goes through Google's Data Manager API, the same infrastructure used for offline conversion imports. If you are still uploading Customer Match data through the legacy Google Ads API, this update does not apply until you migrate, and Google has been encouraging that migration for privacy and security reasons throughout 2026.

The required fields for each record are the raw IP address and at minimum one timestamp. Google recommends including both the first interaction timestamp and the most recent one. The IP address should reflect the session-level IP logged by your server or analytics stack, not a hashed or anonymized version.

Geographic restrictions are a policy requirement. Advertisers must exclude end users located in the EEA, UK, or Switzerland from any IP address upload. Your data pipeline needs to tag records by country of origin before export. If your site logs IP addresses without geographic tagging, you will need to run a geocoding step to classify each record before uploading.

Google is clear that uploaded IP data is used solely for creating Customer Match audiences and ensuring policy compliance. It will not be used for developing user profiles, shared with third parties, or fed into ad targeting outside the Customer Match framework.

What Should You Do Now with Google's Customer Match IP Address Update?

1. Confirm your Data Manager setup. IP address Customer Match uploads require the Data Manager API. If your team is still uploading Customer Match data through the Google Ads API directly, get the Data Manager migration scoped now. Match-rate improvements from IP signals will not appear until you are on the correct upload path.
2. Export IP addresses and timestamps from your site analytics or server logs. Your analytics stack or CRM almost certainly captures session-level IP and timestamp data. Pull a 90-day export of IP address, first interaction date, and most recent interaction date for non-EEA sessions.
3. Filter out EEA, UK, and Switzerland users before upload. Use a geocoding lookup on each IP address to classify by country. Remove any records mapped to EEA countries, the UK, or Switzerland before the file goes to Data Manager. This is a policy requirement.
4. Pair every IP address with its interaction timestamps. Do not upload IP addresses without timestamps. Include the first and most recent interaction dates for each IP. Missing timestamps cause Google to default to a less accurate match that degrades audience quality.
5. Track Customer Match audience sizes week-over-week starting October 1. Google projects match-rate improvements from IP signals to begin activating across accounts in October 2026. Set a weekly check on your Customer Match list sizes starting October 1 to quantify the lift and assess whether the expanded audience changes your retargeting or exclusion campaign structure.

Related Reading

• Google Ads AI Max Now Shows the Full Search Journey: What Ecommerce Brands Need to Know Before Q4
• Google's New Data Strength Metric: What Ecommerce Brands Need to Know
• Work with CTC's Google Ads team to build your first-party data strategy for Q4

Frequently Asked Questions

If you want help building an IP address upload pipeline or integrating this into your Customer Match strategy before Q4, talk to the CTC team. We run first-party data infrastructure for 7 to 9-figure ecommerce brands across Google Search, Shopping, and YouTube.