-
Notifications
You must be signed in to change notification settings - Fork 114
Description
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:
{'entity_id': 'hbvri', 'activity_start_time': '2020-05-27T23:48:58Z', 'activity_end_time': '2020-06-02T17:24:58Z', 'placements': ['ALL_ON_TWITTER']}
{'entity_id': 'hc53a', 'activity_start_time': '2020-05-27T21:21:03Z', 'activity_end_time': '2020-05-28T03:27:57Z', 'placements': ['ALL_ON_TWITTER']}
{'entity_id': 'h8nt6', 'activity_start_time': '2020-05-23T15:39:18Z', 'activity_end_time': '2020-05-23T23:36:40Z', 'placements': ['ALL_ON_TWITTER']}
{'entity_id': 'h7a76', 'activity_start_time': '2020-06-01T05:56:47Z', 'activity_end_time': '2020-06-02T17:24:56Z', 'placements': ['ALL_ON_TWITTER', 'PUBLISHER_NETWORK']}
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.