Skip to content

Commit b6c3f77

Browse files
authored
Documentation edits made through Mintlify web editor
1 parent e2f4a88 commit b6c3f77

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

x-ads-api/analytics.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ Available only through our asynchronous analytics endpoints, segmentation allows
7171

7272
Why don't the Ads API numbers match what's shown in the X Ads UI?
7373

74-
- Make sure you've requested data for both placements: `ALL_ON_TWITTER` and `PUBLISHER_NETWORK`
74+
- Make sure you've requested data for both placements: `ALL_ON_TWITTER` and `PUBLISHER_NETWORK`, `SPOTLIGHT`, and `TREND`.
7575
- Remember that end times in the Ads API are exclusive; they are inclusive in the Ads UI
7676

7777
Why do the numbers change depending on when I request data?
@@ -94,7 +94,7 @@ Why does the API show `null` values while the UI shows 0s?
9494

9595
How can I request metrics associated with a granular placement, such as the X timeline?
9696

97-
- We only support two placement values in analytics: `ALL_ON_TWITTER` and `PUBLISHER_NETWORK` (i.e., the [X Audience Platform](/x-ads-api/audiences))
97+
- We support the following placement values in analytics: `ALL_ON_TWITTER` and `PUBLISHER_NETWORK`, `SPOTLIGHT`, and `TREND` (i.e., the [X Audience Platform](/x-ads-api/audiences))
9898

9999
Is it possible to retrieve metrics for deleted or paused entities?
100100

0 commit comments

Comments
 (0)