Hi Xu,

Thank you for reaching out to us.

Moving forward to this,"I believe the data we upload will not beyond the 
current date time of actual upload ,since it is not feasible to grab data in 
the future." and "So is there a time range(or time zone ) for your server which 
user can be allowed to upload?"
-Since you are encountering “Date is after allowed maximum” then you are 
getting DateError:LATER_THAN_MAXIMUM_DATE, this occurs when the conversion 
event was uploaded for a future date, or when the time zone part of the 
datetime is not worked out.

Here's more from Upload ClickConversion
- The conversion_date_time must have a timezone specified, and the format is as 
yyyy-mm-dd HH:mm:ss+|-HH:mm, for example: 2022-01-01 19:32:45-05:00 (ignoring 
daylight saving time) . The timezone can be for any valid value: it does not 
have to match the account's timezone.

Also enter your GMT offset by indicating + or - and then the 4 digit time 
difference. (For example, New York is offset by -05:00, and Berlin by +01:00). 
If you use Greenwich Mean Time, then simply enter +00:00 It could be tricky so 
this needs care.

And for this, “First error: Too short., at conversions[1].gclid”
- There could be an issue with the actual GCLID string you are passing and 
might have incomplete characters. You can ensure that the GCLIDs you are 
uploading are indeed correct and existing in your account by generating the 
click_view report and verifying the value via the click_view.gclid.

Should issues persist, you may provide the complete request and response logs, 
and request-id, so our team can investigate further. If you haven't yet, python 
logging can be enabled by navigating to this Logging documentation, and by 
using the DEBUG (instead of INFO) log level.

You may then send the requested information via the Reply privately to author 
option. If this option is not available, you may send the details directly to 
our googleadsapi-supp...@google.com alias instead.

Best regards,

Heidi
Google Ads API Team
ref:_00D1U1174p._5004Q2dtH3Z:ref

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+unsubscr...@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 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 adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/F30nj000000000000000000000000000000000000000000000RHFSNA00YXY0l4_8RUywoq-DD7PZFg%40sfdc.net.
  • is... Xu Rico
    • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum

Reply via email to