Create a campaign to deliver your Web Push message. To create a new campaign:
- From the dashboard, select Campaigns.
- Click + Campaign.
- From the Messaging Channels list, select Web Push.
The campaign page displays.
Define all the sections and publish the campaign.
The Start here section displays the setup information.
This section has the following parts:
- Start here: Displays the list of integrated and available browsers.
- Qualification criteria: Here you need to define the criteria for your target audience. You can deliver the web push notification based on Past behavior/Custom list or Live behavior.
- Set a goal: You can track your campaign conversion by setting up a specific goal. Setting a goal allows you to measure your campaign effectively against what you want to achieve in the campaign. This selection is optional.
Define the conversion period by selecting the Conversion Time. You can define your conversion goal further by filtering an event by event properties. For more information on event properties, see Events.
You must indicate the target audience for your campaign. You can specify your target audience from the Target segment section. Here, you can create a new segment or use a previously saved user segment from the segment list.
You can also create the target audience based on past user behavior and user properties or live (ongoing) user behavior. The latter helps send out real-time, triggered campaigns.
Delay > 24 Hours
We recommend creating a Past Behavior campaign for all campaigns where the delay is greater than 24 hours for a live inaction campaign.
For instance, you can create a live Inaction within time campaign that targets users as soon as they add a product to their cart but do not finish transacting within 10 minutes; the golden window within which most users transact on online platforms.
You can trigger a web push message based on an action. For example, a web push message with a promo code can be shown to a set of customers who have just completed a purchase. This will help in incentivizing an existing user. Moreover, such push messages make notifications more contextual and result in increased conversion.
You can also target users basis their past behavior. For example, you might want to target customers who have purchased a specific product in the past.
Using the With user properties filter in the Who section, you can segment your campaign to only reach users who meet specific criteria.
For example, you can send a Web Push notification to all the customers from Mumbai who are currently subscribed to Platinum membership.
The following table explains the various property types:
|Custom user profile properties that you define and send to CleverTap.
|Customer Type = Platinum
|Demographics filters include Age and Gender.
|Age = 25 to 40 years
Gender = Female
|User's coarse location. Filters include Country, Region, and City. CleverTap's SDK can automatically detect this from the user's IP address.
|Country = United States
State = California
City = San Francisco
|User's exact location. You can select a city, and then define the target radius. You can also select multiple cities. You can send this information using CleverTap's SDK. For more information, refer to the iOS and Android developer guides.
|Locations = San Francisco, USA; Paris, France
|Reachability filters include Has email address, Has phone number, Unsubscribed email, and Unsubscribed SMS.
|Unsubscribed email = No
|App fields filters include App Version, Device Make, Device Model, OS Version, and CleverTap SDK Version. This information is sent by CleverTap's SDK for each device that has your app which means a single user can have multiple devices associated with their user profile.
|OS Version = 10
To know more about what segments can be used, see Segments.
You can define the control group to compare and measure the results of your campaign. For more information on control groups, see Control Groups.
Sometimes, you want to send a message to only a subset of the qualifying audience (Target Reach) for a campaign or avoid sending it if the number of qualified users exceeds the specified number.
A relevant use case is a limited offer where you want to send a fixed number of coupon codes you want to distribute. If the total reach for your campaign exceeds the number of coupon codes you can distribute, you can limit the number of users who will receive the message to exactly the number of coupons you want to distribute.
Ensure that you set up a limit of 100 or more, regardless of the qualified user segment size. If the limit specified is less than 100, an error occurs.
You can create the following types of messages for your web push campaigns:
- Single Message
- A/B Test
- Split Delivery
- By User Property
In this campaign, a standard push message is sent to all users who qualify as your target audience. This message type is best for broadcast messages and for applications that do not vary campaign communication based on differences between properties such as language, geography, or any other user properties.
A/B testing helps you understand what type of message copy works best in the push messages to get clicks from users.
You can test up to three push message variants on a test group. The variant that gets the most clicks is declared the winning variant and is automatically sent to the rest of your target audience.
With split delivery, you can define what percentage of your audience receives the respective push message variant for that campaign duration. You can test up to three message variants.
If you would like to send different message variants to your target audience based on the user properties they possess, this campaign type is your best bet. A good example would be when you want to send a localized update to people based on their preferred language.
Similar to creating A/B test variants, click + Variant to add multiple variants based on a user property value. You can send up to 50 message variants to different users based on a user property. In the example below, we have used the Language user property so users with different language preferences will receive corresponding copies of the campaign in their preferred language.
After you select a particular message type, the web push editor displays. The web push notification text fields shown below can be personalized for every user based on specific user property or event property values. For more information, refer to User Profiles.
Enter all the required information.
Deep Link: Specify a deep link, so that upon a web push click, the user is taken back to one of your specific webpages, such as the checkout page. With dynamic replacements, you can take the user right back to the webpage of the product they just added to their cart and present them with an incentive to encourage the transaction.
Image Link: Specify an image link for the image you wish to send along with the web push message. The supported image ratio for the image is 4:3 and the most commonly preferred image sizes are 512x256 and 1440x720 pixels. The supported file formats are JPG, JPEG, and PNG for desktop. Only JPEG is supported for mobile.
Icon Link: Specify an icon link. This is primarily used for displaying brand logos. The recommended size of the icon is 192x192 pixels
Time To Live: It defines how long the push message is preserved for delivery if the device is offline or due to OEM device restrictions.
Custom key-value pairs: It lets you send custom data when a user clicks on the button. This data is not visible to the customers.
Some of the optional items only apply to a certain browser, such as Firefox, Chrome, or KaiOS.
Once you are all done setting up the content of your campaign in the What section, you have the option to send a test notification to any CleverTap user profile you have marked as a Test profile.
Click the Preview & Test button from the message editor to test a message.
You can set up the When to schedule the campaign's start and end.
Past behavior campaigns can be scheduled to run at a specific time:
- On a specific date and time.
- On multiple specified dates and times.
- Recurring at a periodicity you set.
Live campaigns can be set up on a specific event:
- In response to a user event.
- User event/inaction combination (e.g., abandoned cart scenario).
- Based on a date event property value of an event (for example, a reminder for upcoming travel booking).
You can also set the Do Not Disturb (DND) hours during which notifications from this Web Push campaign are prevented from going out, either by discarding them or delaying delivery to after DND hours complete, such as 9 PM to 9 AM.
If you want your campaign to adapt delivery times according to the user’s timezone, check the Timezone checkbox. For more information, refer to Delivery in User’s Timezone.
Since past behavior campaigns can have scheduled times, you have the option to stop a campaign delivery after a certain cut-off time, or even deliver at the specified time in the user’s timezone. For more information, refer to Delivery in User’s Timezone.
If you specify a recurring day for a campaign such as the 7th of each month, then the campaign will start for the specified day and ignore the creation date. This is a precaution to avoid sending a campaign unintentionally on a prior date.
After previewing the appearance of your overall campaign, finalize your campaign by clicking Publish Campaign.
Updated 3 months ago