Send transactional messages

Transactional messages are non-promotional business-critical notifications that you send to your customers. They are automated, real-time communications that you send to customers to keep them updated about certain transactions or activities. Transactional messages are usually sent via email or SMS.

Typical use cases include the following activities:

  • Updates regarding purchases:
    • Order confirmation
    • Billing updates
    • Shipping alerts
    • Delivery confirmation
  • Booking information
  • Appointment confirmations
  • Subscription expiry notifications
  • Password resets

Set up your campaign

Use an API triggered campaign (event triggered) for your transactional messages.

Note: Ensure that you include the required user identifiers and the required details in the API call that you make.


Campaign messaging properties to set

You must set the campaign messaging properties in such a way that you can reach all your customers when required.

  • Select the following messaging properties to ensure that users are not excluded from being messaged:
    • Skip User Messaging Limits Check
    • Do not count towards messaging limits
    • Message users who have unsubscribed or have reported your emails as spam
    • Remove unsubscribe links from email header
  • Do not apply any global or campaign level holdouts.

For more information, see Messaging preferences for transactional campaigns.


Best practices

Here are some recommendations to ensure that your transactional campaigns run smoothly:

  • Use a simple campaign with a minimum level of triggers.
  • Keep your templates simple. If you include recommendations or external fetches in the templates, ensure that you set the template properties in such a way that messages will be sent even if no recommendations are available or if the external fetch fails.
  • Avoid using promo codes in your campaign.
  • Avoid adding delays to the triggers as customers prefer to receive transactional messages as soon as possible.
  • We recommend that you use an API triggered campaign instead of an event triggered to ensure that messages are delivered without any delays. When you send an event to Blueshift, there might be a delay as the event goes through theĀ  event pipeline and is processed by Blueshift.
  • If you do use an event triggered campaign, ensure that you mark the event as high priority for faster processing.
  • Set the campaign journey re-qualification settings to Multiple times concurrently to ensure that users are not skipped if they are already part of the journey.

Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.