Blueshift's Deep Links

Blueshift’s Deep Links (universal links on iOS and app links on Android) provide the ability to point customers to the optimal destination inside a mobile app on any OS, whether it is iOS or Android, to ensure a smooth end-to-end experience for the customer. You can create seamless channel-to-app experiences using this feature. For example, you can send a Blueshift deep link in an SMS or an email. When a customer clicks on the link, iOS or Android can launch your app and open the app's page that is mapped to the link. 

universal-links-workflow.png

Blueshift Deep Links are http/https URLs that take users to a page in the app if they click on one of them or launch them in a browser. If an email or text message that we send as a part of your campaign contains a Blueshift deep link and a user clicks on it, the mobile phone's OS can launch the app and take the user to the page that is mapped to it.

For example, you send an email message from our platform that contains a link to a product. When a user opens the email on a mobile device and clicks on the link, the mobile operating system launches the app installed on the user's device and opens the product's page in the app. 

How to set up a Blueshift deep link

Let's use a basic example of an email template. If you are familiar with email templates on our platform, you might be aware that we use the liquid template language and html to create an email template. If you want to provide URLs of the products, then the a possible liquid variable looks like {{products[0].url}}.

So, first copy the html into the template editor. Now, if you are familiar with the liquid template language, use the liquid variable in the template to link an HTML element with the product. For example:

<!DOCTYPE html>
<html>

<meta http-equiv="Content-Type" content="text/html; charset=utf-8">

<meta name="viewport" content="width=device-width">

<style>

  #main {

    background: #fff; min-height: 400px; padding: 10px;

    font-family:arial,helvetica,sans-serif;

  }

</style>

<body>

<div id="main">

    <br/><a href="{{products[0].url}}">Product URL (Recommendation)</a>

    {% assign url = products[1].url %}

    <br/><a href="{{url}}">Product URL (Liquid variable)</a>

    <br/><a href="https://www.blueshiftreads.com/products/juvenile-fiction-action-adventure-general/matilda">Product URL (Direct URL - Matilda)</a>

    <br/><a href="{{products[2].url}}" bsft-no-track>Product URL (bsft-no-track)</a>

    <br/>

    <br/><a href="https://www.blueshiftreads.com">Blueshift Reads URL without Product path</a>

    <br/>

    <br/><a href="http://blueshiftreads.com">blueshiftreads.com (http without www)</a>

    <br/><a href="https://blueshift.com/">blueshift.com</a>




    {% assign products_in_grid = products %}

    <br/><br/><h2>Regular Product Grid </h2>

    <shared_asset> bsft_generic_product_grid </shared_asset>

  </div>

</body>

</html>

If you look at the content, then you can see that we have used a liquid variable in multiple places. When we send this template to a user, this is how it looks: 

IMG_A550AAADC01E-1.jpeg

The Product URL (Recommendation) is linked using the liquid variable, {{products[0].url}} which is mapped to this URL in our system. When a user clicks on this URL, iOS or Android can directly open the linked page of your app instead of launching it in a browser. 

demo_ULinks.gif

As you may have guessed, a setup like this requires setting up URLs in our system, and configuring our SDKs. For more information on how to get these items done, take a look at information that we provide in our iOS and Android SDKs. Setting up product URLs and domain mappings is an activity that you may have done while setting up campaigns. However, if you need more information on that, reach us on support@blueshift.com

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request