[BSP Integration Request] Urgent Need for GCLID Back-End Matching Solution for Click-to-WhatsApp (CTM) Attribution

10 views

Skip to first unread message

Leo.Lian

unread,

Oct 30, 2025, 8:06:42 PM (2 days ago) Oct 30

to Google Ads API and AdWords API Forum

Dear Google Ads API Team,

We are one of official WhatsApp Business Solution Provider, specializing in serving clients who heavily utilize Click-to-WhatsApp (CTM) advertising through Google Ads Message Assets. We are reaching out to find the official, scalable solution for accurate conversion tracking and Offline Conversion Import (OCI) in this specific environment.

📌 1. Real-World Scenario: The CTM Attribution Gap

Our clients' campaigns rely on the following sequence:

Ad Click (Google Side): A user clicks the WA Message Asset (where interaction_type = 'MESSAGE'). Google generates and logs the GCLID.
Conversion Path Disruption: The user is immediately deep-linked to their WhatsApp App. Crucially, the GCLID cannot be securely embedded or passed through the WA protocol to our system.
Lead Capture (BSP Side): Our platform receives a webhook from whatsapp containing the lead's WhatsApp Phone Number and the session start time after the first message is sent.

🛑 2. The BSP’s Core Technical Challenge

As the BSP, we are the designated party responsible for the conversion data integrity on behalf of our clients. Our problem is:

We have the Phone Number (PII) from the WhatsApp webhook, but we lack the GCLID necessary to fulfill the OCI requirement (ConversionAction requires GCLID or an identifier that links to the GCLID).

We need a mechanism that allows our server-side system to bridge this gap, ensuring that every qualified lead (WA_Qualified_Lead) is correctly attributed back to its originating GCLID.

❓ 3. Request for Official Support and Guidance

We are not seeking a front-end workaround, but rather the official, partnership-level solution for this common BSP integration scenario.

We kindly request guidance on the following:

Backend Matching API: Does Google offer a private or partnership API/service that allows us to query with Hashed Phone Numbers (or other PII data like IP/Timestamp) to securely retrieve the associated GCLID from the CTM click log?
Enhanced Conversions for CTM: If Enhanced Conversions for Leads (ECL) is the recommended path, are there specific integration guidelines for BSPs to ensure that the PII we collect (Phone Number) at Step 4 is matched reliably against the CTM click logged in Step 1?
Dedicated Partnership Channel: Could we be directed to the Google Ads Partner or Business Development team responsible for facilitating these types of server-to-server attribution integrations for CTM/Messaging providers?

Our goal is to integrate the most robust, high-match-rate attribution solution, in full compliance with Google's policies, to ensure the success of our shared advertising clients.

Thank you for your valuable time and direction.