Customer.io

Open your first project by wiring your customer data into one place. Send profiles and events through the HTTP API, or connect your CDP—Segment, RudderStack, mParticle, or Hull—to stream traits in real time. Define identifiers, set consent and locale fields, and map event properties you plan to reference in messages. Import historical records to backfill behavior. Create a couple of test people, trigger key events, and confirm everything on their timelines: attributes, events, deliveries, and attribution notes. When the data looks right, lock in naming conventions and roll to production.

Next, build audiences and flows. Use rule-based filters to group people by attributes, behavior, and time windows; combine AND/OR logic and relative dates. Membership in these segments can drive entry to automated journeys. In the visual builder, lay out triggers, delays, branches, and steps for email, SMS, and push. Personalize each touch with merge fields, conditional logic, and content blocks that react to event data. Add webhooks to tap your internal services, and drop in actions that update profiles or tags. Need to troubleshoot a single person? Open their record to pause, remove, or resend messages and inspect event-by-event logs.

For high-priority system messages, set up the transactional endpoint to send receipts, password resets, or alerts with guaranteed speed and flexible templating. For one-off announcements, create a broadcast that can deliver across channels and schedule by each recipient’s local time. Add frequency caps, link tracking, UTM parameters, and seed lists. Before launch, preview with sample data, run test sends, and configure experiments—A/B or multivariate—to settle subject lines, layouts, or copy across channels.

Measure and improve without leaving the app. Compare campaigns and broadcasts side by side, view cohort trends, and spot top performers in the message ranking view. Drill into any send for opens, clicks, conversions, and attribution. Watch delivery logs and failures in real time to catch issues early. Feed metrics to connected tools and export reports for stakeholders. Iterate often: duplicate flows, adjust segment rules, and rerun tests to lock in gains.