{`

Launch

`} # Simplified Flat Targeting Schema Now Available for Display APIs **Release date:** Available now **Environment:** Sandbox and Production **Change type:** Non-breaking enhancement **Action required:** Optional *** ## Overview Walmart Connect Display APIs now support a new **flat targeting schema** for supported targeting workflows. The flat schema allows developers to represent targeting criteria using structured targeting objects rather than nested logical expression trees that use operators such as `AND`, `OR`, and `NOT`. Depending on the targeting type, criteria can be defined using include and exclude values. The existing expression-based schema remains fully supported, and no changes are required for existing integrations. We have **no plans to deprecate** the expression-based schema at this time. *** ## Why This Matters The flat targeting schema simplifies how targeting data is created, stored, retrieved, and reused across campaign management, forecasting, reporting, and analytics workflows. With the flat schema, partners can: - Reduce custom parsing logic for nested targeting expressions - Store targeting criteria more easily within partner systems - Reuse targeting objects across activation and forecasting workflows - Simplify validation and troubleshooting - Improve consistency across campaign management and reporting use cases *** ## Targeting Schema Options Developers can now work with targeting data using either supported schema format. | Schema | Description | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | | **EXPRESSION** | Existing targeting structure that uses nested logical operators such as `AND`, `OR`, and `NOT`. | | **FLAT** | Simplified targeting structure that represents targeting criteria using structured targeting objects and include/exclude values where supported. | Both schemas represent the same targeting intent but use different structures. *** ## Supported workflows Flat targeting is currently supported for: ### Read APIs The following APIs can return targeting data in either schema format. | API | Endpoint | Flat Targeting Support | | ---------------------------------------- | ------------------------------ | ----------------------------------------------- | | Entity Snapshot API (Line Item Snapshot) | `POST /api/v1/snapshot/entity` | Response format selectable using request header | | List Ad Groups | `POST /api/v1/adGroups/list` | Response format selectable using request header | ### Write APIs The following APIs accept either targeting schema format in request payloads. | API | Endpoint | Flat Targeting Support | | ----------------- | ---------------------------------------------------- | -------------------------- | | Create Ad Group | `POST /api/v1/adGroups` | Accepts FLAT or EXPRESSION | | Update Ad Group | `PUT /api/v1/adGroups`
`PATCH /api/v1/adGroups` | Accepts FLAT or EXPRESSION | | Reach Estimate | `POST /api/v2/reachEstimate` | Accepts FLAT or EXPRESSION | | Delivery Estimate | `POST /api/v2/deliveryEstimate` | Accepts FLAT or EXPRESSION | *** ## Requesting Flat Targeting Responses To receive targeting details in the flat schema from supported read APIs, include the following request header: ```http x-targeting-format: FLAT ``` Supported read APIs include: - Entity Snapshot API (Line Item Snapshot) - List Ad Groups ### Header Values | Header Value | Result | | -------------- | ---------------------------------------------------------------------------------------------------------- | | **EXPRESSION** | Returns targeting details using the existing expression-based schema. This is the default response format. | | **FLAT** | Returns targeting details using the flat targeting schema. | If the `x-targeting-format` header is not included, supported read APIs return targeting data using the expression-based schema by default. > **Note:** The `x-targeting-format` header affects only response formatting for supported read APIs. It is not required for create, update, or forecasting requests. *** ## Creating and Updating Targeting Supported create, update, and forecasting APIs accept targeting data using either schema format. This includes: - Create Ad Group - Update Ad Group - Reach Estimate - Delivery Estimate Developers can choose the schema that best fits their integration architecture and data model. *** ## Important Implementation Guidance > **Important:** A request payload must use either the FLAT schema or the EXPRESSION schema. Mixing both schema types within the same targeting payload is not supported. Additional considerations: - The expression-based schema remains fully supported. - Existing integrations do not require changes. - EXPRESSION remains the default response format unless `x-targeting-format: FLAT` is specified on supported read APIs. *** ## Supported Targeting Types The flat targeting schema is supported for the following targeting types: - Geographic targeting - Behavioral targeting - Contextual targeting - Keyword targeting - Run of Site targeting Refer to the targeting documentation for complete schema requirements, supported targeting rules, and implementation examples. *** ## Backward Compatibility This release is a non-breaking enhancement. Existing integrations that use the expression-based targeting schema will continue to work without modification. Partners can adopt the flat targeting schema at their own pace while continuing to use existing targeting implementations. *** ## Getting Started To begin using the flat targeting schema: 1. Review documentation. 2. Add `x-targeting-format: FLAT` to supported read API requests. 3. Submit FLAT targeting payloads when creating or updating ad groups. 4. Validate integrations in Sandbox before promoting changes to Production. *** ## Documentation For complete targeting schema details, examples, and supported targeting configurations, refer to: - [Targeting object documentation](https://developer.walmart.com/advertising-partners/docs/targeting-object) - [Entity Snapshot API documentation](https://developer.walmart.com/advertising-partners/docs/create-entity-snapshot-1) - [List Ad Groups documentation](https://developer.walmart.com/advertising-partners/docs/list-ad-groups) - [Create Ad Group documentation](https://developer.walmart.com/advertising-partners/docs/create-new-ad-group) - [Update Ad Group documentation](https://developer.walmart.com/advertising-partners/docs/update-existing-ad-group) - [Reach Estimate API documentation](https://developer.walmart.com/advertising-partners/docs/request-reach-estimate-v2) - [Delivery Estimate API documentation](https://developer.walmart.com/advertising-partners/docs/request-delivery-estimate-v2)
{`

Launch

`} ## Expanded reporting metrics available for Display **Status:** Live ### Expanded metric available within Display Walmart Connect has introduced a number of identity and attribution upgrades on June 1st. To support these upgrades, new reporting metrics across existing Display report types are now available. ### Display changes - Introducing `attributionModel` column to all report types. This column will return either `fair_share` or `last_touch`. ### Technical Documentation - [Create Report Snapshot](https://developer.walmart.com/advertising-partners/docs/create-report-snapshot) - [Parameter/metrics definitions](https://developer.walmart.com/advertising-partners/docs/definition-of-various-parameters-generated-across-the-snapshot-reports) - [Metric type availability by Report](https://developer.walmart.com/advertising-partners/docs/metric-type-availability-by-report-type)