Full Answer

The deprecation was not cosmetic. Google Data Manager replaces three previously separate workflows — Customer Match list uploads, offline conversion imports, and store sales data — under a single API surface. For WooCommerce stores that were manually exporting orders and uploading CSVs with gclid values, the immediate consequence is that those uploads no longer process through the old endpoint.

The replacement path splits into two options. The first is Google Data Manager's UI, which accepts CSV uploads in a new schema that requires consent fields and hashed customer identifiers alongside the conversion action and value. The second — and the one Google is pushing — is the Data Manager API (v1.6), which accepts server-to-server payloads and supports automated, recurring imports. For stores already running server-side tracking, the API route is a natural fit because the same event pipeline that sends purchase data to GA4 and Meta CAPI can feed Google Data Manager with minimal additional configuration.

Enhanced Conversions for Leads is the specific mechanism Google now recommends for matching offline sales to the original ad click. It uses hashed first-party customer data — email, phone, name — instead of relying solely on the gclid, which browser privacy measures increasingly strip. Google merged the previously separate Enhanced Conversions for Web and Enhanced Conversions for Leads settings into a single toggle in 2026, simplifying setup but also meaning a misconfiguration affects both pathways simultaneously.

The practical lesson for WooCommerce stores: any integration that was uploading raw gclid-keyed CSVs needs rebuilding. The new schema, the consent fields, and the hashed identifier requirements are not optional — they gate whether the uploaded conversion is accepted. For a deeper look at how these platform changes affect WooCommerce conversion infrastructure, see iOS 26 Advanced Fingerprinting Protection Is the Second Tracking Threa.