Blueshift provides pre-built integrations with several Cloud Apps that you can orchestrate your in-house and custom marketing apps in campaigns/journeys. You can orchestrate cross-channel user journeys that include Email, Push, SMS along with Cloud App APIs. Blueshift supports API calls made to a third party REST API with a JSON payload. Cloud Apps can include 1:1 personalization and predictive content, including user attributes, predictive scores and content recommendations.

Cloud App Templates support Blueshift’s template language, Liquid, to include dynamic content. This allows including user attributes or catalog attributes in the template. Each template can also be customized with the output from a recommendation algorithm created using the Recommendation Studio.

Note

Any custom apps that you add must also use Cloud App templates to send messages in campaigns.

Add a Cloud App template

Note: You can add templates only for apps that are already configured and for which atleast one Adapter is added.

To view existing Cloud App templates or to add a new template, complete the following steps:

  1. Go to Creatives in the left sidebar and select Cloud App.

    cloudapps_templates_list.png

  2. Click +TEMPLATE.

    All apps that are installed and support Cloud App templates are displayed.

  3. Click the app to select it and add a template.

Note: You can also add a template when you are editing a Cloud App by clicking +TEMPLATE.

Edit a Cloud App Template

The Cloud App Template has the 4 following tabs using which you can design the content that will be sent to the customers, add details about how the content will be sent, and set up recommendations.

  • Content
  • Recommendation
  • General
  • External Fetches

Edit Template information

From the General tab, you can edit the template name, add an API endpoint, and select the Adapter according to your requirements. The API endpoint field supports liquid expressions.

slack_template.png

Unique Sent Identifier

Use a Unique Sent Identifier field under the Advanced Settings on the General tab to prevent spamming a user. In addition to preventing spams, setting the Unique Sent Identifier to email will catch users without emails early on and not attempt to send an email to those without email addresses.

For example, if you are sending a net promoter score (nps) survey to users through email and if the Unique Sent Identifier is set to email, then if there are multiple user accounts with the same email, it will only send an email to each email address once. If this field is set to none, it will send an email to all selected users, which might result in the same email address getting spammed by multiple copies of the same message.

By default, this field is set to none. Set the “Unique Sent Identifier” field to a clear user identifier. 

For example, if the Cloud App sends out email to users, then it should be set to “email”. If text messages are being sent, then it should be set to “phone number”. If there is no such field, it is a good practice to set it to “customer_id”, so that no customer in the database will be messaged twice.

Modify HTTP Headers

Use the Advanced Settings on the General tab to modify the default headers of the HTTP request. The default headers cannot be removed but you can change the value of these headers by adding an HTTP Header key-value pair. You can add multiple headers by clicking +HTTP Header.

The default headers are as follows:

  • User-Agent: Blueshift Webhook 1.0
  • Content-Type: application/json
  • Accept: application/json

If you are using a sample template, the HTTP Headers are already set correctly and you do not need to change them.

HTTP Method

This setting is available under the Advanced Settings on the General tab.

This refers to the HTTP method being used to make the API call. Blueshift’s Cloud App channel supports 4 HTTP methods: POST, PATCH, PUT, and GET.

For a custom app, the default HTTP method is “POST”.

If you are using a sample template, the HTTP Method is already set correctly and you do not need to change it.

Send payload as a url encoded form

By default, the payload is sent as a json object with the “Content-Type” header in the request set to “application/json”. If you want the payload to be sent as a url encoded string with the “Content-Type” header as “application/x-www-form-urlencoded”, select this checkbox under the Advanced Settings on the General tab.

Recommendation Algorithm

You can switch the recommendation algorithm from the “Recommendation” tab. A new recommendation algorithm can be created by using Recommendation Studio.

You can also see predictive scores and affinities that are associated with a customer's profile. You can use such values to include or exclude recommendations from the message that your customers receive via the Cloud App channel. Predictive attributes are available under user_metrics.

template_recommendationstab.png

Edit the Content

You can edit the JSON payload from the Content tab. The rendered preview of the JSON template will appear on the left hand side of the screen. It will be rendered for the user specified in the Recommendation tab (just like email).

Blueshift supports impression and click tracking for Cloud App templates, but they are not automatically tracked (like for emails). Instead, we provide impression and click callback URLs that you can include in the JSON payload:

  • Impression URL - {{tracking.impression_url}}
  • Click URL - {{tracking.click_url}}

Blueshift records an impression or click when an HTTP GET request is issued to the respective URL.

slack_template_content.png

External Fetch

Cloud App Studio has built-in support for external fetch. You can include one or more external fetch creatives, each of which calls a unique API endpoint. You can then use the content returned by your API endpoint(s) in your in-app messages using Liquid. For more information, see External Fetch.

template_external_fetch.png

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.