System delivery
EVENT LIST
By default, the 'System delivery' source is set up to incorporate the following events.
| Event name | Description |
|---|---|
Unsubscribed segment | We offer a feature for email templates that enables users to add an 'Unsubscribe' block. 'Unsubscribed segment' event is triggered when readers click the 'Unsubscribe' button in emails sent to them. Subsequently, these readers are collected into a segment for servicing marketing campaigns. |
Entered control group | 'Control group' is a crucial element in the marketing domain, and we enable users to activate this feature within the 'A/B Split' node. 'Entered control group' event is triggered when audiences enter the 'Control group' branch. Subsequently, users can segment these audiences and launch suitable campaigns. |
Destination frequency capping | In every destination, we offer a 'Frequency capping' feature to control the number of messages delivered. 'Destination frequency capping' event is triggered when a destination reaches its delivery limit (limit on user or journey). |
Invalid request tracked | We always encourage users to connect with destination vendors (such as G Suite email, Mailchimp, etc.) that they are familiar with. However, each vendor has its own distinct policy, and a request is only processed when it complies with their guidelines (such as required fields, correct formatting, etc.). 'Invalid request tracked' event is triggered when a request to a third-party vendor fails to adhere to their rules. |
Hard bounce tracked | 'Hard bounce tracked' event triggered when our system receives 'hard bounce error message' responses from third-party vendors. For example: Email channel: hard bounces typically result from issues such as invalid email addresses, domain name errors, or recipient mail server issues. SMS channel: sending an SMS to a phone number that is no longer in use or has been deactivated. |
Soft bounce tracked | 'Soft bounce tracked' event triggered when our system receives 'soft bounce error message' responses from third-party vendors. For example: Email channel: a soft bounce refers to a temporary failure in delivering an email to a recipient's address. It occurs when the recipient's mailbox is full, their server is temporarily down, or there is a message size issue. SMS channel: sending an SMS to a phone number that is temporarily unreachable due to network congestion. |
BO info updated by journey | 'Update info' node enables users to update audience data to two data objects, including 'customer' and 'visitor,' when these audiences meet specific conditions. 'BO info updated by journey' event is triggered when an audience's property is updated to the data object. |
3rd campaign tracking | For example, when a request is sent from CDP 365 to an SMS vendor, the vendor is expected to deliver the message 'Welcome to the store' to Customer A. After sending the message, the vendor forwards a response to CDP 365 regarding the status of the delivery. '3rd campaign tracking' event is triggered when a vendor returns a response about the status of a message. |
Delivery system error | When our system fails to deliver a message to an audience, 'Delivery system error' event is triggered. We rely on this signal to display a warning notification. Additionally, we may activate a suitable campaign to retarget the audience group. |
Ads might be viewed | For example, if a user configures a 'Welcome' popup to appear when an audience accesses the website for the first time. 'Ads might be viewed' is utilized to inform CDP 365 when an audience engages with the popup by viewing it. |
Ads delivered (impression) | Similarly to the above use case, 'Ads delivered' is used to notify CDP 365 when the popup is successfully delivered to an audience. |
Ads clicked | Following the same pattern as the previous use case, 'Ads clicked' event is used to notify CDP 365 when an audience interacts with the popup by clicking on it. |
Request update segment | 'Update segment' node enables users to push an audience group that meets specific conditions to a segment for retargeting purposes. 'Request update segment' event is triggered when an audience is updated to a segment. |
Missing receiver tracking | In order to send a message successfully, we require a targeted audience, content, and the receiver's address (phone number, email, etc.). 'Missing receiver tracking' event is triggered when a message is configured to be sent to an audience, but this audience lacks information about the receiver's address. |
Story frequency capping | If 'Destination frequency capping' event is triggered when a destination reaches its delivery limit, 'Story frequency capping' event is triggered when an audience exceeds the limit of times they enter a customer journey targeted to them. |
EXPLORE EVENT IMPLICATIONS ACROSS CHANNELS
Web personalization
| Event name | Description | Used to calculate metric |
|---|---|---|
Ads might be viewed | The event is triggered when an audience views a media template |
|
Ads clicked | The event is triggered when an audience clicks on a media template |
|
Ads delivered (impression) | The event is triggered when a media template is delivered successfully to an audience |
|
Email
| Event name | Description | Used to calculate metric |
|---|---|---|
Delivery system error | The event is trigger when an email template is delivered unsuccessfully by the system |
|
Hard bounce tracked | The event is trigger when our system recieves 'hard bounce error message' responses from email vendors |
|
Soft bounce tracked | The event is trigger when our system recieves 'soft bounce error message' responses from email vendors |
|
Ads delivered (impression) | The event is triggered when an email template is delivered successfully to email vendors |
|
Ads clicked | The event is triggered when an audience clicks on an email template |
|
Ads might be viewed | The event is triggered when an audience opens an email containing the email template |
|
Invalid request tracked | The event is triggered when a request to an email vendor fails to adhere to their rules |
|
Entered control group | The event is triggered when audiences enter the 'Control group' branch configured within an email journey |
|
Web notification/ App notification/ SMS/ Smart inbox/ FB messenger/ Viber/ Zalo/ WhatsApp/ Telegram/ Line
| Event name | Description | Used to calculate metric |
|---|---|---|
Delivery system error | The event is trigger when a message is delivered unsuccessfully by the system |
|
Ads delivered (impression) | The event is triggered when a message is delivered successfully to third-party vendors |
|
Ads clicked | The event is triggered when an audience clicks on a link included in the message |
|
Hard bounce tracked | The event is trigger when our system recieves 'hard bounce error message' responses from third-party vendors |
|
Soft bounce tracked | The event is trigger when our system recieves 'soft bounce error message' responses from third-party vendors |
|
Invalid request tracked | The event is triggered when a request to a third-party vendor fails to adhere to their rules |
|
Entered control group | The event is triggered when audiences enter the 'Control group' branch configured within a journey |
|
Webhook
| Event name | Description | Used to calculate metric |
|---|---|---|
Delivery system error | The event is trigger when data is delivered unsuccessfully by the system |
|
Ads delivered (impression) | The event is triggered when data is delivered successfully to third-party vendors |
|
Invalid request tracked | The event is triggered when a request to a third-party vendor fails to adhere to their rules |
|
Entered control group | The event is triggered when audiences enter the 'Control group' branch configured within a webhook journey |
|
Journey orchestration
| Event name | Description | Used to calculate metric |
|---|---|---|
Delivery system error | The event is trigger when a message is delivered unsuccessfully by the system |
|
Ads delivered (impression) | The event is triggered when a message is delivered successfully to third-party vendors |
|
Ads clicked | The event is triggered when an audience clicks on a link included in the message |
|
Hard bounce tracked | The event is trigger when our system recieves 'hard bounce error message' responses from third-party vendors |
|
Soft bounce tracked | The event is trigger when our system recieves 'soft bounce error message' responses from third-party vendors |
|
Invalid request tracked | The event is triggered when a request to a third-party vendor fails to adhere to their rules |
|
Entered control group | The event is triggered when audiences enter the 'Control group' branch configured within a journey orchestration |
|
Ads might be viewed | The event is triggered when an audience opens an email containing the email template |
|
Last updated