Event Tracking

Event tracking captures user behavior and feeds segmentation, workflows, and analytics. Clients send events to MailerPath so the platform can turn raw user activity into timely automation, smarter audience segmentation, and clearer reporting. Event data helps MailerPath decide who should receive a workflow, which tags should change, and what recent actions should appear in customer timelines. Before you send events, create and enable an API key in API keys. MailerPath uses that key to authenticate event requests and connect each event to the right contact.

​

Why Clients Send Events

• Trigger the right workflows at the right moment.
• Keep contact tags and lifecycle states up to date.
• Measure product usage, purchases, and other meaningful actions.
• Give support and success teams a better view of customer behavior.

​

What MailerPath Does With The Data

• Matches events to contacts using identifiers like email or user ID.
• Updates tags and audience state based on behavior.
• Queues workflow actions when event rules are met.
• Stores event history for analytics, timelines, and troubleshooting.

​

What Events Power

• behavior history and timeline context
• event-driven tag assignment and removal
• workflow trigger relevance
• troubleshooting of ingestion and processing

​

Data Flow At A Glance

1. Client sends event payload.
2. Event enters incoming processing pipeline.
3. On success, canonical event appears in Events.
4. On failure, Incoming Events exposes status and process_error.

​

Endpoint Families

Common client routes:

• POST /api/v1/client/events
• POST /api/v1/client/events/bulk
• GET /api/v1/public/authenticated/events
• GET /api/v1/public/authenticated/events/incoming

Use API Reference for exact auth and schema details.

​

Event Type Vocabulary

Supported event type values:

• signup
• purchase
• core_activity
• referral
• feature_used
• support_ticket
• cart
• re_engagement

Keep your event naming and enum usage stable across environments.