Enhanced conversions for leads

[Adeola Morren]

Refreshing my memory on something;

It had been suggested that we use enhanced conversions for leads instead of uploading google click id conversions.

1. Enhanced conversions for leads does not work, if the conversion was not sent from the website PRIOR to sending enhanced conversion, is that correct?

In other words its impossible to use enhanced conversion by it self?

2. If that is the case then it is implied that if you can not capture the conversion on the web page first, tht you should NOT use enhanced conversion for leads, but rather you should use Upload Click Conversion action, is that correct?

3. When using Upload Click Conversion, you can not pass in the email, or else it will be treated as an enhanced conversion, and given that there was no prior conversion submitted because we dont use regular conversion tracking on the website, it would just fail, is that correct?

[Google Ads API Forum Advisor]

Hi,

Thank you for reaching out to the Google Ads API support team.

Please find the answers for your questions below:

1. Enhanced conversions for leads does not work, if the conversion was not sent from the website PRIOR to sending enhanced conversion, is that correct? In other words its impossible to use enhanced conversion by it self?

• Enhanced conversions for leads require the initial conversion event to be sent from the website. Enhanced conversions work by supplementing the data of an existing conversion event (such as a form submission or purchase). Therefore, if the conversion was not captured on the webpage first, enhanced conversions alone cannot be used effectively. I would recommend you to refer to the 'Get Started with Enhanced Conversions for Leads' documentation for more information. 

2. If that is the case then it is implied that if you can not capture the conversion on the web page first, tht you should NOT use enhanced conversion for leads, but rather you should use Upload Click Conversion action, is that correct?

• Yes, your understanding is correct. If you are unable to capture the conversion event on the webpage, it is recommended to use Upload Click Conversions instead of Enhanced Conversions for Leads. Enhanced conversions rely on the initial web-based conversion event to function properly.

3. When using Upload Click Conversion, you can not pass in the email, or else it will be treated as an enhanced conversion, and given that there was no prior conversion submitted because we dont use regular conversion tracking on the website, it would just fail, is that correct?

• When using Upload Click Conversions, including the email address would treat the data as enhanced conversion data. If there was no prior conversion submitted (because you don’t use regular conversion tracking on the website), the enhanced conversion would not be processed correctly. Therefore, when uploading click conversions, you should avoid passing the email if the initial conversion event was not tracked on the website. 
• Don't set this 'UserIdentifier' field when uploading conversions using only click IDs. If this field is set, Google Ads treats the upload operation as an upload for enhanced conversions for leads.
• I would recommend you to kindly refer to the 'Create click conversion operations' guide as it explains in detail regarding the mandatory and optional fields that needs to be set while uploading the click conversions. 

 

This message is in relation to case "ref:!00D1U01174p.!5004Q02vEaBm:ref" (ADR-00261066)

Thanks,
 

Google Ads API Team

​​​​​​​

[Nikita Klyuchnikov]

The support team is providing incorrect information. Enhanced conversions for leads do not require that the same conversion event, which you send via API, occurs on the website. Here’s how it actually works: when a user fills out any form on your website that includes an email address, you can use a tag to send this information to Google. This allows Google to link the email with the user's GCLID.

When you send a conversion event via the API, you have the option (but it is not mandatory) to use the email instead of the GCLID. However, if you are already collecting the GCLID and have the capability to send it, there will be no difference in the outcome.

This has been verified through sending events with different setups, all resulting in identical metrics in the Google interface. Moreover, this process is essentially described in the documentation.

If you expect that sending emails in conversions will work like in other advertising networks, where Google will match the email from its data, this functionality is supported by Enhanced Conversions for Web. Enhanced Conversions for Web indeed requires that the conversion event is sent from the web, after which you can later supplement it with user_identifiers via the API.

[Google Ads API Forum Advisor]

Hi,

Thank you for reaching out to the Google Ads API support team.

@ Nikitha - Thank you for your input.

If you face any issue, share with us the complete API logs (request and response with request-id and request header) generated at your end.

If you are using a client library and haven't enabled the logging yet, I would request you to enable logging for the specific client library that you are using. You can refer to the guides 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.

This message is in relation to case "ref:!00D1U01174p.!5004Q02vEsyc:ref" (ADR-00263083)

Thanks,
 

Google Ads API Team

[Nikita Klyuchnikov]

There's no issue, that's just how these conversions work