Open arammaliachi opened 4 years ago
@juanshishido can you advice?
Oh I think I understand now, I think activity_start_time and activity_end_time are greedy to all activity in each ad group returned meaning its range will keep growing while the ad is active... So I guess I have to query stats per day for the resulting range on the resulting line items (ad groups).
Maybe some clarification on this on the docs...
Thanks for the feedback. We recommend using the async analytics endpoints for production applications as the active range can exceed 7 days.
Maybe some clarification on this on the docs...
Do you have any suggestions?
what to do if we want to access data of lifetime or with respect to year'
The example provided at examples/active_entities.py does not work as is.
If I run it as is I am told by the inline documentation of the file that I am pulling active entities for the last day. If I examine the dict returned I see that the activity_start_time and activity_end_time do not match anything at all the 'last day'.
This is causing the end call to analytics to fail because some active entities activity_start_time and activity_end_time ranges are greater than 7 days (as calculated by the date_range function) even though I'm supposedly querying for only the last day.
Why am I getting active entities outside the last day range at all?
e.g.
if I run the script as is today 2020-06-03 I get the following active entities:
I see active entities that begin 2020-05-27 and end 2020-05-28 which is completely out of the last day range.
This is causing the range output by the date_range function to be greater than 7 days and hence all the script fails.