Multi-channel Consent, Journeys & Messaging Analytics
Build Email and WhatsApp journeys using shared identities and measurable outcomes.
Open interactive lesson and quizWhat you will learn
- Configure channel-specific opt-ins and opt-outs
- Extend existing Send Flows without duplicating records
- Distinguish engagement, attribution and verified provider spend
Your team needs an order notification journey, separate channel subscriptions and defensible cost reporting.
Lesson 1
Independent subscriptions
Email unsubscribe, WhatsApp STOP affect their own channels. WhatsApp suppression blocks business-initiated messages; removing it does not restore old category opt-ins. Consent events record the source, evidence, actor and time.
Lesson 2
Journeys reuse the existing engine
Send Flows combines Email and WhatsApp messages with existing schedules, retries, field decisions, tasks, webhooks, entry rules, exit rules and conversion goals. A WhatsApp event check uses a prior message that occurs on every path. Simulation has no provider side effects. External providers and explicit consent are still required for live execution.
Lesson 3
One source transaction
Commerce notifications link to the original Order, payment and Finance invoice. A notification does not create another Order, invoice, receipt or coupon redemption. Secure customer-space links require customer authentication. Anonymous carts without a verified linked contact are not eligible for outreach.
Lesson 4
Observed metrics and cost controls
Sent, delivered and read are different provider-observed states. Read receipts may be disabled. Interactive replies are measurable; ordinary URL-button clicks are not supplied by Meta. Cost estimates use reviewed rates and atomic budget reservations. Actual charges come from confirmed provider statements. Last-touch revenue attribution does not prove a message caused the purchase.
Practice · Review a multi-channel journey
- Open a Subscriber record and compare email and WhatsApp consent
- Build a flow with WhatsApp send and reply wait branches
- Inspect the original Order and invoice used by a commerce rule
- Filter WhatsApp analytics and separate estimated cost from verified statement charges