Start Elements
Name | Icon | Explanation | Example Use |
Subscription | You can start an automation based on a subscription. | Welcome campaign starting at signup (confirmation) | |
Contact filter affliation | You can start a marketing automation with adding a contact to a contact filter. You can than chose an interval for starting the automation (once, daily etc.) | Marketing flow aimed at birthdays | |
Contact Event | You can start an automation based on a contact event. That is a transaction related to a specific contact, for example, buying a ticket. | Marketing flow aimed contacts completing a purchase | |
API Call | You can start an automation based on an API call. Meaning an external system will make a call on the Maileon API to start the automation. | Marketing started by visiting the website |
Action Elements
Name | Icon | Explanation | Example Use |
Wait for time period | Wait for a pre-defined time period | Wait 3 days for contact to open email. | |
Wait for a data | Wait until a specific day to start an event | Wait untill 3.45 pm to take action | |
Wait for a certain time period | Wait until a specific day to start an event | Wait untill 25/12/2021 to take action | |
Wait until a contact_event happens | Wait untill a contact event happens | Wait untill a ticketing transaction arrives | |
Wait until a response event | Wait until on an email response | Wait until someone cliks on an email | |
Unsubscribe a contact | Unsubscribe a contact |
| |
Delete a contact | Delete a contact |
| |
Blacklist a contact | Blacklist a contact |
| |
Change contact field value | Update a contact field | Update the field interested in offer. | |
Contact field function | (Re)calculate a specific numeric field | Open email = add 1 point to a field | |
Webhook | Send data to a webhook | Update the contacts through the supporter API | |
OneSignal Push | Send push message to mobile app | Send welcome message to app when scanning season ticket | |
Trigger-mail Dispatch | Trigger email dispatch | Send thank you email to fan after buying season ticket | |
SMS dispatch |
| Send a personalized sms (additional costs apply) | Remind someone to renew their season ticket with a final SMS |
Branch Elements
Branching allows you to differentiate the Marketing Automation flow based on information about the contact.
Name | Icon | Explanation | Example |
Branching according to contact field value | Spilt workflow based on field values | Different email per gender | |
Branching by contact event value | Spilt workflow based on contact event value | Different email per product in order | |
Branching by contact event existence | Spilt workflow based on contact event value | Different email for contacts with completed purchase | |
Randon branching | Random split | Create different workflow for A/B testing | |
Split branching | A/B testing split | Set-up A/B test for automation | |
Branch by contact preference |
| Branche on the existence of a contact preference (yes/no) | If someone doesn’t have a specific preference, don’t include them in a follow up message. |
Further Elements
Name | Icon | Explanation | Example |
Program End | End |
|