Gbraid or wbraid conversions sent via Offline Conversion Upload do not appear in the conversion summary.

[Márcio Galeno]

Hi everyone!

I've noticed that offline conversion uploads using wbraid and gbraid identifiers aren't showing up as conversions in the Google Ads UI reports. Conversions that include gclid work normally.

I saw in some discussions that setting the Conversion Action to “Count all conversions” instead of “One per click” could fix this, but I’ve tried it and it didn’t work.

The API response indicates success, but the conversion doesn’t appear in the conversion summary  — the total conversion value also isn’t included in the aggregated metrics.

Here’s an example of a successful upload from my logs:

Uploaded click conversion that occurred at 2025-10-28 10:22:24-03:00 

Order id: 123715 

Google Wbraid: ClMKCAjwsPzHBhAfEkMA_SWgPm5Mq4yOZ9JRDtXsgLIQunM19a4Dqr8TYXBR1oX0zal1bBHZTOSP96ZwYps4RTPe7IQab0TkV58rkN0LmzYDGgIwNw

Conversion Actions: customers/4531607647/conversionActions/7138947321 

Job ID: 6167659481904677762

Any insights would be greatly appreciated. Thanks!

[Google Ads API Forum Advisor]

Hi,

Thank you for contacting the Google Ads API support team.

I understand that your conversions are uploaded via the API using wbraid and gbraid identifiers not reflected in the Google Ads UI. We see that the specified conversion action has a tracking status of "Needs attention" due to "Unparseable gclid," but you've confirmed that conversions including gclid are working normally.

To help us investigate why the conversions with wbraid and gbraid identifiers are not appearing, even though the API upload was successful, please provide the following information:

Could you please confirm the total number of conversions uploaded via the API for the date 2025-10-28?

• We verified that the Google Ads UI shows 5 conversions reflected (when referring to All conv. (by conv. time)) and 845 conversions reflected (when referring to All conv. value (by conv. time)).
• Please confirm the total number of conversions that were successfully uploaded via the API.
• Please provide the complete API logs (request and response logs with request-id and request header) where the conversions using the wbraid and gbraid identifiers were uploaded successfully. This will help us verify the identifiers and the overall request structure.

Kindly note that you have to enable logging if you are using a client library. You can refer to the guides for Java, .Net, PHP, Python, Ruby, or Perl to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.

Note: A common reason for conversions not reflecting, even after a successful upload, is missing consent information. If you haven't done so already, please include the consent object in your API request. For conversions to be properly attributed, it is highly recommended to populate the consent field within the ClickConversion object. If this field is not set, it is possible that the conversions, even if successfully uploaded, will not be attributable and therefore won't show up in your reports.

You can send the details via the Reply privately to the author option or direct private reply to this email.

Thanks,
 

Google Ads API Team

Feedback
How was our support today?

               
[2025-10-29 20:12:02Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vS6o2:ref" (ADR-00337239)