WBRAID & GBRAID // Offline Conversion Import via GAds API

[Marco Frighetto]

Hi there,

I am aware that recently two new URL parameters have been introduced to help comply with Apple’s policies and  measure the iOS results. I am referring to the &wbraid and &gbraid parameters. 

I would like to know if those 2 parameters can be imported via Google Ads API to track offline conversions. We have run some preliminary tests and conversions attributed to those parameters seem not to be tracked. 

Do you know if and when those parameters will be supported? Thk

Marco

[Google Ads API Forum Advisor]

Hi Marco,

These new parameters are not supported in the Ads API. Can you confirm if you have seen that this is supported in the Ads UI in some fashion? If so, we can submit a feature request for these parameters?

Thanks,
Matt
Google Ads API Team

Matt Google Ads API Team

ref:_00D1U1174p._5004Q2MidWL:ref

[Marco Frighetto]

Hi Matt,

nope i haven't seen those parameters in the Ads API. At the same times, I am noticing that the volume of traffici identified by those parameters is increasing, therefore I was wondering if and when they could be used to track offline conversion.

Are they present in any way in your roadmap? 

Thk

Marco

 

Marco Frighetto www.boosterboxdigital.com US +1 213 293 3584 | UK +44 161 470 1106 |  IT +39 0584 793057

Best Small PPC Agency - European Search Awards 2019 Winner

Let's dive in into some fun legal terms. This e-mail may be confidential and privileged. This e-mail message including any attachments is for the sole use of the intended recipient and may contain confidential and privileged information pursuant to Legislative Decree 196/2003 and the European General Data Protection Regulation 679/2016 – AKA the beloved GDPR. Any unauthorized review, use, disclosure or distribution is prohibited. If you received this communication by mistake, please don't forward it to anyone else, please erase all copies and attachments, and please let me know that it has gone to the wrong person (thank you for that!). The above terms reflect a potential business arrangement, are provided solely as a basis for further discussion and are not intended to be and do not constitute a legally binding obligation. No legally binding obligations will be created, implied, or inferred until an agreement in final form is executed in writing by all parties involved. If you are not bored enough with these details please find the Italian version below.

Le informazioni contenute in questo messaggio sono da considerarsi strettamente confidenziali e il loro utilizzo é riservato al destinatario. Tutte le informazioni qui contenute, compresi eventuali allegati, sono da ritenere esclusivamente confidenziali e riservate secondo i termini del vigente D.Lgs. 196/2003 in materia di privacy e del Regolamento europeo 679/2016 – il mitico testo GDPR-  e quindi ne è proibita l’utilizzazione ulteriore non autorizzata. Chi, per errore, dovesse ricevere questo messaggio é pregato di informarne, con tempestività, il mittente e di rimuoverlo da ogni supporto elettronico o cartaceo, distruggendone, quindi, il contenuto. Si avvisa, inoltre, che ogni utilizzo non autorizzato del presente messaggio e/o dei suoi allegati é fonte di responsabilità per l'autore di tale improprio utilizzo, secondo la normativa vigente. Wow, complimenti se hai letto fino alla fine.

Privacy policy

--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
 
You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
---
You received this message because you are subscribed to a topic in the Google Groups "AdWords API and Google Ads API Forum" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/adwords-api/_IaMBYG6tGk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to adwords-api+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/WwVor000000000000000000000000000000000000000000000QYO4LS00ACMCSmxpT8SCV0cofqrdIQ%40sfdc.net.

[Google Ads API Forum Advisor]

Hi Marco,

Thank you for the reply.

If this is not available in the UI, then this is most likely not supported as well in the API. The API should only mirror the behavior and features of the UI. With this, if you have question about wbraid and gbraid parameters in the conversion and when will this be available, then I would suggest reaching out to the Product team via this link. If they can provide a roadmap on when will this become available in the UI, then we can raise a feature request in the API so that we can review if it is feasible to add.

Additionally, you may refer to this document to know more information about offline conversion in Google Ads API.

Regards,

Ernie John Blanca Tacata Google Ads API Team

ref:_00D1U1174p._5004Q2MidWL:ref

[al...@mayple.com]

Hi there,

As you know, gclid has been supported for conversion creation for many years now, in both the Google Ads UI and API.

Now, as seen in the Google documentation - wbraid and gbraid are supported by the Google Ads API for conversion creation.
However, the Google Ads UI does not support wbraid and gbraid for conversion creation.
This is where there is a lack of feature parity between the Google Ads API and UI.

Also, there is an internal inconsistency in the API - as stated, conversion creation using the API can be done with gclid, wbraid and gbraid.
However, conversion update (restating of value) can only be done with gclid. There is no support for wbraid and gbraid.
This is the internal inconsistency.

Thanks,

[Google Ads API Forum Advisor]

Hi Alon,

Thank you for your reply.

For wbraid and gbraid support in the Google Ads UI, our API support team would unfortunately not be able to comment. I would recommend raising this concern to the Google Ads Product Support team via this link, for further insights.

Our API support team also cannot comment further regarding feature parity between the two Google Ads platforms. However, if a specific feature is supported in the UI and yet to be available in the API, our team can raise a feature request, subject for review, for that feature's availability in the API.

As for conversion updates or conversion adjustments, below are two current ways on how these adjustments can be performed :

• There are two types of adjustments that can be made:
  • When you have a Google click ID (GCLID) and conversion date time available, you can adjust a conversion by uploading a ConversionAdjustment.
  • You can also adjust a conversion when you have an order ID available instead of a Google click ID and conversion date time

That said, seeing that this section does not appear to restrict including either of the wbraid and gbraid, and an order ID, when uploading click conversions, then you should be able to perform adjustments later on using the order ID instead.

Let us know if this helps.

Best regards,

Peter Laurence Google Ads API Team

ref:_00D1U1174p._5004Q2MidWL:ref

[Robert De Vivo]

so can you or can you not upload/import a conversion that has a wbraid ClickID instead of a gclid? Please help

[Google Ads API Forum Advisor]

Hi Robert,

Thank you for the reply.

Kindly note that you may upload conversions that have a wbraid field using the ConversionUploadService. UploadClickConversions. However, you may also upload a gclid field using this service. You may check this reference for the fields you may use in ClickConversion.

Best regards,

Heidi Google Ads API Team

ref:_00D1U1174p._5004Q2MidWL:ref