Renewable quest

Create an expression that returns the number of products purchased

In this part of the process, create an expression that returns the number of products purchased from the Paper_towels category. This expression uses the aggregate and expression created in the previous steps.

1. Go to Analytics > Expression > New expression.
2. Enter the name of the expression as [UC]Products purchased
3. Leave the Expression option at default (Attribute).
4. Build the following formula of the expression:

   

5. Save the expression.

Create an expression that determines the number of products required to complete the quest

In this step, create an expression that checks if the number of products bought is equal to or greater than the target amount, indicating whether the customer has met all the conditions to finish the quest.

1. Go to Analytics > Expression > New expression.
2. Enter the name of the expression as [UC]Comparing amount of products bought
3. Leave the Expression option at default (Attribute).
4. Build the following formula of the expression:

   

5. Save the expression.

Create a workflow

In this part of the process, create a workflow to determine if the customer has successfully completed the quest. The condition that needs to be met is the purchase of 10 products from the “Paper_towels” category. If the condition is met, two events will be generated for the customer:

• An event quest.renewableComplete will be generated to inform about the quest completion.
• An event points.upcharge will be generated to assign 1000 loyalty points to the customer.

1. Go to Automation > Workflows > New workflow.
2. Enter the name of the workflow as [UC]Renewable Quest.

Define the Profile Event node

The workflow will be triggered by the product.buy when customers will purchase any product from the Paper_towels category.

1. As the first node of the workflow, add Profile Event.
   1. From the Choose event dropdown menu, choose the product.buy event,
   2. As the parameter, choose category,
   3. As the operator, choose Equal,
   4. As the value of the parameter, add Paper_towels,
2. Confirm by clicking Apply.

Define the delay

We need to set up a short delay of 10 seconds to ensure that events have been calculated before proceeding to the next condition in the workflow.

1. Add the Deley node,
   1. Enter the name of the delay as 10s,
   2. Set the Delay number as 10,
   3. In Unit section choose Second,
2. Confirm by clicking Apply.

Define the Profile Filter node

In this part of the process, we will check if the customer has completed the quest. We will use the previously created expression that determines whether the customer has met all the conditions to finish the quest. If the quest has been completed, the next step in the workflow will generate the quest.renewableComplete event. Otherwise, the process ends.

1. Add the Profile Filter node. In the node settings:
   1. Click Choose event and select expression created earlier in the process,
   2. From the operator drop-down, choose Is true (Boolean),
2. Confirm by clicking Apply.

Define the Generate Event node

In this part of the process the quest.renewableComplete event is generated, which informs us about the completion of the quest.

1. To the matched path, add the Generate Event node.
2. In the configuration of the node:

   1. Enter the Event name. In our case, we are using quest.renewableComplete event.
      The Label field exists for backwards compatibility. If your integration does not require this parameter, skip it.

   2. In the Body section, use the following Jinjava and modify it to your needs:

              {
                  "gameName": "Towel's quest"
              }
              

3. Confirm by clicking Apply.

Define the secound Generate Event node

In this part of the process, a points.upcharge event will be generated, assigning 1000 loyalty points to customers who have finished the quest.

1. Add the Generate Event node. 2. In the configuration of the node:
   1. Enter the Event name. In our case, we are using points.upcharge event. The Label field exists for backwards compatibility. If your integration does not require this parameter, skip it.
   2. In the Body section, use the following Jinjava and modify it to your needs:

              {
                  "gameName": "Towel's quest",
                  "points": 1000
              }
              

2. Confirm by clicking Apply.

Add the finishing node and set capping

1. Add the End node.
2. In the upper right corner, click Set Capping and define the limit of workflows a profile can start in a specific time range.
3. In the upper right corner, click Save & Run.

Create a document

In the final step of this process, you will create a document that will display in a selected channel (for example, a mobile application) the results of the expressions you created before, showing your customers how far are they in their quest.

1. Go to Data Management > Documents > Add document.
2. Enter the name for your document.

To create a document, you have to set up three steps of settings: audience, configuration, and schedule.

Set up Audience

In the audience section, determine who will be the recipient of the document.

2. Click Define,
3. Select Everyone,
4. Save by clicking Apply.

Set up the Configuration section

In the configuration section, determine the content of the document.

1. In the Slug field, enter the slug of the document, we recommend using the following name convention: this-is-slug-name. In our example enter the name of the event as towels.

2. In the Priority field, use a number to define the document priority. The order of documents is defined by the priority value (1 is the highest, 100 is the lowest). In our example it will be 1.

3. From the Type dropdown list, select a document type. Document type defines how the document is validated by your mobile application. To create a new type, from the dropdown list, click Add type. In our example it will be StampCampaign.

4. In the Body field, add the content of the promotion in the JSON format. Body content will depend on the scenario of loyalty program. In our case, we display the results of the expressions created in previous parts of the process, a description, image, and some more information about the conditions of completing quest.

       {
               "current_status": " {% expression %} 1c92f585-3342-4fbd-af05-93f53ebe5882 {% endexpression %} ",
               "description": "Buy 10 product from towels category and get 1000 loyalty points",
               "format": "stamps",
               "image": "https://ecommerce.pl/media/catalog/product/towels/1/image/9df78eab33525d08d6e5fb8d27136e95/94989/regina-wish-recznik-papierowy-bialy-2-rolki-reczniki-papierowe-artykuly-higieniczne_0.jpg",
               "name": "Towels",
               "prize": "1000",
               "prizeType": "points",
               "target": "{% expression %} 930673cb-28d2-4a81-9100-7306bdfcce86 {% endexpression %}",
               "visibility": "1"
       }
    

   In the current_status and target parameters, we are referring to the expressions created earlier in the process. The current_status expression returns the actual number of products bought by the client, while the target expression determines the number of products needed to complete the quest.

5. Save by clicking Apply.

Set up Schedule

In the schedule section, set the document activation date.

1. Define the period as Run Imediately
2. Save by clicking Apply.

To activate immediately or at a scheduled date, click the Activate button.

What’s next

For a screen view to be visible in a mobile application, you must fetch it using the appropriate SDK method for:

• Android,
• iOS,
• React Native.

Check the use case set up on the Synerise Demo workspace

You can check the configuration of every element of this process directly in Synerise Demo workspace:

• Aggregates with timestamp of last finished quest
• Aggregates with number of products purchased after last finished quest
• Expressions with the number of products required to complete the quest
• Expressions that returns the number of products purchased
• Expressions checking the conditions for completing the quest
• Documents
• Workflow

If you don’t have access to the Synerise Demo workspace, please leave your contact details in this form, and our representative will contact you shortly.

Read more

• Automation
• Aggregates
• Expressions
• Documents