Gclid in Enhanced Conversions

[Jonathan]

I see I can also add a gclid_date_time_pair to Enhanced Conversions sent via the API. 

Will this gclid be used to help identify the conversion, together with the order ID? (I know this is the case for conversion adjustment types other than 'enhancement').

Or will the gclid in enhancements be used like the user_identifiers: to match conversions that initially had no gclid and thus improve measurement accuracy? 

[Google Ads API Forum Advisor]

Hi Jonathan,

How ad tags and GCLID work is beyond Google Ads API support scope, I suggest you reach out to our product support team for further assistance.

With that being said, here's Use a transaction ID to minimize duplicate conversions. My guess based on About enhanced conversions is that uploading enhanced conversions via API relies on an order Id that is matched with the order Id sent to an ad tag that generated the GCLID that the order Id is associated with. I would also guess you would use the API for enhanced conversions when the user data you want to match the conversion with isn't available on the page where the order Id is sent to the ad tag, but to be certain you would have to ask our product support team.

Regards,

Aryeh Google Ads API Team

 

ref:_00D1U1174p._5004Q2cVd2I:ref

[Matthias Laqueur - BossData]

Hi Jonathan 

We are working in the same thing. Did you get this working via the Google Ads API? We manage it perfectly when a click ID is present. But when sending the same data without a click ID but with hashed mail for example we get 0 results. 

[Google Ads API Forum Advisor]

Hi Matthias,

Thank you for commenting on this forum thread.

I can see that you have an ongoing email thread for this concern. With this, let us continue our discussion there for better tracking of updates. We have also raised the issue with the rest of them to further investigate the issue and to provide accurate insights to address the issue.

Regards,

Ernie John Google Ads API Team

ref:_00D1U1174p._5004Q2cVd2I:ref

[Matthias Laqueur]

Hi Ernie

Ok I will not try to get an answer via the forum on top of the existing mail conversation we have. The reason I also approached the subject via the forum is because we have the feeling we are not moving forward on the topic. Have you received our last correspondence with Dimitris Terzopoulos (dimit...@google.com)? My colleague Sander (san...@bossdata.be) wrote the following to Dimitris:

I don't understand why that is the feedback - I am either not understanding the reply correctly or API support is not understanding me. 

I know I am sending the conversions to 2 different pixels through the API. That is the point of our test to show you that we are not getting any enhanced conversions registered.

To recap my problem : after testing we noticed that we never get any conversions based on enhanced data, while all our gclid based api uploads are working fine. We decided to test it by sending the same events to pixels: 1x with click gclid and 1x  to another pixel without click data to see how many conversions we could register when using lead enhanced data only.

Specifically - I am doing this through the API:

- API upload all conversions to 1017354921 including the GCLID that we have captured for that event.

- API upload all conversion (identical) to 1017355137 excluding the GCLID and including enhanced data (hashed email) so it can only be matched on enhanced data.

If there is an attributed conversion in 1017354921 then we can be sure that that event is from GADS

We would expect some of them to show in the other enhanced data only pixel 1017355137 at some point.

However there are 0 conversions in the pixel that is receiving enhanced data only, but we would expect some/many conversions to show up in pixel 1017355137 based on the enhanced data.

We followed the exact same approach as given by the SDK examples for uploading conversions for which you do not have click data (Upload Enhanced Conversions For Leads)

""Instead of setting gclid, populate the user_identifiers with the standardized and hashed email address or phone number of the user. If available, you may add both values in separate UserIdentifiers on the same ClickConversion.""

Our conclusion is that:

A) we are doing something wrong, but at this point I can't understand what that could be as the API accepts and replies 'click not found for enhanced data' in 100% of the API uploaded conversions? B) coverage of enhanced data matching to a click is really poor - but then what would be the point of offering this?

C) the API method / SDK is not yet fully supporting enhanced data in some way?

Those conversion ID's belong to these pixels in the user interface - please see the results here:

Met vriendelijke groeten,
With kind regards,

Matthias Laqueur BossData - Business Driven, Digital Inspired M: +32479449408 E: matt...@bossdata.be A: Broederminstraat 9, 2000 Antwerp, BE W: Bossdata.be

[Google Ads API Forum Advisor]

Hi Matthias,

Thank you for your patience.

I understand where you are coming from. I can confirm that we received that email. However, our team will need to further check this. Whenever new information becomes available, you can be sure that we will let you know. For now, I would advise you to wait for the response from my colleague on the one email thread you sent for the time being in order to properly follow updates.

Best regards,

Heidi Google Ads API Team

ref:_00D1U1174p._5004Q2cVd2I:ref