Skip to content

Commit 6e2156b

Browse files
authored
Merge pull request #2826 from Adobe-Enterprise-Docs/cja-consent-updates-luke
updates
2 parents 4e659cf + 91cd8d3 commit 6e2156b

3 files changed

Lines changed: 18 additions & 14 deletions

File tree

help/connections/consent-reporting-filtering/consent-analyze.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ topic_v2:
2929

3030
You can ingest consent policy data from Experience Platform Profile datasets into a Customer Journey Analytics connection.
3131

32-
After you [create a consent reporting and filtering configuration](/help/connections/consent-reporting-filtering/consent-configure.md), consent policy data becomes available as new components in the data views under the configured connection. You can use these components anywhere in Analysis Workspace if you have access to a data view where they exist.
32+
After you [create a consent reporting and filtering configuration](/help/connections/consent-reporting-filtering/consent-configure.md) and enable reporting, consent policy data becomes available as new components in the data views under the configured connection. You can use these components anywhere in Analysis Workspace if you have access to a data view where they exist.
3333

3434
## Consent policy components
3535

help/connections/consent-reporting-filtering/consent-configure.md

Lines changed: 8 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -35,14 +35,6 @@ System administrators can enable consent reporting and, optionally, consent filt
3535
>
3636
>Consent filtering excludes non-consenting visitor data at ingest time. Data that is excluded by filtering is not stored in Customer Journey Analytics and cannot be recovered for past dates. Review your marketing action selections carefully before you enable filtering.
3737
38-
## Prerequisites
39-
40-
Before you configure consent reporting and filtering, make sure that:
41-
42-
* You have system administrator permissions in Customer Journey Analytics.
43-
* The sandbox that you want to use contains a Profile dataset with consent policy membership data in the `consentPoliciesIDMap` field.
44-
* The connection that you want to configure already exists. For more information, see [Create or edit a connection](/help/connections/create-connection.md).
45-
4638
## Create a configuration
4739

4840
When you create a configuration for consent reporting and filtering, you select the sandbox and Profile dataset that contain your consent policy membership data, choose the connection or connections to configure, and choose whether to filter data for each marketing action. Customer Journey Analytics then creates the consent policy lookup dataset and the consent policy components automatically.
@@ -60,18 +52,22 @@ To create a consent reporting and filtering configuration:
6052
| **[!UICONTROL Name]** | Specify a name for the configuration. |
6153
| **[!UICONTROL Sandbox]** | Select the Experience Platform sandbox that contains the Profile dataset with your consent policy membership data. <p>A maximum of one consent policy lookup dataset exists per sandbox. Multiple configurations in the same sandbox share the same lookup dataset.</p> |
6254

63-
1. In the **[!UICONTROL Profile dataset]** section, select the Profile dataset that contains the consent policy membership data (the `consentPoliciesIDMap` field) that you want to report on. This Profile dataset is added to the connection that you select.
55+
1. In the **[!UICONTROL Profile dataset]** section, select the Profile dataset that contains the consent policy membership data (the `consentPoliciesIDMap` field) that you want to report on. When you enable consent reporting, this Profile dataset is added to the connection that you select if it is not already part of it.
6456

6557
1. In the **[!UICONTROL Connection]** section, select **[!UICONTROL Select a connection]**, select the checkbox next to one or more connections to configure, then select **[!UICONTROL Use connection]**.
6658

6759
Consent reporting and filtering is applied at the connection level. All data views under a configured connection inherit the same behavior.
6860

61+
1. In the **[!UICONTROL Data views]** section, click **[!UICONTROL Select data views]**.
62+
63+
1. In the Data views dialog, select the checkbox next to one or more data views that you want to use for consent reporting. These data views are automatically configured with Experience Platform consent data for reporting.
64+
65+
1. Select **[!UICONTROL Use data views]**.
66+
6967
1. (Optional) In the **[!UICONTROL Filtering]** section, you can enable filtering for the following marketing actions:
7068

7169
>[!NOTE]
7270
>
73-
>Leave both toggles unselected to enable consent reporting without filtering.
74-
>
7571
>When filtering for a marketing action is enabled, Customer Journey Analytics ingests a visitor's data only if the visitor matches **all** consent policies that apply to that marketing action. For more information, see [Consent filtering](/help/connections/consent-reporting-filtering/consent-overview.md#consent-filtering) in [Consent reporting and filtering overview](/help/connections/consent-reporting-filtering/consent-overview.md).
7672
7773
| Marketing action | Description |
@@ -81,12 +77,11 @@ To create a consent reporting and filtering configuration:
8177

8278
1. Select **[!UICONTROL Create]** to create the configuration.
8379

84-
Customer Journey Analytics automatically:
80+
If you enabled reporting, Customer Journey Analytics automatically:
8581

8682
* Adds the selected Profile dataset to the connection.
8783
* Creates a consent policy lookup dataset for the sandbox (if one does not already exist) and syncs policy names and descriptions from Experience Platform.
8884
* Adds the consent policy components (dimensions, metrics, and a derived field) to the data views within the configured connection.
89-
* Applies the **consent** internal label to the new components so that you can filter for them in the data view. For more information about internal labels, see [Labels and policies](/help/data-views/data-governance.md).
9085

9186
1. After the configuration completes, [view the consent policy components in the data view](#view-consent-policy-components-in-the-data-view) to verify that they are available.
9287

help/connections/consent-reporting-filtering/consent-overview.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -33,6 +33,15 @@ topic_v2:
3333

3434
Consent reporting and filtering uses the consent policy membership data stored in your Adobe Experience Platform Profile datasets to help you report on visitor consent and, optionally, exclude non-consenting visitors before their data is ingested into Customer Journey Analytics.
3535

36+
## Prerequisites
37+
38+
Before you configure consent reporting and filtering, make sure that:
39+
40+
* Your organization has licensed Adobe Healthcare Shield or Privacy & Security Shield.
41+
* You have system administrator permissions in Customer Journey Analytics.
42+
* The sandbox that you want to use contains a Profile dataset with consent policy membership data in the `consentPoliciesIDMap` field.
43+
* The connection that you want to configure already exists. For more information, see [Create or edit a connection](/help/connections/create-connection.md).
44+
3645
The following diagram and associated table show a high-level representation of how consent reporting and filtering makes consent policy data available in Analysis Workspace and filters visitor data at ingest time:
3746

3847
![Consent reporting and filtering overview](assets/consent-overview.png)

0 commit comments

Comments
 (0)