List of Emails
- ID: ID refers to the unique experiment ID for each email within an account which is assigned to each and every campaign.
- Name: This refers to the name given to an email campaign. This can be any generic name that the marketer chooses. When a user gets a push notification, this is the name that flashes on their screen.
- Schedule: This is the state of the campaign. A campaign could either be in draft, paused and completed stage.
- Sending: Toggle this switch to pause an already active campaign.
- Subscribers: For triggered campaign, toggle the switch to pause an already active campaign. For one time blast campaign, the switch resets to OFF once the campaign is complete.
- Open Rate: Count of users who qualify to receive the email campaign.
- CTR: CTR is the ratio of unique clicks and unique emails delivered.
- ESP: Campaign manager can choose to select custom ‘Email Service Provider’. WebEngage currently offers three options: sendgrid, mandril, Amazon SES.
- From Name: Sender’s name for the email campaign.
- From Email: This is the sender’s email ID. Email should be from the same domain which has been verified by the ESP.
- Subject: Subject line of the email campaign. Add tokens within the subject line to personalize subject line.
- Body: In the body of the email, an email creator can write their message to explain in detail the purpose of the email.
- WYSIWYG Mode: This is the default html editor that accepts plain text and supports rich text format.
- Raw Mode: When you choose this mode, the body of email will appear in a raw HTML format. This format allows custom css and html codes added as part of an email template.
- Insert Unsubscribe Link: Using this section, campaign managers can give their audiences the option to opt out of receiving emails.
- Upload: Using this section, campaign managers can upload various attachments like text files, images and videos with email.
Targeting rules for Email campaign
Targeting rules for email campaigns to include whom to show (segment) & when to show (triggering rules).
- Whom to show: Select a segment (pre-defined or new segment) to send the campaign.
- When to send: Emails can be send based on whether the campaign is one time blast or triggered in nature. One time blast can be scheduled to be sent at a pre-defined time stamp.
Email can be triggered based on a custom event and attribute value associated with an event. Combinations of attribute values can be used for creating triggering rules.
- ID: Distinct experiment ID associated with each SMS campaign.
- Name: This is any name given to a SMS campaign by a campaign manager.
- Schedule: This section displays the status of a campaign – draft, paused and completed.
- Sending: This is a toggle switch which can be used to activate or deactivate a campaign.
- Sent: Count of users to whom the campaign has been delivered
- Attempted: Count of users whom the SMS service provider had attempted to deliver.
- Failed: Count of users whom the SMS campaign was attempted but not delivered.
Create New Message
A. Transactional Message: Transactional Messages are messages that are triggered by an event initiated by a user or a change in a system attribute. These messages are triggered when a user interacts with an app or a website.
B. Promotional Message: Promotional Messages are messages that are sent with the intention of promoting a product or service.
SMS Service Provider: WebEngage allows you to deliver SMS campaigns with 3rd party service providers. WebEngage currently supports Twilio and SMSGupshup.
Sender: Registered sender name with respective SMS service provider.
SMS message can be personalised with tokens and event attribute values.
Targeting rules for SMS campaigns to include whom to show (segment) & when to show (triggering rules).
Whom to show: Select a segment (pre-defined or new segment) to send the campaign.
When to send: Messages can be send based on whether the campaign is one time blast or triggered in nature. One time blast can be scheduled to be sent at a pre-defined time stamp.
SMS messages can be triggered based on a custom event and attribute value associated with an event. Combinations of attribute values can be used for creating triggering rules.