Hi Robert,
Thanks for providing the requested logs. I've filed these requests internally.
Relevant changes in subsequent versions can be found in the release notes.
Regards,
Matt
Google Ads API Team
Matt
Google Ads API Team
ref:_00D1U1174p._5004Q2WxrfJ:ref
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=
Hi Matt,
I've sent request and response examples in a private message.
However I wanted to add publicly:
If there is no conversion_last_received_request_date_time tracked, instead
of NULL, Google Ads API returns the UNIX epoch timestamp *in the account’s
timezone*! See
https://developers.goog
Hi Robert,
Thanks for reaching out. Can you please provide us with a sample request and
response for the date-time formatting inconsistency and the UNIX epoch
timestamp behavior?
Thanks,
Matt
Google Ads API Team
Matt
Google Ads API Team
ref:_00D1U1174p._5004Q2WxrfJ:ref
--
--
=~=~=~=~=~=~=~=
Dear Google Ads API team,
when fetching data from `conversion_action` source (Google Ads API v9,
using ruby gem v15.0.0), we noticed, that the timestamp format for
metrics.conversion_last_received_request_date_time is inconsistent. The
timestamp pattern is mixing "-MM-dd HH:mm:ss.SSS" and "
