User import
Learn about Braze’s various user import options, like CSV import, REST API, Cloud Data Ingestion, and more.
About HTML validation
Keep in mind that Braze does not sanitize, validate, or reformat HTML data during import, meaning script tags must be removed from all import data you use for web personalization.
When importing data into Braze that is specifically meant for personalization usage in a web browser, ensure that it is stripped of HTML, JavaScript, or any other script tag that potentially could be leveraged maliciously when rendered in a web browser.
Alternatively, for HTML, you can use Braze Liquid filters (strip_html
) to HTML-escape rendered text. For example:
1
{{ "Have <em>you</em> read <strong>Ulysses</strong>?" | strip_html }}
1
Have you read Ulysses?
Import options
Braze CSV import
You can use CSV import to record and update the following user attributes and custom events. To get started, see CSV Import.
Type | Definition | Example | Maximum file size |
---|---|---|---|
Default Attributes | Reserved user attributes recognized by Braze. | first_name , email |
500 MB |
Custom Attributes | User attributes unique to your business. | last_destination_searched |
500 MB |
Custom Events | Events unique to your business that represent user actions. | trip_booked |
50 MB |
Lambda user CSV import
You can use our serverless S3 Lambda CSV import script to upload user attributes to Braze. This solution works as a CSV uploader where you drop your CSVs into an S3 bucket, and the scripts upload it through our API.
Estimated execution times for a file with 1,000,000 rows should be around five minutes. See User attribute CSV to Braze import for more information.
REST API
Use the /users/track
endpoint to record custom events, user attributes, and purchases for users.
Cloud Data Ingestion
Use Braze Cloud Data Ingestion to import and maintain user attributes.
Legally required transactional emails
Do not send legally required transactional emails to SMS gateways as there’s a strong likelihood that those emails will not be delivered.
Although emails you send using a phone number and the provider’s gateway domain (known as an MM3) can result in the email being received as an SMS (text) message, some of our email providers do not support this behavior. For example, if you send an email to a T-Mobile phone number (such as “[email protected]”), your SMS message would be sent to whoever owns that phone number on the T-Mobile network.
Keep in mind that even though these emails may not be delivered to the SMS gateway, they will still count towards your email billing. To avoid sending emails to unsupported gateways, review the list of unsupported gateway domain names.