SMS Integration for Journeys

Prev Next
Your title goes here
Before starting the integration, you can read about SMS in Architect.

Before starting to use SMS as a channel in your journeys:

  • You must provide Insider with your users' phone numbers, GDPR opt-in, and SMS opt-in information. Otherwise, users cannot be matched with the user ID initially assigned by Insider. For further details, refer to SMS Integration.
  • The Insider One team will set a sender name to display to your users on SMS.
  • The Insider One team will configure a keyword and a short code for users to opt out of SMS (e.g., Send STOP to 5555 to stop receiving messages).

If your company obtains your users' consent in compliance with the local regulations, make sure to pass the GDPR opt-in field to Insider. If you want to stop collecting and processing the data of an identified user, the GDPR opt-in field should have the false value. Insider cannot be held liable if these obligations are not fulfilled and reserves the right to seek compensation from your company.

Your title goes here
Every country has its own regulations for sending marketing SMS. If your brand is subject to additional regulations and steps to complete, please inform the Insider One team.

Capabilities and integrations

See the table below for the capabilities that would require additional integrations:

RequirementBasic SMSDynamic custom contentCross-Channel (App & Web)Omni-Channel Segmentation (App & Web & CRM)Unification
Insider TagYesYesYesYesYes
Mobile SDKNoNoYesYesYes
Insider ObjectYesYesYesYesYes
Upsert User Data APIConditionalConditionalNoYesConditional
Conditional status is provided as an alternative data ingestion method, tailored to your needs and applications.

Frequently Asked Questions

Q: What type of dynamic content can I use in the message?
A: You can use default and custom attributes and event parameters, coupon codes, and recommendations.

You can read the SMS FAQ for further questions.