Access the CleverTap dashboard at: https://eu1.dashboard.clevertap.com
Admins can add new CleverTap managers under Settings > Users.
Useful links:
Two-factor authentication: https://docs.clevertap.com/docs/account-2fa
CleverTap User Documentation: https://docs.clevertap.com/docs/push
First, clearly name the push campaign. Best with date and identifiable content (e.g. event title, promotional offer, etc.)
Qualification Criteria: Select the option "Past behaviour/Custom list", if your push is targeting user actions that have already happened.
Set a goal: "charged" should be set as the goal in combination with the filter of an event property such as eventid, performanceid, tag. If only charged is selected without an additional filter, all purchases in the conversion period will be measured. Make sure that "amount" is selected as revenue property for charged. The conversion period should be between 2-5 days.
Save Draft: Make use of the "Save Draft" button in the upper right corner after every section, to avoid losing any important information you have already entered.
Add rules to your target segment. Most often you will need "Event (Did)" or "Event (Have Not Done)" and then selecting actions in the app that a user would have/have not already done to qualify. For memberships, age, city, or other general properties add the rule "User property" and then further define it.
The target audience can be made smaller or larger by combining AND (all must be met) or OR (at least 1 filter must be met) filter settings.
Users who did:
charged = purchased ticket
add to cart = has/had ticket in cart
show seatplan = viewed seating plan
show event = viewed event in app
click/show category = clicked on a category in the app
Event Properties:
eventId equals ID number of a production (event) in the easy-connect admin interface. Example: eventID = 12345
performanceId equals ID of an event's performance (singular date). Use only for events with several different performances when targeting a specific date.
tags contains name of a tag in the easy-connect console. Example: tags contains concert
Who Have Not Done:
charged (e.g.: exclude all who have already purchased for the pushed event/performance)
show event
User Properties:
Subscription contains ACTIVE
Age between/under/over xx
Marketing Push doesn't equal FALSE (when relevant for local data protection laws)
After each change, the potentially targetable users can be displayed on the right under "Calculate".
You can define an individual control group for each push, or define one for your entire account under Settings > Control Groups > System Control Group.
If you wish to save your targeting settings as a fixed segment, you can do this in the "Segment" section BEFORE you create a new push. These segments can then be added to your push notification.
Title and message must be filled in. The title should be short enough in the preview display so that it is not cut off (approx. 35 characters). The message should not exceed 3-4 lines (100-120 characters). The most important information should always be placed at the beginning or in the title. Important: eliminate every word that is not absolutely necessary.
Set these settings for Android:
Notification Channel to default
RenderMax checked (optional)
No additional settings need to be set under the Advanced iOS section.
This function defines where within the app a user is sent after tapping on the push notification. The Key is always deeplink_url and the boxes for Android and iOS need to be checked.
Available paths:
performances/<eventid> — Path to a specific production
app/home/booking/<eventid>/<performanceid> — Path to a specific performance booking options page
events/<categoryid> — Path to a category of productions
info-page/<categoryid> — Path to a category with action type "Flexible Route in the App"
Events – eventid: In the "event name" filter field, search for the event name. The event ID can be found between the image and the title in the table. The event must be visible/active in the app for the push notification to work.
Performances – performanceid: Click on the production in the event overview, then click on "Performances" in the event's sub menu. Note both the event ID and performance ID. Example path: performances/14002/48052
When all required fields have been filled, save your draft, then click "Preview & Test". Select "default" in the Notification channel drop-down and enter the email address of the user you wish to send a preview to (address must correspond to the one used to register in the app).
It is advisable to test each push on both an Android and iOS device. Test users should close the app before tapping the push notification to verify the correct destination.
Choose between "Send Now" or a scheduled point in time at a later date. If you haven't saved your push draft at this point, do it now — otherwise you won't be able to amend your scheduled push notification after finalizing it.
Best practice: send no more than one marketing push notification within a 24-hour period to prevent users from unsubscribing. Automated push notifications like ticket alerts should be exempt from this limit.
The Time to Live value can be used to extend the delivery period for reaching users who may be in a focus mode or "Do Not Disturb" mode.
For "Send Now" campaigns, delivery starts within 1-2 minutes. For pre-scheduled campaigns, the push notification is automatically sent at the desired date and can still be edited up to 5 minutes before its send time.
In-app messages can be used as additional information or notifications. Typically triggered by a live action performed by the user, shown when opening the app or navigating to a seat plan/event/category.
The target audience is defined by the live action they are taking within the app (e.g., the interstitial shows up upon app launch).
Select "Single Message" in the WHAT section, then choose a template. We recommend "Alert" or "Header"/"Footer" for very short text. General recommendations:
Shorter is better
Images should not be overused
You can also use customized HTML templates by selecting "Custom HTML Templates" and choosing a size.
A time span needs to be specified for displaying the message. The message can be set to display permanently (from "now" to "never") and manually ended if needed.
The frequency of displaying the message to users is determined in the delivery settings. "Exclude from campaign limits" is the best option if it should be shown every time the targeted activity is performed.
Create a Push Campaign and choose the "Live behavior" qualification criteria. Live actions in the app are taken as the basis. A shorter conversion window may be beneficial depending on the goal.
This feature can be used for cart reminders or promotional codes.
Targeting: All users who've had tickets in their shopping cart but haven't purchased them in the last 24 hours.
Content: To display the event name in the user's shopping cart, use the parameter "@Add to Cart - eventName | default: 'xy'". Replace 'xy' with a fallback term like 'your next show'.
Path into the App: Use: performances/@Add to Cart - eventId | default: "1"/@Add to Cart - performanceId | default: "1"
To see how a push notification performed, click on a completed campaign in your campaign dashboard. Note that some users' privacy settings will lead to their behavior and revenue not showing up in statistics.
CleverTap distinguishes between:
Click-through conversions: A completed push goal (mostly a ticket purchase) after the user tapped on the push notification.
View-through conversions: A completed push goal by a user who saw the push notification but didn't tap on it, yet went into the app and performed the desired action anyway. View-through conversions are usually higher.
