Overview
There are many events that Zaius automatically understands or generates as part of integrations. These events are classified using a two-tier convention with the fields event_type (in APIs this is the same as type) and action.
This is the definitive list of what Zaius automatically knows about and how data should be sent if you are sending one of these types of events a user took.
E-Commerce & website events
| Event Type | Action | Description |
| pageview | (none) | User viewed a webpage |
| product | detail | User viewed a product page |
| product | add_to_cart | User added product to cart |
| product | remove_from_cart | User removed product from cart |
| order | purchase | User ordered (with line items) |
| order | cancel | Order was canceled for User |
| order | return | User returned item |
Email events
| Event Type | Action | Description |
| sent | Email sent to user | |
| open | Email opened by user | |
| click | Email link clicked by user | |
| abort | Email send was aborted to the user | |
| soft_bounce | Email soft bounced to user | |
| hard_bounce | Email hard bounced to user | |
| spamreport | Email was marked as spam by user |
Soft bounce vs hard bounce
A soft bounce means that the email address was valid, and the email message reached the recipient’s mail server. However, common reasons it bounced back include:
- The server was down.
- The mailbox was full (the user is over their quota).
- The message was too large for the recipient’s inbox.
Additional delivery attempts will occur for up to 72 hours. If a message is continuously deferred for 72 hours, the message will be dropped. If a customer experiences multiple soft bounces in a row, they will effectively experience a hard bounce and become ineligible.
A hard bounce occurs when the message has been permanently rejected either because:
- The email address is invalid.
- The email address doesn’t exist.
Hard bounced addresses are added to a suppression list. The customer will be marked as ineligible, and additional delivery attempts will not be made. This is done to protect your sending reputation as continuing to send to known bad addresses will harm your reputation with the receiver (e.g., Gmail, Outlook, etc.).
Mobile/Web Push events
| Event Type | Action | Description |
| push | sent | Push sent to user |
| push | open | Push tapped by user |
| push | add_token | User subscribed for push |
| push | remove_token | User blocked push for that token |
Subscription events
| Event Type | Action | Description |
| list | subscribe | User subscribes to a list |
| list | unsubscribe | User unsubscribes from a list |
Web Campaign events
| Event Type | Action | Description |
| web_modal | impression | User viewed web modal |
| web_modal | submission | User submitted form for modal |
| web_modal | click | User clicked a link that is not a form submission |
| web_modal | exit | User exited without any clicks or submissions |
| web_embed | impression | User viewed web embed (when at least 50% of the embed is on the screen) |
| web_embed | submission | User submitted the form in the embed |
| web_embed | click | User clicked a link that is not a form submission |