...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Table of Contents |
|---|
User guide:
- This document explains how to use the Notification Campaign feature for sending notifications to end-users based on the event group, event, site, or the type of contigent ticket they hold.
- This feature allows organizer to schedule a campaign to run on a defined date-time, provides the number of impacted users, and allows staff to set up the content and title of notifications per supported languages.
- Only an account with administrative privileges is able to access and create a campaign on this screen.
- The system only checks if the spectator has the NotificationTokenID connected with AppID to send the notification. Therefore, the user who hasn't downloaded or registered an account won't be able to receive any notifications.
...
...
- Organizers can search any campaign by its name and content language.
- The list of campaigns is ordered by Scheduled-Date and displayed with all related information including campaign ID, name, created date, scheduled date, status (scheduled, canceled,inprogress or sent), the number of impacted spectators, successfully sent and failed notifications (all those numbers are updated after the campaign is sent as they come from reporting).
When creating a campaign:
To schedule a notification campaign, follow these steps:
- Log in to your account with administrative privileges.
- Navigate to the Campaigns page.
- Click on the "New Campaign" button
...
...
- .
- Fill in the necessary details for the schedule, including the information of general details and scheduling options:
- Campaign name
- Redirection on click
- Filters: Event Group Name, Event Site, Event Name, Contigent (if any)
- If you already have a list of spectator email to send, choose file to upload instead
- Time for sending notification campaign (date, time & timezone)
- Define the Title & Content for default language of notification (This default content will be sent in case no other language defined)
- Select another language from drop-down list if you need to support other languages.
- In the language section, set up the content and title for the notification in the selected language.
- Repeat steps 6 and 7 for each supported language.
- Click on the "Submit" button to schedule the job.
- Double check on how many users will be impacted before saving your campaign.
Input general info:
Input notification content:
- If Redirection on click is External_URL, please make sure you provide the url for that at content section
Add new language:
How filter works:
...
- Event filters on the list of spectator that have tickets for that event, if none is selected, then campaigns targets all spectator having the Mobile App.
- Upload a CSV file of emails (e.g. input every emails in an Excel sheet under one column and export it to CSV), those email are used as a second filter
e.g. All users having ticket for the Event and are in the provided email list.
After creating a campaign:
Clicking on the Campaign Name to open a popup box displaying the campaign's contents in all languages.
Under action column, you can:
- Edit a scheduled campaign by clicking pencil icon
- Cancel a scheduled campaign by clicking close icon
- Download list of all impacted spectator sending status by clicking download icon
...
- While editing a campaign, if the text "CSV already uploaded" and the button "Download here" is visible, that means the CSV file the user previously input is still present and will be used as filter unless he uploads a new one.
- The table also shows the number of impacted spectators, successfully sent and failed notifications (all those numbers are updated after the campaign is sent as they come from reporting)
Campaign's statuses:
SCHEDULED: a campaign is successfully created
IN PROGRESS: a campaign is in progress to sent notifications to spectators on scheduled date-time
SENT: a campaign is executed
CANCELLED: campaign is cancelled before scheduled date-time
Split notification campaign's batches
In order to avoid performance issue, we recommend organizers to split whole campaign into smaller batch size.
How to use:
Going to Organizer Settings => Set the values for 2 keys push.notification.campaign.delay and push.notification.campaign.batch_size
Use case: Organizer want to send notification to all spectators of Match A (which already has 40000 spectators). It's recommended organizer to set up a batch size of maximum 20000 and delay time of 10 minutes.
...
What's on user's phone
...
- The following manual outlines the features of a push notification system for user's phones. When a campaign is created, the organizer can define the title and content
...
- of the push notification that will be sent to impacted users at a scheduled time.
- Depending on the Click Action
...
- configuration set by the organizer, the behavior
...
- of the user's app
...
- will vary when they tap on the notification
...
- . To ensure the best experience
...
- for your fans, refer to the explanations below.
- NONE: no action is triggered
- SCREEN_FAQ:
- One pop-up with correct title and content is displayed with OK and Cancel button
- Select OK: FAQ page is opened
- Select Cancel: pop-up is disappeared
- SCREEN_PROFILE:
- One pop-up with correct title and content is displayed with OK and Cancel button
- Select OK: My Profile screen is opened
- Select Cancel: pop-up is disappeared
- SCREEN_LIST_MATCHES:
- One pop-up with correct title and content is displayed with OK and Cancel button
- Select OK: My Events screen is opened
- Select Cancel: pop-up is disappeared
- SCREEN_NEXT_MATCHES:
- One pop-up with correct title and content is displayed with OK and Cancel button
- Select OK: The closest future event (with next event start time) screen is opened
- Select Cancel: pop-up is disappeared
- EXTERNAL_URL:
- One popup with correct title and content is displayed with OK and Cancel button
- Select OK: Open a page with configured URL by organizer
- Select Cancel: pop-up is disappeared