The first screen you will generally see is the campaign list: from here you can get a quick overview of upcoming, active and previous campaigns, as well as a few core metrics to check performance.
You can filter, sort and search for campaigns as well as execute a few common actions directly from the list.
Editing, deleting, cloning campaigns
If you chose to clone a campaign you will be brought straight to the edit screen of the new campaign. By default any cloned campaigns will have
CLONE MM.DD prepended to the title.
Adding a new Campaign
To add a new campaign, click the plus icon in the top right. Check out the next few sections of our docs for help on each of the different steps that go into creating a campaign.
Ignoring frequency caps
As previously stated in the apps section, there may be a per-device frequency cap set for your app. If the campaign you are creating is of some special value and should ‘bust’ through these caps and be delivered no matter what, you can opt to ignore frequency caps on the first campaign creation screen.
Even if you select that a campaign does not respect frequency caps, it will still count with respect to the cap, so, for example, if you chose to ignore frequency caps for three campaigns which are sent at 00:00, 00:05 and 00:10 on a day and have a frequency cap of 3 messages per day, a user receiving all three campaigns will receive no further messages that day unless they are also set to ignore frequency caps.
Many campaigns are time sensitive and need to go out at a particular time on a particular day - think a Valentine’s or Mother’s Day promotion, or a campaign to simply boost the current number of active users. Other campaigns may benefit from users receiving campaign messages at different intervals after the trigger or broadcast moment. This can both ease the load on your servers, as well as keep a stable number of users coming back, rather than simply provide a short-term bump that doesn’t do much for the overall health of the app.
With our delivery pacing feature you can now set a campaign to add a random delay within a given time frame for every action of a campaign, and for every user. The distribution will be statistically uniform, so you may see some bunching at low volumes or early in a campaign’s run, but these will even out over the entire time window.
To add delivery pacing to your campaign simply enable the option in the campaign settings tab and add a time window and unit over which to spread delivery. If you are using AB testing or using multiple workflows for any other purpose this pacing strategy will be applied to all workflows by default. You can amend the settings for a particular workflow, or turn off pacing all together, in the AB testing distribution menu.
Delivery pacing will be used for every action in a workflow with a scheduled send out time.
Scheduling a campaign end date
In the last step of setting up your campaign you can elect to provide an end date and time after which no new devices will be targeted for this campaign or trigger the first campaign action in a campaign they had already been targeted for.
The end date will always be applied in the device’s local timezone, so there is no need to adjust for different time zones for campaigns targeting users in multiple countries or geographies.
While no new users can be targeted for the campaign or trigger the first action in the workflow after the scheduled end has been reached, any user who has already triggered the first action to be sent or any user who is already in the middle of a campaign with a multi-step workflow will still remain in the campaign till the end of the conversion window.
This means that to achieve a hard cutoff for a campaign with a delay on the first action, you will need to subtract this delay from your scheduled end. For example, to make sure that no new users receive actions from campaign which has a one day delay on the first message, from the midnight on the 31st December, you will need to set your end date to be midnight on the 30th of December. Similarly if your campaign has a delay of half an hour, you would set your scheduled end date to be half an hour before the desired cutoff.
Typically, campaigns run once for each user. If you have a campaign where you need to run it semi-irregularly, and maybe change content in between send-outs, you can restart a campaign by clicking on the restart icon in either the campaign list view or the campaign review screen. Any user who previously received the campaign will receive all the messages again as well as any new users who also match the targeting criteria.
Event and attribute viewers
Before setting any campaigns live for your users it is a good idea to test first to make sure that everything runs smoothly and as you would expect. While our reporting API is generally the go-to place for all things event related, we have also now introduced a simple event viewer to make this particular part of the day a little easier.
You will find the event viewer with your account settings and there is a shortcut in the menu at the top right of the app.
You can use an advertising id such as IDFA (iOS) or Google Play Advertising ID (Android), a 360dialog device ID (also known as
header.recipient_id if querying our reporting api directly) or an app instance id to filter for your device and check events from up to the last seven days.
By adding a campaign filter you will limit your results to only campaign-related events such as being targeted, sending or receiving campaign actions or clicking and converting on received messages. You can add more than one campaign id to your query.
There is a cache, so if you reload the same request over and over again you may get the same results until the cache is cleared; changing either the timeframe of your query, or including or excluding a different campaign to change things up, will bust through and get the latest data.
We also provide an attribute viewer where you can similarly provide a device ID and receive a chronological list of the personalisation attributes for that device.
We will only show the last 100 entries, so if you include an attribute that changes many, many times, you might find it easier to leave this one out of your query and check it separately.