Managing SMS preferences effectively is essential for ensuring accurate communication with your customers. This guide provides instructions on updating SMS preferences in Blueshift, including mapping required attributes, formatting data for imports, and handling both subscriptions and unsubscriptions.
Please note
This page is exclusively for Blueshift's SMS Full Service customers. Click here for details on supported message types, tracked events, and additional information about the SMS Full Service.
SMS preferences mapping
To successfully import customer SMS subscription preferences, ensure that the following fields are included and correctly mapped in your import file:
| Source attribute | Blueshift field | Data type | Example value |
|---|---|---|---|
| standard_identifier | |||
|
phone_number (non-mandatory) |
phone_number | String | +15555555555 |
| sms_sender_id | sms_sender_id | String | 12345 |
| sms_subscribed | sms_subscribed | Boolean (TRUE/FALSE) | TRUE |
| sms_subscribed_at | sms_subscribed_at | Date (ISO 8601 format) | 2023-12-01T10:00:00Z |
| sms_unsubscribed_at | sms_unsubscribed_at | Date (ISO 8601 format) | 2024-12-05T08:25:07Z |
Mapping instructions:
-
Customer identifier: A customer identifier attribute is mandatory for Blueshift to locate and update the correct customer profile for SMS preferences.
Note: A phone number is not mandatory. SMS preferences can be updated even if no phone number is available in the customer profile. You can also add phone_number as a standard identifier to address SMS marketing use cases. You can define the required hierarchy for this identifier with respect to the other standard identifiers. Please reach out to your CSM to use phone_number as a standard identifier.- Phone number (optional): If provided, the customer’s phone number should be in string format and include the country code.
- SMS sender ID: The sender ID, which can be a short or long code, must include the country code.
- SMS subscribed: A boolean value indicating the customer’s subscription status (TRUE for subscribed, FALSE for unsubscribed).
-
SMS subscribed at: The timestamp indicating when the customer subscribed. Use the standard ISO 8601 format.
Defaults to the system timestamp if not provided. -
SMS unsubscribed at: The timestamp indicating when the customer unsubscribed. Use the standard ISO 8601 format.
Defaults to the system timestamp if not provided.
Example CSV file:
A sample CSV file containing these fields can be downloaded here: download sample CSV.
Notes
- This guide applies to importing SMS preferences not only through CSV files but also via customer profile imports from any supported sources, such as data warehouse integrations or file uploads. Additionally, SMS preferences can be updated using APIs for real-time data management.
- You can use a flat structure for SMS preferences. Nested structures are not required for this import method.
- Please make sure all date-related fields are correctly formatted in ISO 8601 (e.g., YYYY-MM-DDTHH:MM:SSZ).
- Based on your requirements, you can include any additional attributes relevant to your import scenario, such as first_name, last_name, or country.
Edge Cases:
- If you use multiple sms_sender_id values for a single customer, please ensure each sender ID is listed in a separate row with the appropriate subscription details.
- Incorrectly formatted attributes may result in failed imports.
These instructions will help you precisely map and import SMS subscription preferences as well as other customer data attributes.
Comments
0 comments