Skip to content

Commit 6273ea8

Browse files
update marketing consent
1 parent 7a4a588 commit 6273ea8

File tree

1 file changed

+11
-3
lines changed

1 file changed

+11
-3
lines changed

src/content/docs/integrate/third-party-tools/kinde-loops.mdx

Lines changed: 11 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -178,9 +178,17 @@ Now that you have decoded the JWT, you can use the extracted data to add contact
178178
- **Last Name**: Map to the `Last Name` field from the Code step output
179179
- **Source**: Set to `kinde` or `zapier` (optional)
180180
- **Subscribed**: Set to `true` (default) to ensure users receive emails
181-
- **User Group**: Map to the `Org Code` field from the Code step output (useful for segmentation by user or audience groups)
182-
- **User ID**: Map to the `User ID` field from the Code step output (useful for syncing with Kinde)
183-
- **Mailing list**: Add the user to a mailing list in Loops. Enter the list ID you copied from Step 1 and set the value to `true`
181+
182+
<Aside title="Marketing consent">
183+
Setting `subscribed` to `true` automatically opts users into marketing emails. Under GDPR and CAN-SPAM regulations, explicit consent is typically required before sending marketing communications.
184+
185+
**Best practices:**
186+
- Add clear consent language at signup (e.g., "I agree to receive marketing emails") and only set `subscribed` to `true` if the user explicitly consents
187+
- Alternatively, default `subscribed` to `false` and implement a double opt-in flow where users confirm their email address before receiving marketing emails
188+
- Log and store the user's consent timestamp and source (e.g., "signup_form", "profile_settings") for auditability and compliance purposes
189+
190+
If the user doesn't consent, set `subscribed` to `false`.
191+
</Aside>
184192
185193
6. Select **Continue**
186194
7. Select **Test step** to verify the contact is created in Loops

0 commit comments

Comments
 (0)