Skip to main content

Marketing & destinations

Once profiles and events are in Masivo, you use that data to segment customers, run automated journeys, and sync audiences to the tools you connect.

Audiences

Audiences are groups of customers who match conditions you define — for example “purchased in the last 30 days” or “VIP tier members.” Membership updates when:
  • You change audience rules and recalculate.
  • A qualifying event arrives and the profile matches in real time (identified customers only).
  • You import a list from a file (static membership; not re-evaluated automatically).
  • Scheduled jobs remove customers who no longer match the rules.

Journeys and messages

Journeys can start from event triggers (e.g. a purchase or custom event) or from audience membership, depending on how you configure entry conditions. They send:
  • Email — campaigns from your templates.
  • Push — mobile notifications (requires a registered device token).
  • WhatsApp — approved template messages.
  • In-app — messages shown inside your app.
Steps can wait for a delay or condition (e.g. cart abandoned for 1 hour) before sending. Time-based transitions run on a schedule even when no new event arrives.
Journeys vs one-shot campaigns: Journeys are multi-step automations tied to events or audiences. One-shot audience sends (batch email, push, or WhatsApp to a segment) are a separate flow in marketing automation.

Push devices

Push delivery requires a device token from your mobile app. Register it via the customer devices endpoint. When a customer enters an audience with push consent, their token can be subscribed to that audience’s notification topic.

Connected destinations

When you set up integrations, audience and event data can sync to:
Destination typeCommon use
Ad platformsMeta, Google, TikTok remarketing and conversion tracking
Engagement CRMBraze and similar customer engagement tools
Your stackWebhooks, Amazon S3, analytics exports
Audience sync can send a full list after recalculation or incremental adds and removes between runs. Event and customer profile changes can sync in near real time when destinations support it. Sync respects the customer’s consent preferences where you collect them (see Privacy & consent). ← Back to overview