Paid Media — October 1, 2026 — 2 min read

Customer Match IP address matching: Google Ads just learned to read your server logs.

Author

Portrait of Vineet Vijay Vineet Vijay

Published

October 1, 2026

Reading time

2 min

Topic

Paid Media

Customer Match IP address matching illustrated: IP address, timestamp, customer data and hashed email signals connected to one person and combined into a matched Google Ads audience Customer Match IP address matching illustrated: IP address, timestamp, customer data and hashed email signals connected to one person and combined into a matched Google Ads audience

Google Ads now lets you match Customer Match lists on IP address and interaction timestamp. For most advertisers, this means visitors who never gave you a usable email can now be added to an audience. Google's announcement makes it sound smaller than it is.

What changed

Search Engine Land reported on 25 September that upload files now accept "User IP address" and a timestamp column. They sit alongside email, phone, mailing address and mobile device ID. Google's support page adds two details that matter. IPs and timestamps are uploaded unhashed, and you can't send a timestamp without an IP.

Why marketers should care

Customer Match has always been limited by match rate. Lists full of mistyped emails, or work addresses nobody uses to sign in to Google, match poorly. Small lists stay too small to serve.

IP plus timestamp gives Google a second way to find the same person at a specific moment. Bigger, more accurate lists mean better seed audiences for PMax and Demand Gen. They also give you cleaner exclusions and retention lists that reach the people on them.

The bigger shift is that any interaction you log with an IP and a time can now be a match key. That covers call-back requests, gated downloads and quote forms. Your server logs just got a job.

What to do next?

1.

Check whether your CRM or form backend captures IP and submission time. Many store it, but few export it.

2.

Re-upload your top lists with the new columns and compare match rates before and after.

3.

Get consent language signed off first. Google requires disclosure and consent, and the feature is unavailable for users in the EEA, UK and Switzerland. In the UAE, the PDPL still applies.

The catch

Shared IPs on office networks, public Wi-Fi and mobile carriers will produce false matches. Treat early jumps in match rate with suspicion until conversions back them up.

Better matching helps only if the data behind it was collected honestly. Done properly, this is free reach. Done carelessly, it becomes a compliance problem aimed at a bigger audience.

Sources

Subscribe

New essays,

in your inbox.

Once every fortnight. The essay only — no newsletter, no promotion.

Scroll to Top