Your dashboard comes with a highly-intuitive 6-step campaign creation interface that enables you to customize, personalize and test your messages with great ease. Here are a few questions that are frequently asked by WebEngage users:
Yes, this can be achieved by setting up a Private SSP at your end. You can think of a Private SSP as a middle layer between WebEngage and your SSP (SMS Service Provider) that enables you to decrypt the encrypted phone numbers shared with your WebEngage account. This is a great way to maintain your user's privacy and protect their Personally Identifiable Information (PII Data).
(In case you're wondering - a Private SSP setup works for sending all types of campaigns, including transactional messages.) Here's how it works:👇
Step 1: Create and launch your SMS campaign. (Step-by-step guide)
- Once launched, we will send the messages to the endpoint URL specified as the Private SSP under Integrations < Channels < SMS section in your dashboard.
Step 2: Your Private SSP receives the messages and decrypts phone numbers of your target audience.
Step 3: The Private SSP forwards the SMS campaign with the real phone numbers to the SSP (SMS Service Provider) you're using to deliver the messages to users.
Step 4: The SSP receives the campaign and starts delivering the messages to the specified phone numbers.
Step 5: Users included within the campaign's target audience receive the message and start interacting with it!
- All interactions can be analyzed in real-time through the SMS Campaign's Overview section.
Step 6: The SSP pings back your Private SSP (Decryption Layer) with the delivery status of each message which could be any of:
Step 7: Your decryption layer forwards the delivery status for each user to your WebEngage dashboard through a Webhook.
Step 8: As soon as we receive data, it starts reflecting under the SMS Campaign's Overview section.
Yes! Here's how you can go about it:
Step 1: Create a custom domain that will exclusively be used to add links in your campaigns.
Step 2: Add a CNAME entry for the custom domain and point it to weurl.co with a TTL (
time to live) of 30 minutes in your DNS (Domain Name System) zone file. Doing so will ensure that your domain name is not replaced with weurl.co when the link is shortened.
Step 3: Add the domain to your dashboard under Settings > Campaign Custom Domain, as shown below.
And you're all set! (Detailed read)
Geotargeted messages can be sent through the Journeys section in your dashboard. You can easily leverage the Geofence Trigger block to start a Journey experience for users who enter/exit the fence and engage them with highly personalized text messages in real-time! (Step-by-step Guide)
You can easily combine multiple segments under Step 1: Audience while creating a campaign.
As highlighted above:
Step 1: Select Send to users in multiple segments and/or... against the field, Audience Type
Step 2: Select the logic by which you'd like to combine the segments: Send to only those users who are included in ALL Segments OR Send to users in ANY of the selected Segments
Step 3: Continue building your campaign
As highlighted above:
Step 1: Select Later against Delivery Time
Step 2: Specify the delivery date-time, select In User's timezone from the last dropdown and you're all set!
Step 3: Continue building your campaign.
Here are a few questions that are frequently asked by WebEngage users:
1. What happens when SMS is sent to a user who is out of network coverage / has switched off their phone?
All SMS campaigns are sent to an SSP (SMS Service Provider) intergated with your WebEngage account. So, both cases, the SSP will continue to attempt delivery for the Queueing Duration specified while creating the campaign.
In cases where the queueing duration expires before the user can be reached, the message is dropped by the SSP.
If you have disabled Queueing while creating the campaign, then the message will be dropped immediately by the SSP after attempting delivery for the first time.
In all cases, since the SMS was successfully delivered to the SSP, the message will be counted towards the performance indicator, Sent for the campaign.
If a user is sent multiple messages when they're out of network coverage/ their phone is switched off: All messages will be delivered back-to-back as soon the user is reachable (only if their queueing duration hasn't expired).
SMS campaigns may fail to get delivered to a few users for various reasons like, incorrect phone number, user is out of coverage area, SSP's monthly quota has expired and so on.
The term, Queued indicates the number of messages that have been sent to a campaign's target audience but are currently lined up for delayed delivery. It usually happens when DND Hours or Frequency Capping settings are applicable for a user.
Please feel free to drop in a few lines at [email protected] in case you have any further queries or feedback. We're always just an email away!
Updated almost 2 years ago