Update the Prerequisites steps to include "Destination Filters" #6703
Conversation
prigiattiperrut
requested review from
forstisabella
and removed request for
a team
|
@prigiattiperrut @forstisabella , if i am reading the changes correct, i dont think it is in the suggested spot. I thought we wanted to add this to the Pre-req steps? no? I think that is the right spot, plus we should call out, if using Analytics.js and Device Mode destination, enable destination filters. |
| 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**. |
There was a problem hiding this comment.
| 1. For Analytics.js sources only - On the Source Settings page, enable **Destination Filters**. | |
| 1. _For Analytics.js sources only_ : Navigate to your Analytics.js source and select **Settings > Analytics.js**. Enable **Destination Filters**. |
There was a problem hiding this comment.
I agree with @atitsh - this seems like the right information, but is just in the wrong place. I think you could add this one of two places:
- In the prerequisites section, as the last step
- In the section about wrappers, as a note under the link to the A.js wrapper link
|
@forstisabella - i like that, lets move these changes to those 2 places and publish the doc. best to publish a patch now and not wait for next week's tuesday release train. |
|
closing this PR, as the information was replicated in #6706. Thank you for catching this issue and drafting the language @prigiattiperrut! |
Proposed changes
Added a required step to the Prerequisites section, so customers are aware that enabling "Destination Filters" is necessary.