Skip to main content
Use this reference when integrating events into your application. Sending the correct type, action, status, and source values is what triggers tag assignment and workflow automation in MailerPath.

Event types

Type stringDescription
signupA new user signed up or was created.
purchaseA purchase, subscription change, or billing event.
core_activityGeneral product usage: logins, feature actions, content creation.
referralA referral was generated or completed.
feature_usedA specific product feature was accessed or used.
support_ticketA support interaction was created or escalated.
cartA cart was created, updated, or abandoned.
re_engagementA re-engagement signal was detected by your system.

Event payload fields

FieldTypeRequiredDescription
email or uidstringYes (one of)Identifies the contact. Use email when you have it; uid for anonymous or internal IDs.
typestringYesThe event category from the table above.
actionstringNoThe specific action within the event type.
statusstringNoThe outcome or state of the event.
sourcestringNoWhere the event originated (e.g., api, organic, cold_outreach).
featurestringNoThe product feature involved.
planstringNoThe subscription plan involved (e.g., trial, pro, enterprise).
amountnumberNoMonetary amount for purchase events.
upgradebooleanNoWhether the event represents an upgrade.
idempotency_keystringRecommendedPrevents duplicate processing on retries.
tsstring (RFC3339)NoEvent timestamp. Defaults to ingestion time if omitted.

Canonical action values

These are the action values used by MailerPath’s tag rules. Use them exactly as shown. core_activity
login
email_sent
campaign_created
automation_created
profile_updated
onboarding_started
onboarding_step_completed
demo_requested
feature_used
preview
explored
first_use
upsell_prompt_shown
re_engagement
dormant_detected
no_response
returned
cart
abandoned
support_ticket
multiple_tickets

Canonical status values

purchase
success
failed
cancelled
trial_started
re_engagement
at_risk
dormant
churned
low_frequency
success
core_activity
incomplete
feature_used
trial_started
advanced
single_feature
cart
abandoned

Canonical source values

organic
cold_outreach
api
referral
Source is free-form — use consistent values across your integration to keep filtering reliable.

Tag trigger reference

Each event type, action, and status combination can trigger tag assignment. Here are the most important mappings:
EventTriggers tag
type: signupLead, New Signup, Onboarding
type: signup, source: organicOrganic Lead
type: signup, source: cold_outreachCold Lead
type: purchase, status: trial_started, plan: trialTrial User
type: purchase, status: successConverted
type: purchase, status: failedFailed Payment, Churn Risk
type: purchase, status: cancelledChurned
type: core_activity, action: loginActive User
type: core_activity, action: demo_requestedHot Lead
type: feature_used, action: exploredFeature Explorer
type: feature_used, status: advancedPower User
type: cart, status: abandonedCart Abandoner
type: re_engagement, status: at_riskChurn Risk
type: re_engagement, action: dormant_detectedDormant User
type: re_engagement, action: returnedRe-Engaged
type: support_ticket, action: multiple_ticketsFrequent Support Contact
For the full tag rule set, see Tags and segmentation.

Minimal valid payloads by type

{ "email": "user@example.com", "type": "signup" }
{ "email": "user@example.com", "type": "purchase", "status": "success" }
{ "email": "user@example.com", "type": "core_activity", "action": "login" }
{ "email": "user@example.com", "type": "cart", "status": "abandoned" }
{ "email": "user@example.com", "type": "re_engagement", "action": "returned" }