Below are notes on some of the specific campaign events.
In the send email action, there is an option to select Transaction or Marketing. A transactional email is one that can be sent to the contact multiple times. A marketing email is one that can only be sent to the contact once across multiple sources (e.g. another campaign). If the contact has already received this email from another source or the current campaign, the email will not be sent again and the contact simply progresses on through the campaign.
This action will allow you to send email to:
Emails sent through this action will not generate any statistics for contacts nor emails.
The email tokens will get populated with the real values including contact field values. But the email hash is bogus so the links like unsubscribe won't work correctly. It's similar behaviour like when a user sends itself a test email.
Action Send a Webhook with GET, POST, PUT, PATCH, DELETE, TRACE request support (curl). It was created based on GitHub discussion. Return true if page status code is 200/201. Data and headers values support contact field tokens (
Mautic 2.15.0 adds possibility to use contact's IP address as a token
Mautic 3.1.0 adds the possibility to send webhook payloads in JSON format. To send a JSON payload, add a header entry with the label
content-type and value
This action will permanently delete the contact who will trigger this action in your campaign flow, together with all the information Mautic knows about that contact. See in the segment docs about how to use this action to delete all contacts in a segment.
It will also delete the campaign event log record about that contact so this action will always show 0% progress in the campaign detail page. Even though it could have deleted some contacts. There is no record about it.
See the documentation on Focus items for an in-depth walk through
A campaign action was added in Mautic 2.14 which allows you to edit a contact's primary company via a campaign. Read also about Mautic's companies support.
Action update contact's primary company based on company custom fields.
If you try update company name, then action will add new or existed company with same name to contact and mark it as primary.
A pretty nifty feature which lets you jump to any campaign step in the campaign. You don't have to build reoccuring campaign workflows, just define them once and use the "Jump to Event" action!
Decisions are things the user does which we can track, like his page visit or wheter he opens an email or not.
Specify single or multiple pages you want the Contact to visit. Once a page that you specified is visited, the contact will advance to the next campaign step.
Note: The decision uses the OR operator between fields (Limit to Pages, URL, Referrer).
Specify and seperate visits from different devices. You can define the Device Type (desktop, smartphone etc.), Device Brand (Acer, Apple, Samsung etc.) and the Devise OS (IOS, Android etc.)
Choose the Asset you want the Contact to download before advancing in the campaign. Once the chosen Asset has been downloaded, the contact will continue in the campaign.
Note: You can choose multiple Assets to download, once one of them was downloaded the step is fullfilled.
Step needed to use campaign based Dynamic Content. Click here to read more about campaign based Dynamic Content
Define one or more forms, which the Contact needs to fill out.
Note: You can choose multiple Forms, once one of them was submitted the step is fullfilled.
These decision camppaign steps can only be used if the previous campaign action is "Send Email".
The contact opens up the email.
The contact clicks on a link within the send email.
If correctly setup in the Email settings, you can track if a contact replied to the mail you send to him.
Found errors? Think you can improve this documentation? edit this page on Github