Adding WhatsApp Marketing Consent to Your Klaviyo Flows

Modified on Sat, 6 Sep at 1:50 AM

Overview

Add a clear WhatsApp marketing consent field to your website and surface that consent inside your analytics/CRM (“client view”) so you can use it in segments, flows, and reporting.

Learning Objectives

Use the consent flag in flows and segmentation

Step-by-Step Guide

1) Add the Consent Field on Your Website

Create a checkbox where customers can opt in to WhatsApp marketing. Place it where you normally collect contact permissions (e.g., signup form, checkout, account page).

Label text: Must clearly mention “WhatsApp” and that it’s for marketing messages.
Default state: Unchecked.
Storage target: Save as a boolean (true/false) field in your backend/profile record.

Example field name suggestions

whatsapp_marketing_consent (boolean)
consent.whatsapp_marketing (boolean)

2) Surface Consent in Your Client View

Expose the stored field on each customer’s profile so teams and automations can use it.

Property type: Boolean / Yes–No
Display name: “WhatsApp Marketing Consent”
Value mapping: Checked → true, Unchecked → false

Tip: Klaviyo organizes properties under “Properties about someone,” ensure the dimension/property includes “WhatsApp” in the name so it’s easy to find (e.g., “WhatsApp Marketing Consent (true/false)”).

3) Use the Consent in Segments & Flows

Build a segment where whatsapp_marketing_consent = true.
In flows/automations, filter or branch using this property so only opted-in users get WhatsApp marketing.

4) Validate & Monitor

Submit the form yourself and verify the profile shows the property as true.
Trigger a test flow to confirm the consent filter behaves as expected.
Log timestamp/source for auditability if your stack supports it.

Technical Details

Data type: Boolean (recommended).
Suggested key: whatsapp_marketing_consent.
Where used: Segments, flow filters/branches, suppression logic, reporting.
Client view name: Include “WhatsApp” for clarity (e.g., “WhatsApp Marketing Consent”).

Troubleshooting

Consent not visible: Confirm the website form is saving to the correct profile field.
Segments empty: Check values are truly boolean true, not strings like "Yes".
Flow sending without consent: Re-check filters/branches and ensure the property key matches exactly.

Best Practices

Clear disclosure: The label should say it’s for WhatsApp marketing.
Unbundled consent: Keep WhatsApp consent separate from email/SMS.
Opt-out path: Provide simple instructions (e.g., reply STOP) wherever relevant.
Default unchecked: Do not pre-check the box.
Audit trail: Capture timestamp, source (page/form), and IP where possible.

Key Takeaways

Create a clearly labeled WhatsApp marketing checkbox, store it as a boolean consent property, surface it in your client view, and enforce it in segments and flows so only opted-in users receive WhatsApp marketing.