Documentation edits made through Mintlify web editor

Author: tcaldwell-x

x-ads-api/analytics.mdx

@@ -582,7 +582,7 @@ The Active Entities response for the request above is shown below.
 ```
 The `data` array includes an object for every entity that should be included in a subsequent analytics request. You should not request analytics for IDs outside of this set.
 
-Each object includes four fields: `entity_id`, `activity_start_time`, `activity_end_time`, and `placements`. The activity start and end times represent the time range that the associated entity's change events apply to and, thus, determine the dates that should be specified in subsequent analytics requests. The `placements` array can include either or both of the following values: `ALL_ON_TWITTER`, `PUBLISHER_NETWORK`. It indicates which placements should be requested for the given entity ID.
+Each object includes four fields: `entity_id`, `activity_start_time`, `activity_end_time`, and `placements`. The activity start and end times represent the time range that the associated entity's change events apply to and, thus, determine the dates that should be specified in subsequent analytics requests. The `placements` array can include the following values: `ALL_ON_TWITTER`, `PUBLISHER_NETWORK`, `SPOTLIGHT`, and `TREND`. It indicates which placements should be requested for the given entity ID.
 
 #### Usage
 
@@ -601,7 +601,7 @@ These are discussed in greater detail in each of the two subsections, below, aft
 Use the Active Entities endpoint in the following way to dictate how analytics requests are made. Follow this after you've decided how often to request active entities information and, thus, how often to pull analytics.
 
 1.  Make the Active Entities request.
-2.  Split the response by placement. One group for `ALL_ON_TWITTER` and one for `PUBLISHER_NETWORK`.
+2.  Split the response by placement. One group for `ALL_ON_TWITTER`, one for `PUBLISHER_NETWORK`, one for `SPOTLIGHT`, and one for `TREND`.
 3.  For each placement group, do the following.
     1.  Extract the entity IDs.
     2.  Determine the analytics `start_time` and `end_time` values.

x-ads-api/campaign-management.mdx

@@ -620,7 +620,6 @@ As example:
 
 #### Target Bidding
 
-
 Using target bidding, you can specify a target cost you want to pay and the X Ads platform will optimize your campaign for performance while staying near or below your target cost.
 
 This feature gives you the flexibility to reach users who are especially likely to take the desired action (such as a link click, a lead or a follow) while maintaining cost control. This is a powerful feature for advertisers who desire more options for campaign setup and optimization (including bidding options).
@@ -833,6 +832,8 @@ There are several places where X ads can be displayed. This is set at the [line
 * `TWITTER_PROFILE`
 * `TWITTER_SEARCH`
 * `TWITTER_TIMELINE`
+* `SPOTLIGHT`
+* `TREND`
 
 The line item’s `product_type` and `objective` determine which placements are allowed. The [GET line_items/placements](/x-ads-api/campaign-management#line-item-placements) endpoint can be used to retrieve the valid placement options for each product type.