we encountered an issue when querying for stats with segmentation_type = “EVENTS” (across all entity levels) - the payload that is returned always contains just one segment with name = “Unknown” while the Twitter UI displays the correct event name.
For illustration - check this campaign level job. All relevant info (campaign_id, time range, account_id…) can be found in the response of this
twurl -t -H ads-api.twitter.com '/4/stats/jobs/accounts/18ce54fslkj?job_ids=1039163129622683648' | jq
This seems like a bug - could you please check if this is really an intended behaviour and what could be the cause of it? If it is, is there a way to fix it? At the moment this renders the event segmented stats data we intake unusable and impacts all of our customers.