September Updates

You can now set up native integration with Snapchat and Blueshift for audience syndication. The direct integration provides a much more frequent audience update cadence – you can now update your custom audiences in Snapchat as frequently as daily. The direct integration will be available to customers outside US market as well. The native integration also enables error reporting so it’s much easier to spot and then resolve errors.

You can now enable SendGrid click tracking for all emails sent outside the Blueshift platform while using Blueshift for tracking clicks on all emails sent from the Blueshift platform. Thus, you will no longer need to choose between Blueshift or SendGrid for tracking clicks. You will be able to take advantage of both platforms.

The Blueshift developer portal is enhanced to provide an updated and intuitive user interface. The new UI has an improved left navigation and a dedicated page for each API endpoint. We have also added support for the EU API endpoint. You can now select the US data center or the EU data center as your Base URL when you test the APIs.

If you are a new customer in the EU, Blueshift has created a new app instance to help ensure none of your data ever leaves the EU region. By simply selecting EU on the login screen’s region selector, the app will redirect you to the EU instance of Blueshift. You can also access the app from app.eu.getblueshift.com and the APIs from api.eu.getbleshift.com.

If you are an existing customer of Blueshift, your URL remains the same and nothing changes for you. You can reach out to our Support team here at Blueshift to make sure they set up the EU region instance for you if you are a new customer.

In order to quickly view and differentiate between email subject lines, Blueshift has changed the subject line format for seed list and BCC emails to make it shorter. In the past, it was hard to differentiate which sends were from which email just by looking at subject lines. Now with the new release, we have changed the subject line format by moving actual content to the front as well as removing redundant information so it’s easier to view and compare. So moving forward, you can easily differentiate between two different email sends with a quick glance.

Earlier, the subject line for seed list and BCC emails had the following format respectively:

• Seed List- Seedlist: {$seed list name}, Original Email To: {$customer email address}, {$original subject line}
• BCC – Original Email To: {$customer email}, {$original subject line}

For example, if the subject line was “Best scooters in town”, the customer email address was ‘gavin.belson@hooli.com’ and the seed list was ‘Default Seed List’, the subject line would have looked like:

• Seed List- Seedlist: Default Seed List, Original Email To: gavin.belson@hooli.com, Best scooters in town
• BCC – Original Email To: gavin.belson@hooli.com, Best scooters in town

Going forward, the subject line will have the following format:

• Seed List – {$original subject line} : ( {$seed list name}, {$customer email address} )
• BCC – {$original subject line} : ( {$customer email} )

For the example above, the subject line will look like:

• Seed List- Best scooters in town: (Default Seed List, gavin.belson@hooli.com)
• BCC – Best scooters in town: (gavin.belson@hooli.com)

To help you track in-app message engagement more precisely, we have created a new metric, ‘dismiss’, so that you can now distinguish between instances when users are engaging with your in-app notifications by clicking on the CTA (call to action) buttons and instances when users are dismissing your notifications. Blueshift will now track click actions which lead to dismissing an in-app notification as ‘dismiss,’ as opposed to CTA ‘clicks’. You’ll also be able to create reports and segments based on users dismissing in-app notifications.

Apart from the native dismiss actions supported by the Blueshift SDK, you can also create custom dismiss actions. All you will need to do is use “blueshift://dismiss” as the URL for these actions.

In order to help you declutter catalogs that are no longer in use so that you can better manage the relevant ones, Blueshift now enables you to archive old catalogs. Archiving a catalog will hide it from the index screen, automatically set the status of all the items in the catalog to “out of stock” but it will not permanently delete the catalog and its items so that you can still refer to them if required.

We’ve released new versions of our mobile SDKs for both Android (V3.2.3) and iOS (V2.2.1). This new update includes customizable action buttons for push notifications, ‘dismiss’ action tracking for in-app notifications, faster image loading using the new image cache for Android and improved events ordering for iOS. For more information on the SDKs, please refer to our Android documentation or iOS documentation.