diff --git a/src/privacy/consent-management/configure-consent-management.md b/src/privacy/consent-management/configure-consent-management.md
index 497024a9ae..add7065e66 100644
--- a/src/privacy/consent-management/configure-consent-management.md
+++ b/src/privacy/consent-management/configure-consent-management.md
@@ -24,10 +24,11 @@ Before you can configure consent in Segment, take the following steps:
 > info "Limited availability of destinations"
 > AWS S3 and Engage destinations do not enforce consent preferences. 
 
-1. From the [Segment homepage](https://app.segment.com/goto-my-workspace/){:target="_blank”}, select the Privacy tab and click **Consent Management**.
-2. On the Consent management page, click **Create categories**.
-3. Confirm that you have completed the required prerequisites, and click **Next**.
-4. On the Create consent categories page, add the following information to the category form:
+1. For Analytics.js sources only - On the Source Settings page, enable **Destination Filters**.
+2. From the [Segment homepage](https://app.segment.com/goto-my-workspace/){:target="_blank”}, select the Privacy tab and click **Consent Management**.
+3. On the Consent management page, click **Create categories**.
+4. Confirm that you have completed the required prerequisites, and click **Next**.
+5. On the Create consent categories page, add the following information to the category form:
   - **Category name**: Enter a name that describes your use case for the data sent to this destination. This field only accepts category names that are 20 characters or less.
   - **Category ID**: In OneTrust, this is a string of up to five alphanumeric characters, but other CMPs may have a different format. This field is case sensitive.
   - **Mapped destinations**: Select one or more of your destinations to map to this category. Category mappings apply to all instances of a destination.