Merge branch 'main' into PLAT-226814-Remove-Airship-Attributes-upgrade-message-from-docs

Author: vladfalon

help/ai-assistant/landing.md

@@ -36,6 +36,17 @@ Get started by reading the material in the links below to familiarize yourself w
     </tr>
 </table>
 
+### Hands-on guide to boost your productivity with AI Assistant
+
+>[!NOTE]
+>
+>This workbook was last updated on March 31, 2025. Since then, some capabilities may have evolved or expanded. Additionally, a few features referenced in this guide may still be in early access. If you encounter something that is not yet available in your environment and you are interested in exploring it, please reach out to your Adobe Account Team to request early access.
+
+Read the following for a hands-on guide on how to boost your productivity with AI Assistant.
+
+* [Supercharge your productivity with AI Assistant](./assets/landing/ai-assistant-lab-workbook.pdf)
+
+
 ## New features
 
 Get a glimpse of the newest enhancements in AI Assistant, including capabilities currently in the Alpha or Beta stages.
@@ -434,16 +445,6 @@ Watch the following videos for additional AI Assistant use case examples:
 
 >[!ENDTABS]
 
-### Boost your productivity with AI Assistant
-
->[!NOTE]
->
->This workbook was last updated on March 31, 2025. Since then, some capabilities may have evolved or expanded. Additionally, a few features referenced in this guide may still be in early access. If you encounter something that is not yet available in your environment and you are interested in exploring it, please reach out to your Adobe Account Team to request early access.
-
-Read the following for a hands-on guide on how to boost your productivity with AI Assistant.
-
-* [Supercharge your productivity with AI Assistant](./assets/landing/ai-assistant-lab-workbook.pdf)
-
 ## Next steps
 
 Browse the links below to further your understanding of AI Assistant use cases, capabilities, and much more.

help/catalog/images/datasets/dataset-retention-ttl-guide/manage-experience-event-dataset-retention-in-the-data-lake.png

@@ -99,8 +99,8 @@ To create a static schema with profile attributes, define the target attributes
 |`profileRequired` | Boolean | Optional | Use `true` if users should be able to map profile attributes from Experience Platform to custom attributes on your destination platform. |
 |`segmentRequired` | Boolean | Required | This parameter is required by Destination SDK and should always be set to `true`. |
 |`identityRequired` | Boolean | Required | Set to `true` if users should be able to map [identity types](identity-namespace-configuration.md) from Experience Platform to the attributes you defined in the `profileFields` array . |
-|`segmentNamespaceAllowList`| Array | Optional | Defines specific audience namespaces from which users can map audiences to the destination. Use this parameter to restrict Experience Platform users to export audiences from only the audience namespaces that you define in the array. This parameter cannot be used together with `segmentNamespaceDenyList`.<br> <br> Example: `"segmentNamespaceAllowList": ["AudienceManager"]` will allow users to map only audiences from the `AudienceManager` namespace to this destination. <br> <br> To allow users to export any audience to your destination, you can ignore this parameter. <br> <br> If both `segmentNamespaceAllowList` and `segmentNamespaceDenyList` are missing from your configuration, users will only be able to export audiences originating from the [Segmentation Service](../../../../segmentation/home.md).|
-|`segmentNamespaceDenyList`| Array | Optional | Restricts users from mapping audiences to the destination, from the audience namespaces defined in the array. Cannot be used together with `segmentNamespaceAllowed`. <br> <br> Example: `"segmentNamespaceDenyList": ["AudienceManager"]` will block users from mapping audiences from the `AudienceManager` namespace to this destination. <br> <br> To allow users to export any audience to your destination, you can ignore this parameter. <br> <br> If both `segmentNamespaceAllowed` and `segmentNamespaceDenyList` are missing from your configuration, users will only be able to export audiences originating from the [Segmentation Service](../../../../segmentation/home.md). <br> <br> To allow the export of all audiences, regardless of the origin, set `"segmentNamespaceDenyList":[]`.|
+|`segmentNamespaceAllowList`| Array | Optional | Allows users to map only audiences from the audience namespaces defined in the array to the destination. <br><br> Use of this parameter is discouraged in most cases. Instead, use `"segmentNamespaceDenyList":[]` to allow all types of audiences to be exported to your destination. <br><br> If both `segmentNamespaceAllowList` and `segmentNamespaceDenyList` are missing from your configuration, users will only be able to export audiences originating from the [Segmentation Service](../../../../segmentation/home.md). <br><br>`segmentNamespaceAllowList` and `segmentNamespaceDenyList` are mutually exclusive.|
+|`segmentNamespaceDenyList`| Array | Optional | Restricts users from mapping audiences from the audience namespaces defined in the array to the destination. <br><br>Adobe recommends to allow the export of all audiences, regardless of the origin, by setting `"segmentNamespaceDenyList":[]`. <br><br>If both `segmentNamespaceAllowed` and `segmentNamespaceDenyList` are missing from your configuration, users will only be able to export audiences originating from the [Segmentation Service](../../../../segmentation/home.md). <br><br>`segmentNamespaceAllowList` and `segmentNamespaceDenyList` are mutually exclusive. |
 
 {style="table-layout:auto"}
 

help/destinations/assets/ui/export-datasets/edit-schedule-control-highlighted.png

@@ -78,6 +78,16 @@ You can select from multiple types of audiences, depending on their origin:
 >title="Schedule"
 >abstract="Use the pencil icon to set the file export type (full files or incremental files) and the export frequency."
 
+>[!CONTEXTUALHELP]
+>id="platform_destinations_activate_schedule_weekly_messaging"
+>title="Weekly exports"
+>abstract="<sup>*</sup> Select the start date and subsequent exports will occur on that day of the week until the selected end date."
+
+>[!CONTEXTUALHELP]
+>id="platform_destinations_activate_schedule_monthly_messaging"
+>title="Monthly exports"
+>abstract="<sup>*</sup> 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."
+
 [!DNL Adobe Experience Platform] exports data for email marketing and cloud storage destinations as [different file types](#supported-file-formats-export). In the **[!UICONTROL Scheduling]** page, you can configure the schedule and the file names for each audience you are exporting.
 
 Experience Platform automatically sets a default schedule for each file export. You can modify the default schedule according to your needs, by selecting the pencil icon next to each schedule, and defining a custom schedule.

help/destinations/assets/ui/export-datasets/export-datasets-control-highlighted.png

@@ -0,0 +1,55 @@
+---
+title: Update the end date of dataset export dataflows (Action required by May 1, 2025)
+type: Tutorial
+hide: yes
+hidefromtoc: yes
+description: Learn how to update the end date for dataset export dataflows with a current end date of May 1, 2025.
+exl-id: 3f8ff535-3c54-47ac-b297-32f8298881db
+---
+# Update the end date of dataset export dataflows (Action required by May 1, 2025)
+
+>[!IMPORTANT]
+>
+>The action items on this page apply if your organization set up dataset export dataflows before the September 2024 release of Experience Platform.
+
+## What is happening?
+
+The [September 2024 release of Experience Platform](/help/release-notes/latest/latest.md#destinations) introduced the option to set an `endTime` date for export dataset dataflows. Adobe has also introduced a default end date of May 1, 2025, for all dataset export dataflows created *prior to the September 2024 release*. These dataflows currently display a message similar to the one shown below.
+
+![UI notification about the need to update the end date of the export dataset dataflow.](/help/destinations/assets/ui/export-datasets/update-end-date.png)
+
+**Action item**: For any of these dataflows, you must manually update the end date before it expires; otherwise, your exports will stop. Use the Experience Platform UI to identify which dataflows are set to stop on May 1, 2025.
+
+## Why am I being notified?
+
+Your organization has been identified as having active dataset export dataflows with an end date of May 1, 2025.
+
+## Use the UI to update the end date
+
+Use the Experience Platform UI to identify dataflows with an end date of May 1, 2025, and update them to a future date.
+
+### Find the dataflows that need updating
+
+Navigate to **Destinations > Browse** and look for the data type **Datasets** in the **Data Type** column, as shown below. Select the desired dataflows to inspect them.
+
+![Dataset export dataflows highlighted in the Browse tab.](/help/destinations/assets/ui/export-datasets/view-dataset-dataflows.png)
+
+### Update the end date of the dataflows
+
+To update the end date of dataflows:
+
+1. In the dataflows that you have selected for inspection in the previous step, select **Export datasets**.
+  ![Export datasets control highlighted in the Browse tab.](/help/destinations/assets/ui/export-datasets/export-datasets-control-highlighted.png)
+2. In the workflow, proceed to the **Scheduling** step and select **Edit schedule**. 
+  ![Edit schedule control highlighted in the Scheduling step.](/help/destinations/assets/ui/export-datasets/edit-schedule-control-highlighted.png)
+3. Choose a desired end date after May 1, 2025 and select **Save**.
+  ![Select end date control highlighted in the Scheduling step.](/help/destinations/assets/ui/export-datasets/select-end-date.png)
+4. Proceed to the end of the workflow and save your updates.
+
+For extensive information about the scheduling step, read the [export datasets UI tutorial](/help/destinations/api/export-datasets.md#scheduling). 
+
+## Use the API to update the end date
+
+### Find the dataflows that need updating
+
+### Update the end date of the dataflows

help/destinations/assets/ui/export-datasets/select-end-date.png

@@ -24,6 +24,7 @@ role: User,Developer
     - SQL Insights for extended app reporting {#sql-insights}
         - [Overview](data-distiller/sql-insights/overview.md)
         - [Query pro mode](data-distiller/sql-insights/query-pro-mode.md)
+        - [Accelerated Store overview](data-distiller/sql-insights/accelerated-store-overview.md)
         - [Send accelerated queries](data-distiller/sql-insights/send-accelerated-queries.md)
         - [Reporting insights data model guide](data-distiller/sql-insights/reporting-insights-data-model.md)
     - AI/ML feature pipelines {#ml-feature-pipelines}

help/destinations/assets/ui/export-datasets/update-end-date.png

@@ -0,0 +1,61 @@
+---
+title: Accelerated Store Overview
+description: Learn how to use the accelerated store in Adobe Experience Platform for fast, SQL-based insights using aggregated data. This page outlines its intended use, restrictions on identity and BI data, and best practices to ensure compliance with Adobe's data governance policies.
+exl-id: 4ec09bd2-b0a2-4559-9b4d-295369880317
+---
+# Accelerated store overview
+
+The accelerated store in Adobe Experience Platform is a performance-optimized storage layer available through the Data Distiller SKU. It is designed to hold pre-aggregated datasets, enabling fast, SQL-based insights and dashboard rendering.
+
+This document outlines how to use the accelerated store appropriately, explains why aggregated datasets are exempt from standard data hygiene processes, and emphasizes that identity data must not be stored. To stay compliant with Adobe guidelines, you must adhere to the data governance policies and usage restrictions outlined in this document.
+
+## Key capabilities {#key-capabilities}
+
+The accelerated store is purpose-built for performance and efficiency. It enables streamlined querying and reporting workflows by focusing on aggregated data. The list below highlights its core capabilities:
+
+- Serve high-performance dashboards and widgets using SQL queries
+- Store pre-aggregated datasets designed for recurring insights
+- Support custom data model creation for reporting use cases
+
+## Intended use {#intended-use}
+
+The accelerated store is designed **solely** for storing aggregated data that enables streamlined dashboarding and visualization. Its architecture is not intended to support complex workloads, such as business intelligence processing or data warehousing.
+
+>[!IMPORTANT]
+>
+>The accelerated store is not a replacement for the data lake or a general-purpose storage solution.
+
+## Usage restrictions {#usage-restrictions}
+
+To ensure compliance with Adobe's data governance model and licensing terms, the following restrictions apply:
+
+- **Do not store raw event data**
+- **Do not store identity data**
+- **Do not store personally identifiable information (PII)** such as email addresses, healthcare data, or customer identifiers
+- **Do not use the accelerated store to replicate your entire data lake**
+
+Only aggregated, non-identifiable data may be stored in the accelerated store. Aggregated datasets cannot be reverse-engineered to reveal the original source data, which makes them exempt from Experience Platform's centralized data hygiene processes.
+
+## Governance and compliance {#governance-and-compliance}
+
+Using the accelerated store outside its intended purpose may place your organization at risk of violating Adobe's license agreement and data governance boundaries. If data governance incidents occur due to unsupported usage patterns, your organization assumes full responsibility.
+
+Adobe is not be liable for any consequences arising from the misuse of this feature.
+
+To learn more about how to manage data responsibly in Experience Platform, see [Governance, privacy, and security in Experience Platform](../../../landing/governance-privacy-security/overview.md). This page outlines the services and tools that help you control your experience data in alignment with business policies, legal requirements, and development standards. For links to more detailed guidance on usage labeling and policy enforcement, visit the [Data Governance overview](../../../data-governance/home.md).
+
+## Best practices {#best-practices}
+
+To ensure efficient and compliant use of the accelerated store, follow these recommended best practices:
+
+- Use derived datasets to create pre-aggregated tables specifically tailored to your dashboard needs
+- Avoid using the accelerated store as a staging or backup location for raw datasets
+- Regularly review your usage to ensure alignment with Adobe's recommended guardrails
+
+## Next steps
+
+By reading this document, you've learned what the accelerated store is, its intended use for aggregated data in reporting scenarios, and the governance rules that must be followed to ensure compliant usage. To deepen your understanding and apply these guidelines effectively, explore the following resources:
+
+- [SQL Insights overview](./overview.md): Learn how SQL Insights enables performance-optimized reporting using aggregated datasets.
+- [Send accelerated queries](./send-accelerated-queries.md): Understand how to run queries against the accelerated store to power dashboards and widgets.
+- [Data governance and hygiene](../../data-governance/overview.md): Review Adobe's data hygiene policies and governance guidelines to ensure compliant usage.

help/destinations/assets/ui/export-datasets/view-dataset-dataflows.png

@@ -74,6 +74,7 @@ role: Admin
     * [Engage and acquire new customers without dependency on third-party cookies](/help/rtcdp/partner-data/prospecting.md)  
     * [Personalize onsite experiences for unknown visitors using partner-aided visitor recognition](/help/rtcdp/partner-data/onsite-personalization.md)
     * [Offsite retargeting of unauthenticated users](./partner-data/offsite-retargeting.md)
+    * [Offsite retargeting of unauthenticated users](./partner-data/unauthenticated-retargeting.md)
   * Profile enrichment {#profile-enrichment}
     * [Supplement first-party profiles with partner-provided attributes](/help/rtcdp/partner-data/supplement-first-party-profiles.md)
   * Personalized insights and engagement {#personalization-insights-engagement}