Merge pull request #6509 from ens25212/plat-253179

PLAT-253179 - Audiences - AC++ Enhancements Offline Doc - REVIEW

Author: Caleb Kwan

help/profile/api/preview-sample-status.md

@@ -31,10 +31,10 @@ To learn more about profiles and their role within Experience Platform, please b
 
 ## How the sample job is triggered
 
-As data enabled for Real-Time Customer Profile is ingested into [!DNL Experience Platform], it is stored within the Profile data store. When the ingestion of records into the Profile store increases or decreases the total profile count by more than 5%, a sampling job is triggered to update the count. The way in which the sample is triggered depends on the type of ingestion being used:
+As data enabled for Real-Time Customer Profile is ingested into [!DNL Experience Platform], it is stored within the Profile data store. When the ingestion of records into the Profile store increases or decreases the total profile count by more than 3%, a sampling job is triggered to update the count. The way in which the sample is triggered depends on the type of ingestion being used:
 
-* For **streaming data workflows**, a check is done on an hourly basis to determine if the 5% increase or decrease threshold has been met. If it has, a sample job is automatically triggered to update the count. 
-* For **batch ingestion**, within 15 minutes of successfully ingesting a batch into the Profile store, if the 5% increase or decrease threshold is met, a job is run to update the count. Using the Profile API you can preview the latest successful sample job, as well as list profile distribution by dataset and by identity namespace.
+* For **streaming data workflows**, a check is done on an hourly basis to determine if the 3% increase or decrease threshold has been met. If it has, a sample job is automatically triggered to update the count. 
+* For **batch ingestion**, within 15 minutes of successfully ingesting a batch into the Profile store, if the 3% increase or decrease threshold is met, a job is run to update the count. Using the Profile API you can preview the latest successful sample job, as well as list profile distribution by dataset and by identity namespace.
 
 The profile count and profiles by namespace metrics are also available within the [!UICONTROL Profiles] section of the Experience Platform UI. For information on how to access Profile data using the UI, please visit the [[!DNL Profile] UI guide](../ui/user-guide.md).
 

help/segmentation/images/ui/composition-enhancements/enrichment-tree.png

@@ -0,0 +1,57 @@
+---
+title: Audience Composition Enhancements
+description: Learn about the enhancements made to Audience Composition with audience enrichment and faster activation.
+hide: yes
+hidefromtoc: yes
+---
+
+# Audience Composition enhancements
+
+You now have access to **two** enhancements for Audience Composition:
+
+- [Audience enrichment](#audience-enrichment)
+- [Faster activation](#faster-activation)
+
+## Audience enrichment {#audience-enrichment}
+
+Audience enrichment lets you output the array of values that let your profiles qualify for the audience you created.
+
+To add audience enrichments to your composition, select the topmost **[!UICONTROL Audience]** block within the canvas. After giving the audience, a name, select **[!UICONTROL Build rule]** to open the rule-builder canvas.
+
+![The Audience block is highlighted, as well as the Build rule button.](/help/segmentation/images/ui/composition-enhancements/select-build-rule.png)
+
+The rule-builder canvas appears. You can now create a filter criteria for your audience enrichment. This filter criteria **must** include an attribute that is within an array. The attribute being an array is dependent on your organization's schema structure. After you created your filter criteria, select **[!UICONTROL Delivery]** within the right-hand panel.
+
+![The rule builder canvas shows an example of an audience that can have enrichments. The Delivery button is also highlighted.](/help/segmentation/images/ui/composition-enhancements/view-delivery.png)
+
+ Choose the object array you want to use for enrichment from the list on the left panel. If there is only one array on the profile, the array is automatically selected for you. Select **[!UICONTROL Save]** to return to audience composition.
+
+ <!-- , as well as the fields you want to be used in the enrichment. -->
+
+![The schema tree for the enrichment tree is displayed.](/help/segmentation/images/ui/composition-enhancements/view-schema-tree.png)
+
+Within audience composition, your [!UICONTROL Audience] block is now a "[!UICONTROL Rule builder with enhancement]" type. Select **[!UICONTROL Publish]** to activate your audience with the next daily batch.
+
+![The Audience block is highlighted, showing that an audience with enrichment is added.](/help/segmentation/images/ui/composition-enhancements/rule-builder-with-enrichment.png)
+
+### Behavior details and guardrails
+
+Please keep the following details and guardrails in mind while using audience enrichment:
+
+- You can only use audience enrichment within audiences created within Audience Composition
+- The first block used within the composition **must** be a rule-based audience.
+- You **cannot** use any other operations within the composition.
+- Once published, you **cannot** edit the composition on the rule-based audience.
+  - You *can* copy the composition into a draft and edit the draft if you wish to make changes to the base composition or rule-based audience.
+- Only **one** object array can be used to generate the enrichment payload within a single audience
+  - The payload array can be nested within an object (up to seven layers within the profile schema), but **cannot** be contained in another array.
+  - The payload array **must** have 50 or fewer rows.
+  - All the columns output within the payload **must** be a primitive type.
+  - Only the first **twenty** columns of the array are outputted.
+- Only **ten** audience compositions are available for use at this time
+
+## Faster activation {#faster-activation}
+
+Faster activation lets you activate your audience to a downstream destination immediately after the composition has evaluated. As a result, if your destination is set to activate after segment evaluation, you no longer need to wait for 24 hours for the evaluation job to finish.
+
+For more information, read the [activate audiences to batch profile destinations guide](/help/destinations/ui/activate-batch-profile-destinations.md#export-full-files).