Welcome App Use Case with Cheetah Digital

The Welcome App Moment aims to send real-time communications to customers installing the app. These customers will receive a personalized welcome message to trigger their interest and get them excited about your brand. First impressions are important, so by interacting with them at this moment in time, they will feel embraced by your brand.

To achieve this, the following steps need to be taken. These steps include configuration on the Interactive Moments side as well as on the Cheetah Digital side. Some of these steps might already be set up for other use cases and can be skipped if needed.

 

Prerequisites

Note: These tasks are to be performed by technical marketers or expert users in partnership with our Technical Services team. Please contact your Zeta Global Representative to learn more.

Before you can use Moments templates, make sure the following items are in place. These are typically set up once by your system administrator or the Zeta Services team.

  • The Audience configuration - If unsure this has been set up, confirm with your system administrator that the correct Audience configuration is set up for your use case.

  • Integration – Ensure that the integration is successfully set up with Interactive Moments. Ask your system administrator if the integration is live and supports your specific use case.


Step 1: In Moments, create the Welcome App Moment

A Moment is a specific event in the consumer's journey at which timely communication or interaction with the consumer is triggered. It captures certain signals and applies rules, turning a specific event into a Moment you can act upon.

For the Welcome App use case, create a Moment in the Moments application, using the Welcome App template. The Moment is triggered when the customer installs the app, either immediately or after a set time.

  • For more general information on how to create a Moment and the general settings for a Moment, check out this topic
  • For more information on the Welcome App template specific settings, check out this topic.

 

Step 2: In your messaging workspace, create the necessary messages

When the Welcome App Moment occurs, it needs to trigger a journey that sends out one or more communications to the visitor. These communications need to be designed first.

Create the necessary email campaigns that you want to use in your Welcome App Journey. Which emails you require will depend on the setup of your Welcome App Journey itself, explained in step 3.

Note: This step requires basic knowledge on how to create messages in Cheetah Digital. For more information, please check out Creating Email Campaigns in the Cheetah Digital help center.

Some things to consider when creating these email campaigns:

1. The email campaign needs to be of type Event-triggered.

2. The email needs to be set up with Advanced Event Triggering activated to allow these messages to be personalized with data from the event. This is done on the Setup tab of the campaign:

Apply the above steps for all other messages used in the journey. For more details on creating email campaigns and personalization, please check out the corresponding topics on Creating Email Campaigns in the Cheetah Digital help center.

Note: For consistency, all messages used in the journey can be set up with Advanced Event Triggering on. However, when you choose to save the payload of the first email campaign in the journey (this is an option set when adding an email campaign to the journey), you can configure all subsequent messages with Simple Event Triggering on, and only use Advanced Event Triggering for the first email.

Technical note: When Interactive Moments is set up for your environment, a dedicated table is created, storing the event data. The data in this table can then be used to personalize the message. To be able to use this data, it needs to be sent first in the payload when sending signals using the API.

In the message, you can now add personalization fields from the events generated in the Moment:

Note: The table Moment_Events, joined to the recipient table, stores the data on event level and can be used directly as such to personalize your message.
The Moment_Event_Item table, joined with the Moment_Event table, stores all the items linked to an event.
These tables contain 1:N data and therefore to use this data for personalization in email campaigns, a looping block is required.

 

Step 3: In your Journey builder, create the Welcome App journey

Note: This step requires basic knowledge of how to create journeys in Cheetah Digital. For more detailed information on all the journey options, please check out the topic on how to build a journey.

In this step you create a journey with all the necessary components for your flow.

Things to consider when creating a journey triggered by the Welcome app Moment.

1. The journey must be of type Real-time.

2. The Start component of the journey must be triggered by the Welcome event.

3. In the Settings of the journey, check that the Event Subscription type is set to Subscribe Automatically

4. Also, in the settings of the journey, if there are multiple sources (for example multiple apps producing the same event) for the incoming moment, you need to select these apps in Settings > App selection > Event sources:



5. In the Audience Selection, you can filter out the audiences for who this journey will be triggered. Typically, this is the audience that has been selected in the Audience configuration in the Moments app. If you leave this field blank and there is more than one audience, the journey is triggered for all audiences.


 

Step 4: In your Journey builder, select the messages to be sent out in the journey

Once the Welcome app journey has been created and configured to launch when a Welcome App Moment comes in, you must replace all the messages in the journey with your own, as explained in step 2.

Things to consider for the messages in your journey:

1. You must make sure that the messages used in the journey, are configured for Event-based Personalization.This is done in the properties of the message. (Remember, when creating the message, the option Advanced Event Triggering had to be activated. This option in the message and event-based personalization in the journey need to be activated for data to come through to the message.)

Note: The Event-based Personalization option is toggled on but grayed out by default when the message has been configured for advanced event triggers only. If simple and advanced event triggers were selected for the message, this option will not be grayed out and you will have to toggle it on to ensure advanced event triggers are used.

When Save payload data is activated, you will also be able to see the payload in the activity log:

In addition, when Save payload is activated, you will be able to use simple event triggering for all subsequent emails. Only the first email in the journey needs to be set to Advanced Event trigger (see Step 2).