Google's Data Manager API Version 1.9 Accepts Call Conversions With Hashed Numbers Only
TLDR
Version 1.9 of Google's Data Manager API, released November 4, accepts call conversions but only as hashed phone numbers, and lead IDs cannot yet drive attribution.
What this Google Ads launch means for your accounts
- Status
- Available
- Platform
- Google Ads
- Affects
- Data Manager API, call conversions, lead IDs
- Who
- developers and data partners
- Effective
- November 4
- Action needed
- Not specified in the source
Google's Data Manager API version 1.9, released November 4, accepts call conversions, but only when the numbers are hashed. PPC Land reports that the update also lists the position of each failed record for developers and data partners. Lead IDs can be received, but they cannot yet be used to drive attribution.
How we got here: earlier Google Ads coverage
- Oct 25Google releases DV360 API v5 beta with Customer Match audience management changes
Google launched DV360 API v5 beta with changes to Customer Match audience management and DOOH insertion orders, while v4 sunset remains unscheduled.
- Oct 18Google Ads Data Manager will no longer require SHA-256 hashing for customer data uploads
Google Ads is replacing SHA-256 hashing with encryption for customer data uploads in the Data Manager starting November 16.
- Oct 16Floodlight gains ability to track conversions via Google signed-in data
Google's Floodlight system can now use signed-in user data to recover previously unattributed conversions across DV360, Search Ads 360, and Campaign Manager 360.
- Aug 3Google Expands Data Manager API with New Audience Management and Data Validation Tools
Google's Data Manager API now offers bulk audience removal, field-level validation warnings, and expanded address data fields to streamline advertiser workflows.
