A trigger is an element which is required to start a Data Journey. Through a trigger, you will be able to begin a Data Journey which produces and uses data, and will automate campaign, contact, report processes.
Note: These are triggers for Data Journeys, for campaign Journey triggers click here.
- Import Finished
- Export Finished
- Campaign Sent
- Report Generated
- File Uploaded
- API Event
This trigger initiates at a specified time and date.
Double click on this element to set the date and time for this Data Journey to begin.
This trigger can be initiated to start on a weekday, date in a month and at different time intervals. Multiple selection is allowed in each of the options. You can either choose single or multiple weekdays and choose appropriate time slots to trigger it. Same way, you can do it for dates and hours.
With this trigger, a Data Journey is initiated when importing contacts in a specific list gets completed.
Multiple selections are allowed in this trigger.
With this trigger, a Data Journey is initiated when exporting contacts from a specific list or segment has completed.
This trigger is initiated when a campaign has been sent from your account. This trigger only applies to promotional campaigns, specifically priority sent campaigns and recurring campaigns.
You can select a specific campaign name, or you can include a repeated aspect of a campaign name to trigger a Data Journey. E.g. You have multiple campaigns with ‘Giveaway’ in the title, you can select ‘Starts With’ > Giveaway, and the trigger will be initiated whenever a campaign with ‘Giveaway’ is in the title.
This trigger displays all the email campaign reports as well as custom reports in the account. Any activity in the reports selected (when any selected custom report is generated you can do any action) will trigger the Data Journey.
This trigger will activate when a file is uploaded to your account folder on the Maropost SFTP server.
You will need to enter the file name and the file path (if using a sub-directory of the default /uploads folder)
This trigger allows you to initiate the Data Journey via an external resource.
The API endpoint displayed in the field is unique to the Data Journey and to your account.