Frequently asked questions

Which browsers can I use to access Blueshift?

The Blueshift app is developed to work on the latest versions of Google Chrome on laptop/desktop devices. Browsers on desktops and laptops that use the latest version of Google Chrome's rendering engine (Blink), such as Brave or Microsoft Edge, might work even though we don't officially support them.

Other browsers such as Safari or Mozilla Firefox are not officially supported. In addition, browsers on mobile devices such as tablets and smartphones are not supported.

How does Blueshift identify a user and corresponding activities?

• A known user is identified based on the customer_id (preferable), email, and/or device_id sent by you.
• For unknown users, we capture cookies on the web by setting up a first party cookie.
• For non-identify events, the event data must include either the customer_id or device_id.

Can you link anonymous user activity to a known customer?

Blueshift can link anonymous user activity on your website to a known customer profile if:

• A user clicks on a URL in a Blueshift sent email, and the link click is redirected to a page on your site.
• A known customer profile contains the customer's email address.

Reach out to support@blueshift.com or your CSM if you'd like to enable this feature.

Can I add user attributes on an ongoing basis?

Yes, you can upload as many user attributes as you want and as often as you want through the dashboard as long as you map them to an email.

How do I unsubscribe users manually?

• For a small set of users, search for the user using Customer Attributes and edit the status manually.
• For a larger set of users, create a CSV file with the email and with unsubscribe set to true. Upload using the Customer Attributes UI.

Can I use the dashboard to upload CRM data?

• Yes, we recommend that you upload no more than ~500K rows at a time.
• For larger data, split the file into smaller segments and/or work with the Blueshift team to upload via S3.

What information should be provided in historical data?

We only need order/purchase data. Other event data is not required. In the CSV file, add a separate row for each transaction.

Are there any specific formats for field types?

For dates, you must send the data in iso8601 format.

What type of events should we send to Blueshift?

We recommend sending at least the following events:

• identify (the event that passes the email/customer id of a user upon login and sign up),
• viewed page (essential for everything else to work, should be on every page),
• viewed product,
• add to cart,
• checkout,
• purchase

How does Blueshift track conversions/revenue?

To track conversions/revenue, you must first set the Attribution parameters in the Account Settings (https://app.getblueshift.com/dashboard#/account/other). Then use the standard Purchase event to track revenue.

How can we ensure that events we send are processed in Blueshift?

You can view event logs by dates, including errors, here: https://app.getblueshift.com/dashboard#/click_stream/index

What data should be included in the Inventory/Product catalog?

Product/Item data must include the product ID, product name, product url, image url, price, and sale price. We also recommend that you include the category, on sale, in/out of stock information.

Does Blueshift accept multiple product catalogs?

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

How do I set a product status to out-of-stock?

Set rules in the catalog settings to set a product as OUT_OF_STOCK or IN_STOCK based on one of the fields in the catalog file.

For example, consider that the catalog has an “inventory” field. Set the "inventory" field to "0" to set it to "OUT_OF_STOCK" and set the default value to IN_STOCK. Or use a field like “'status” where “Active” maps to IN_STOCK and “InActive” maps to OUT_OF_STOCK.

How do I expire/remove a product?

For each product you can send "start_date" and "end_date" fields when you upload a catalog. The expected format is iso8601 for these two fields. Blueshift uses these fields to automatically set a product to OUT_OF_STOCK if the current_date does not fall within that range.

What happens when we import a catalog again or update a catalog?

INSERT/UPDATE logic is used to INSERT new products and UPDATE existing products as identified by SKU/product_ID.

What data can I use to create segments?

All data sent to Blueshift by you (event, user attributes, product catalog, historical) is available for segmentation. Blueshift retains different types of data for varying durations:

• Recent events for identified or known customers (those linked to a user profile) are retained for at least 31 days.
• Events containing product_id information matching the catalog are retained for 183 days (e.g., adding a product to the cart or watching a video).
• Messaging engagement data (e.g., opens and clicks) is indexed for 183 days, while message “delivered” events are indexed for 31 days.
• Transactions are indexed for up to 10 years.

How often are Segments refreshed?

Segments refresh automatically based on the campaign type. For segment-triggered campaigns, they are refreshed every 3-5 minutes to maintain accuracy and reflect the latest data.

I have campaigns (e.g., Reactivation) where I need to segment users based on events greater than 90 days. How can I accomplish that in Blueshift?

Blueshift retains event data for specific durations based on the type of event. For example:

• Product-based events (e.g., add to cart) are retained for 183 days.
• Transactions are indexed for up to 10 years.

If your campaigns require segmentation beyond the standard retention periods, please contact the Blueshift team to explore custom options tailored to your needs.

Can I get a CSV file of all users in the current Segment?

Yes, click the Export User List icon to download a CSV file with all users in the current segment. The file will reflect the most recent data based on the segment refresh.

How do I personalize an email template?

Blueshift uses an open source templating language called Liquid to reference and create personalized content. You can include user, product, and transaction attributes in your email templates. To find out more, see Personalization using Liquid.

What level of personalization is available in a push notification?

The personalizations available for push templates are the same as that available for email templates. However, given the size limitations of a push notification, you might want to include only a few select attributes in the template.

Can I preview the email in a browser?

Yes, by inserting the variable {{email_preview_link}} in your template.

Can I preview my templates prior to launching a campaign?

Yes, there is a Test Send feature for each messaging channel. You can send the test user’s personalized email to your email address. However, personalization preview is only available for Email templates.

Can I overwrite UTM parameters in email template?

Yes, by defining the parameters in a campaign trigger.

Can you host a preference center for us?

Contact the Blueshift team to discuss options.

Do you support deep-linking within mobile apps?

Yes. For more information, see Blueshift's Deep Links.

How does a push message get delivered?

Whenever an app is installed (or re-installed) by a customer on the device, a device_token is created and is sent to Blueshift. Blueshift sends a push message to this device_token. If multiple customers sign into the same device, they are all assigned the same device token.

Do you store multiple device tokens per customer?

Yes, we append any new tokens. Device tokens are removed if we receive a notification from Apple or GCM that a token is no longer in use. A push notification is sent for each device token registered with Blueshift.

Can you tell me more about the Use last device token setting?

By default, Blueshift sends a push notification to only one device per customer even if the customer has multiple mobile devices. That device is the last device used by the customer.

To send a push notification to all active devices (Android and iOS) for a given customer, contact support@blueshift.com.

See Reporting FAQs.