When you have created your campaign you have a number of ways to deliver this messaging to your users.
The most basic campaign is just to broadcast a message to any users matching your target criteria. For a campaign like this there are no futher settings and you can simply click ‘start now’ to begin the campaign.
This will simply continually attempt to find all devices who match the conditions of your campaign and send them the message once. Depending on the size of your userbase it may take up to a few minutes before you see the numbers go up.
For this type of campaign an important thing to remember is that if left active, this campaign will be out hunting for new prospects, ie. new users and users who newly match the target criteria. This can be a good thing or a bad thing depending on your use case. For example, a campaign targeting users who have logged in more than five times in a week and don’t have an app version less than 4.20 could run for as long as there are users who haven’t updated yet, this makes a lot of sense. For a simple broadcast message where you want a one-time communication bounded in time, the campaign should be disabled after around ten minutes so that an out-of-date message such as ‘look outside there’s a rainbow’ isn’t still being sent out to matching users who will only be disappointed when they run to their window to find no sign of that ephemeral rainbow.
Also note that if you have set any delay on your workflow actions the actual send out will be delayed by that value after a device has matched the targeting criteria.
You can set up a campaign to start on a particular day. In conjunction with send out times attached to your workflow actions you can use this to time messages to be sent on particular days and at particular times.
The good thing about a scheduled send is that even before sendout the campaign is actively hunting for devices matching the targeting criteria and following these closely. We won’t wait until the date and time to first look up in the databases, and so we won’t waste any time when it comes to sending the actual content.
Automating your campaign will link it to a particular event so that a device enters a workflow only once they have carried out a set action in the app. This can be a simple event like
d360_app_open, an event with filters for example
value is greater than
420, or a custom event you might be sending from your own app with its own filter properties, eg.
For these events and properties you will only be provided events, event properties and property values that exist for your app - but remember that the filter conditions do not compound in the selection boxes. This means that if you have set a filter for, for example,
device.os (device Operating System) to be
Android, when setting a filter for
device.osv (device OS version) you will also get values for operating system versions that exist for iOS or any other operating system you might be supporting so remember to sanity check your conditions with a colleague before sending something out.
You can set your automation campaigns to fire every time the user carries out the action or only once. If you choose to trigger the campaign each time the event occurs you can set a time interval of any number of minutes, hours or days until a user will be able to reenter the campaign, even if they still meet the targeting criteria and perform the trigger event during that time.