Merge branch 'PLAT-234038/add-use-case-in-data-mgmt-guide' of https://git.corp.adobe.com/ens60013/experience-platform.en into PLAT-234038/add-use-case-in-data-mgmt-guide

Carlo Javier · Carlo Javier · commit 3762110f7fc7 · 2025-07-18T12:52:43.000-07:00
diff --git a/help/destinations/catalog/advertising/google-customer-match-dv360.md b/help/destinations/catalog/advertising/google-customer-match-dv360.md
@@ -1,10 +1,15 @@
 ---
 title: Google Customer Match + Display & Video 360 connection
 description: With the Google Customer Match + Display & Video 360 destination connector, you can use your online and offline data from Experience Platform to reach and re-engage with your customers across Google's owned and operated properties, such as Search, Shopping, Gmail, and YouTube.
+badge: Limited Availability
 exl-id: f6da3eae-bf3f-401a-99a1-2cca9a9058d2
 ---
 # [!DNL Google Customer Match + Display & Video 360] connection
 
+>[!NOTE]
+>
+>**Limited availability of the Google Customer Match + DV360 connector**<br>As we're going through the full lifecycle of maturity on this integration with Google, we're seeing data that points to weaknesses in implementation that need to be corrected before wider adoption can happen. Given these concerns, Adobe has reduced the visibility of this destination to a limited number of customers. We are in active conversations with Google to improve the product experience. We understand this may be disappointing news, but we believe it's the responsible approach to ensure a high-quality, reliable experience for our customers.</br>
+
 Use this destination to activate your first-party PII-based [[!DNL Google Customer Match]](https://support.google.com/google-ads/answer/6379332?hl=en) lists directly to [!DNL Google Display & Video 360] properties such as [!DNL Search], [!DNL YouTube], [!DNL Gmail], and the [!DNL Google Display Network].
 
 Certain Google-integrated third parties, such as Adobe Real-Time CDP, can use the [!DNL Google Audience Partner API] to create [!DNL Customer Match] audiences directly in customers' [!DNL Display & Video 360] account.
diff --git a/help/destinations/catalog/streaming/http-destination.md b/help/destinations/catalog/streaming/http-destination.md
@@ -39,7 +39,7 @@ This section describes which types of audiences you can export to this destinati
 Refer to the table below for information about the destination export type and frequency.
 
 | Item | Type | Notes |
----------|----------|---------|
+| ---------|----------|---------|
 | Export type | **[!UICONTROL Profile-based]** | You are exporting all members of a segment, together with the desired schema fields (for example: email address, phone number, last name), as chosen in the mapping screen of the [destination activation workflow](../../ui/activate-segment-streaming-destinations.md#mapping).|
 | Export frequency | **[!UICONTROL Streaming]** | Streaming destinations are "always on" API-based connections. As soon as a profile is updated in Experience Platform based on audience evaluation, the connector sends the update downstream to the destination platform. Read more about [streaming destinations](/help/destinations/destination-types.md#streaming-destinations).|
 
@@ -52,6 +52,7 @@ To use the HTTP API destination to export data out of Experience Platform, you m
 * You must have an HTTP endpoint that supports REST API.
 * Your HTTP endpoint must support the Experience Platform profile schema. No transformation to a 3rd-party payload schema is supported in the HTTP API destination. Refer to the [exported data](#exported-data) section for an example of the Experience Platform output schema.
 * Your HTTP endpoint must support headers.
+* Your HTTP endpoint must respond within 2 seconds to ensure proper data processing and avoid timeout errors.
 
 >[!TIP]
 >
@@ -357,4 +358,8 @@ Below are further examples of exported data, depending on the UI settings you se
 
 In 95 percent of the time, Experience Platform attempts to offer a throughput latency of less than 10 minutes for successfully sent messages with a rate of less than 10 thousand requests per second for each dataflow to an HTTP destination.
 
-In case of failed requests to your HTTP API destination, Experience Platform stores the failed requests and retries twice to send the requests to your endpoint.
+In case of failed requests to your HTTP API destination, Experience Platform stores the failed requests and retries twice to send the requests to your endpoint.
+
+## Troubleshooting {#troubleshooting}
+
+To ensure reliable data delivery and avoid timeout issues make sure that your HTTP endpoint responds within 2 seconds to Experience Platform requests, as specified in the [prerequisites](#prerequisites) section. Responses which take longer will result in timeout errors.
diff --git a/help/destinations/toc.md b/help/destinations/toc.md
@@ -85,7 +85,7 @@ role: Admin,User
         * [Google Ad Manager connection](./catalog/advertising/google-ad-manager.md)
         * [(Beta) Google Ad Manager 360 connection](./catalog/advertising/google-ad-manager-360-connection.md)
         * [Google Customer Match connection](./catalog/advertising/google-customer-match.md)
-        * [Google Customer Match + DV360 connection](./catalog/advertising/google-customer-match-dv360.md)
+        * [(Limited Availability) Google Customer Match + DV360 connection](./catalog/advertising/google-customer-match-dv360.md)
         * [Google Display & Video 360 connection](./catalog/advertising/google-dv360.md)
         * [Google gtag extension](./catalog/advertising/gtag-advertising.md)
         * [LinkedIn Insight Tag extension](./catalog/advertising/linkedin.md)
diff --git a/help/destinations/ui/activate-batch-profile-destinations.md b/help/destinations/ui/activate-batch-profile-destinations.md
@@ -137,6 +137,18 @@ Select **[!UICONTROL Export full files]** to trigger the export of a file contai
     * **[!UICONTROL Weekly]**: select the start date and subsequent exports will occur on that day of the week until the selected end date.
     * **[!UICONTROL Monthly]**: select the start date and subsequent exports will occur on that date of the month until the selected end date. For months with fewer than 30 or 31 days, the export occurs on the last day of the month.
 
+    >[!NOTE]
+    >
+    > Weekly and monthly scheduling options are currently supported only for the following file-based cloud storage destinations, and only when activating [people audiences](../../segmentation/types/overview.md#people-audience) and [prospect audiences](../../segmentation/types/overview.md#prospect-audience).
+    > 
+    > * [Amazon S3](../catalog/cloud-storage/amazon-s3.md)
+    > * [Azure Blob Storage](../catalog/cloud-storage/azure-blob.md)
+    > * [Data Landing Zone](../catalog/cloud-storage/data-landing-zone.md)
+    > * [Google Cloud Storage](../catalog/cloud-storage/google-cloud-storage.md)
+    > * [SFTP](../catalog/cloud-storage/sftp.md)
+    > 
+    > Weekly and monthly scheduling options are not available for other destination types.
+
 2. Use the **[!UICONTROL Time]** toggle to select whether the export should happen immediately after audience evaluation or on a scheduled basis, at a specified time. When selecting the **[!UICONTROL Scheduled]** option, you can use the selector to choose the time of day, in [!DNL UTC] format, when the export should take place.
 
     Use the **[!UICONTROL After segment evaluation]** option to have the activation job run immediately after the daily Experience Platform batch segmentation job completes. This option ensures that when the activation job runs, the most up-to-date profiles are exported to your destination. This might result in an audience being exported multiple times a day, based on your actions.
diff --git a/help/segmentation/TOC.md b/help/segmentation/TOC.md
@@ -15,8 +15,10 @@ role: User
 - Segmentation API {#api}
     - [Overview](api/overview.md)
     - [Getting started](api/getting-started.md)
+    - [Create audience metadata](api/create-audience.md)
     - [Audiences](api/audiences.md)
     - [Export jobs](api/export-jobs.md)
+    - [External audiences](api/external-audiences.md)
     - [Previews and estimates](api/previews-and-estimates.md)
     - [Schedules](api/schedules.md)
     - [Segment definitions](api/segment-definitions.md)
diff --git a/help/segmentation/api/create-audience.md b/help/segmentation/api/create-audience.md
@@ -0,0 +1,85 @@
+---
+title: Create Audience API Endpoint
+description: Learn how to create the metadata for an external audience using the API.
+hide: yes
+hidefromtoc: yes
+exl-id: e841a5f6-f406-4e1d-9e8a-acb861ba6587
+---
+# Create audience endpoint
+
+The POST `/audiences` endpoint can be used create the metadata for an external audience. You should use this endpoint if the audience ingestion will be managed in a separate service, such as batch ingestion.
+
+## Getting started
+
+>[!IMPORTANT]
+>
+>The endpoints in this guide are prefixed with `/core/ais`, as opposed to `/core/ups`.
+
+In order to use Experience Platform APIs, you must have completed the [authentication tutorial](https://www.adobe.com/go/platform-api-authentication-en). Completing the authentication tutorial provides the values for each of the required headers in Experience Platform API calls, as shown below:
+
+- Authorization: `Bearer {ACCESS_TOKEN}`
+- x-api-key: `{API_KEY}`
+- x-gw-ims-org-id: `{ORG_ID}`
+
+All resources in [!DNL Experience Platform] are isolated to specific virtual sandboxes. All requests to [!DNL Experience Platform] APIs require a header that specifies the name of the sandbox in which the operation will take place:
+
+- x-sandbox-name: `{SANDBOX_NAME}`
+  
+>[!NOTE]
+>
+>For more information on working with sandboxes in [!DNL Experience Platform], see the [sandboxes overview documentation](../../sandboxes/home.md).
+
+**API format**
+
+>[!IMPORTANT]
+>
+>You **must** include the `createAudienceMetaOnly=true` query parameter as part of the request.
+
+```http
+POST /audiences?createAudienceMetaOnly=true
+```
+
+**Request**
+
+>[!IMPORTANT]
+>
+>You **must** include the `Accept: application/vnd.adobe.external.audiences+json; version=2` header as part of the API request.
+
+```shell
+curl -X POST https://platform.adobe.io/core/ais/audiences?createAudienceMetaOnly=true \
+ -H 'Authorization: Bearer {ACCESS_TOKEN}' \
+ -H 'Content-Type: application/json' \
+ -H 'x-gw-ims-org-id: {ORG_ID}' \
+ -H 'x-api-key: {API_KEY}' \
+ -H 'x-sandbox-name: {SANDBOX_NAME}'\
+ -H 'Accept: application/vnd.adobe.external.audiences+json; version=2'
+ -d '{
+    "name": "Sample audience name",
+    "description" "A sample description for the audience.",
+    "namespace": "agora",
+    "originName": "Agora_Collaboration"
+ }'
+```
+
+| Property | Type | Description |
+| -------- | ---- | ----------- |
+| `name` | String | The name for the audience. |
+| `description` | String | An optional description for the audience. |
+| `namespace` | String | The namespace for the audience. |
+| `originName` | String | The name of the audience's origin. |
+
+**Response**
+
+A successful response returns HTTP status 200 with information about the newly created audience.
+
+```json
+{
+    "name": "Sample audience name",
+    "audienceId": "4a815904-f2f9-4237-82fb-55605bcc2ad7"
+}
+```
+
+| Property | Type | Description |
+| -------- | ---- | ----------- |
+| `name` | String | The name of the audience you created. |
+| `audienceId` | String | The ID of the audience you created. |
diff --git a/help/segmentation/api/external-audiences.md b/help/segmentation/api/external-audiences.md
diff --git a/help/sources/home.md b/help/sources/home.md
diff --git a/help/sources/tutorials/ui/create/adobe-applications/analytics.md b/help/sources/tutorials/ui/create/adobe-applications/analytics.md
