FAQs and troubleshooting

Blueshift is built for the latest version of Google Chrome on laptop or desktop. Chromium-based browsers such as Brave and Microsoft Edge may work, but are not officially supported.

Safari, Firefox, and all mobile browsers are not supported.

Known users are identified by customer_id (preferred), email, and/or device_id. Unknown users on the web are tracked via a first-party cookie. For non-identify events, include either customer_id or device_id in the event data.

Yes. Blueshift can link anonymous web activity to a known customer profile if the user clicks a URL in a Blueshift email that redirects to your site, and a matching customer profile with that email address exists.

Yes. Upload as many user attributes as needed, as frequently as needed, through the dashboard — as long as each row is mapped to an email address.

Small set of users: Search for the user in Customer Attributes and edit their status manually.

Large set of users: Create a CSV with the user's email and unsubscribe set to true, then upload via the Customer Attributes UI.

Yes. We recommend uploading no more than ~500K rows at a time. For larger datasets, split the file into smaller segments or work with the Blueshift team to upload via S3.

Only order and purchase data is required. Other event data is not needed. Add a separate row for each transaction in the CSV file.

Yes. All date fields must be sent in ISO 8601 format.

We recommend sending at least: identify (on login and sign-up), viewed_page (required on every page), viewed_product, add_to_cart, checkout, and purchase.

Set the Attribution parameters in Account Settings, then use the standard purchase event to track revenue.

View event logs by date — including any errors — in the Event Stream.

Required: product ID, name, URL, image URL, price, and sale price.

Recommended: category, on-sale status, and in/out of stock information.

Yes. However, product IDs must be unique across all catalogs.

Configure rules in catalog settings to map a field value to OUT_OF_STOCK or IN_STOCK. For example, set inventory = 0 to map to OUT_OF_STOCK, or map a status field where Inactive maps to OUT_OF_STOCK.

Send start_date and end_date in ISO 8601 format. Blueshift automatically sets the product to OUT_OF_STOCK when today's date falls outside that range.

Blueshift uses INSERT/UPDATE logic — new products are inserted and existing products are updated, identified by their SKU or product_id.

All data in Blueshift is available for segmentation. Retention periods: recent events (31 days), events with product_id data (183 days), messaging engagement (183 days), transactions (up to 10 years).

Segments refresh automatically. For segment-triggered campaigns, they refresh every 3–5 minutes.

Product-based events such as add-to-cart are retained for 183 days, and transactions for up to 10 years. For custom retention needs, contact the Blueshift team.

Yes. Click the Export User List icon on the segment page. The file reflects the most recent segment refresh.

Blueshift uses Liquid to insert personalized content — user, product, and transaction attributes. See Personalization using Liquid.

The same personalizations as email templates. Given size limitations, include only a few key attributes in push notifications.

Yes. Insert {{email_preview_link}} in your template to enable browser preview.

Yes. Each messaging channel has a Test Send feature. Personalization preview is available for email templates only.

Yes, by defining the UTM parameters directly in the campaign trigger settings.

Contact the Blueshift team to discuss available options.

Yes. See Blueshift's Deep Links for setup details.

When a customer installs or re-installs your app, a device_token is generated and sent to Blueshift. Push messages are sent to this token.

Yes. New tokens are appended as generated. A token is removed only when Apple or GCM notifies Blueshift it is no longer in use.

By default, Blueshift sends to only one device per customer — the last device used. To enable delivery to all active devices, contact support@blueshift.com.

See the dedicated Reporting FAQs article.