Hi,

Please find the answers for your questions below:

1. Google Ads uses the Google Click Identifier (GCLID) to track clicks and 
associate them with conversions. While Google Ads does not store the GCLID 
itself in your account data, it uses the associated metadata, including 
timestamps, to determine when the click occurred.

2. Google Ads records the exact timestamp when a click occurs. This timestamp 
is in UTC (Coordinated Universal Time). When you upload a conversion, you 
provide a conversionDateTime. This value can be in any timezone, but it must be 
formatted correctly and should ideally be in UTC for consistency. If you 
provide a timezone offset, Google Ads will convert the conversionDateTime to 
UTC before comparing it with the click timestamp. If your conversion timestamp 
(2024-07-09 10:30:47+00:00) is correctly later than the click timestamp 
(2024-07-09 09:57:47+00:00), then there should be no CONVERSION_PRECEDES_EVENT 
error unless there was an issue with the timezone conversion or the recorded 
click timestamp. I would recommend you to kindly refer to the 
''conversion_date_time" guide for more detailed information.

In order to investigate your issue further, kindly provide us with the complete 
API logs (request and response logs with request-id and request header) 
generated at your end to better assist you further.

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.

You can send the details via Reply privately to the author option, or direct 
private reply to this email.
This message is in relation to case "ref:!00D1U01174p.!5004Q02a4A3A:ref" 
(ADR-00102574)

Thanks,

Google Ads API Team


Register for the upcoming workshop: Performance Max and the Google Ads API!

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 [email protected]
To unsubscribe from this group, send email to
[email protected]
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 the Google Groups 
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/49BlV000000000000000000000000000000000000000000000SGGW0I00deC9tTXZR1-nxlzyibwvbw%40sfdc.net.
  • Re... Vogels
    • ... Vogels
      • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum

Reply via email to