Skip to content

Commit ede41c4

Browse files
authored
Clarify consent handling for Permutive integration
1 parent 5396ff5 commit ede41c4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

dev-docs/modules/permutiveRtdProvider.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ as well as enabling settings for specific use cases mentioned above (e.g. acbidd
7171

7272
### Consent
7373

74-
If you are also using the [TCF Control Module](/dev-docs/modules/tcfControl.html), by default Permutive will not be blocked. If you choose to gate Permutive on their vendor id, 361, should add their vendor ID to your CMP.
74+
If you are also using the [TCF Control Module](/dev-docs/modules/tcfControl.html), by default Permutive will not be blocked as it will rely on the publisher purpose consents to read from storage. If you choose to gate Permutive on their vendor id, 361, should add their vendor ID to your CMP.
7575

7676
Before making any updates to your consent configuration, please ensure that your approach aligns with internal policies and current regulations regarding consent.
7777

0 commit comments

Comments
 (0)