Search Engine Land reported on September 25 that Google Ads Customer Match can now use IP addresses and interaction timestamps as additional matching signals. For performance marketers, the temptation is obvious: stronger matching may mean more usable first-party audiences. But the operational question is not only “will this improve match rate?” It is “are we allowed, prepared and governed enough to upload these signals?”
The detail that changes the conversation is that IP addresses and timestamps are reported as unhashed uploads, and the option is not available for end users in the EEA, the UK or Switzerland. That makes this a paid-media control issue, not a routine audience update. CRM, analytics, legal, agency and media teams need one checklist before anyone turns a broader data feed into a campaign input.
The decision point
Customer Match already depends on first-party data and account eligibility. Google’s developer documentation frames Customer Match around customer information a business has collected and around consent planning for audience uploads. Adding IP and interaction time makes the data closer to server logs, consent records and regional processing rules. Those systems are usually owned by different people.
If a media team asks for “all available identifiers,” the answer should not be a CSV export. It should be a decision meeting. Which interactions created the signal? Which privacy notice covered that use? Which users must be excluded by region? Which vendor or account will upload the data? Which campaigns are allowed to use the audience, and for how long?
A pre-upload checklist
First, document source and purpose. Do not mix support logs, security logs, ecommerce sessions and CRM events simply because they sit in the same warehouse. Second, confirm consent and disclosure. If the user did not agree to advertising personalization or data sharing for this use, the list should not include that record. Third, enforce regional exclusions before upload, not after campaign launch.
Fourth, keep raw-signal handling narrow. If IP and timestamp fields must be unhashed, access, retention and transfer controls should be stricter than for ordinary campaign reports. Fifth, separate matching from targeting policy. A better match rate does not automatically make the audience strategically useful. Test whether the audience improves incremental reach, conversion quality or suppression accuracy rather than celebrating list size.
What to ask before using it
Paid-media leaders should ask five practical questions. Who owns the data lineage from collection to upload? Can we prove consent and region at the record level? Are we using Data Manager or another recommended workflow rather than a fragile legacy process? Is the audience used for inclusion, exclusion, lookalike expansion or measurement? What is the rollback plan if match quality or compliance review fails?
Those questions sound operational, but they are budget questions. A Customer Match audience can influence bidding, remarketing, suppression and incrementality tests. If the underlying controls are weak, the campaign may optimize against a list the business cannot defend.
The takeaway
IP and timestamp matching may be useful for advertisers with mature first-party data operations. It is not a shortcut around consent, regional limits or CRM hygiene. The right response is a data-control checklist: prove collection, consent, region, ownership, retention and test design before the media team treats the new signals as spendable audience quality.
