Your Store Name

> Synerise Documentation — Use Cases (Part 1 of 3) > > This is part 1 of 3 of the "Use Cases" section. To reconstruct the full section, fetch all 3 parts in order (part 1, part 2, …) and concatenate them. Each article begins with a top-level "# " heading. The manifest listing all sections is at https://hub.synerise.com/llms-full.txt # Adding Gmail Promotions Annotation Gmail allows highlighting your messages in the “Promotions” tab with Gmail Promotions Annotation. Those annotations let you enhance the visibility of your emails and engage your recipients more effectively. With this feature, you can include a header, image, your company logo, the promotion's end date, and a variety of other details to make your emails stand out. This use case demonstrates how to integrate the Gmail Promotions Annotation feature into email communication sent from Synerise. It provides a predefined HTML insert, making it easier to customize the Promotions Annotation in the Config tab in the code editor.

This feature is supported only for mailboxes associated with the gmail.com domain for individual users. This feature will work if the following conditions are met: - The recipient opens the message using the Gmail mobile app. - The message is delivered to the 'Promotions' tab. - Annotations will only appear for one-time emails; subsequent messages with the same subject will be grouped into a thread and may not display properly.

## Prerequisites --- - Configure a [sender account](/docs/campaign/e-mail/configuring-email-account). - The domain must have SPF, DKIM, and DMARC configured. - [Create an email etmplate](/docs/campaign/e-mail/creating-email-templates). ## Updating the template --- 1. Go to

**Experience Hub > Email**. 2. On the left pane, click **Templates** and search for the template you prepared as a part of prerequisites. **Result:** You are redirected to the code editor. 3. In the code editor, go to the **HTML** section and in the head section after the `` tag, add the code below:

<!--[if mso ]><style>sup, sub { font-size: 100% !important; } sup { mso-text-raise:10% } sub { mso-text-raise:-10% }</style> <![endif]-->
           <!-- Start Gmail Promo Tab annotations code -->
           <div itemscope itemtype="http://schema.org/Organization">
               <meta itemprop="name" content="#### type: "string", groupName: "Promotion tag", groupId: "promotion-tag", defaultValue: "Synerise Demo Shop", id: "promotion-tag__company-name", label: "Company name" !####" />
               <meta itemprop="logo" content="#### type: "string", groupName: "Promotion tag", groupId: "promotion-tag", defaultValue: "https://demoshop.synerise.com/media/athlete2/Demos/ca/logo-ca.png", label: "Company image", id: "promotion-tag__img-link" !####" />
           </div>

           <div itemscope itemtype="http://schema.org/EmailMessage">
               <meta itemprop="subjectLine" content="#### type: "string", groupName: "Promotion tag", groupId: "promotion-tag", defaultValue: "Free shipping", label: "Subject line", id: "promotion-tag__subject-line" !####" />
           </div>

           <div itemscope itemtype="http://schema.org/DiscountOffer">
               <meta itemprop="description" content="#### type: "string", groupName: "Promotion tag", groupId: "promotion-tag", defaultValue: "Free shiping", label: "Description", id: "promotion-tag__description" !####" />
               <meta itemprop="discountCode" content="#### type: "string", groupName: "Promotion tag", groupId: "promotion-tag", id: "promotion-tag__code", label: "Code", defaultValue: "WELCOME20" !####" />
               <meta itemprop="availabilityStarts" content="#### type: "string", groupName: "Promotion tag", groupId: "promotion-tag", defaultValue: "2024-10-15T00:00:00+00:00", label: "Start date", id: "promotion-tag__start-date" !####" />
               <meta itemprop="availabilityEnds" content="#### type: "string", groupName: "Promotion tag", groupId: "promotion-tag", defaultValue: "2024-10-17T23:59:59+00:00", label: "End date", id: "promotion-tag__end-date" !####" />
           </div>

           <div itemscope itemtype="http://schema.org/PromotionCard">
               <meta itemprop="image" content="FILL BANNER IMG" />
           </div>
           <!-- End Gmail Promo Tab annotations code -->

This will add the following fields in the **Config** section:

The view of config form for adding Gmail Promotions Annotation — The config form for adding Gmail Promotions Annotation

### Edit the form in the Config tab The form in the Config tab is pre-filled with default values, which you can modify to suit your business needs. 1. In the **Company name** field, enter the name of your company. 2. In the **Company image** field, you can provide a link to an image. 3. In the **Subject line** field, you can type the subject you want to display. 4. In the **Description** field, you can type the text that displays with the deal badge. 5. In the **Code** field, you can type the discount or promotion code for the offer. 6. In the **Start date** field, you can type the date and time when the offer begins in [ISO 8601 format](https://support.google.com/merchants/answer/7055760). 7. In the **End date** field, you can type the end date and time of the promotion in [ISO 8601 format](https://support.google.com/merchants/answer/7055760). 8. If the template is ready, click **Save** in the upper right corner.

The view of the configured Gmail Promotions Annotation with corresponding fields from the config form — Configured Gmail Promotions Annotation with corresponding fields from the config form

## What's next --- Now you can use this template in emails you sent through the Experience Hub and Automation Hub. ## Check the use case set up on the Synerise Demo workspace --- You can check the [template configuration](https://app.synerise.com/campaigns/email/content-manager/template/153289) directly in Synerise Demo workspace. If you’re our partner or client, you already have automatic access to the **Synerise Demo workspace (1590)**, where you can explore all the configured elements of this use case and copy them to your workspace. If you’re not a partner or client yet, we encourage you to fill out the contact [form](https://demo.synerise.com/request) to schedule a meeting with our representatives. They’ll be happy to show you how our demo works and discuss how you can apply this use case in your business. ## Generated events This use case generates approximately 3 events per profile that completes the flow: [`message.send`](/docs/assets/events/event-reference/email#messagesend) (~1), [`newsletter.open`](/docs/assets/events/event-reference/email#newsletteropen) (~1), [`newsletter.click`](/docs/assets/events/event-reference/email#newsletterclick) (~1). ## Read more --- - [Email campaigns](/docs/campaign/e-mail) - [Google's Guide](https://developers.google.com/gmail/promotab/overview) to the Gmail Promotions Annotation function # Date-Driven and Transaction-Based Email Banners for Customer Segments In today's fast-paced digital landscape, email marketing has evolved into a powerful tool for businesses to connect with their customers. The effectiveness of email campaigns often hinges on personalization. The ability to tailor content, products, and offers to individual recipients can significantly impact Key Performance Indicators (KPIs) and enhance the overall user experience. Email personalization goes beyond addressing the recipient by their first name; it's about delivering content that speaks directly to their interests, needs, and preferences. Such personalization can be done based on any attributes or activities of the customer, such as, for example, the customer's club status, transaction history, age in combination with any other variables, such as even the day of the month/week. The number of possible scenarios is huge, making it a great place to implement the most daring ideas.

Email campaigns with catalog-based banners

This use case describes a scenario in which customers receive email banners tailored to the following criteria: - **Current Day of the Month:** Depending on the day, customers receive banners with special promotions relevant to that day. - **Transaction History:** Customers are segmented into two groups based on whether they have made a transaction in the last 180 days or not. **Assumptions:** - The email is part of a specific marketing campaign scheduled for a particular month. - All banner graphics and their links are stored in a catalog, with each day of the month having its own banner graphic for the respective audience. **Scenarios:** Group 1: Customers with recent transactions For customers who have made at least one transaction in the last 180 days: - **Days 1-15:** They receive Banner 1, offering a special promotion. - **Days 16-31:** They receive Banner 2, featuring a different special promotion. Group 2: Customers with no recent transactions For customers who have not made any transactions in the last 180 days: - **Days 1-15:** They receive Banner 1, offering a specific discount for a particular product category. - **Days 16-31:** They receive Banner 2, with a different discount for another product category. ## Prerequisites --- - Implement [Synerise tracking code](/developers/web/installation-and-configuration#creating-a-tracking-code) on your website. - Permissions that allow access to Catalogs section and adding new catalogs. - Implement the [transaction events](/developers/web/transactions-sdk) using [SDK](/developers/web/transactions-sdk) or [API](https://hub.synerise.com/api-reference/data-management#operation/CreateATransaction). - Configure a [sender account](/docs/campaign/e-mail/configuring-email-account). - Prepare a CSV file with banner graphics and corresponding links assigned to a specific day of the month and customer segment. The file used in this use case contains the following columns: - `DayOfTheMonth` - column that contains the days of the month (this column will be used as a catalog key) - `Group1banners` - column that contains banners dedicated to Group 1 (customers who have made at least one transaction in the last 180 days) - `Group2banners` - a column that contains banners dedicated to Group 2 (customers who have not made any transaction in the last 180 days) - `link1` - column that contains links to banners dedicated for Group 1 - `link2` - column that contains links to banners dedicated to Group 2

Example file

## Process --- 1. [Create a catalog](/use-cases/dynamic-email-campaign#create-a-catalog) with banners assigned to specific days of the week and customer segments. 2. [Create an aggregate](/use-cases/dynamic-email-campaign#create-an-aggregate) showing whether a customer has made a transaction in the last 180 days. 3. [Create a jinjava](/use-cases/dynamic-email-campaign#create-a-jinjava-insert) insert to be used in the email template. 4. [Create an email template](/use-cases/dynamic-email-campaign#create-an-email-template). ## Create a catalog --- In this part of the process, create a catalog and import there your CSV file you prepared as a part of prerequisites. 1. Go to **Data Modeling Hub > Catalogs > New Catalog**. 2. Enter the name of the catalog and confirm it by clicking **Apply**.

Don't use diacritical letters and spaces.

3. Click the catalog on the list and click **Import Local File**. If you prepared a CSV file in Excel, open it in a text editor to check whether commas are used as separators. If not, replace them with commas. 4. Click the **Upload a new file** button and select the file to be uploaded, then click **Next** button. 5. You will see the information that your file has been successfully uploaded. Click **Next** button to continue the import process. 6. In the **Primary key** field, type the name of the column whose values are treated as the key. In this case it will be `DayOfTheMonth`. Click **Next** button to continue the process.

7. In the next screen you will find the summary of your import. If no changes are needed click **Run import** button.

## Create an aggregate --- Create an aggregate that show whether a customer has made a transaction in the last 180 days. The ID of this aggregate will be later used in the Jinjava code. 1. Go to

**Behavioral Data Hub > Live Aggregates > Create aggregate**. 2. As the aggregate type, select **Profile**. 2. Click **Analyze profiles by** and select **Exists**. 4. From the **Choose event** dropdown list, select the **transaction.charge** event. 5. Set the period from which the aggregate will analyze the results to the last **180 days**. 6. Save the aggregate.

Decision Hub Exists aggregate returning whether a customer has made a transaction.charge event in the last 180 days — Configuration of the aggregate

## Create a Jinjava insert --- In this part of the process, prepare a Jinjava insert that will be used in the email template to display the relevant banner from the current day of the month to the appropriate customer segment. Below you can find the jinjava insert used in this use case. There is the list of used values that you need to replace to tailor this Jinjava to your campaign: - replace `insert_aggregate_ID` with the ID of your aggreagate - replace `insert_aggregate_name` with any unique aggregate name - replace `insert_catalog_name ` with your catalog name - in the `{{ catalog_result.link1 }}`, `{{ catalog_result.link2 }}` and `{{ catalog_result.Group1banners }}`, `{{ catalog_result.Group2banners }}` replace the `link1`, `link2` and `Group1banners`, `Group2banners` with the names of respective columns from the created catalog.

Check the Jinjava code

<!-- The purpose of the following part of Jinjava is to calculate the day of the month that corresponds to the current date plus 1 hour and save it as a string.).--> {% set now = (unixtimestamp(null)|plus_time(1, 'hours'))|unixtimestamp() %} {% set now_sec = now|divide(1000) %} {% set current_date = (now_sec|int*1000)|datetimeformat('%d.%m.%y') %} {% set current_date_array = current_date|split('.') %} {% set today = current_date_array[0] %} {% set todayString = today|int|string %} <!-- The logic behind the remaining part of Jinjava determines which set of HTML elements to generate based on the value of the aggregate result and the relevant links and image data from the catalog. This part divides customers into 2 groups based on their transaction activity (customers who have or have not made any transaction in the last 180 days).--> {% aggregate insert_aggregate_ID %} {% set insert_aggregate_name = aggregate_result|last %} {%if insert_aggregate_name =='true' %} {% catalogitemv2.insert_catalog_name(todayString) %} <a href="{% preparelink %}{{ catalog_result.link1 }}{% endpreparelink %}"> <img src="{{ catalog_result.Group1banners }}"> </a> {% endcatalogitemv2 %} {% else %} {% catalogitemv2.insert_catalog_name(todayString) %} <a href="{% preparelink %}{{ catalog_result.link2 }}{% endpreparelink %}"> <img src="{{ catalog_result.Group2banners }}"> </a> {% endcatalogitemv2 %} {% endif %} {% endaggregate %}

## Create an email template --- In this part of the process, create an email template. You can use a predefined template or create your own template from scratch. In this case, we will use the predefined template. 1. Go to

**Experience Hub > Email**. 2. On the left pane, click **Templates** and from the list of template folders, select **Predefined simple templates**. 3. Select any template that mostly fits the campaign assumptions. **Result:** You are redirected to the code editor. 4. Edit the template according to your needs and add the row dedicated to the banner section. 5. Add **HTML** from the **Content** section to the created row and insert the Jinjava code you created in the previous step. 6. After you make changes to the template, you can check the preview. 1. Click the **Preview Contexts** button on the upper left side. 2. Enter the ID of a customer. 3. Click **Apply**. 7. If the template is ready, in the upper right corner, click the arrow next to **Next**, and from the dropdown select **Save as**. 8. On the pop-up: 1. In the **Template name field**, enter the name of the template. 2. From the **Template folder** dropdown list, select the folder where the template will be saved. 3. Confirm by clicking **Save**. Below you can find an example of email context preview.

## What's next --- You can use this template in an email campaign by sending it manually or setting it up in Automation Hub as part of your business scenario. ## Generated events This use case generates approximately 3 events per profile that completes the flow: [`message.send`](/docs/assets/events/event-reference/email#messagesend) (~1), [`newsletter.open`](/docs/assets/events/event-reference/email#newsletteropen) (~1), [`newsletter.click`](/docs/assets/events/event-reference/email#newsletterclick) (~1). ## Check the use case set up on the Synerise Demo workspace --- You can check the configuration of each step directly in the Synerise Demo workspace: - [Catalog](https://app.synerise.com/assets/catalogs/182804) - [Aggregate](https://app.synerise.com/analytics/aggregates/860f507b-b2db-3b71-b98e-63a040183502) If you’re our partner or client, you already have automatic access to the **Synerise Demo workspace (1590)**, where you can explore all the configured elements of this use case and copy them to your workspace. If you’re not a partner or client yet, we encourage you to fill out the contact [form](https://demo.synerise.com/request) to schedule a meeting with our representatives. They’ll be happy to show you how our demo works and discuss how you can apply this use case in your business. # Post-purchase receipt with personalized recommendations and store coupon via in-app message Bridging the gap between offline purchases and digital engagement is a key challenge for omnichannel retailers. When a customer completes a transaction in a physical store, the experience typically ends at the checkout counter. However, this moment represents a valuable opportunity to deepen the relationship by delivering a rich, personalized follow-up directly in the customer's mobile app. This use case describes how to generate **a personalized digital receipt displayed as an in-app message** shortly after an offline purchase. The receipt consolidates multiple data sources into a single view. The generated receipt includes: - **Personalized greeting** with the customer's first name - **Store name** based on the location where the purchase was made - **Transaction details:** order ID, date, list of purchased products with images, names, SKUs, prices, and total amount - **Loyalty program status:** current points balance and membership tier with a visual progress bar - **AI-driven cross-sell recommendations** ("Recommended for you") based on the purchased products - **Store-specific promotional coupon** with a tap-to-copy code, description, and expiration date The entire payload is assembled using [Brickworks](/docs/assets/brickworks), which combines customer attributes, aggregates, expressions, external data, AI recommendations, and catalog lookups into a ready-to-render template. The workflow is triggered by the `transaction.charge` event (indicating an offline purchase), waits briefly via a delay node, and then sends a silent mobile push that triggers the in-app message display. The in-app template renders a receipt-style layout with all the personalized data.

In-app receipt message example — Example of the personalized digital receipt displayed as an in-app message

## Prerequisites --- - [Implement Synerise SDK in your mobile app](/developers/mobile-sdk). - Implement the [transaction events](/developers/web/transactions-sdk) using [SDK](/developers/web/transactions-sdk) or [API](https://hub.synerise.com/api-reference/data-management#operation/CreateATransaction). The `transaction.charge` event must include a `storeId` parameter identifying the physical store. - Import a product feed to Synerise. You can find instructions [here](/docs/settings/configuration/ai-engine-configuration/engine-configuration-for-search). Check the [use case](/use-cases/import-product-feed-to-catalog). - [Configure AI engine](/docs/settings/configuration/ai-engine-configuration/engine-configuration-for-recommendations) for recommendations; enable the cross-sell recommendation type. - Have a [loyalty program](/use-cases/loyalty-programs-basics) configured in Synerise with points and tiers. - Create a [catalog](/docs/assets/catalogs/introduction-to-catalogs) mapping store IDs to promotion UUIDs. Each record in this catalog should contain at minimum: a key matching the `storeId` and a `promotion` attribute holding the UUID of the promotion assigned to that store. - Create [promotions](/docs/ai-hub/promotions/creating-promotions) in Synerise that will serve as store-specific coupons to be displayed on the receipt. - Create [API keys](/docs/settings/tool/api#adding-api-keys) with appropriate permissions for the Brickworks external data fields (access to activities API and promotions API). ## Process --- In this use case, you will go through the following steps: 1. [Create aggregates for transaction data](#create-aggregates-for-transaction-data). 2. [Create an expression for loyalty points balance](#create-an-expression-for-loyalty-points-balance). 3. [Create an expression for loyalty level](#create-an-expression-for-loyalty-level). 4. [Create an AI recommendation for cross-sell products](#create-an-ai-recommendation-for-cross-sell-products). 5. [Create a Brickworks schema](#create-a-brickworks-schema) combining all data sources. 6. [Create the Brickworks record](#create-the-brickworks-record). 7. [Create an in-app campaign](#create-an-in-app-campaign) with the receipt template. 8. [Create a workflow to trigger the in-app via silent push](#create-a-workflow). ## Create aggregates for transaction data --- In this part of the process, you will create aggregates that retrieve the details of the customer's most recent transaction. These aggregates will be used as default values in the Brickworks schema fields. ### Expression for transaction date Before creating the aggregate, you need an expression that extracts a human-readable date from the `transaction.charge` event's timestamp. This expression applies a regular expression (Regexp) to the `TIMESTAMP` event attribute of the `transaction.charge` event to parse the date value. 1. Go to

**Behavioral Data Hub > Expressions > New expression**. 2. Enter the name of the expression, for example `date [transaction.charge]`. 3. Set **Expressions for** to **Event**. 4. From the event dropdown list, select `transaction.charge`. 5. In the **Formula definition** section, build the following formula presented on the screen below. 6. **TIMESTAMP** is an **Event attribute** of type `TIMESTAMP` from the `transaction.charge` event, and the Regexp pattern extracts the date portion from the timestamp. 7. Save the expression.

Configuration of the date expression for transaction.charge

### Aggregate for last transaction date This aggregate returns the date of the customer's most recent `transaction.charge` event, using the expression created above. 1. Go to

**Behavioral Data Hub > Live Aggregates > Create aggregate**. 2. As the aggregate type, select **Profile**. 3. Enter the name of the aggregate, for example `Last transaction.charge lifetime - date`. 4. Click **Analyze profiles by** and select **Last**. 5. From the **Choose event** dropdown list, select the `transaction.charge` event. 6. As the event parameter, select the expression `date [transaction.charge]` created in the [previous step](#expression-for-transaction-date). 7. Define the period to **Lifetime**. 8. Save the aggregate.

Configuration of the last transaction date aggregate

### Aggregate for last transaction order ID This aggregate returns the order ID from the customer's most recent `transaction.charge` event. 1. Go to

**Behavioral Data Hub > Live Aggregates > Create aggregate**. 2. As the aggregate type, select **Profile**. 3. Enter the name of the aggregate, for example `Last transaction.charge lifetime - $orderId`. 4. Click **Analyze profiles by** and select **Last**. 5. From the **Choose event** dropdown list, select the `transaction.charge` event. 6. As the event parameter, select `$orderId`. 7. Define the period to **Lifetime**. 8. Save the aggregate.

Configuration of the last transaction order ID aggregate

### Aggregate for last transaction amount This aggregate returns the total amount from the customer's most recent `transaction.charge` event. 1. Go to

**Behavioral Data Hub > Live Aggregates > Create aggregate**. 2. As the aggregate type, select **Profile**. 3. Enter the name of the aggregate, for example `Last transaction.charge lifetime - $totalAmount`. 4. Click **Analyze profiles by** and select **Last**. 5. From the **Choose event** dropdown list, select the `transaction.charge` event. 6. As the event parameter, select `$totalAmount`. 7. Define the period to **Lifetime**. 8. Save the aggregate.

Configuration of the last transaction amount aggregate

### Aggregate for last transaction timestamp This aggregate returns the timestamp of the customer's most recent `transaction.charge` event. The timestamp is used in the in-app template to calculate a time window (±50 seconds) for retrieving the exact `product.buy` events belonging to that transaction via the external data field. 1. Go to

**Behavioral Data Hub > Live Aggregates > Create aggregate**. 2. As the aggregate type, select **Profile**. 3. Enter the name of the aggregate, for example `Last transaction.charge lifetime - timestamp`. 4. Click **Analyze profiles by** and select **Last**. 5. From the **Choose event** dropdown list, select the `transaction.charge` event. 6. As the event parameter, select `timeSent`. 7. Define the period to **Lifetime**. 8. Save the aggregate.

Configuration of the last transaction timestamp aggregate

### Aggregate for last store ID This aggregate returns the store ID from the customer's most recent transaction. It is used in the workflow as an additional parameter in the silent push, enabling the in-app message to display the correct store name and store-specific coupon. 1. Go to

**Behavioral Data Hub > Live Aggregates > Create aggregate**. 2. As the aggregate type, select **Profile**. 3. Enter the name of the aggregate, for example `Last transaction storeId`. 4. Click **Analyze profiles by** and select **Last**. 5. From the **Choose event** dropdown list, select the `transaction.charge` event. 6. As the event parameter, select `storeId`. 7. Define the period to **Lifetime**. 8. Save the aggregate. ## Create an expression for loyalty points balance --- Create an expression that calculates the current loyalty points balance for the customer. The expression sums up all points earned (from transactions, registration, and manual additions) and subtracts all points spent (from promotion activations and manual deductions). 1. Go to

**Behavioral Data Hub > Expressions > New expression**. 2. Enter the name of the expression, for example `Loyalty points balance`. 3. In the description, enter `Expression shows current amount of points that user is able to use`. 4. Set **Expressions for** to **Attribute**. 5. In the **Formula definition** section, build the following formula presented on the screen below. Where each component is a **Profile**-type aggregate: - **Transaction points sum**: Aggregate **Sum** of the `points.loyalty` event, parameter `points`, period **Lifetime**. - **Points for registration sum**: Aggregate **Sum** of the `points.register` event, parameter `points`, period **Lifetime**. - **Manually added points sum**: Aggregate **Sum** of the `points.upcharge` event, parameter `points`, period **Lifetime**. - **Points for promotion activation sum**: Aggregate **Sum** of the `client.activatePromotion` event, parameter `promotionRequireRedeemedPoints`, period **Lifetime**. - **Manually deducted points sum**: Aggregate **Sum** of the `points.downcharge` event, parameter `points`, period **Lifetime**. 6. Save the expression.

Configuration of the Transaction points sum aggregate within the expression

Configuration of the Points for registration sum aggregate within the expression

Configuration of the Manually added points sum aggregate within the expression

Configuration of the Points for promotion activation sum aggregate within the expression

Configuration of the Manually deducted points sum aggregate within the expression

The exact event names and parameter names for the loyalty points aggregates depend on your loyalty program configuration. The names listed above correspond to the Synerise Demo workspace loyalty setup. Adjust them to match your implementation.

## Create an expression for loyalty level --- Create an expression that returns the customer's current loyalty tier based on conditional logic. The expression evaluates a series of segmentations — each representing a loyalty tier — and returns the corresponding label (for example, "Base member", "Silver member", "Gold member", or "Premium member"). 1. Go to

**Behavioral Data Hub > Expressions > New expression**. 2. Enter the name of the expression, for example `[UC] Loyalty level`. 3. Set **Expressions for** to **Attribute**. 4. In the **Formula definition** section, build a nested conditional (If) formula with the following logic: `If( [UC] Loyalty level - Base, "Base member", If( [UC] Loyalty level - Silver, "Silver member", If( [UC] Loyalty level - Gold, "Gold member", If( [UC] Loyalty level - Premium, "Premium member", null ) ) ) )` Each green node (`[UC] Loyalty level - Base`, `[UC] Loyalty level - Silver`, `[UC] Loyalty level - Gold`, `[UC] Loyalty level - Premium`) is a **segmentation** that checks whether the customer falls into the corresponding loyalty tier based on their points balance. The expression evaluates them in order and returns the first matching tier label. If none matches, it returns `null`. 5. Save the expression.

The segmentations referenced in this expression (for example, `[UC] Loyalty level - Gold`) define the point thresholds for each tier. You need to create these segmentations separately in **Decision Hub > Segmentations** before building this expression. Each segmentation should use a condition based on the customer's loyalty points sum (for example, "points sum ≥ 4000 AND points sum < 10000" for the Gold tier). Adjust the thresholds to match your loyalty program requirements.

## Create an AI recommendation for cross-sell products --- In this part of the process, you will configure a cross-sell (complementary products) recommendation. This recommendation suggests products related to what the customer has just purchased and is displayed in the "Recommended for you" section of the receipt. 1. Go to

**AI Hub > (AI Recommendations) Models > Add recommendation**. 2. Enter the name of the recommendation, for example `Recommending complementary products`. 3. In the **Type & Items feed** section, click **Define**. 1. From the **Items Feed** dropdown list, select the item catalog which you configured as a part of [prerequisites](#prerequisites). 2. In the **Type** section, choose the **Cross-sell** recommendation type. 3. Confirm the settings by clicking **Apply**. 4. In the **Items** section, click **Define**. 1. Define the items slot configuration according to your needs. 2. Confirm by clicking **Apply**. 5. In the **Slots and items ordering** section, click **Define**. 1. Set **Slots and items ordering** to **Arrange items in slot order**. 2. Set **Items sorting method within slots** to **Sort by score**. 3. Confirm by clicking **Apply**. 6. Optionally, define the **Boosting** factors. 7. In the **Additional settings** section, click **Define**. 1. Enable **Exclude already bought products** with the **Elastic** option and set the period to **180 days**. 2. Set **Item context from analytics (aggregate, expression)** to an aggregate or expression that returns the SKU of the last purchased product (for example, `Last 1 product.buy sku`). 3. Confirm by clicking **Apply**. 8. In the upper right corner, click **Save**. ## Create a Brickworks schema --- In this part of the process, you will [create a Brickworks schema](/docs/assets/brickworks/quick-start/creating-a-schema) that serves as a structured container for all the data displayed on the personalized receipt. The schema combines customer attributes, aggregates, expressions, AI recommendations, external API data, and catalog lookups into a single renderable payload. 1. Go to **Data Modeling Hub > Brickworks > New schema**. 2. Choose **Simple Schema**. 3. Enter a name for the schema, in **Display name** for example `Receipt Intelligence`. **API name** is pre-filled with the value from Display name. 4. Optionally, fill in the **Description** field. ### Add Firstname field 5. Click **Add new field** and choose **Customer attribute**. 6. Complete the fields: - **Display name**: `Firstname` - **API name**: `firstname` (pre-filled automatically) 7. Configure the field to return the customer's `firstname` attribute. 8. To save your changes, click **Apply**.

Configuration of the Firstname field in the Brickworks schema — Configuration of the Firstname field

### Add Points balance field 5. Click **Add new field** and choose **Expression**. 6. Complete the fields: - **Display name**: `Points balance` - **API name**: `pointsBalance` (pre-filled automatically) 7. In **Configuration**, enable **Default value** and select the expression `Loyalty points balance [LOYALTY-DEMO]` created in the [previous step](#create-an-expression-for-loyalty-points-balance). 8. Enable **Return null when object is missing** to prevent rendering errors if the expression returns no data. 9. To save your changes, click **Apply**.

Configuration of the Points balance field in the Brickworks schema — Configuration of the Points balance field

### Add Loyalty level field 5. Click **Add new field** and choose **Expression**. 6. Complete the fields: - **Display name**: `Loyalty level` - **API name**: `loyaltyLevel` (pre-filled automatically) 7. In **Configuration**, enable **Default value** and select the expression `[UC] Loyalty level` created in the [previous step](#create-an-expression-for-loyalty-level). 8. Enable **Return null when object is missing**. 9. To save your changes, click **Apply**.

### Add Cross-sell reco field 5. Click **Add new field** and choose **AI Recommendations**. 6. Complete the fields: - **Display name**: `Cross-sell reco` - **API name**: `crossSellReco` (pre-filled automatically) 7. In **Configuration**, enable **Default value** and select the AI recommendation `Recommending complementary products` created in the [previous step](#create-an-ai-recommendation-for-cross-sell-products). 8. The **Item context** field can be left empty or configured with a Jinjava expression if you want to pass a specific product context for the cross-sell recommendation. 9. To save your changes, click **Apply**.

Configuration of the Cross-sell reco field in the Brickworks schema — Configuration of the Cross-sell reco field

### Add product buy field (External Data) This field uses an external API call to retrieve the `product.buy` events that belong to the customer's most recent transaction. It uses the transaction timestamp (passed via context) with a ±50 seconds window to identify the exact products from that transaction. 5. Click **Add new field** and choose **External data**. 6. Complete the fields: - **Display name**: `product buy` - **API name**: `productBuy` (pre-filled automatically) 7. In **Configuration**, select the external data source (in this example named `Transactions`). The external data source makes the following API call:

curl -X POST "https://api.synerise.com/activities-api/events/by/email" \
         -H "Authorization: Basic USERNAME:PASSWORD" \
         -d '{
         "additionalData": {
           "raw": "true",
           "limit": "100",
           "dateTo": "{{context.dateTo}}",
           "actions": "product.buy",
           "dateFrom": "{{context.dateFrom}}"
         },
         "identifierValue": "{{ customer.email }}"
       }'

8. To save your changes, click **Apply**.

Configuration of the product buy external data field in the Brickworks schema — Configuration of the product buy external data field

The `dateFrom` and `dateTo` context parameters are calculated dynamically in the in-app template code by taking the last transaction timestamp and adding/subtracting 50000 milliseconds (~50 seconds). This ensures only the `product.buy` events belonging to that specific transaction are returned.

### Add Promotion list field (External Data) This field uses an external API call to retrieve the list of active and assigned promotions for the current customer. The in-app template then matches the promotion UUID (retrieved from the store-to-promotion catalog) against this list to display the correct store-specific coupon. 5. Click **Add new field** and choose **External data**. 6. Complete the fields: - **Display name**: `Promotion list` - **API name**: `promotionDetails` (pre-filled automatically) 7. In **Configuration**, select the external data source (in this example named `Promotion list`). The external data source makes the following API call:

curl -X GET "https://api.synerise.com/v4/promotions/v2/promotion/get-for-client/clientId/{{customer.id}}?status=ACTIVE,ASSIGNED&fields=code,name,expireAt,discountType,discountValue,uuid,description,expireAt" \
         -H "Authorization: Basic USERNAME:PASSWORD"

8. To save your changes, click **Apply**.

Configuration of the Promotion list external data field in the Brickworks schema — Configuration of the Promotion list external data field

### Add Last transaction date field 5. Click **Add new field** and choose **Expression**. 6. Complete the fields: - **Display name**: `Last transaction date` - **API name**: `lastTransactionDate` (pre-filled automatically) 7. In **Configuration**, enable **Default value** and select the aggregate `Last transaction.charge lifetime - date` created in the [earlier step](#aggregate-for-last-transaction-date). 8. To save your changes, click **Apply**.

Configuration of the Last transaction date field in the Brickworks schema — Configuration of the Last transaction date field

### Add Last transaction orderId field 5. Click **Add new field** and choose **Expression**. 6. Complete the fields: - **Display name**: `Last transaction orderId` - **API name**: `lastTransactionOrderId` (pre-filled automatically) 7. In **Configuration**, enable **Default value** and select the aggregate `Last transaction.charge lifetime - $orderId` created in the [earlier step](#aggregate-for-last-transaction-order-id). 8. To save your changes, click **Apply**.

Configuration of the Last transaction orderId field in the Brickworks schema — Configuration of the Last transaction orderId field

### Add Last transaction amount field 5. Click **Add new field** and choose **Expression**. 6. Complete the fields: - **Display name**: `Last transaction amount` - **API name**: `lastTransactionAmount` (pre-filled automatically) 7. In **Configuration**, enable **Default value** and select the aggregate `Last transaction.charge lifetime - $totalAmount` created in the [earlier step](#aggregate-for-last-transaction-amount). 8. To save your changes, click **Apply**.

Configuration of the Last transaction amount field in the Brickworks schema — Configuration of the Last transaction amount field

### Add Last transaction timestamp field 5. Click **Add new field** and choose **Expression**. 6. Complete the fields: - **Display name**: `Last transaction timestamp` - **API name**: `lastTransactionTimestamp` (pre-filled automatically) 7. In **Configuration**, enable **Default value** and select the aggregate `Last transaction.charge lifetime - timestamp` created in the [earlier step](#aggregate-for-last-transaction-timestamp). 8. To save your changes, click **Apply**.

Configuration of the Last transaction timestamp field in the Brickworks schema — Configuration of the Last transaction timestamp field

### Overview of all schema fields

Overview of all fields in the Brickworks schema — Overview of all fields in the Receipt Intelligence Brickworks schema

### Set up the Audience & Settings 1. Click the **Audience & Settings** tab. 2. In the **Audience** section, click **Define**. 3. Choose the schema recipients, in this case, choose **Everyone**. 4. Click **Apply**. 5. In the upper-right corner, click **Save**. ## Create the Brickworks record --- [Creating a record](/docs/assets/brickworks/quick-start/creating-a-record) fills the schema with actual values. In this case, the record uses dynamic context to resolve all fields at render time based on the requesting customer and their latest transaction. 1. Go to **Data Modeling Hub > Data collections > Select schema**. 2. Choose the [schema created in the previous step](#create-a-brickworks-schema). 3. Click **Add record**. 4. Add a name for the record. 5. Add a slug for the record. Slug is a unique, URL-friendly version of the name. In this case, it is `receiptSimpleSchema1`. 6. The record fields will inherit default values from the schema configuration: - **Firstname**: `firstname` (customer attribute) - **Points balance**: [Loyalty points balance [LOYALTY-DEMO]](https://app.synerise.com/analytics/expressions/ff12ecbd-b89f-4e8f-b85e-6854f7fea9c0) (expression) - **Loyalty level**: `[UC] Loyalty level` (expression) - **Cross-sell reco**: [Recommending complementary products](https://app.synerise.com/ai-v2/recommendations/ly321Pc82ALq) (AI recommendation) - **product buy**: `Transactions` (external data) - **Promotion list**: `Promotion list` (external data) - **Last transaction date**: [Last transaction.charge lifetime - date](https://app.synerise.com/analytics-v2/aggregates/97739400-4da7-350c-9111-757ff57ac17b) (aggregate) - **Last transaction orderId**: [Last transaction.charge lifetime - $orderId](https://app.synerise.com/analytics-v2/aggregates/058e59ef-74f1-3073-871b-9377721d91a1) (aggregate) - **Last transaction amount**: [Last transaction.charge lifetime - $totalAmount](https://app.synerise.com/analytics-v2/aggregates/ef870a4c-1743-3d73-aa85-fae786ff1f42) (aggregate) - **Last transaction timestamp**: [Last transaction.charge lifetime - timestamp](https://app.synerise.com/analytics-v2/aggregates/6ce58d75-bbe6-3040-94b3-b532138d42a8) (aggregate) 7. Click **Publish** to publish your record. ### Previewing records After publishing the record, you can [preview the record](/docs/assets/brickworks/quick-start/creating-a-record#previewing-records) for the context of a selected user. This context-driven approach enables your records to adapt dynamically based on the requesting customer and their transaction history. 1. Go to **Data Modeling Hub > Records**. 2. In the header, from the **Select schema** dropdown list, select the schema created previously. 3. Find the record which you want to preview. 4. Enter the record configuration. 5. Click the **Preview context**. 6. From the dropdown list, find a profile for whom you want to generate the record preview. 7. Click **Add parameter** and add the context parameters: - `storeId` - the ID of the store (for example, `1`) - `locale` - the locale (for example, `pl-PL`) - `dateFrom` - the start of the time window for product.buy events (timestamp in milliseconds) - `dateTo` - the end of the time window for product.buy events (timestamp in milliseconds) - `currency` - the currency code (for example, `PLN`) **Result**: You will see a dynamic preview with the customer's first name, loyalty data, transaction details, cross-sell recommendations, and available promotions. ## Create an in-app campaign --- In this part of the process, you [create an in-app campaign](/docs/campaign/in-app-messages/create-inapp-message) that displays the personalized receipt. The in-app is triggered by a silent push notification sent from the workflow after a purchase. 1. Go to

**Experience Hub > In-app messages > Create new**. 2. Enter the name of the in-app, for example `Receipt Intelligence`. ### Define the audience --- 1. In the **Audience** section, click **Define**. 2. Click **Everyone**. 3. To save the audience, click **Apply**. ### Define content --- In this part of the process, you will create the in-app template from scratch using the code editor. The template is written in HTML, CSS, and JavaScript with Jinjava inserts that dynamically resolve data from the Brickworks schema at render time. 1. In the **Content** section, click **Define**. 2. Click **Create message**. 3. Create a new template. 4. Choose a **code editor**. **Result:** You are redirected to the code editor where you can write the HTML, CSS, and JavaScript code for the receipt template. The template code uses Jinjava to assemble the receipt from multiple data sources. Below is a description of the key parts of the template logic and the Jinjava inserts used in each part. #### Retrieving the store-specific promotion UUID The template first looks up the promotion UUID assigned to the store where the purchase was made. It does this by querying a catalog that maps store IDs to promotion UUIDs. The store ID is passed as a parameter (`lastStoreId`) via the silent push from the workflow.

{% catalogitemv2.CATALOG_ID(key) %}
{% do promoId.append(catalog_result.promotion) %}
{% endcatalogitemv2 %}

#### Calculating the transaction time window The template uses the [aggregate for last transaction timestamp](#aggregate-for-last-transaction-timestamp) to retrieve the timestamp of the most recent purchase. It then calculates a ±50 second window around this timestamp. This window is passed as `dateFrom` and `dateTo` context parameters to the Brickworks external data field, ensuring that only the `product.buy` events from that specific transaction are returned.

{% aggregate 6ce58d75-bbe6-3040-94b3-b532138d42a8 %}
  {% set date1 = aggregate_result[0] - 50000 %}
  {% set date2 = aggregate_result[0] - (-50000) %}

#### Generating the Brickworks payload The template calls the `brickworksgeneratevar` Jinjava tag, passing the schema ID, record ID, and a dynamic context object. This triggers the Brickworks engine to resolve all fields in the schema (customer attributes, expressions, aggregates, AI recommendations, and external data) and return the result as a single `brickworks_result` object.

{% set myContext={
    "storeId":"1",
    "locale":"pl-PL",
    "dateFrom": date1,
    "dateTo": date2,
    "currency": "PLN"
    } 
%}
{% brickworksgeneratevar schemaId=480b5a15-8b55-4645-9fc2-13962e88f551 recordId=18d3296f-8016-4933-b0aa-9ead88243bac context=myContext %}

#### Rendering the receipt sections The template accesses the resolved data through the `brickworks_result` object and renders each section of the receipt: - `brickworks_result.firstname` — customer's first name for the greeting - `brickworks_result.pointsBalance` — loyalty points balance - `brickworks_result.loyaltyLevel` — loyalty tier label - `brickworks_result.lastTransactionOrderid` — order ID - `brickworks_result.lastTransactionDate` — transaction date - `brickworks_result.lastTransactionAmount` — total amount - `brickworks_result.productBuy.data` — array of purchased products (iterated with `{% for product in brickworks_result.productBuy.data %}`) - `brickworks_result.crossSellReco.data` — array of recommended products - `brickworks_result.promotionDetails.data` — array of available promotions #### Matching and displaying the store-specific coupon The template iterates through the list of promotions returned by the external data field and matches the promotion UUID from the catalog lookup. Only the promotion matching the store is displayed to the customer.

{% for promo in brickworks_result.promotionDetails.data %}
  {% if promo.uuid == promoId|last %}
    <div class="coupon-name">{{ promo.name }}</div>
    <div class="coupon-code" onclick="copyCode('{{ promo.code }}', this)">
      {{ promo.code }}
    </div>
  {% endif %}
{% endfor %}

The rendered template includes the following visual sections: - **Header**: Store name, thank-you message, personalized greeting with the customer's first name - **Transaction details**: Order ID and transaction date - **Loyalty strip**: Points balance and loyalty tier with a visual progress bar - **Purchase details**: List of products from the transaction with images, names, SKUs, and prices - **Total amount**: Sum of the transaction - **Recommendations**: Horizontally scrollable cross-sell product cards with images, names, and prices - **Coupon**: Store-specific promotion with a tap-to-copy coupon code, description, and expiration date - **Footer**: Call-to-action to visit again with the store name

Preview of the in-app receipt message with all personalized sections

#### JavaScript for coupon copy functionality The code includes JavaScript that enables a tap-to-copy functionality for the coupon code:

function copyCode(code, el) {
  var hint = document.getElementById('copy-hint');
  try {
    if (navigator.clipboard) {
      navigator.clipboard.writeText(code).catch(function() { legacyCopy(code); });
    } else {
      legacyCopy(code);
    }
  } catch(e) { legacyCopy(code); }

  el.classList.add('copied');
  hint.textContent = 'Copied!';
  hint.style.fontStyle = 'normal';
  hint.style.fontWeight = '700';
  hint.style.color = 'var(--ink-mid)';

  setTimeout(function() {
    el.classList.remove('copied');
    hint.textContent = 'tap to copy';
    hint.style.fontStyle = '';
    hint.style.fontWeight = '';
    hint.style.color = '';
  }, 2000);
}

function legacyCopy(text) {
  var ta = document.createElement('textarea');
  ta.value = text;
  ta.style.cssText = 'position:fixed;opacity:0;top:0;left:0;';
  document.body.appendChild(ta);
  ta.select();
  try { document.execCommand('copy'); } catch(e) {}
  document.body.removeChild(ta);
}

5. After completing the template, click **Save this template > Save as**. 6. On the pop-up: 1. In the **Template name** field, enter the name of the template. 2. From the **Template folder** dropdown list, select the folder where the template will be saved. 3. Confirm by clicking **Apply**. 7. To continue the process of configuring the in-app campaign, click **Next**. 8. To save your content changes, click **Apply**. ### Select events that trigger the in-app message display --- The in-app message is triggered by the silent push notification sent from the workflow. Configure the trigger event according to the content identifier used in the silent push. 1. In the **Trigger events** section, click **Define**. 2. Configure the trigger event to match the silent push content identifier. In our case it will be `transaction.charge`. 3. Click **Apply**. ### Schedule the message and configure display settings --- 1. In the **Schedule** section, click **Define** and set the time when the message will be active. 2. In the **Display Settings** section, click **Change**. 3. Define the **Delay display**, **Priority index** and enable the **Frequency limit** toggle to manage the frequency of the in-app message display. 4. Click **Apply**. 5. Optionally, you can define the UTM parameters and additional parameters for your in-app campaign. 6. Click **Activate**. ## Create a workflow --- Create a workflow that triggers the in-app receipt display after an offline purchase. The workflow listens for `transaction.charge` events with a `storeId` parameter, waits for a short delay, and then sends a silent mobile push that activates the in-app message with the necessary context parameters. 1. Go to

**Automation Hub > Workflows > New workflow**. 2. Enter the name of the workflow, for example `Trigger in-app via silent push after purchase`. ### Define the Profile Event trigger node --- 1. As the first node of the workflow, add **Profile Event**. In the configuration of the node: 1. From the **Choose event** dropdown menu, choose the `transaction.charge` event. 2. Click the **+ where** button, from the **Choose parameter** dropdown menu, choose `storeId`. 3. From the **Choose operator** dropdown, choose **Exist**. 2. Confirm by clicking **Apply**.

Configuration of the Profile Event node

### Configure the Delay node --- 1. As the next node, add **Delay**. 2. Set the delay duration according to your business needs (for example, a few minutes to allow all transaction data to be processed and indexed). 3. Confirm by clicking **Apply**. ### Configure the Send Mobile Push node --- 1. As the next node, add **Send Mobile Push**. In the configuration of the node: 1. In the **Mobile push type** section, click **Change** and select **Silent push**. 2. In the **Content** section, click **Change** and select the in-place content linked to the in-app campaign. 3. In the **Additional parameters** section, add two custom parameters: - **Parameter**: `campaignName`, **Value**: `[UC] Receipt Intelligence` - **Parameter**: `lastStoreId`, **Value**: Insert the [aggregate for last store ID](#aggregate-for-last-store-id) created earlier. The value uses the Jinjava aggregate insert to dynamically resolve the store ID for each customer. 4. Confirm by clicking **Apply**.

Configuration of the Send Mobile Push node with additional parameters

The `lastStoreId` parameter is critical — it is passed to the in-app template as context and used to look up the store name and the store-specific promotion UUID from the catalog. The value is retrieved dynamically using the aggregate that returns the last `storeId` from the `transaction.charge` event.

### Add the finishing node --- 1. Add the **End** node. 2. In the upper right corner, click **Save & Run**.

The complete workflow configuration — The complete workflow: Profile Event → Delay → Send Mobile Push → End

## What's next --- After implementing this use case, you can extend the receipt experience in several ways: - Add a **store locator** link in the footer to help customers find the store for their next visit. - Include a **feedback survey** link to gather post-purchase satisfaction data. - Extend the template with **loyalty program milestones** (for example, showing how many points until the next tier). - Reuse the Brickworks schema across other channels such as email or web push for a consistent post-purchase experience. ## Check the use case set up on the Synerise Demo workspace --- You can check the configuration of each step directly in the Synerise Demo workspace: - [Aggregate: Last transaction.charge lifetime - timestamp](https://app.synerise.com/analytics-v2/aggregates/6ce58d75-bbe6-3040-94b3-b532138d42a8) - [Aggregate: Last transaction.charge lifetime - $totalAmount](https://app.synerise.com/analytics-v2/aggregates/ef870a4c-1743-3d73-aa85-fae786ff1f42) - [Aggregate: Last transaction.charge lifetime - $orderId](https://app.synerise.com/analytics-v2/aggregates/058e59ef-74f1-3073-871b-9377721d91a1) - [Aggregate: Last transaction.charge lifetime - date](https://app.synerise.com/analytics-v2/aggregates/97739400-4da7-350c-9111-757ff57ac17b) - [Expression: Loyalty points balance [LOYALTY-DEMO]](https://app.synerise.com/analytics/expressions/ff12ecbd-b89f-4e8f-b85e-6854f7fea9c0) - [AI Recommendation: Recommending complementary products](https://app.synerise.com/ai-v2/recommendations/ly321Pc82ALq) - [Brickworks schema and record](https://app.synerise.com/assets/brickworks/schemas/480b5a15-8b55-4645-9fc2-13962e88f551/records/18d3296f-8016-4933-b0aa-9ead88243bac) - [In-app campaign](https://app.synerise.com/communications/in-app/0cabb677-bcda-4f97-b46d-127d1106e0b2/content-manager/template/editor?variant=0) - [Workflow](https://app.synerise.com/automations/workflows/automation-diagram/da894e1f-c44a-4f6b-81e5-053803cb73b7) If you’re our partner or client, you already have automatic access to the **Synerise Demo workspace (1590)**, where you can explore all the configured elements of this use case and copy them to your workspace. If you’re not a partner or client yet, we encourage you to fill out the contact [form](https://demo.synerise.com/request) to schedule a meeting with our representatives. They’ll be happy to show you how our demo works and discuss how you can apply this use case in your business. ## Generated events This use case generates approximately 15 events per profile that completes the flow: [`transaction.charge`](/docs/assets/events/event-reference/items#transactioncharge) (~1), [`product.buy`](/docs/assets/events/event-reference/items#productbuy) (~2), [`automation.clientStartPath`](/docs/assets/events/event-reference/automation#automationclientstartpath) (~1), [`automation.clientPathStep`](/docs/assets/events/event-reference/automation#automationclientpathstep) (~3), [`automation.clientEndPath`](/docs/assets/events/event-reference/automation#automationclientendpath) (~1), [`push.send`](/docs/assets/events/event-reference/mobile-push#pushsend) (~1), [`inApp.show`](/docs/assets/events/event-reference/inapp#inappshow) (~1), [`inApp.click`](/docs/assets/events/event-reference/inapp#inappclick) (~1), [`brickworks.generated`](/docs/assets/events/event-reference/brickworks#brickworksgenerated) (~1), [`recommendation.generated`](/docs/assets/events/event-reference/recommendations#recommendationgenerated) (~1), [`recommendation.view`](/docs/assets/events/event-reference/recommendations#recommendationview) (~1), [`recommendation.click`](/docs/assets/events/event-reference/recommendations#recommendationclick) (~1). ## Read more --- - [Aggregates](/docs/crm/aggregates) - [Brickworks](/docs/assets/brickworks) - [AI Recommendations](/docs/ai-hub/recommendations-v2) - [Catalogs](/docs/assets/catalogs/introduction-to-catalogs) - [Expressions](/docs/crm/expressions) - [In-app messages](/docs/campaign/in-app-messages) - [Automation Hub](/docs/automation) - [Loyalty programs](/use-cases/loyalty-programs-basics) - [Mobile push](/docs/campaign/Mobile/mobile_campaign) - [Promotions](/docs/ai-hub/promotions/creating-promotions) # Handle non-existing phrases in search engine With Synerise AI search, you can effectively control how your search engine processes queries. You can manage the behavior of the search engine by telling it to promote specific products, replace the query or a word in the query or remove a word from it in specific circumstances. This use case describes the process of replacing a specified phrase used in the search query with a new one, defined by us, in case there are no results for a phrase because it does not appear in the catalog.

## Prerequisites --- - Enable [The Search Engine](/docs/ai-hub/ai-search/introduction-to-ai-search) for your workspace and create an [index](/docs/ai-hub/ai-search/create-index). - [Implement AI search](https://hub.synerise.com/api-reference/ai-search) in any of your channels (mobile app, website etc.). ## Add rules --- In this use case, you replace query: 'NYC' and 'the city that never sleeps' with new query. When a customer types any of these words into a search engine, it will return 'New York' as a relevant search result. 1. Go to

**AI Hub > Indexes**. 2. Select an index from the list. 3. Click the **Rules** tab. 4. On the right side of the screen, click **Add rule**. 5. Name the rule. 6. To adjust the query conditions, in the **Conditions** section, click **Define**. 1. Choose the **Query** tab. 2. Next to **If query** choose **is** from the dropdown list. 3. In the field **Type word** in the **Phrase** section, type a word (or a phrase) in a singular form, that doesn't exist in the search engine catalog. 4. You can add more phrases. 5. Click **Apply**.

Example of conditions the query needs to meet so the rule can be triggered

7. To define how the search engine reacts to the defined conditions, in the **Consequences** section, click **Define**. 1. Click **Add consequence** and choose **Replace query** from the dropdown list. 2. Enter a query replacement. 3. Click **Apply**.

Example of what happens if the conditions are fulfilled

8. You can define when the query rule applies, in the **Schedule** section. 8. Click **Save & Publish**. ## Check the use case set up on the Synerise Demo workspace --- You can also check the query rules configuration directly in Synerise Demo workspace at this [link](https://app.synerise.com/ai-v2/search/indices/50b0e2ac14e8e7643da4965e6631242e1729069084/query-rules/33482). If you’re our partner or client, you already have automatic access to the **Synerise Demo workspace (1590)**, where you can explore all the configured elements of this use case and copy them to your workspace. If you’re not a partner or client yet, we encourage you to fill out the contact [form](https://demo.synerise.com/request) to schedule a meeting with our representatives. They’ll be happy to show you how our demo works and discuss how you can apply this use case in your business. ## Generated events This use case generates approximately 2 events per profile that completes the flow: [`item.search`](/docs/assets/events/event-reference/search#itemsearch) (~1), [`item.search.click`](/docs/assets/events/event-reference/search#itemsearchclick) (~1). ## Read more --- - [Configuring AI Search](/docs/ai-hub/ai-search/introduction-to-ai-search#configuring-ai-search). - [Creating rules](/docs/ai-hub/ai-search/query-rules) # Boost High-Margin Products in Personalized Recommendations It's hard to disagree that the ultimate goal of business is to make a profit. To achieve specific profit margin targets, marketers need to create an effective plan to achieve these goals. One of the ways to increase profits is to recommend higher-margin items to customers than the average margin of items typically purchased by customers while personalizing the results of product recommendations. This approach can streamline sales efforts without involving high costs. ## Prerequisites --- - [Create items catalog](/docs/ai-hub/recommendations-v2/item-feed-requirements). The item catalog must include an attribute which will be used to denote (in this use case, it's the `margin` attribute, which contains the margin value for each product). - [Configure an item catalog for recommendations](/docs/settings/configuration/ai-engine-configuration/engine-configuration-for-recommendations). Enable personalized recommendations. - Implement transaction events using [SDK](/developers/web/transactions-sdk) or [API](https://hub.synerise.com/api-reference/data-management#operation/CreateATransaction). When implementing transaction events, remember to add a `margin` parameter, which will contain the value of the margin on the sold product. ## Process --- 1. [Create an aggregate](/use-cases/boost-higher-margin-products#create-an-aggregate). 2. [Create recommendation](/use-cases/boost-higher-margin-products#create-a-recommendation). ## Create an aggregate --- In this part of the process, create an aggregate that returns the average margin value of the products bought by an individual customer. 1. Go to

Decision Hub Average aggregate returning the average margin value from product.buy events — Configuration of the aggregate

## Create a recommendation --- 1. Go to

**AI Hub > (AI Recommendations) Models > Add recommendation**. 2. In the top left corner, enter the name of your recommendation. 3. In the **Type & Items feed** section, click **Define**. 4. From the **Items feed** dropdown menu, choose the provided feed. 5. Choose the **Personalized** recommendation type.

AI Hub recommendation model Type and Items feed section with Personalized recommendation type selected — Configuraion of the catalog and recommendation type section

6. Click **Apply**. 7. In the **Items** section, click **Define**. 1. Click **Add slot**. 2. Define the minimum and maximum number of items that will be recommended to the user in each slot. 3. Confirm by clicking **Apply**. 8. In the **Boosting** section: 1. Click **Define**. 2. Click **Add rule**. 3. Click **Define rule** and select **Visual Builder**. **Result**: The Visual Builder window opens. 4. From the **Select attribute** dropdown list, select the **margin** attribute. You can use the search field. 5. From the **Operator** dropdown list, select **More than**. 6. Click the value type icon (

) and choose **Aggregate**. 7. From the **Choose aggregate** dropdown list, select an aggregate created in [the previous step](/use-cases/boost-higher-margin-products#create-an-aggregate). The configured filter allows you to boost items with a margin higher than the one returned in the created aggregate. 8. Click **Apply**.

Boosting items with margins higher than the average margin of products purchased by the customer

9. In the **Promote/Demote** selector, select **Promote** (default value). 10. Use the slider to adjust how much you want the rule to affect the results. 11. Save the **Boosting** section settings by clicking **Apply**. 12. Optionally, you can define the settings in the **Additional settings** section. 13. Save the recommendation. ## What's next --- You can display the recommendation to customers in several ways, for example by using the [recommendation insert](/developers/inserts/recommendations-v2) in [dynamic content](/docs/campaign/dynamiccontent/creating-dynamic-content) or in a mobile app using documents - [iOS SDK](/developers/mobile-sdk/displaying-recommendations/content-widget/ios), [Android SDK](/developers/mobile-sdk/displaying-recommendations/content-widget/android). If you decide to implement recommendations through dynamic content then you need to implement [Synerise JS SDK](/developers/web/installation-and-configuration) and [OG tags](/developers/web/og-tags) into your website. Alternatively, you can also implement campaigns through [API](https://hub.synerise.com/api-reference/ai-recommendations#operation/GetRecommendationsByCampaignV2). ## Check the use case set up on the Synerise Demo workspace --- You can also check the [aggregate](https://app.synerise.com/analytics/aggregates/f8a165a0-1deb-3ab8-8e20-9b1a520ebe72) and [AI recommendation](https://app.synerise.com/ai-v2/recommendations/Pk2EKr9IlyTw) configuration directly in Synerise Demo workspace. If you’re our partner or client, you already have automatic access to the **Synerise Demo workspace (1590)**, where you can explore all the configured elements of this use case and copy them to your workspace. If you’re not a partner or client yet, we encourage you to fill out the contact [form](https://demo.synerise.com/request) to schedule a meeting with our representatives. They’ll be happy to show you how our demo works and discuss how you can apply this use case in your business. ## Generated events This use case generates approximately 3 events per profile that completes the flow: [`recommendation.generated`](/docs/assets/events/event-reference/recommendations#recommendationgenerated) (~1), [`recommendation.view`](/docs/assets/events/event-reference/recommendations#recommendationview) (~1), [`recommendation.click`](/docs/assets/events/event-reference/recommendations#recommendationclick) (~1). ## Read more --- - [Creating aggregates](/docs/crm/aggregates/creating-profile-aggregates) - [Creating recommendations](/docs/ai-hub/recommendations-v2/creating-recommendation-campaign) - [Filters in recommendations](/docs/ai-hub/recommendations-v2/recommendation-filters) - [Requirements for item feed](/docs/ai-hub/recommendations-v2/item-feed-requirements) # Excluding category of recently purchased products in recommendations Personalized product recommendations are incredibly effective because they use your customers' search, browsing, and purchase history to recommend products that are tailored to their specific requirements and preferences. To create even better communication, you can exclude from recommendations the categories of items recently bought by a customer. In this use case, you will learn how to create a personalized recommendation campaign which uses an aggregate to exclude the categories of recently purchased products. ## Prerequisites --- - Configure an [item feed](/docs/ai-hub/recommendations-v2/item-feed-requirements). - [Configure an item catalog for recommendations](/docs/settings/configuration/ai-engine-configuration/engine-configuration-for-recommendations). Enable the personalized recommendation model. - Implement transaction events using [SDK](/developers/web/transactions-sdk) or [API](https://hub.synerise.com/api-reference/data-management#operation/CreateATransaction). ## Process --- 1. [Create an aggregate](/use-cases/reco-excluding-recently-purchased-category#create-an-aggregate) of recently purchased products' categories to exclude them from personalized recommendation campaign. 2. [Create a recommendation](/use-cases/reco-excluding-recently-purchased-category#create-a-recommendation). ## Create an aggregate --- In this part of the process, create an aggregate that will return categories of products already bought by the customer. 1. Go to

**Behavioral Data Hub > Live Aggregates > Create aggregate**. 2. As the aggregate type, select **Profile**. 2. Enter the name of the aggregate. 3. Click **Analyze profiles by** and select **Last Multi**. 4. Select **Consider only distinct occurrences of the event parameter**. 5. In the **Size** field, enter the number of returned categories. 5. Select the **product.buy** event. 6. Select the **category** parameter. 7. Define the period from which the aggregate will return products from the event. This period will affect which purchases are included when checking for categories to exclude from the recommendation. 8. Save the aggregate.

Decision Hub Last Multi aggregate returning the distinct categories of recently purchased products — Configuration of the aggregate

## Create a recommendation --- 1. Go to

**AI Hub > (AI Recommendations) Models > Add recommendation**. 3. In the top left corner, enter the name of your recommendation. 4. In the **Type & Items feed** section, click **Define**. 5. From the **Items feed** dropdown menu, choose the provided feed. 6. Choose the **Personalized** recommendation type. 7. Click **Apply**.

8. In the **Items** section, click **Define**. 1. Click **Add slot**. 2. Define the minimum and maximum number of items that will be recommended to the user in each slot. In our example, one slot returns 4 products. In the **Items** section, click the **Define** button. Click the plus button to add more slots. This will allow you to define new slots for your recommendation setup. In the slot settings, specify the minimum and maximum number of items to be recommended to the user within this slot. 3. Click **Static filter**.

Learn about the difference between [elastic, static](/docs/ai-hub/recommendations-v2/creating-recommendation-campaign#select-conditions-of-displaying-items), and [distinct](/docs/ai-hub/recommendations-v2/creating-recommendation-campaign#distinct-filter) filters.

4. From the dropdown list, choose **Visual Builder**. 2. Click **Select attribute**. 3. From the dropdown list, choose the **category** attribute. 4. Click **Operator**. 5. From the dropdown list, choose **Does not equal**. 6. Click the value type icon (

) and choose the aggregate icon from the list. 7. From the dropdown list, choose [the aggregate you have created](/use-cases/reco-excluding-recently-purchased-category#create-an-aggregate). 8. In the **Level range** input area that appear, you can choose how you want to select your category level. Choose: **Whole category.**

If your products categories have a `X > Y > Z` structure, level 0 will be `X > Y > Z`. Level 1 will be `X > Y` and so on. Here, you define how granular the category recommendations will be. For example, if you are selling shoes, you will have an `Outdoor > Sport > Running` category and an `Outdoor > Sport > Football` category. If level 0 is selected, the two categories are excluded. If level 1 is provided, the `Outdoor > Sport` category and any of its subcategories will be excluded.

14. Click **Apply**.

9. In the **Items** section, click **Apply**. 10. Optionally, you can define the settings in the **Boosting** and **Additional settings** sections.

Learn more about [boosting](/docs/ai-hub/recommendations-v2/creating-recommendation-campaign#define-the-boosting-factors) and [additional settings](/docs/ai-hub/recommendations-v2/creating-recommendation-campaign#additional-settings).

11. Save the recommendation. ## What's next --- You can display the recommendation to customers in a number of ways. For example by using the [recommendation insert](/developers/inserts/recommendations-v2) in [dynamic content](/docs/campaign/dynamiccontent/creating-dynamic-content), or in mobile application with content widget, both on [Android](/developers/mobile-sdk/displaying-recommendations/content-widget/android) and [iOS](/developers/mobile-sdk/displaying-recommendations/content-widget/ios). ## Check the use case set up on the Synerise Demo workspace --- You can also check [the aggregate](https://app.synerise.com/analytics/aggregates/474a464f-175e-34e4-9890-ce922955390e) and [recommendation configuration](https://app.synerise.com/ai-v2/recommendations/wWmX7O8uxptZ) directly in Synerise Demo workspace. If you’re our partner or client, you already have automatic access to the **Synerise Demo workspace (1590)**, where you can explore all the configured elements of this use case and copy them to your workspace. If you’re not a partner or client yet, we encourage you to fill out the contact [form](https://demo.synerise.com/request) to schedule a meeting with our representatives. They’ll be happy to show you how our demo works and discuss how you can apply this use case in your business. ## Generated events This use case generates approximately 3 events per profile that completes the flow: [`recommendation.generated`](/docs/assets/events/event-reference/recommendations#recommendationgenerated) (~1), [`recommendation.view`](/docs/assets/events/event-reference/recommendations#recommendationview) (~1), [`recommendation.click`](/docs/assets/events/event-reference/recommendations#recommendationclick) (~1). ## Read more --- - [Creating aggregates](/docs/crm/aggregates/creating-profile-aggregates) - [Creating recommendations](/docs/ai-hub/recommendations-v2/creating-recommendation-campaign) - [Filters in recommendations](/docs/ai-hub/recommendations-v2/recommendation-filters) - [Requirements for item feed](/docs/ai-hub/recommendations-v2/item-feed-requirements) # Promotion for the first transaction after joining the loyalty program It is very important to engage new users who have just joined your in-app loyalty program and encourage them to make purchases. For this purpose, you can use a push notification that will automatically notify them about a promotion in the application that will give them a discount on their first purchase. This is a good way to generate profits, especially if the promotion is time limited and the first purchases must be made within a certain period. This approach can lead to boosting customer satisfaction, increasing revenue and customer loyalty to your business. In this use case, we will create a promotion for new loyalty program members and a workflow which will send a mobile push notification with the information about the special promotion in the mobile app (10% discount for the whole cart). The promotion will be available for 14 days from the date of joining the loyalty program and can be used only once. ## Prerequisites --- - [Implement Synerise SDK in your mobile app](/developers/mobile-sdk). - [Implement promotions in your mobile application](/developers/mobile-sdk/loyalty) and through [API](https://hub.synerise.com/api-reference/loyalty-and-engagement#operation/profileLogin). - Implement mobile pushes in your mobile application: [iOS](/developers/mobile-sdk/configuring-push-notifications/ios), [Android](/developers/mobile-sdk/configuring-push-notifications/android). - Collect the [custom event](/developers/mobile-sdk/event-tracking) which sends information to Synerise about joining a loyalty program (for example `account.status` with parameter `accountStatus` equal to `active`). Such an event with the appropriate status should be sent each time the membership status changes (when the customer resigns from the program or joins again).

In this case, when a customer joins the loyalty program, a custom event is generated on their card. However, these conditions and the scenario can be adapted to your business needs, for example, you can count the customers who joined the loyalty program using the registration event in the mobile application.

## Process --- In this use case, you will go through the following steps: 1. [Create aggregates](/use-cases/discount-promotion-for-first-transaction#create-aggregates) which return the time of joining the loyalty program and current status of customer's membership. 2. [Create a segmentation](/use-cases/discount-promotion-for-first-transaction#create-a-segmentation) of customers who have your mobile app and joined the loyalty program during last 14 days. 3. [Create a promotion](/use-cases/discount-promotion-for-first-transaction#create-a-promotion). 4. [Prepare a mobile push notification](/use-cases/discount-promotion-for-first-transaction#prepare-a-mobile-push-notification) with information about the promotion. 5. [Create a workflow](/use-cases/discount-promotion-for-first-transaction#create-a-workflow) to send the mobile push. ## Create aggregates --- ### Time of joining the loyalty program Start with creating an aggregate that returns the time of the first occurrence of the `account.status` event. 1. Go to

**Behavioral Data Hub > Live Aggregates > Create aggregate**. 2. As the aggregate type, select **Profile**. 2. Enter the name of the aggregate. 3. Click **Analyze profiles by** and select **First**. 4. Select the event `account.status`. 5. As a parameter choose **Timestamp**. 6. Select the **accountStatus**. 7. Use operator **equal** and add as the value `active`. 8. Define the period for the event as **Lifetime**. 9. **Save** the aggregate.

Decision Hub First aggregate returning the TIMESTAMP of the first account.status event with active status over a customer's lifetime — Configuration of the aggregate

### Current status of the membership Create the second aggregate analyzing the current status of the customer's membership. 1. Go to

**Behavioral Data Hub > Live Aggregates > Create aggregate**. 2. As the aggregate type, select **Profile**. 2. Enter the name of the aggregate. 3. Click **Analyze profiles by** and select **Last**. 4. Select the event **account.status**. 5. As a parameter choose **accountStatus**. 6. Define the period for the event as **Lifetime**. 7. To save the aggregate, click **Save**.

Decision Hub Last aggregate returning the last accountStatus parameter of account.status events in a customer's lifetime — Configuration of the aggregate

## Create a segmentation --- In this part of the process, you create a segmentation of customers who installed your mobile app and joined the loyalty program during last 14 days. 1. Go to

**Decision Hub > Segmentations > New segmentation**. 2. Enter the name of segmentation. 3. Choose **Add condition** and find the [aggregate counting the time of joining the loyalty program](/use-cases/discount-promotion-for-first-transaction#time-of-joining-the-loyalty-program), created in the previous step. 4. Choose option **Custom** and select the date range as last 14 days. This way we can be sure that we analyze only the customers who joined the loyalty club for the first time during last 14 days (time in which the promotion is available), and we exclude the customers who join the club, resign and try to join another time to use the promotion for the second time. 5. Choose **Add condition** and find the [aggregate analyzing the active status of the customer's membership](/use-cases/discount-promotion-for-first-transaction#current-status-of-the-membership), created in the previous step. 6. As an operator, choose **Equal** and add the value `active`. 7. Save the aggregate.

## Create a promotion --- Create a promotion for customers who joined the loyalty program. The promotion gives a 10% discount for the entire transaction and is valid only once per user. It will be targeted for the audience created in the previous step. 1. Go to

**AI Hub > Regular Promotions > Add promotion**. 2. Select the **For entire cart** option. 3. In the **Audience** section, select the segmentation created in [this step](/use-cases/discount-promotion-for-first-transaction#create-a-segmentation). Your promotion will be activated only for this group of customers. Confirm your selection, by clicking **Apply**. 4. In the **Content** section, define the name, description, and an image of the promotion. Confirm the settings by clicking **Apply**. 5. In the **Limit per profile** field, enter `1` to make sure that this discount can be used only once. 6. In **Type & limits** section: 1. As a Discount type, choose **Percentage**. 2. In the Cart section, as the minimum value, enter `10`, and click **Apply**. 6. In the **Schedule** section, define the distribution period. 7. **Optional**: In the **Stores** section, specify stores where the promotion is available.

This is possible only if the list of stores is imported into a [catalog](/docs/assets/catalogs).

8. In **Items** section, choose the main product catalog with all products a customer can buy with this discount. If you want to narrow down the list of categories a customer can choose from, use one of the options presented below (Selected items/Filtered items). If discount should be active for all products, choose **Entire catalog**. 9. In **Exclude items** section, you can exclude a specific product or categories for which the discount is not active. 10. To apply all changes and run the promotion, click **Publish**. Once the promotion is published, it will be visible immediately to all customers defined in the **Audience** section in your mobile app (users who joined loyalty program during last 14 days). ## Prepare a mobile push notification --- 1. Go to **Experience Hub > Mobile > Templates**. 2. Create your mobile push in the code editor. For more information on creating a simple mobile push, visit our [User Guide](/docs/campaign/Mobile/creating-mobile-push).

## Create a workflow --- In this part of the process, prepare a workflow that notifies customers who joined loyalty program about the promotion in the mobile app. 1. Go to **Automation Hub > Workflows > New workflow**. 2. Enter the name of the workflow. 3. As the first node of the workflow, add **Profile Event**, and choose the event which signifies joining the loyalty program. 4. As the next node, choose **Delay**. In the settings of the node, set the delay period to 10 minutes. 5. Add **Profile Filter** to check if the user made a transaction during last 10 minutes. To do it, select the `transaction.charge` event and set up the time range as last 10 minutes. Mark this filter as not matched. 6. As the last node, add **Send Mobile Push** for users who matched used Profile Filter. In the configuration of the **Send Mobile Push** node: 1. Select the type of the mobile push notification.. 2. Select the push template created in [this part](/use-cases/discount-promotion-for-first-transaction#prepare-a-mobile-push-notification) of the process. 6. Set up the Action limit for the Send Mobile Push as one time per workflow. 7. Set the capping for the workflow to make sure that it will be available once for every user (choose very distant date for example, once in 1000 months). 7. Confirm the settings by clicking **Apply**. 7. Add the **End** node to finish the workflow. 8. Click **Save & Run**.

Automation Hub workflow for sending a discount promotion on first transaction — Workflow configuration

## Check the use case set up on the Synerise Demo workspace --- In the Synerise Demo workspace, you can check: - [Segmentation](https://app.synerise.com/analytics-v2/segmentations/e87b4f75-803a-4593-9649-9c35bae5b377) - [Aggregate returning the time of joining the loyalty program](https://app.synerise.com/analytics/aggregates/9b862d15-7301-31c1-a830-ea6b5c3e392d) - [Aggregate returning current status of membership](https://app.synerise.com/analytics/aggregates/4538a92b-b5e7-338e-a7f0-a4c690b63272). - [Promotion](https://app.synerise.com/campaigns/promotions/de7a11c5-795f-4eda-ade6-cc45f021022c) - [Workflow](https://app.synerise.com/automations/automation-diagram/3b673608-34c4-4013-8d60-99f01b0a8cf1) If you’re our partner or client, you already have automatic access to the **Synerise Demo workspace (1590)**, where you can explore all the configured elements of this use case and copy them to your workspace. If you’re not a partner or client yet, we encourage you to fill out the contact [form](https://demo.synerise.com/request) to schedule a meeting with our representatives. They’ll be happy to show you how our demo works and discuss how you can apply this use case in your business. ## Generated events This use case generates approximately 9 events per profile that completes the flow: `account.status` (~1), [`automation.clientStartPath`](/docs/assets/events/event-reference/automation#automationclientstartpath) (~1), [`automation.clientPathStep`](/docs/assets/events/event-reference/automation#automationclientpathstep) (~3), [`automation.clientEndPath`](/docs/assets/events/event-reference/automation#automationclientendpath) (~1), [`push.send`](/docs/assets/events/event-reference/mobile-push#pushsend) (~1), [`push.view`](/docs/assets/events/event-reference/mobile-push#pushview) (~1), [`push.click`](/docs/assets/events/event-reference/mobile-push#pushclick) (~1). ## Read more --- - [Creating promotions](/docs/ai-hub/promotions) - [Loyalty programs basics](/use-cases/loyalty-programs-basics) - [Mobile push notifications](/docs/campaign/Mobile) - [Workflow](/docs/automation/creating-automation) # Send a message encouraging replenishment on WhatsApp WhatsApp is a trusted platform by millions of users worldwide, making it a valuable channel for customer communication. It's a channel where you can get closer to your customers by forming personalized communication with them, building a stronger bond with your brand, and increasing loyalty. Thanks to Synerise's integration with WhatsApp, you have unlimited possibilities to customize your communication with customers. You can take advantage of all the insights you collect in Synerise and use them effectively to deliver the greatest value to your customers. This use case shows a scenario with a replenishment campaign. You will learn how to perform a simple integration with WhatsApp to send a personalized message to customers encouraging them to reorder a product from a specific category, additionally incentivizing the reorder by giving them a discount code for that purchase.

## Prerequisites --- - Make sure you meet all [prerequisites](/docs/automation/integration/whats-app/send-template-message#prerequisites) to work with the **Send Template Message** node. - Implement transaction events either through [SDK](/developers/web/transactions-sdk) or [API](https://hub.synerise.com/api-reference/data-management#operation/CreateATransaction). - Create [item feed](/docs/ai-hub/recommendations-v2/item-feed-requirements) - Create a [voucher pool](/docs/assets/code-pools). The ID of this voucher pool will be used as a dynamic value during the message creation process, allowing discount codes to be assigned to each customer participating in this scenario. ## Process --- 1. [Create an aggregate](/use-cases/send-replenishment-message-on-whats-app#create-an-aggregate) which returns the SKU of the last purchased product from the specified category. 2. [Create a message template in the Meta portal](/use-cases/send-replenishment-message-on-whats-app#create-a-message-template-in-the-meta-portal) 3. [Create a workflow to send a message to customers on WhatsApp](/use-cases/send-replenishment-message-on-whats-app#create-a-workflow-to-send-message-to-customers-on-whatsapp) ## Create an aggregate --- In this part of the process, create an aggregate that returns the SKU of the last purchased product from the `Coffee` category. 1. Go to

**Behavioral Data Hub > Live Aggregates > Create aggregate**. 2. As the aggregate type, select **Profile**. 2. Enter the name of the aggregate. 3. Click **Analyze profiles by** and select **Last**. 4. From the **Choose event** dropdown list, select the `product.buy` event. 4. As the event parameter, select **$sku**. 5. Next to the **$sku**, click **+where**. 6. From the dropdown list, select **$category**. 7. As the operator, choose **Equal**. 9. In the text field, enter the value of the category you want to use in replenishment campaign - in this use case, it will be `Coffee`. 8. Define the period analyzed in the aggregate. 9. Save the aggregate.

Decision Hub Last aggregate returning the SKU of the last Coffee category product.buy event — Configuration of the aggregate

## Create a message template in the Meta portal --- Create a message template in the Meta portal that you will use in the next part of the process. In the body of the message, mark places where the dynamic elements will be added. In addition, if you would like to add a CTA at the end of the message, you can add a button and define its copy. The page to which the customer will be redirected after clicking the button can be defined in Synerise. The example message used in this use case: `Hello {{1}}, it looks like you’re almost out of Coffee! Make an order for {{2}} now before it’s too late. Use the {{3}} code to get your 20% discount on your next purchase.` Where `{{1}}, {{2}}` and `{{3}}` are markers that will be replaced with the dynamic values. This step will be done in Synerise. The screen below shows an example of creating a template message in the Meta portal:

An example of body section configuration in Meta platform

In the following screen, you can see how a button can be defined in the Meta portal:

An example of button section configuration in Meta platform

## Create a workflow to send message to customers on WhatsApp --- The workflow will be triggered by the `product.buy` event from the selected product category. The delay is defined up to 30 days. If a customer does not make another purchase from the defined category after that period, we will send a WhatsApp message with the recommended products from the defined category. 1. In Synerise, go to

**Automation Hub > Workflows > New workflow**. 2. Enter the name of the workflow. ### Define the trigger node 3. As the trigger node, add **Profile Event**. In the configuration of the node, select the event that triggers the workflow. In this use case, it's a `product.buy` event. 4. Click **+ where** and choose **$category**. 5. As the logical operator, select **Equal**. 6. In the text field, enter `Coffee`. 4. Confirm by clicking **Apply**.

Configuration of the Profile Event node

### Configure the Delay node 1. Add the **Delay** node. In the node settings: 1. In the **Delay** field, type `30`. 2. From the dropdown list, choose **Day**. 2. Click **Apply**. ### Define the profile filter node As the next node, choose **Profile Filter** to check if customers have bought a product from the Coffee category during last 30 days. To do this: 1. Choose the `product.buy` event. 2. As the parameter, choose **$category**. 5. As the logical operator, select **Equal**. 6. In the text field, enter `Coffee`. 3. Set the time range to last 30 days. 4. Click **Apply**. 7. To the **Matched** path, add the **End** node.

Configuration of the Profile Filter node

### Define the Send Template Mesage node 8. To the **Not matched** path, add the WhatsApp **Send Template Message** node. 1. Click **Select connection**. 2. From the dropdown list, select the connection. - If no connections are available or you want to create a new one, see [Create a connection](/docs/automation/integration/whats-app/send-template-message#create-a-connection). - If you selected an existing connection, proceed to defining the integration settings. 3. In the **Sender ID** field, enter the phone number ID from which the message will be sent. [You can find more information about phone number ID here](https://developers.facebook.com/docs/whatsapp/cloud-api/get-started/add-a-phone-number). 4. In the **Receiver** field, enter the phone number of the customer who will receive this message. We recommend using the `{% customer phone %}` insert, which inserts the phone number of an individual customer who goes through this node. 5. In the **Message template** field, enter the name of the [message template](/use-cases/send-replenishment-message-on-whats-app#create-a-message-template-in-the-meta-portal) you created earlier in the Meta portal. 6. From the **Language code** dropdown list, select the language used in the message. 7. In the **Message components** field, insert the object that contains the dynamic values in the order defined in the message template. The example of object used in this use case:

The aggregate and voucher pool IDs are used as examples for the purpose of this use case.

[
     {
            "type": "body",
            "parameters": [
            {
                "type": "text",
                "text": "{% customer firstname %}"
            },
            {
                "type": "text",
                "text": "{% aggregate c37acfe7-08a1-345c-a3e7-da795bb6a326 %}{% for item in aggregate_result %}{% catalog.store-1(item).name %}{% endfor %}{% endaggregate %}"
            },
            {
                "type": "text",
                "text": "{% voucher %} 8c3c8fd3-e7e9-487d-ba89-0b7824f65f33 {% endvoucher %}"
            }
        ]
    }, 
    { 
        "type": "button", 
        "parameters":
        "index": "0",
        "sub_type": "url", [
            {
                "type": "url",
                "text": "{% aggregate c37acfe7-08a1-345c-a3e7-da795bb6a326 %}{% for item in aggregate_result %}{% catalogvar.store-1(item).url %}{{ catalog_result|replace('https://yourshop.com', '') }}{% endcatalogvar %}{% endfor %}{% endaggregate %}" 
            }
        ]
    },
    { 
        "type": "header",
        "parameters": [ 
            {
                 "type": "image",
                 "image": {
                      "link": "{% aggregate c37acfe7-08a1-345c-a3e7-da795bb6a326 %}{% for item in aggregate_result %}{% catalogvar.store-1(item).image %}{{ catalog_result }}{% endcatalogvar %}{% endfor %}{% endaggregate %}"
                 }
             }
         ]
     }
   ]

9. Click **Apply**. The following table explains all the inserts used in the body, button and header sections shown above. | Section | Insert value | Insert explanation | |---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | body | `{% customer firstname %}` | The value of this insert is used as the value of `{{1}}`, so the name of a customer can be displayed in the message. | | body | `{% aggregate c37acfe7-08a1-345c-a3e7-da795bb6a326 %} {% for item in aggregate_result %} {% catalog.store-1(item).name %} {% endfor %} {% endaggregate %}` | The value of this insert is used as the value of `{{2}}` to return a product that the customer bought the last time and did not purchase again within the estimated time period. | | body | `{% voucher %} 8c3c8fd3-e7e9-487d-ba89-0b7824f65f33 {% endvoucher %}` | The value of this insert is used as the value of `{{3}}`. In this example, we assign a voucher code from the voucher pool to an individual customer. | | button | `{% aggregate c37acfe7-08a1-345c-a3e7-da795bb6a326 %}{% for item in aggregate_result %}{% catalogvar.store-1(item).url %}{{ catalog_result\|replace('https://yourshop.com', '') }}{% endcatalogvar %}{% endfor %}{% endaggregate %}` | The value of this insert is used to return product url. Here we specify the URL omitting the domain, because we define the domain in the Meta platform, as you can see in the screenshot with the [button creation](/use-cases/send-replenishment-message-on-whats-app#create-a-message-template-in-the-meta-portal). | | header | `{% aggregate c37acfe7-08a1-345c-a3e7-da795bb6a326 %}{% for item in aggregate_result %}{% catalogvar.store-1(item).image %}{{ catalog_result }}{% endcatalogvar %}{% endfor %}{% endaggregate %}` | This value of insert is used to return the url to the product image in header. |

Automation Hub workflow for sending a replenishment WhatsApp message — Workflow configuration

## Check the use case set up on the Synerise Demo workspace --- You can check the configuration of the [aggregate](https://app.synerise.com/analytics/aggregates/c37acfe7-08a1-345c-a3e7-da795bb6a326) and the [workflow](https://app.synerise.com/automations/automation-diagram/998f1dc1-932d-4636-bb98-d1d823b00af6) directly in our Synerise Demo workspace. If you’re our partner or client, you already have automatic access to the **Synerise Demo workspace (1590)**, where you can explore all the configured elements of this use case and copy them to your workspace. If you’re not a partner or client yet, we encourage you to fill out the contact [form](https://demo.synerise.com/request) to schedule a meeting with our representatives. They’ll be happy to show you how our demo works and discuss how you can apply this use case in your business. ## Generated events This use case generates approximately 8 events per profile that completes the flow: [`product.buy`](/docs/assets/events/event-reference/items#productbuy) (~1), [`automation.clientStartPath`](/docs/assets/events/event-reference/automation#automationclientstartpath) (~1), [`automation.clientPathStep`](/docs/assets/events/event-reference/automation#automationclientpathstep) (~3), [`automation.clientEndPath`](/docs/assets/events/event-reference/automation#automationclientendpath) (~1), [`voucherCode.assigned`](/docs/assets/events/event-reference/loyalty#vouchercodeassigned) (~1), [`whatsapp.sendTemplateMessage`](/docs/assets/events/event-reference/integration#whatsappsendtemplatemessage) (~1). ## Read more --- - [Aggregates](/docs/crm/aggregates) - [Automation Hub](/docs/automation) - [Jinjava inserts](/developers/inserts) - [Recommendations](/docs/ai-hub/recommendations-v2) - [WhatsApp **Send Template Message** node](/docs/automation/integration/whats-app/send-template-message) # Predict replenishment Recurring purchases are those purchases that are usually made with some frequency and regularity, such as the purchase of coffee, printer paper, hygiene products, etc. Products purchased on a regular basis fill the greater part of most customers' shopping baskets. That's why it's so important to provide customers with the best experience when making such purchases, reminding them of an upcoming purchase and encouraging them to return more often for these products in your store. The prediction created in this case is based entirely on analytics and calculates the average time between purchases for customers who have made at least three transactions in a given category, so we can calculate when a customer may make the next purchase, anticipating their intention by sending them an email reminder of the upcoming purchase. The described process consists of two automations, where one calculates the average interval between purchases and the other sends an email to the customer at the appropriate time to encourage to replenishment.

Communication for customers making repetitive coffee purchases

## Prerequisites --- - Implement transaction events using [SDK](/developers/web/transactions-sdk) or [API](https://hub.synerise.com/api-reference/data-management#operation/CreateATransaction). - [Create an email account](/docs/campaign/e-mail/configuring-email-account). - [Create an email template](/docs/campaign/e-mail/creating-email-templates) to be used in the email campaign.

We recommend including an [insert](/developers/inserts/recommendations-v2) in the email template with a product recommendation from the specific category to make the buying decision process easier for customers. You can refer to [this use case](/use-cases/personalized-category-reco#create-a-recommendation) to see how to build recommendations filtered to the product category.

## Process --- 1. [Create an event expression](/use-cases/repetitive-purchases#create-an-expression) that converts the time of transaction to a number. 2. [Create an aggregate](/use-cases/repetitive-purchases#create-an-aggregate) that returns the timestamps of the purchased products from the specific category. 3. [Create a workflow](/use-cases/repetitive-purchases#create-a-workflow-to-predict-purchase-time) that calculates the average number of days between a customer's purchases of a product in a specific category and calculates the date of the next purchase based on that number. 4. [Create a workflow](/use-cases/repetitive-purchases#create-a-workflow-to-encourage-a-purchase) that is responsible for sending a reminder to a customer about the next recurring purchase. ## Create an expression --- In this part of the process, you need to create an event expression that converts the timestamp of transaction to a number. This expression will be used later to create an aggregate. 1. Go to

**Behavioral Data Hub > Expression > New expression**. 2. Enter the name of the expression. 3. Set the **Expression for** option to **Event**. 4. From the drop-down list, select **product.buy**. 5. In the **Formula definition** section, click **Select**. 6. From the list that opens, select **Function > To number**. 7. In the brackets, click the **Select** button and from the list, select **Event attribute**. 8. Click the **Unnamed** node that appeared. 9. At the bottom of the page, click **Choose parameter**. 10. In the list of attributes, find and select **TIMESTAMP**. 11. Save the expression.

An expression that converts the timestamp to a number

## Create an aggregate --- In this part of the process, you create a dynamic aggregate that returns timestamps of purchases from a specific category. The aggregate will return timestamps (as numbers) from **product.buy** events. 1. Go to

**Behavioral Data Hub > Live Aggregates > Create aggregate**. 2. As the aggregate type, select **Profile**. 2. Enter a meaningful name of the aggregate. 3. Click **Analyze profiles by** and select **Last Multi** and size `15`.

This is the maximum number of a customer's past transactions to be used in the calculation. You can change the number according to your business needs.

4. Select **Consider only distinct occurences of the event parameter**. 5. Select the **product.buy** event. 6. From the **Choose event** drop-down list, select the expression you created [in the previous step](/use-cases/repetitive-purchases#create-an-expression). 7. Click the **+ where** button and from the **Choose parameter** drop-down menu, choose **category**. 8. From the **Choose operator** drop-down, choose **Equal**. 9. Enter the name of the product category. In our example, it's `coffee`. 10. Define the time range as **Last 365 days**. 11. Confirm by clicking **Apply**.

The final configuration of the aggregate — The final configuration of an aggregate

## Create a workflow to predict purchase time --- You need to create a workflow that calculates the average number of days between a customer's purchases from a given category. The result is used to calculate the customer's next purchase probability. 1. Go to **Automation Hub > Workflows > New workflow**. 2. Enter the name of the workflow. ### Define the Profile Event trigger node At this stage you will configure the conditions that will trigger the workflow. As a trigger, you will use the `product.buy` event for the coffee category. 1. As the first node of the workflow, add **Profile Event**. In the configuration of the node: 1. From the **Choose event** drop-down menu, choose the **product.buy** event. 2. Click the **+ where** button and from the **Choose parameter** drop-down menu, choose **category**. 3. From the **Choose operator** drop-down, choose **Equal**. 4. Enter the name of the product category for which you want to predict the time of the customer's next purchase. In our case, it's `coffee`. 5. Confirm by clicking **Apply**. ### Define the Profile Filter node In this part of the process, you need to identify customers for whom the workflow calculates the date of next purchase. It takes into consideration customers who have made at least three separate transactions (**transaction.charge** event) with products from the "coffee" category. 1. Add the **Profile Filter** node. 2. Click the node to open its settings. 3. Click the **Choose filter** button and choose the **product.buy** event. 4. Click the **+ where** button and from the **Choose parameter** drop-down menu, choose **category**. 5. From the **Choose operator** drop-down, choose **Equal**. 6. Enter the name of the product category for which you want to predict the time of the customer's next purchase. In our case it's `coffee`. 7. Click **+ Add funnel step** button and repeat steps 3-6. 8. Set the time range to **Last 365 days before 1 days**. 9. Click the **Choose filter** button and choose the **transaction.charge** event. 10. Click **+ Add funnel step** button and another **transaction.charge** event. 11. Set the time range to **Last 365 days before 1 days**. 12. Confirm by clicking **Apply**. 13. For the **Not matched** path, add the **End** node.

The Profile Filter node configuration

### Define the Generate Event node At this stage, an event is generated on the customer's profile, returning the number of days between purchases and the date when the customer may make the next purchase. It contains the following parameters: - **category** - the category of products for which the calculation is made, - **itemId** - the ID of last product bought from the specific category, - **predictedTime** - calculated date of the next purchase from the specific category, - **predictedTimeInDays** - average number of days between purchases from the specific category. 1. To the **Matched** path of the **Profile Filter** node created earlier, add a **Generate Event** node. In the configuration of the node: 1. In the **Event name**, enter the name of the event that will be generated on the customer's profile. In this case, it is `product.purchasePredictedTime` 3. Add the JSON body of the event. You can use the example below.

Example jinjava code

{ "category": "coffee", "itemId": "{{ event.params.$sku }}", "predictedTime": "{% set avgTime = [] %}{% aggregate PASTE_AGGREGATE_ID_HERE %}{%set timeDiff = []%}{% for item in range(aggregate_result|length-1) %}{%set diff = aggregate_result[loop.index] - aggregate_result[loop.index-1]%}{% do timeDiff.append(diff)%}{% endfor %}{% set temp = timeDiff|sum/(aggregate_result|length-1) %}{% do avgTime.append(temp) %}{{ datetimeformat(unixtimestamp(null) + avgTime[0], '%Y-%m-%d') }}{% endaggregate %}", "predictedTimeInDays": "{{avgTime[0]/86400000}}" }

The above jinjava code contains the logic of calculating the average number of days between purchases from the specific category and calculating the date of a next purchase. It can be copied 1:1 into the Generate Event node. However, remember to replace the ID of aggregate in this code with the [ID of the aggregate created earlier in the process](/use-cases/repetitive-purchases#create-an-aggregate).

4. Confirm by clicking **Apply**.

Configuration of the Generate Event node

Example of a generated **product.purchasePredictedTime** event:

### Add final settings to your workflow 1. Add the **End** node. 2. Launch the workflow by clicking **Save & Run**.

Automation Hub workflow for re-engaging customers with repetitive purchase patterns — Configuration of the workflow

## Create a workflow to encourage a purchase --- With the above workflow in place, you can create another workflow in which you send a message reminding the customer of the next purchase. This workflow starts each day for a group of customers whose expected purchase date is the current day. 1. Go to **Automation Hub > Workflows > New workflow**. 2. Enter the name of the workflow. ### Define the Audience node In this stage, you create an Audience that checks for the presence of the **product.purchasePredictedTime** event on a user's card in the last 30 days with a specific product category (in our case, coffee), where the predicted purchase date is on the current day. In addition, the Audience filter includes only those customers who have agreed to receive communications. 1. Start the workflow with the **Audience** node and open the node's settings. 2. In **Define audience**, choose **New Audience** and click **Define conditions**. 3. From the **Choose filter** drop-down menu, choose the **product.purchasePredictedTime** event. 4. Click the **+ where** button and from the **Choose parameter** drop-down menu, choose **predictedTime**. 5. From the **Choose operator** drop-down menu, select **Date > Current date > Matches current day**. 6. Click the **+ where** button and from the **Choose parameter** drop-down menu, choose **predictedTime**. 7. From the **Choose operator** drop-down menu, select **Date > Current date > Matches current month**. 8. Click the **+ where** button and from the **Choose parameter** drop-down menu, choose **predictedTime**. 9. From the **Choose operator** drop-down menu, select **Date > Current date > Matches current year**. 10. Click the **+ where** button and from the **Choose parameter** drop-down menu, choose **category**. 11. From the **Choose operator** drop-down, choose **Equal**. 12. Type the name of the product category - `coffee`. 13. Define the time range to the **Last 30 days**. 14. From the **Choose filter** drop-down, choose the **newsletter_agreement** parameter. 15. From the **Choose operator** drop-down, choose **Equal** and and specify the condition as **enabled**. 16. Confirm by clicking **Apply**.

Configuration of the Audience node

### Define the Send Email node In this step, choose an email template for the upcoming purchase. 1. To the **Matched** path, add the **Send Email** node and open its settings. 2. In the **Sender details** section, choose the email account from which the email is sent. 3. In the **Content** section, select the template that you prepared as a part of the prerequisites. 4. **Optional**: In the **UTM & URL parameters** section, define the UTM parameters added to the links included in the email. 5. In the **Additional parameters** section, optionally describe campaigns with [additional parameters](/docs/campaign/e-mail/creating-email-campaigns#adding-custom-parameters). 6. Click **Apply**. ### Add final settings to your workflow 1. Add the **End** node. 2. Launch the workflow by clicking **Save & Run**.

Automation Hub workflow for sending upcoming purchase reminder notifications — Configuration of the workflow

## Check the use case set up on the Synerise Demo workspace --- You can check the configuration of each step directly in the Synerise Demo workspace: - [Expression](https://app.synerise.com/analytics/expressions/04e342d8-5e14-4d7b-be39-a6bf117c1bff) - [Aggregate](https://app.synerise.com/analytics/aggregates/0b329a23-4a80-3522-8938-981254f92150) - [Workflow for purchasing time calculations](https://app.synerise.com/automations/automation-diagram/44c9e618-f72a-4720-8dbc-774f8752ad30) - [Workflow for sending a mailing communication](https://app.synerise.com/automations/automation-diagram/dfaf267d-c186-40c3-965f-810646b4a982) If you’re our partner or client, you already have automatic access to the **Synerise Demo workspace (1590)**, where you can explore all the configured elements of this use case and copy them to your workspace. If you’re not a partner or client yet, we encourage you to fill out the contact [form](https://demo.synerise.com/request) to schedule a meeting with our representatives. They’ll be happy to show you how our demo works and discuss how you can apply this use case in your business. ## Generated events This use case generates approximately 12 events per profile that completes the flow: [`product.buy`](/docs/assets/events/event-reference/items#productbuy) (~1), [`automation.clientStartPath`](/docs/assets/events/event-reference/automation#automationclientstartpath) (~2), [`automation.clientPathStep`](/docs/assets/events/event-reference/automation#automationclientpathstep) (~3), [`automation.clientEndPath`](/docs/assets/events/event-reference/automation#automationclientendpath) (~2), `product.purchasePredictedTime` (~1), [`message.send`](/docs/assets/events/event-reference/email#messagesend) (~1), [`newsletter.open`](/docs/assets/events/event-reference/email#newsletteropen) (~1), [`newsletter.click`](/docs/assets/events/event-reference/email#newsletterclick) (~1). ## Read more --- - [Aggregates](/docs/crm/aggregates) - [Automation Hub](/docs/automation) - [Email campaigns](/docs/campaign/e-mail) - [Expressions](/docs/crm/expressions) - [Segmentation](/docs/analytics/segmentations) # Send offline conversion to Google Ads With Synerise, businesses can optimize their marketing strategies and bridge the gap between digital advertising and brick-and-mortar sales. By integrating online and offline operations, you can accurately track conversions from Google Ads when customers purchase through an ad and choose in-store pickup and payment. Thanks to Synerise's integration with Google Ads, you can automate the process of sending offline conversions to your Google Ads account. This seamless attribution of offline conversions to specific ad campaigns empowers businesses to optimize their marketing strategies and successfully connect digital advertising with brick-and-mortar sales. It's important to note that an offline conversion can encompass various offline events, such as visiting a store, restaurant, or any other conversion event your business recognizes. In this use case, we will create a workflow to send offline conversion data to Google Ads. The workflow will be triggered by a custom event - purchase through an ad with in-store pickup and payment. ## Prerequisites --- - [Implement SDK to a website](/developers/web/installation-and-configuration) to which a profile is referred after clicking the ad. - [Implement sending events about completing offline conversion](https://hub.synerise.com/api-reference/data-management#operation/CustomEvent). It can include `value` and `currency` parameters (there is an option to send these additional parameters to Google Ads) - Create a Google Ads account. - Launch an ad campaign through Google Ads. - [Create an event expression](/docs/automation/integration/google-ads/google-ads-send-offline-conversions#create-an-expression) to extract the `gclid` parameter from the URL of visited website. - [Create an aggregate](/docs/automation/integration/google-ads/google-ads-send-offline-conversions#create-an-aggregate) that retrieves the value of the `gclid` parameter from the latest page visit to your website (or according to your business needs).

In this case, the conversion will be attributed to the last clicked ad before the conversion. This attribution is configurable, allowing you to determine which clicked ad should be associated with the conversion. You can configure these settings by specifying the date or other conditions, or by changing the aggregator from "last" to "first."

## Create a workflow to send conversion data to Google Ads --- Create a workflow which sends offline conversion data to Google Ads, after a customer pays for an order in a brick-and-mortar store. 1. Go to

**Automation Hub > Workflows > New workflow**. 2. Enter the name of the workflow. ### Define the trigger node As a trigger, we will use the `offline.transaction` custom event for a transaction made in brick-and-mortar store when picking up an order. 1. As the first node of the workflow, add **Profile Event**. 2. In the configuration of the node, from the **Choose event** dropdown menu, choose `offline.transaction` event. 2. Click **Apply**. ### Configure the Send Offline Conversion node 1. As the next node, add **Google Ads > Send Offline Conversion**. 2. In the configuration of the node, from the dropdown list, select the connection. - If no connections are available or you want to create a new one, see [Create a connection](/docs/automation/integration/google-ads/google-ads-send-offline-conversions#create-a-connection). - If you selected an existing connection, proceed to next step. 2. In the **Google Ads customer ID** field, enter the ID of the Google Ads account. It can't contain dashes. [Learn how to find this number](https://support.google.com/google-ads/answer/1704344?hl=en). 2. In the **The Google click ID (GCLID) associated with this conversion** field, enter the part of the URL that starts with `?gclid=`. For that purpose, you can enter a Jinjava tag that inserts the value of the [aggregate you created as the part of the prerequisites](#prerequisites): `{% aggregate AGGREGATE_ID %}{{ aggregate_result[0] }}{% endaggregate %}`. Replace the `AGGREGATE_ID` with an actual ID of the aggregate, you can find it in the URL while previewing the aggregate. 5. In the **Conversion action ID** field, enter the ID of the conversion. You can find it in the Google Ads panel. When you go to conversion action details, the URL contains the `ctId` parameter (for example, `ctId=123456789`) whose value is the conversion action ID. [Learn more about conversion action in Google Ads](https://support.google.com/google-ads/answer/6032150?hl=en). 6. In the **Conversion time** field, enter the time of the conversion in the following format: `yyyy-mm-dd hh:mm:ss+|-hh:mm`. For that purpose, you can use [a Jinjava code](/developers/inserts/automation) that inserts date of conversion dynamically, from the trigger, that is, offline conversion. For example, `{{ event.params.time|timestamp_to_time|datetimeformat('%y-%m-%d %H:%M:%S+2:00') }}`. 7. Optionally, in the **Conversion value for the advertiser** field, enter the value. For that purpose, you can use [a Jinjava code](/developers/inserts/automation) that inserts the value dynamically based on the event context from the trigger, that is, offline conversion. For example, `{{ event.params.value }}`. 8. Optionally, in the **Currency associated with the conversion value** field, enter the currency. For that purpose, you can use [a Jinjava code](/developers/inserts/automation) that inserts the value dynamically based on the event context from the trigger, that is, offline conversion `{{ event.parmas.currency }}`. 9. In **Customer match consent import script** type jinjava script to import customer match consent from your database. You can use constant value. 10. In **Ad Personalization consent import source** type jinjava script to import ad personalization consent from your database. You can use sonstant value. 9. Confirm the settings by clicking **Apply**.

The view of the configuration of the Send Offline Conversion node — Configuration of the Send Offline Conversion node

### Add the finishing node 1. Add the **End** node. 2. In the upper right corner, click **Save & Run**. **Result**:

Automation Hub workflow for sending offline conversion data to Google Ads — Workflow configuration

## Check the use case set up on the Synerise Demo workspace --- In Synerise Demo workspace, you can check the configuration of: - [expression](https://app.synerise.com/analytics/expressions/3e366c6a-f4a4-4013-8c92-e3b22274e296) - [aggregate](https://app.synerise.com/analytics/aggregates/8ebdd493-0d08-3ad0-9aa8-d87c616ca286) - [workflow](https://app.synerise.com/automations/automation-diagram/4bac04d4-f883-4800-8b83-215b9a123a43) If you’re our partner or client, you already have automatic access to the **Synerise Demo workspace (1590)**, where you can explore all the configured elements of this use case and copy them to your workspace. If you’re not a partner or client yet, we encourage you to fill out the contact [form](https://demo.synerise.com/request) to schedule a meeting with our representatives. They’ll be happy to show you how our demo works and discuss how you can apply this use case in your business. ## Generated events This use case generates approximately 5 events per profile that completes the flow: `offline.transaction` (~1), [`automation.clientStartPath`](/docs/assets/events/event-reference/automation#automationclientstartpath) (~1), [`automation.clientPathStep`](/docs/assets/events/event-reference/automation#automationclientpathstep) (~1), [`automation.clientEndPath`](/docs/assets/events/event-reference/automation#automationclientendpath) (~1), [`googleAds.sendOfflineConversion`](/docs/assets/events/event-reference/integration#googleadssendofflineconversion) (~1). ## Read more --- - [Aggregates](/docs/crm/aggregates) - [Automation Hub](/docs/automation) - [Expressions](/docs/crm/expressions) - [Google Ads integration](/docs/automation/integration/google-ads) - [Reusing event context from preceding nodes](/developers/inserts/automation) # In-app survey Understanding user preferences from the start is essential for creating a personalized app experience. A well-timed in-app survey after a user's first visit can capture valuable insights into their interests, expectations, and reasons for downloading the app. This direct engagement helps businesses tailor their offerings, improve user satisfaction, and foster long-term engagement. In this specific use case, we plan to introduce a first-time user survey triggered after the app's introductory tour. This use case provides instructions on how to implement a ready-made survey template designed to gather key user insights and enhance the overall experience. ## Prerequisites --- - [Implement Synerise SDK in your mobile app](/developers/mobile-sdk). - Implement a dedicated custom event that is sent to the customer's profile when they first enter the mobile app. This event should be sent only one time, during the first visit to the mobile application. In this use case, we use the `app.firstVisit` event. ## Create an in-app message --- Create an in-app campaign triggered by the `app.firstVisit` event for customers who logged into the mobile application for the first time. We will use a predefined template for this message, so there is no need to create a template from scratch. 1. Go to

**Experience Hub > In-app messages> Create in-app**. 2. Enter the name of the in-app. ### Define the audience --- As the first step, define the target group of customers for the in-app message. In this use case, segmentation based on the [`inApp.show` event](/docs/assets/events/event-reference/inapp#inappshow) acts as an additional security measure that helps to include only people who have never seen this in-app message before.

The accuracy of this segmentation depends on the retention set for the **inApp.show** event.

1. In the **Audience** section, click **Define**. 2. Click **New Audience** and then **Define conditions**. 3. Click **Add condition**, from the dropdown list, select the **inApp.show** event. 4. Next to the **inApp.show**, click **+where**. 5. From the dropdown list, select **id**. 6. As the operator, choose **Equal**. 7. Enter the In-app campaign ID in the text field. You can locate the ID in the campaign's URL link. For instance, in the URL https://app.synerise.com/communications/in-app/d7c03448-a586-4f18-ad9b-cff063c65aef the ID is `d7c03448-a586-4f18-ad9b-cff063c65aef`. 8. Change **matching** condition to **not matching** to find all profiles that don't meet the defined condition. 9. Use the time filter to define analysed time period. 10. Click **Apply**. 11. To save the audience, click **Apply**.

### Define content --- In the next step, you will create the content of the in-app message that will appear in the mobile application with the help of ready-made template. 1. In the **Content** section, click **Define**. 2. Click **Create message** and from the list of template folders, select **Predefined templates**. 3. Select the **Survey form** template. **Result:** You are redirected to the code editor. 4. Edit the template according to your needs. In the Configuration panel, you'll find a comprehensive list with descriptions of the core components that make up your survey.

The configuration of the questions and answers themselves happens in JavaScript panel. There is an object that you have to fill, according to the example given. It is an array of questions, where each question has its answers and settings depending on the type.

Javascript object with questions and answers

**Example:** You want to add/edit question To add an additional question to the **QUESTIONS** array, you'll want to follow the pattern established by the existing questions. Each question is an object that may contain different properties depending on its type (single, multi, scale, text). Here's a step-by-step guide on how to do it: Decide on the question you want to add and the type of question it will be. The type determines what properties the question object should have. For instance: - `single` and `multi` types need question, `answers`, and `type`. - `scale` needs `question`, `type`, and `length`. - `text` needs `question`, `type`, and optionally `limit` for the character limit. Construct the question object according to the type you've chosen. Add the new question object to the `QUESTIONS` array. Here's an example of how you can add a new question that asks about a favorite color (a single type question with predefined answers):

const QUESTIONS = [
              {
                  "type": "single",
                  "question": "What motivated you to download our app?",
                  "answers": [
                      "To browse products",
                      "To make a purchase",
                      "To explore exclusive offers",
                      "To compare prices",
                      { "answer": "Other (please specify):", "options": { "isOpen": true, "limit": 20 } },
                  ],
                  "shuffleAnswers": false,
                  "required": true
              },
              {
                  "type": "multi",
                  "question": "What types of products or services are you most interested in?",
                  "answers": [
                      "Fashion",
                      "Electronics",
                      "Home and Kitchen",
                      "Health and Beauty",
                      "Sports and Outdoors",
                      { "answer": "Other (please specify):", "options": { "isOpen": true, "limit": 20 } }
                  ],
                  "shuffleAnswers": false,
                  "required": true
              },
              {
                  "type": "single",
                  "question": "How do you prefer to shop?",
                  "answers": [
                  "I like to browse and explore new products",
                  "I prefer targeted recommendations based on my preferences",
                  "I usually know what I want and search directly",
                  "I’m mainly looking for deals and offers",
                  ],
                  "shuffleAnswers": false,
                  "required": true
              },
              {
                  "type": "multi",
                  "question": "What factors influence your purchasing decisions the most?",
                  "answers": [
                  "Product quality",
                  "Price",
                  "Brand reputation",
                  "Customer reviews",
                  "Sustainability",
                  { "answer": "Other (please specify):", "options": { "isOpen": true, "limit": 20 } }
                  ],
                  "shuffleAnswers": false,
                  "required": true
              },
              {
                  "type": "scale",
                  "question": "How likely would you recommend our company to your friends and known ones?",
                  "length": 10,
                  "required": true,
              },
          ];

5. After customising your survey, save the template. ### Select events that trigger the in-app message display --- In this part of the process, you will define the event triggering the display of the in-app message. 1. In the **Trigger events** section, click **Define**. 2. Select **Add event...** and from the dropdown list, choose `app.firstVisit` event. 3. Click the **+ where** button and select `source`. 4. As the logical operator, select **Equal**. 5. In the text field enter **MOBILE_APP**. 5. Click **Apply**. ### Schedule the message and configure display settings --- As the final part of the process, you will set the display settings of the in-app message such as schedule, capping, priority of the message among other in-app messages. 1. In the **Schedule** section, click **Define** and set the time when the message will be active. 2. In the **Display Settings** section, click **Define**. 1. Define the **Delay display**, **Priority index**, **Frequency limit** and/or **Capping limit**. 2. In our case, we want to display the message once per user. To do this, switch on **Capping limit**, and in the **Show maximum** section text field type `1`. 4. Click **Apply**. 5. Optionally, you can define the UTM parameters, additional parameters or test your in-app campaign. 6. Click **Activate**. ## Check the use case set up on the Synerise Demo workspace --- You can check the [in-app message](https://app.synerise.com/communications/in-app/6d39ca33-542c-4c18-950c-0620ca5c486e) configuration directly in Synerise Demo workspace. If you’re our partner or client, you already have automatic access to the **Synerise Demo workspace (1590)**, where you can explore all the configured elements of this use case and copy them to your workspace. If you’re not a partner or client yet, we encourage you to fill out the contact [form](https://demo.synerise.com/request) to schedule a meeting with our representatives. They’ll be happy to show you how our demo works and discuss how you can apply this use case in your business. ## Generated events This use case generates approximately 4 events per profile that completes the flow: `app.firstVisit` (~1), [`inApp.show`](/docs/assets/events/event-reference/inapp#inappshow) (~1), [`inApp.click`](/docs/assets/events/event-reference/inapp#inappclick) (~1), [`form.submit`](/docs/assets/events/event-reference/web-and-app#formsubmit) (~1). ## Read more --- - [In-app messages](/docs/campaign/in-app-messages) - [Mobile campaigns](/docs/campaign/Mobile) - [Using in-app template builder](/docs/campaign/in-app-messages/creating-inapp-templates/creating-inapp-template) # Promote Complementary Products in Search Using Contextual Rules AI Search allows you to improve the search experience of your users by customizing search results to individual requirements by setting rules. The possibilities are endless. Define a rule condition and consequence which tailors results based on the context of the search, so customers can find the products they're looking for easier and faster than ever before. This use case describes the process of creating a rule in AI search which promotes mobile chargers when a customer searches for `charger` from a mobile device. ## Prerequisites - An item feed must be provided. - Enable [the search engine](/docs/ai-hub/ai-search/introduction-to-ai-search) for your workspace and create an [index](/docs/ai-hub/ai-search/create-index). - [Implement AI search](https://hub.synerise.com/api-reference/ai-search#operation/profileLogin) in any of your channels (mobile app, website etc.). - Implement the context parameter with value mobile to search request. It should be added when your customer enters the query on the mobile device. ## Create rules --- 1. Go to

**AI Hub > Indexes**. 2. Select an index from the list. 3. Go to the **Rules** section. 4. On the right side of the screen, click **Add rule**. 5. Enter the name of the rule. 6. To adjust the query conditions, in the **Conditions** section, click **Define**. 1. On the **Query** tab, to define the method of checking the query, choose the **is** condition. The **is** condition means the rule works only if a customer searches exactly for the phrase defined in the rule. 2. In the text field, enter: `charger` 3. In the **Context (optional)** field, enter: `mobile`. This means that the rule only works when the search request has the `context = mobile` parameter.

1. Confirm the settings by clicking the **Apply** button. 7. To define how the search engine reacts to the defined conditions, in the **Consequences** section, click **Define**. 1. Click **Add consequence**. 2. From the dropdown list, select the **Filter query results** consequence. 3. Click **Add filter**. 4. Select attribute that corresponds to **product type**. 5. In the field next to the attribute name, enter the value that denotes mobile phone chargers or select it from the dropdown list.

Please note that the attribute name and its value depends on the rules used in the implementation process.

8. Toggle the **Mark as elastic** switch on. 9. Confirm by clicking **Apply**. 10. To save and enable the query rule, click **Publish**.

## Check the use case set up on the Synerise Demo workspace --- You can check the [rule configuration](https://app.synerise.com/ai-v2/search/indices/1c7fac97ddd2c12b7cf1e71d7b4489261657270872/query-rules/14432) directly in Synerise Demo workspace. If you’re our partner or client, you already have automatic access to the **Synerise Demo workspace (1590)**, where you can explore all the configured elements of this use case and copy them to your workspace. If you’re not a partner or client yet, we encourage you to fill out the contact [form](https://demo.synerise.com/request) to schedule a meeting with our representatives. They’ll be happy to show you how our demo works and discuss how you can apply this use case in your business. ## Generated events This use case generates approximately 2 events per profile that completes the flow: [`item.search`](/docs/assets/events/event-reference/search#itemsearch) (~1), [`item.search.click`](/docs/assets/events/event-reference/search#itemsearchclick) (~1). ## Read more --- - [Configuring AI Search](/docs/ai-hub/ai-search/introduction-to-ai-search#configuring-ai-search) - [Creating rules in AI Search](/docs/ai-hub/ai-search/query-rules) # Group customers by purchase days In this use case, you will learn how to create a segmentation that allows you to divide your customers into segments based on the time of week on which they bought a product. You may use that information further for targeted communication. ## Prerequisites --- - Implement transaction events using [SDK](/developers/web/transactions-sdk) or [API](https://hub.synerise.com/api-reference/data-management#operation/CreateATransaction). ## Create a segmentation --- Create a segmentation that organizes customers into two groups: - Weekend - It gathers the customers who bought products on weekends, - Week days - It gathers the customers who bought products on week days. 1. Go to

**Decision Hub > Segmentations > New Segmentation**. 2. Enter the name of the segmentation. 3. Name the first segment, in our case `Weekend` 4. To add the first step to the segment, click the **Performed event...** button. 5. From the dropdown list, select the `product.buy` event. 6. For the event parameter, click the **+ where** button and select `TIMESTAMP`. 7. As the logical operator, select **Custom** date. 8. Click **Start date -> End date**: 1. In the **Relative date range** section, click **Custom**, type 365 and from the the dropdown list, select **Days**. 2. In the **Filter** section, click **Add filter** and then **Every week**. 3. Select **Sat** and **Sun**. 4. Click **Add time**. 4. Click **Apply**.

9. Click **Apply**. 10. In the calendar in the right bottom of the page: 1. In the **Relative date range** section, click **Custom**, type 365 and from the the dropdown list, select **Days**. 2. Click **Apply**.

11. Create the second segment by duplicating the one you have just created. 12. Name this segment `Week days`. 13. Change the date range: 1. In the **Filter** section, click **Change** . 2. Click on **Select all** and clear selection of **Sat** and **Sun**. 4. Click **Add time**. 3. Click **Apply**.

14. Click **Apply**.

15. In the calendar in the right bottom of the page: 1. In the **Relative date range** section, click **Custom**, type 365 and from the the dropdown list, select **Days**. 2. Click **Apply**. 16. Click **Save**. The segments are saved and can be viewed in **Preview** where you can preview how your customer base splits according to the defined conditions. ## What's next --- To use this segments in **Experience Hub**: 1. Click **Define** in the **Audience** section. 2. Click **New Audience**. 3. Click **Define conditions**. 1. Click **Choose filter** and from the dropdown list choose the segmentation you have created in [this step](/use-cases/number-of-transactions-weekend-vs-workdays#create-a-segmentation). 2. Choose operator **Equal**. 3. Type the name of the segment. Depending on whether you want to send the communication to customers who buy on the weekend, enter the name of the segment `Weekend`, and if to those who buy during week days - `Week days`. 4. Click **Apply**. 4. Click **Apply**.

## Check the use case set up on the Synerise Demo workspace --- You can also check the [segmentation configuration](https://app.synerise.com/analytics-v2/segmentations/0d06b767-6168-4e8f-8c08-9bfb2ad6544c) directly in Synerise Demo workspace. If you’re our partner or client, you already have automatic access to the **Synerise Demo workspace (1590)**, where you can explore all the configured elements of this use case and copy them to your workspace. If you’re not a partner or client yet, we encourage you to fill out the contact [form](https://demo.synerise.com/request) to schedule a meeting with our representatives. They’ll be happy to show you how our demo works and discuss how you can apply this use case in your business. ## Generated events This use case does not generate any events. ## Read more --- - [Segmentations](/docs/analytics/segmentations) # Automate Sending NPS Survey Results to Google BigQuery Integrating Synerise with Google BigQuery enables you to easily export data from Synerise to BigQuery tables using the **Upload Data to Table** node. This connection can be used to export various types of data, such as NPS survey data. By integrating with Google BigQuery, Synerise sends data to be directly uploaded into BigQuery tables, facilitating easy exportation and further analysis. The uploaded data can also be used in other Google tools, such as Google Analytics. In this use case, we will create a workflow which sends information with NPS survey data to Google BigQuery using a dedicated node in our Automation. ## Prerequisites --- - Implement a custom event for NPS survey data, which will be available in the customer profile. In this example, the event is called `nps.send`. Implement custom events in your [mobile application](/developers/mobile-sdk/event-tracking#basic-custom-event) or website [Web](/developers/web/event-tracking#declarative-tracking-custom-events). You can learn more about NPS survey in [this use case](/use-cases/dynamic-nps). - Check [the requirements](/docs/automation/integration/google-bigquery/upload-data-to-bigquery#prerequisites) you must meet to integrate Synerise with BigQuery. ## Create a workflow --- Create a workflow which sends information with NPS survey data to Google BigQuery. Every time the `nps.send` event is generated, the data from the event is sent automatically to BigQuery. 1. Go to

**Automation Hub > Workflows > New workflow**. 2. Enter the name of the workflow. ### Define the Profile Event trigger node --- At this stage, we will configure conditions that launch the workflow. As a trigger, we will use the `nps.send` event. 1. As the first node of the workflow, add **Profile Event**. In the configuration of the node: 1. Enter the following title to the node: `nps survey`. 2. From the **Choose event** dropdown menu, choose the `nps.send` event. 2. Confirm by clicking **Apply**

Click here to see example event and its parameters for an example customer

{ "time": "2023-02-15T15:24:49Z", "action": "nps.sent", "label": "", "client": { "id": 5092159999, "email": "e0097757-d1e2-44ac-ba3c-d97979a354c1@anonymous.invalid", "uuid": "e0097757-d1e2-44ac-ba3c-d97979a354c1" }, "params": { "eventCreateTime": "2023-02-15T15:25:08.861Z", "name": "John", "surname": "Doe", "location": "Warsaw", "age": "23", "feedback": "Great customer serviece and product selection." } }

### Configure the Upload Data to Table node --- At this stage, we will configure the BigQuery node. 1. As the next node, add **Google BigQuery > Upload Data to Table**. 2. Click **Select connection**. 3. From the dropdown list, select the connection. - If no connections are available or you want to create a new one, see [Create a connection](/docs/automation/integration/google-bigquery/upload-data-to-bigquery#create-a-connection). - If you selected an existing connection, proceed to defining the integration settings. 4. In the configuration of the node: 1. In the **Project ID** field, enter the unique identifier of your project in Google BigQuery. You can learn how to find the project ID [here](https://support.google.com/googleapi/answer/7014113). 2. In the **Dataset ID** field, enter the unique identifier of the dataset in the BigQuery project. 3. In the **Table ID** field, enter the unique identifier of the table in the dataset. 4. In the **Rows** field, enter JSON that extracts name, surname, location and the contents of feedback from the event selected in the **Profile Event** node. The example body contains the [Automation inserts](/developers/inserts/automation) that retrieve data from the event included in the **Profile Event** node.

In this JSON you define only those parameters you want to send to BigQuery.

[
    {
      "insertId": "{{ currentStep.actionId }}",
      "json": {
        "name": "{{ automationPathSteps['nps survey'].event.params.name }}",
        "surname": "{{ automationPathSteps['nps survey'].event.params.surname }}",
        "location": "{{ automationPathSteps['nps survey'].event.params.location }}",
        "feedback": "{{ automationPathSteps['nps survey'].event.params.feedback }}"
      }
    }
]

### Add the finishing node --- 1. Add the **End** node. 2. In the upper right corner, click **Save & Run**.

Automation Hub workflow for sending NPS events to BigQuery — The workflow configuration

## Check the use case set up on the Synerise Demo workspace --- You can check the [workflow configuration](https://app.synerise.com/automations/automation-diagram/c1765019-5e46-46c9-bf5d-2def3b13d2c2) directly in Synerise Demo workspace. If you’re our partner or client, you already have automatic access to the **Synerise Demo workspace (1590)**, where you can explore all the configured elements of this use case and copy them to your workspace. If you’re not a partner or client yet, we encourage you to fill out the contact [form](https://demo.synerise.com/request) to schedule a meeting with our representatives. They’ll be happy to show you how our demo works and discuss how you can apply this use case in your business. ## Generated events This use case generates approximately 5 events per profile that completes the flow: `nps.send` (~1), [`automation.clientStartPath`](/docs/assets/events/event-reference/automation#automationclientstartpath) (~1), [`automation.clientPathStep`](/docs/assets/events/event-reference/automation#automationclientpathstep) (~1), [`automation.clientEndPath`](/docs/assets/events/event-reference/automation#automationclientendpath) (~1), [`bigQuery.uploadData`](/docs/assets/events/event-reference/integration#bigqueryuploaddata) (~1). ## Read more --- - [Automation Hub](/docs/automation) - [Uploading data to BigQuery](/docs/automation/integration/google-bigquery/upload-data-to-bigquery) # Search engine for a brand with multiple languages and currencies AI search is not difficult tool to use, especially when we use one language. A lot of our customers are operating in many markets and want to use search in different languages. It is hard to avoid a situation where a user enters a different language when searching certain categories in his language on the website. We can accept it and the fact that he will find a blank page with no results, but on the other hand we can set up the search process and, based on that, show him the products he is looking for no matter which language he uses. **Challenge** Our client had one e-commerce platform that uses different variants depending on the region chosen by customers, currencies available on the chosen region and website language. Additionally, each market had its own product stock. So, in fact we had several e-commerce operations under one domain. Our customer wanted to have all the data in one place and execute all campaigns from the one place as well. He was also interested in creating AI search which makes it possible to search for products in different languages. ![Screenshot presenting ai search](/api/docs/image/47a8d475c1503bce19aa1212867cd2995b1c3dd2/use-cases/all-cases/_gfx/aisearch-products1.png) ## Prerequisites --- - Synerise [tracking code](/docs/settings/tool/tracking_codes), to collect all necessary events from the website. - [Product feed](/developers/product-feed) implemented. - [OG tags](/developers/web/og-tags). - Collecting [transactional events](/docs/automation/actions/synerise-integrations/import-events). ## Process --- 1. [Prepare product feeds](/use-cases/search-multiple-languages#prepare-product-feeds) for each market. 2. [Prepare a search ranking](/use-cases/search-multiple-languages#prepare-a-search-ranking). 3. [Set up AI search](/use-cases/search-multiple-languages#set-up-ai-search) - query rules and synonyms. ## Prepare product feeds --- 1. **Create separated product feeds** for each market with additional information about those languages on the website which we want to use in our search - every attribute like description, title, type, category should be added in two languages. Everything in the Google merchant format. Thanks to that, even if the customer is on the English version of the website, he can search using Arabic words as well.

2. Every search for each region has to be built on the basis of separate product feeds. So, we have to prepare **different indexes for such an AI search**. Thanks to that we can choose, based on which product feed we want to build our models on. As you can see below, we can choose one of the imported product catalogs and later use it to prepare the appropriate campaign. ![Screenshot presenting index](/api/docs/image/47a8d475c1503bce19aa1212867cd2995b1c3dd2/use-cases/all-cases/_gfx/indexes.png) ## Prepare a search ranking --- In the case of a search engine, the most important step of setting it up is to **prepare a search ranking**. This means you have to indicate which attributes around the product have to be searchable and assign their importance. ![Screenshot presenting ranking](/api/docs/image/47a8d475c1503bce19aa1212867cd2995b1c3dd2/use-cases/all-cases/_gfx/aisearchranking.png) As you can see here, we have a lot of attributes from the product feed, from this customer, but the most important are searchable attributes which will be search at the beginning. In our case it will be: - Category - itemID - attributes.product_type_ar – second language - brand - title In medium and low importance, we have also the next attributes from the product; description, gender, attributes.title_ar, attributes.description_ar, and more of them in the low importance (e.g. size, pattern etc.).

## Set up AI Search --- ### Query rules Synerise lets you optimize search using our query rules. It also allows us to prepare seven better search results. Based on this, in just a few steps you can decide that if somebody enters a query, you can replace it with a different phrase and show him specific content. We can prepare such query rules in AI Hub – Indexes - New index, clicking button “create new” in query rules. We have to complete 3 sections: - Conditions - Consequences - Schedule ![Screenshot presenting query rules](/api/docs/image/47a8d475c1503bce19aa1212867cd2995b1c3dd2/use-cases/all-cases/_gfx/queryrules.png) Let’s say that we want to prepare a query for when someone enters “dress” - we would like to show him products from the dress category in the Arabic language “فستان”. So, we choose the title from the first steps subpage and add it to the consequences section. In this way we will define that if somebody enters “dress” we would like to replace this query with a new query, which is dress in Arabic. ### Synonyms You can also use synonyms to make the search more effective. To do this, add new synonym in the synonym section. Choose if it should work in one way or two ways. ![Screenshot presenting query rules](/api/docs/image/47a8d475c1503bce19aa1212867cd2995b1c3dd2/use-cases/all-cases/_gfx/synonyms.png) It can be helpful if a lot of similar words for your category exist (sweatshirt and hoodie) or a lot of different products are in the same category e.g. beach accessories, where you can find towels, bags, umbrellas etc.

You can always check the **zero page results section** in your search configurator to see what kind of words are often entered by your customers. It may be that some categories or product names are entered by mistake and you can automatically replace them with the proper word.

## Generated events This use case generates approximately 2 events per profile that completes the flow: [`item.search`](/docs/assets/events/event-reference/search#itemsearch) (~1), [`item.search.click`](/docs/assets/events/event-reference/search#itemsearchclick) (~1). ## Read more --- - [AI search](/docs/ai-hub/ai-search/introduction-to-ai-search) - [Catalogs](/docs/assets/catalogs/creating-catalogs) - [Product Search API documentation](https://hub.synerise.com/api-reference/ai-search) # Send Automated Slack Messages Based on Metric Results You can integrate Synerise with Slack using a dedicated node to build a variety of business scenarios. One of them is building a workflow that sends messages to a Slack channel based on metrics, expressions, reports or any other analyses created in Synerise. This particular use case reuses a metric (which is a part of an analytical dashboard) that counts the number of customers who signed up for the video call the day before. The message to the channel contains information with the value of the metric.

Screenshot presenting personalized search on a website with no results — Slack integration

## Prerequisites --- - Create [an incoming webhook in Slack](https://api.slack.com/messaging/webhooks). - Implement [an event](/docs/assets/events/event-definitions) that you want to use in the metric whose result will be sent in a message to a Slack channel.

In this use case, we track data from the form that enables to sign up for the video call using [SDK form tracking method](/developers/web/tracking-form-data/tracking-form-data-sdk). This method generates a `form.submit` event which we will later used in the metric. Learn more about other ways to implement events using [web SDK](/developers/web/event-tracking#declarative-tracking-custom-events), [mobile SDK](/developers/mobile-sdk/event-tracking) or [API](https://hub.synerise.com/api-reference/data-management#operation/CustomEvent).

## Process --- 1. [Create a metric in Synerise](/use-cases/slack-integration#create-a-metric-in-synerise). 3. [Create a workflow in Synerise](/use-cases/slack-integration#create-a-workflow-in-synerise). ## Create a metric in Synerise --- In this step, we will create a metric whose result will be later sent in the Slack message. The configuration is exemplary, it may vary depending on your implementation of events. 1. In Synerise, go to

**Decision Hub > Metrics > New metric**. 2. Leave the metric kind at default (**Simple**). 3. Leave the metric type at default (**Event**) 2. From the **Choose event** dropdown list, select the **form.submit** event. 3. As the event parameter, select the **formType**. 4. As a logical operator, select **Equal (String)**. 5. In the text field, enter `videocall`.

In this use case, the metric is included in the [analytical dashboard](/docs/analytics/analytics-dashboard) which is later linked in the alert message in Slack.

## Create a workflow in Synerise --- In this part of the process, you will create a workflow that sends a message to a Slack channel with the number of customers who signed up for a video call. The message will contain the metric result and the link to the analytical dashboard that contains the metric. 1. In Synerise, go to **Automation Hub > Workflows > New workflow**. 2. Start with the **Scheduled Run** node. In the configuration of the node: 1. Set the **Run trigger** option to **all time**. 2. Select the **Everyday** tab. 3. Select the time zone. 3. Select the time when the workflow will be launched. 4. Confirm by clicking **Apply**.

Configuration of the workflow that sends alert messages with the metric results to the Slack channel

### Configure Slack Integration node In this step, you will configure the settings of the outgoing integration that sends the message to a Slack channel. #### Create a connection 1. On the **Scheduled Run** node, click **THEN**. 2. From the dropdown list, select **Slack > Send Channel Message**. 3. In the configuration of the node: - If you already create a connection, select the connection from the list. - If you haven't created any connection yet: 1. At the top of the dropdown list, click **Add connection**. 2. In the **Incoming Webhook URL** field, enter the incoming webhook URL you created as a part of [prerequisites](/use-cases/slack-integration#prerequisites). 3. Click **Next**. 4. In the **Connection name** field, enter the name for the connection you created. 5. Click **Apply**. **Result**: A connection is created and selected. #### Define the integration parameters 1. In the **Type of message** field, choose **interactive message (JSON)**. 2. Below add JSON body of message which should be sent to Slack channel.

{
       "blocks": [
           {
               "type": "section",
               "text": {
                   "type": "mrkdwn",
                   "text": "Number of people signed in for the videocall: `{% metricsvar metric_id:XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX %}{{ metric_result }}{% endmetricsvar %}`\nNumber of people having the videocall today: `{% metricsvar metric_id:XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX %}{{ metric_result }}{% endmetricsvar %}`"
               },
               "accessory": {
                   "type": "button",
                   "text": {
                       "type": "plain_text",
                       "text": "check dashboard",
                       "emoji": true
                   },
                   "url": "https://app.synerise.com/spa/modules/dashboards/analytics/dashboards/XXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
               }
           }
       ]
       }

In the JSON body: - Insert the ID of the metric you created in the [previous step](/use-cases/slack-integration#create-a-metric-in-synerise). - Optionally, if you want to refer users to the analytical dashboard, for the `url` parameter, insert the link to the dashboard. If you choose not to, remove the `accessory` object from the JSON body. 3. Confirm by clicking **Apply**. 5. Add the **End** node. 6. Launch the workflow by clicking **Save&Run**.

Configuration of the workflow that sends alert messages based on the metric results to the Slack channel

**Result**: The message is sent to the Slack channel.

## Check the use case set up on the Synerise Demo workspace --- You can check the configuration of use case in Synerise Demo workspace: - [Metric](https://app.synerise.com/analytics/metrics/b4a6958d-7f86-47d6-a8c8-c89fe1c76aba) - [Workflow configuration](https://app.synerise.com/automations/workflows/automation-diagram/3509dfae-73b4-4333-9e16-c3d957568748) If you’re our partner or client, you already have automatic access to the **Synerise Demo workspace (1590)**, where you can explore all the configured elements of this use case and copy them to your workspace. If you’re not a partner or client yet, we encourage you to fill out the contact [form](https://demo.synerise.com/request) to schedule a meeting with our representatives. They’ll be happy to show you how our demo works and discuss how you can apply this use case in your business. ## Generated events This use case generates approximately 4 events per workflow execution: [`automation.clientStartPath`](/docs/assets/events/event-reference/automation#automationclientstartpath) (~1), [`automation.clientPathStep`](/docs/assets/events/event-reference/automation#automationclientpathstep) (~1), [`automation.clientEndPath`](/docs/assets/events/event-reference/automation#automationclientendpath) (~1), [`slack.sendChannelMessage`](/docs/assets/events/event-reference/integration#slacksendchannelmessage) (~1). ## Read more --- - [Automation Hub](/docs/automation) - [Integration](/docs/automation/integration) - [Inserts](/developers/inserts) # Import transactional data from Google Cloud Storage to Synerise Synerise allows you to collect data from any customer touchpoint. Using Synerise's seamless integration with Google Cloud Storage (GCS), you can transfer any data stored in the GCS directly to Synerise and use it in the platform. In this use case, we will import a file with transactional data and purchase history from Google Cloud Storage. ## Prerequisites --- - You must have a Google Cloud account. - Create a project in Google Cloud. ## Prepare a workflow --- Create a workflow which performs a single import of the file with transactional data and purchase history from Google Cloud Storage to Synerise. 1. Go to

**Automation Hub > Workflows > New workflow**. 2. Enter the name of the workflow. ### Define the Scheduled Run trigger node --- At this stage, we will configure conditions that launch the workflow. As a trigger, we will use the **Scheduled Run** node. 3. As the trigger node, add **Scheduled Run**. 4. In the configuration of the node: 1. Change the **Run trigger** option to **one time**. 2. Select **Immediately**. 4. Confirm by clicking **Apply**.

Automation Hub Scheduled Run node configuration for triggering Google Cloud Storage file retrieval — The configuration of the Scheduled Run node

### Configure the Get File node --- In this step, to allow the data exchange, establish a connection between Synerise and Google Cloud Storage. 1. Add **Google Cloud Storage > Get File** node. 2. Click **Select connection**. 3. From the dropdown list, select the connection. - If no connections are available or you want to create a new one, see [Create a connection](/docs/automation/integration/google-cloud-storage/get-file-from-gcs). - If you selected an existing connection, proceed with the integration settings. 1. In the **Project ID** field, enter the unique identifier of your project in Google Cloud. You can learn how to find the project ID [here](https://support.google.com/googleapi/answer/7014113). 2. In the **Bucket** field, enter the name of an existing bucket (container) from which you will download a file with data. 3. In the **Path to directory** field, enter the path from which the file will be downloaded. 4. In the **File name** field, enter the name of the file you want to download from the storage. If the file already exists, the contents of the file will be overwritten. 5. From the **File format** dropdown list, select the format of the file which will be downloaded. 6. Confirm by clicking **Apply**.

The configuration of the Get file from Google Cloud Storage node — The configuration of the Get File node

### Add Import Transactions node --- In this step, add the **Import Transactions** node to import the file with transactions directly to Synerise. 1. Choose **Synerise** node. 2. From the list that opens, select **Synerise > Import Transactions**. ### Add the finishing node 12. Add the **End** node. 13. In the upper right corner, click **Save & Run**.

Automation Hub workflow for retrieving a file from Google Cloud Storage — The workflow configuration

## Check the use case set up on the Synerise Demo workspace --- You can check the configuration of the [workflow](https://app.synerise.com/automations/automation-diagram/79b22158-ca02-4d10-8e03-e26bc7839b3a)in this use case on our Synerise Demo workspace. If you’re our partner or client, you already have automatic access to the **Synerise Demo workspace (1590)**, where you can explore all the configured elements of this use case and copy them to your workspace. If you’re not a partner or client yet, we encourage you to fill out the contact [form](https://demo.synerise.com/request) to schedule a meeting with our representatives. They’ll be happy to show you how our demo works and discuss how you can apply this use case in your business. ## Generated events This use case generates approximately 8 events per workflow execution: [`automation.clientStartPath`](/docs/assets/events/event-reference/automation#automationclientstartpath) (~1), [`automation.clientPathStep`](/docs/assets/events/event-reference/automation#automationclientpathstep) (~2), [`automation.clientEndPath`](/docs/assets/events/event-reference/automation#automationclientendpath) (~1), `googleCloudStorage.getFile` (~1), [`transaction.charge`](/docs/assets/events/event-reference/items#transactioncharge) (~1), [`product.buy`](/docs/assets/events/event-reference/items#productbuy) (~2). ## Read more --- - [Get File](/docs/automation/integration/google-cloud-storage/get-file-from-gcs) - [Workflows](/docs/automation) # Dynamic remarketing with AI recommendations --- Not all potential customers that come to your website purchase right away. You need to continue to influence them not only from your website, but also across Google’s display network. Segmenting visitors and remarketing to those that have ‘Abandoned the Shopping Cart’ or ‘Visited A Product Page” may not be enough. If you want to beat your competitors you should take your **remarketing campaign** a step further, **using our AI recommendation engine** and showing customers the most relevant products. ## Example of use - Home appliances industry **Challenge** A client from the home appliance industry decided to use AI recommendation campaigns outside their website with Google remarketing. They wanted to show customers personalized recommendations based on their behavior. They already had such a campaign on their homepage and they wanted to display those products to customers while they browsed the Internet. To do this, they added Google Data Layer events to the script with a recommendations campaign to get the ID of products recommended to each customer. In this way they were able to **display their campaigns with personalized products on external websites** as remarketing to customers who previously visited their page. ![Screenshot presenting dynamic remarketing](/api/docs/image/47a8d475c1503bce19aa1212867cd2995b1c3dd2/use-cases/all-cases/_gfx/dynamic_remarketing.png) ## Requirements --- 1. Basic elements of AI integration: - Tracker - Product feed, filled with appropriate custom attributes - Transactional events - OG tags 2. Google Data Layer implemented on the website ## How to do it --- You need to send a dataLayer.push event to every visitor of your website. Add the script below in the java script section in the dynamic content with the recommendation campaign:

<script> 
dataLayer.push({ 
'pid': 'product_id', 
'event': 'event_name' 
'sce': 'campaign_name'}); 
</script>

Where: - `product_id`- recommended product ID - `event_name`- name of the event, by which you will recognize AI recommendation's campaign - `campaign_name`- optionally, name of the recommendation campaign. Very useful if you send to the Data Layer products from more than one AI campaign a time

Remember that you need to send a separate event for every product.

## Generated events This use case generates approximately 5 events per profile that completes the flow: [`dynamicContent.show`](/docs/assets/events/event-reference/dynamic-content#dynamiccontentshow) (~1), [`dynamicContent.click`](/docs/assets/events/event-reference/dynamic-content#dynamiccontentclick) (~1), [`recommendation.generated`](/docs/assets/events/event-reference/recommendations#recommendationgenerated) (~1), [`recommendation.view`](/docs/assets/events/event-reference/recommendations#recommendationview) (~1), [`recommendation.click`](/docs/assets/events/event-reference/recommendations#recommendationclick) (~1). ## Read more --- - Read more about [AI](/docs/ai-hub/recommendations-v2/recommendation-types#personalized) - Read more about [creating metrics](/docs/analytics/metrics) - Read more about [dynamic content](/docs/campaign/dynamiccontent) - Read more about [recommendation types](/docs/ai-hub/recommendations-v2) # Email with the products most frequently visited by a customer It is worth remembering how important it is to analyze what users view on the website, what subpages they visit and how much time they spend there. Behavioral data is the basis for creating a specific marketing strategy and appropriate personalization. Remember that even if the users do not add anything to the basket, they can be reminded of the products they most often visited by sending them a personalized email. ## Example of use - Electronic industry A client from the electronics industry decided to make use of information about the products customers viewed. However, instead of sending them the products they viewed recently, they were sent most viewed products in general.

Screenshot presenting personalized email with top products — Email with top products

If the customers were on the site but did not add anything to the cart, after the session ended, they would receive an email with the products they visited more than once - ordered from the most to the least frequently visited. ## Prerequisites --- To implement this use case, you have to: - Implement [tracking code](/docs/settings/tool/tracking_codes) on your website. - Implement [OG Tags](/developers/web/og-tags). - Import [product feed](/developers/product-feed). - Create [product catalog](/docs/assets/catalogs). - Integrate [transaction events](/developers/web/transactions-sdk). - Have [add to cart event](/docs/assets/events/event-definitions). - Create and set up your [email account](/docs/campaign/e-mail/configuring-email-account). - Import your [subscriber's database](/docs/automation/actions/synerise-integrations/import-customers) to Synerise. ## Process --- To create an email with products most frequently visited, perform the steps in the following order: 1. [Prepare the aggregate](/use-cases/email-with-products-most-frequently-visited#prepare-the-aggregate). 2. [Prepare a product catalog](/use-cases/email-with-products-most-frequently-visited#prepare-a-product-catalog) 2. [Prepare the workflow](/use-cases/email-with-products-most-frequently-visited#prepare-the-workflow). ## Prepare the aggregate --- Build an aggregate that collects the SKUs of the most frequently visited products. 1. Go to

**Behavioral Data Hub > Live Aggregates > Create aggregate**. 2. As the aggregate type, select **TOP MULTI**. 3. In the Size field, enter the number of recent events (for example, 10). 4. Select the event `page.visit` and the `retailer_part_no`. 5. Click button + where and add the condition that the `product:retailer_part_no` parameter is true. This will give us confidence that we only take into account the visited product pages. 5. Save your aggregate.

`Screenshot presenting aggregate with recently viewed product` — The aggregate with recently viewed product

## Prepare a product catalog --- The event page.visit contains the most important information about the product - its ID in the product:retailer_part_no parameter. To add additional information about the product in the email template, such as a photo, price, link, you need a product catalog. You can import your feed following these [instructions](/docs/assets/imports) or you can use Snrs-product-ogTag catalog which is automatically built from the product page og tags. ## Prepare the workflow --- 1. Go to

**Automation Hub > Workflows > New workflow**. 2. Add an **Profile Event** as a trigger node. 3. Select the **session.end** event.

`Screenshot presenting using trigger` — Configuration of the Profile Event node

4. Click **Delay** to define the duration of delay - after the session ends, the system waits for the time defined in the Delay node before the email is sent.

`Screenshot presenting delay` — Configuration of the Delay node

Remember that event session.end appears 30 minutes after the last user activity on the website.

5. Add the **Generate Event** node. It generates an event on the customer's profile. In this case, the event will contain ID of the most frequently viewed products by a customer. 1. In the **Event name**, enter the name, for example `topvisited.products`. 3. In the **Body**, enter the Jinjava code available below. Replace AGGREGATE_HASH with the hash of the aggregate you in the previous step. As a result you will analyze the products that the user has viewed, sort them in order of the most frequently viewed to the least viewed (products that have been viewed at least two times) and return them to the user’s card in this event.

Generate Event

An event created in this way will return all the products that the user saw at least twice within the time specified in your aggregate. The event with parameter will be returned in the form of the sku listed after the decimal point, e.g.: top: sku1, sku2, sku3.

CHECK JINJA CODE

{ "top": "{% set skus = [] %} {% set counter = [] %} {% set skusTmp = [] %} {% set skuDict = [] %} {% set sortDict = [] %} {% aggregate AGGREGATE_HASH %} {% for sku in aggregate_result|unique %}{% set k = [] %}{% for tmp in aggregate_result %}{% if sku == tmp %}{% do k.append('+') %}{% endif %}{% endfor %}{% do skuDict.append({'sku':sku,'counter':k|length }) %}{% endfor %}{% endaggregate %}{% for dictItem in skuDict %}{% do counter.append(dictItem.counter)%}{% endfor %}{% set sortCounter = counter|sort() %}{% for count in sortCounter %}{% for dictItem in skuDict %}{% if dictItem.counter == count && dictItem.sku in skusTmp == false %}{% do skusTmp.append(dictItem.sku) %}{% do sortDict.append(dictItem) %}{% endif %}{% endfor %}{% endfor %}{% set top = [] %}{% set len = sortDict|length + 1 %} {% for i in range(len) %}{% set ind = sortDict|length - i %}{% set item = sortDict[ind] %}{% if sortDict[ind].counter > 1 %}{% do top.append(sortDict[ind].sku) %}{% endif %}{% endfor %}{{ top|join(',')|trim }}" }

`Screenshot presenting effect after implementing jinjava` — Effect after implementing jinjava

6. Add **Profile Event Filter**. This node allows you to wait for the event sent in the previous node. When the event appears on the customer's profile, it will be possible to refer to its parameters in the next node - here in **send.email**, you will refer to the "Top" parameter via `{{event.params.top}}`

Configuration of the Profile Event Filter node

7. Add the **Send Email** node. In the message template, we can use {{event.params.top}} which will return the "top" parameter of the last event we sent. For example, sku1, sku2, sku3 which can then be converted into an array using the | split (',') function and use in the template structure.

{% set topProducts = event.params.top %} 
      {% set skus = topProducts|split(',') %}

Additionally - to add the most visited products , you will have to use Jinjava and add your own CSS. If you want to display all objects that are under the key products, follow the instruction:

<!-- Opening the tag that retrieves the value from the aggregate prepared in point 1 -->
   {% aggregate XXXXXXXXXXX %}
   <!-- In the section {% for r in aggregate_result %} ... {% endfor %} there is access to product:retailer_part_no of the 10 most visited products -->
   {% for r in aggregate_result %}
   next item:
   {{r}}
   <!-- r is a single product:retailer_part_no and can be used as the key: {% catalog.Snrs-produktu-ogTag(r).og:XXX %} downloads additional data from a catalog built on the basis of og tags - which information about the product you want to add in the template depends on you. If you want to add the product name, photo, link, price in the e-mail - you can take it from the catalog -->
   {% catalog.Snrs-produktu-ogTag(r).og:image %}
   {% catalog.Snrs-produktu-ogTag(r).og:title %}
   {% catalog.Snrs-produktu-ogTag(r).product:price:amount %}
   {% catalog.Snrs-produktu-ogTag(r).og:url %}
   {% endfor %}
   <!-- Closing of the tag that gets the value from the aggregate prepared in point 1 -->
   {% endaggregate %}

To find the aggregate ID to replace XXX in the code, simply navigate to the aggregate in the Synerise application. The ID is the part of the URL that comes after /aggregates/, for example: **bfba46b4-e0d6-3ea9-8ae6-c7a2495c54c7** in the URL `https://app.synerise.com/analytics-v2/aggregates/bfba46b4-e0d6-3ea9-8ae6-c7a2495c54c7`. Copy this ID and use it in your code where needed.

8. Add final settings: - Add the End nodes where the workflow should finish for users. - Specify capping (here 1 for 1 day). - Optionally add titles to each node so the workflow will be more understandable for your colleagues. - Name the automation and Save it or Save & Run. - Save your workflow. **Results:**

`Screenshot presenting automation` — Workflow

**It will result in an array:** skus = [sku1, sku2, sku3] which we can then use to build a template - we can, for example, download items from the product catalog and simply display them in our email or download similiar recommendations for the most viewed item (skus [0])

Based on this workflow, you can also extract the user's favorite brand (by creating an aggregate that collects the brand parameter transferred in page visits, adding products to the cart or transactions).

## Check the use case set up on the Synerise Demo workspace --- You can check the configuration of each step directly in the Synerise Demo workspace: - [Aggregate](https://app.synerise.com/analytics/aggregates/bfba46b4-e0d6-3ea9-8ae6-c7a2495c54c7) - [Workflow](https://app.synerise.com/automations/workflows/automation-diagram/e2685ff9-390e-47c7-805f-377f35f49bc4) If you’re our partner or client, you already have automatic access to the **Synerise Demo workspace (1590)**, where you can explore all the configured elements of this use case and copy them to your workspace. If you’re not a partner or client yet, we encourage you to fill out the contact [form](https://demo.synerise.com/request) to schedule a meeting with our representatives. They’ll be happy to show you how our demo works and discuss how you can apply this use case in your business. ## Generated events This use case generates approximately 11 events per profile that completes the flow: [`session.end`](/docs/assets/events/event-reference/web-and-app#sessionend) (~1), [`automation.clientStartPath`](/docs/assets/events/event-reference/automation#automationclientstartpath) (~1), [`automation.clientPathStep`](/docs/assets/events/event-reference/automation#automationclientpathstep) (~4), [`automation.clientEndPath`](/docs/assets/events/event-reference/automation#automationclientendpath) (~1), `topvisited.products` (~1), [`message.send`](/docs/assets/events/event-reference/email#messagesend) (~1), [`newsletter.open`](/docs/assets/events/event-reference/email#newsletteropen) (~1), [`newsletter.click`](/docs/assets/events/event-reference/email#newsletterclick) (~1). ## Read more --- - [Aggregates](/docs/crm/aggregates/creating-profile-aggregates) - [Email template](/docs/campaign/e-mail/creating-email-templates) - [Jinjava inserts](/developers/inserts/insert-usage) - [Product feed to catalogs](/use-cases/import-product-feed-to-catalog) - [Workflow](/docs/automation/creating-automation) # Recommendations of similar products with item context Similar item recommendations are a valuable tool for online retailers, offering customers product suggestions closely aligned with their current interests or past purchases. These recommendations serve a dual purpose: helping customers uncover new items they may have otherwise missed, while also boosting seller revenue by highlighting products that align with customer preferences. To take these recommendations to the next level, you can add extra context by tailoring them to individual customer interests and needs. One example of this is considering the products a customer has added to their favorites. This use case explores the scenario of creating a dynamic content (DC) campaign featuring similar recommendations enriched with the context of customers' favorite items. This approach enables you to provide a more personalized browsing experience for your customers, while also introducing them to a wider array of products similar to their favorites.

Recommendations of similar products with item context

## Prerequisites --- - [Configure an item catalog for recommendations](/docs/settings/configuration/ai-engine-configuration/engine-configuration-for-recommendations). Enable Similar recommendations. - [Configure AI engine](/docs/settings/configuration/ai-engine-configuration/engine-configuration-for-recommendations). - Implement a custom event for adding a product to favorites, which will be available in the customer profile. In this example, the event is called `product.addToFavorite`. Implement custom events in your [mobile application](/developers/mobile-sdk/event-tracking#product-added-to-favorites) or [website](/developers/web/event-tracking#declarative-tracking-custom-events). ## Process --- In this use case, you will go through the following steps: 1. [Create an aggregate](/use-cases/dynamic-content-item-context-recommendation#create-an-aggregate) that returns products added to favorites. 1. [Prepare AI recommendations](/use-cases/dynamic-content-item-context-recommendation#prepare-ai-recommendations). 2. [Create dynamic content](/use-cases/dynamic-content-item-context-recommendation#create-dynamic-content-campaign) with similar item recommendations using the predefined dynamic content web layer template. ## Create an aggregate --- In this part of the process, create an aggregate that will return the products customers added to favorites. 1. Go to

**Behavioral Data Hub > Live Aggregates > Create aggregate**. 2. As the aggregate type, select **Profile**. 2. Enter the name of the aggregate. 3. AClick **Analyze profiles by** and select **Last**. 4. Select the **product.addToFavorite** event. 5. Select the **sku** parameter. 6. Define the period from which the aggregate will return products from the event. 7. Save the aggregate.

Decision Hub Last aggregate returning the SKU of the last product added to favorites — Configuration of the aggregate

## Prepare AI recommendations --- In this part of the process, you will configure a similar items recommendation with context of items that customers added to their favorites. This recommendation will be later used in the dynamic content. 1. Go to

**AI Hub > (AI Recommendations) Models > Add recommendation**. 2. Enter the name of the recommendation (it is only visible on the list of recommendation). 3. In the **Type & Items feed** section, click **Define**. 4. From the **Items feed** dropdown list, select an item feed. 5. In the **Type** section, choose the **Similar items** recommendation type. 6. Confirm the settings by clicking **Apply**. 7. In the **Items** section, click **Define**. 1. Click **Add slot**. 2. Define the minimum and maximum number of items that will be recommended to the customer in each slot. 3. Optionally, define [Static filters](/docs/ai-hub/recommendations-v2/creating-recommendation-campaign#static-filters) and [Elastic filters](/docs/ai-hub/recommendations-v2/creating-recommendation-campaign#elastic-filters). 4. Confirm by clicking **Apply**. 8. Optionally, you can define the **Boosting** factors. 9. In the **Additional settings** section click **Define**. 1.Enable the **Item context from analytics (aggregate, expression)** switch. 2. From the dropdown list select the created you created [in this part of the process](/use-cases/dynamic-content-item-context-recommendation#create-an-aggregate). 3. Click **Apply**. 9. In the right upper corner, click **Save**. ## Create dynamic content campaign --- Create a dynamic content campaign with recommendations of similar products to those added to favorites using the predefined web layer dynamic content template. This dynamic content will be displayed as a pop-up on your site for the customers who have added products to their favorites. 1. Go to

**Experience Hub > Dynamic content > Create new**. 2. Enter the name of the dynamic content. 3. Choose the **Web layer** type. 4. In the **Audience** section, click **Define**. 1. In the **New Audience** section, click **Define conditions**. 2. From **Choose filter** dropdown menu, choose **product.addToFavorite** event. 3. Define the period from which the segmentation will return customers. 4. Confirm the settings by clicking **Apply**. 5. Confirm the settings by clicking **Apply**. ### Define content 5. In the **Content** section, click **Define**. 6. In the **Content** tab, click **Create Message**. 7. From the list of template folders, select a folder with the predefined **Web layer templates**. **Result**: You are redirected to the list of predefined templates.

8. Select the **Recommendations** template. **Result**: You are redirected to the template builder.

You can edit the template in two ways, by editing the code of the template ([add inserts](/docs/campaign/dynamiccontent/creating-dynamic-content-templates/dynamic-content-template-builder#adding-a-snippet-to-the-template-code), [add variables](/docs/campaign/dynamiccontent/creating-dynamic-content-templates/dynamic-content-template-builder#adding-a-variable)) and/or by [filling out the form in the Config tab](/use-cases/dynamic-content-item-context-recommendation#edit-the-form-in-the-config-tab). In this use case, we will use the capabilities of the predefined Config tab.

#### Edit the form in the Config tab The form in the **Config** tab is already filled in with default values. You can keep them or change them to fit your business needs. 1. From the **Recommendation campaign** dropdown list, select the ID of recommendation campaign you created [in the previous step](/use-cases/dynamic-content-item-context-recommendation#prepare-ai-recommendations). You can find it by typing its name or ID in the search box. 2. In the **Header text** field, define the header text to appear in the popup message. 3. In the **Currency** field, specify the currency in which you want to display the prices of the recommended products. 4. In the **Bottom text** field, define the copy you want to appear in this section. 5. In the **Font** field, define the font of all text displayed in the dynamic content. 6. Define the colors in the **Bottom bar background** and **Bottom bar text color** fields. 7. Choose the most suitable carousel scrolling method for you by enabling one or all toggles at the same time: - **Carousel autoplay**: activation of this toggle allows automatic scrolling of items in the carousel; - **Carousel loop**: activation of this toggle allows users to navigate to the first article in the carousel by clicking the arrow after the last article displayed in the carousel; - Enabling these two options at the same time will combine these functionalities. In this case, the recommendation carousel will scroll automatically and return to the first item automatically after displaying the last one. - If you don't activate any of the toggles, users will have to scroll through the carousel on their own, and when they get to the last item, it won't automatically redirect them to the beginning of the carousel. 8. In the following fields, define the item amount that you would like to display in small, medium, large and extra large screens. 7. After you make changes to the template, you can check the preview. 1. Click the **Preview Contexts** button on the upper left side. 2. Enter the ID of a customer and define the product context. 3. Click **Apply**.

If you are using custom attributes in your product feed, you need to replace the names of the standard attributes used in the template code with the names of the attributes used in your feed. In our case, we changed the names of following attributes (according to the custom attribute names used in our product feed): - `link` -> `productUrl` - `imageLing` -> `image` - `title` -> `name` - `item.price.value`-> `item.price` - `item.salePrice.value` -> `item.salePrice`

4. If the template is ready, in the upper right corner click **Save this template > Save as**. 5. On the popup: 1. In the **Template name field**, enter the name of the template. 2. From the **Template folder** dropdown list, select the folder where the template will be saved. 3. Confirm by clicking **Apply**. 6. To continue the process of configuring the dynamic content campaign, click **Next**. 7. To save your content changes, click **Apply**. ### Define schedule and display settings 1. In the **Schedule** section, click **Define** and set the time when the message will be active. 2. In the **Display Settings** section, click **Define**. 3. Specify circumstances for dynamic content to be displayed. Optionally, you can also define the Advanced options. In our case, we will define the frequency of dynamic content to be displayed to **Once per day**. You can also define the type of device you want to show your dynamic content. 4. Click **Apply**. 5. Optionally, you can define the UTM parameters and additional parameters for your dynamic content campaign.

6. Click **Activate**. ## Check the use case set up on the Synerise Demo workspace --- You can check the configuration of each step from this use case in our Synerise Demo workspace: - [Aggregate](https://app.synerise.com/analytics/aggregates/8b2c2e9e-24e0-30ff-aca6-a9f024a99306) - [AI Recommendation](https://app.synerise.com/ai-v2/recommendations/CWP9JaQ05YAB) - [Dynamic content](https://app.synerise.com/campaigns/create/84798cba-0cc3-4810-9207-114bdcf7989c) If you’re our partner or client, you already have automatic access to the **Synerise Demo workspace (1590)**, where you can explore all the configured elements of this use case and copy them to your workspace. If you’re not a partner or client yet, we encourage you to fill out the contact [form](https://demo.synerise.com/request) to schedule a meeting with our representatives. They’ll be happy to show you how our demo works and discuss how you can apply this use case in your business. ## Generated events This use case generates approximately 5 events per profile that completes the flow: [`dynamicContent.show`](/docs/assets/events/event-reference/dynamic-content#dynamiccontentshow) (~1), [`dynamicContent.click`](/docs/assets/events/event-reference/dynamic-content#dynamiccontentclick) (~1), [`recommendation.generated`](/docs/assets/events/event-reference/recommendations#recommendationgenerated) (~1), [`recommendation.view`](/docs/assets/events/event-reference/recommendations#recommendationview) (~1), [`recommendation.click`](/docs/assets/events/event-reference/recommendations#recommendationclick) (~1). ## Read more --- - [Aggregates](/docs/crm/aggregates) - [Dynamic content](/docs/campaign/dynamiccontent) - [Dynamic content template builder](/docs/campaign/dynamiccontent/creating-dynamic-content-templates/dynamic-content-template-builder) - [Recommendations](/docs/ai-hub/recommendations-v2) # Integration with Accredible You can integrate a full-service digital credentialing solution, Accredible, with Synerise to issue digital certificates, diplomas, badges, and many other credentials to the users based on their profiles and activity in Synerise. This use case presents the integration used for the purposes of user certification in Synerise. The workflows include sending data of users who reached a certification level in Synerise to Accredible in order to issue their certificate and badge.

In this use case, we cover only the part of issuing the digital credentials.

## Prerequisites --- - Access to Accredible. - If you want to [trigger the workflow](/use-cases/integration-with-accredible#create-a-workflow) by occurrence of a custom event, you must add one in Synerise in **Data Modeling Hub > Events** and implement it in your application. You can read more about adding events [here](/docs/assets/events/event-definitions). - Create a schema that stores the certification questions in [Schema Builder](/docs/assets/schema-builder). ## Process --- In this use case, you will go through the following steps: 1. [Create credentials in Accredible](/use-cases/integration-with-accredible#create-credentials-in-accredible). 3. [Create a catalog](/use-cases/integration-with-accredible#create-a-catalog). 4. [Create a workflow](/use-cases/integration-with-accredible#create-a-workflow). 5. [Test](/use-cases/integration-with-accredible#testing) your integration. ## Create credentials in Accredible --- In this part of the process, in your Accredible account, create a group of credentials.

You can find the full documentation [here](https://help.accredible.com/how-do-i-create-a-group).

A group receives a unique identifier.

## Create a catalog --- In this part of the process, prepare a CSV file that contains Accredible group identifier and Synerise ID of the certificate level. Next, create a catalog to which you import the file. 1. Go to **Data Modeling Hub > Catalogs > Create new**. 2. Enter the name of the catalog.

Don't use diacritical letters and spaces.

3. Click **Import CSV**. If you prepared a CSV file in Excel, open it in a text editor to check whether commas are used as separators. If not, replace them with commas. 4. Upload the file by clicking **Upload file**. 5. In the **Order key** field, type the name of the column which values are treated as the key - `syneriseID`.

The value of `syneriseID` is the ID of the schema created as a part of [prerequisites](#prerequisites).

6. Complete the process by clicking **Import**. **Result**:

## Create a workflow --- In this part of the process, create a workflow that is triggered by receiving a certification. Then, a request is sent to Accredible to issue credentials for the user who received the required score. 1. In Synerise, go to **Automation Hub > Workflows > New workflow**. 2. Enter the name of the workflow. 3. As the first node, add **Profile Event**. In the configuration of the node, select the event that triggers the workflow. In this use case, it's a custom event - `certification.acquired`.

If it suits your business scenario, you may use default Synerise events, or instead of **Profile Event**, you may use the **Audience** node to trigger the workflow for the selected group.

4. Confirm the settings by clicking **Apply**. 4. Add the **Outgoing integration** to the workflow. In the configuration of the node: 1. Change the webhook type to **Custom**. 2. As the connection type, select **No authentication**. 3. Click **Select connection** and select a connection. If you want to create a connection, click **Add connection** and [create it](/docs/automation/actions/webhook-node#set-up-a-connection). 1. Select **Custom** and **no authentication**. 1. Enter the name of the node. 2. In the **Webhook name** field, enter the value of the `name` parameter of the event generated by this node. 3. In **Webhook event name**, click **Create event** and create a new event: 1. As **Name**, enter `accredible.userSent` 2. As **Display name**, enter `User sent to Accredible` 3. Select the **POST** method. 4. In the **URL** field, enter `https://api.accredible.com/v1/credentials`

You can find more information about this endpoint [here](https://docs.api.accredible.com/#tag/Credentials).

5. In the **Headers** section, use the following headers: - Set `Content-type` to `application/json`. - Set `Authorization` to `Token token=YOUR ACCREDIBLE API_KEY` 6. Enter the request body, you may reuse and modify the example request below according to your needs:

{
               "credential": {
                   "recipient": {
                       "name": "{{ event.params.firstName }} {{ event.params.lastName }}",
                       "email": "{% customer email %}",
                   "group_id":"{% set key = event.params.certificationId %}{% catalogitem.certificationList(key) %}{% set object = catalog_result %}{{ object.get('accredibleid')}}{% endcatalogitem %}"
               }
           }}

The example request contains three Jinjava inserts: 1. Customer's name sourced from Profile Event node, [read more about reusing information in nodes](/developers/inserts/automation) 2. Customer's email address according to the context 3. Reference to the catalog column You can read more about inserts in Automation [here](/developers/inserts/automation).

Configuration of the Outgoing Integration node

8. Confirm by clicking **Apply**. 9. Add the **End** node. 10. Click **Save&Run**.

Automation Hub workflow for sending certificates via Accredible integration — Final configuration of the workflow

## Testing --- 1. Use the API to send a test event and simulate a user completing a certification 2. Open the **Statistics** tab available in your workflow. 3. Click the **Outgoing Integration** node. If the **Entered** and **Executed** counters have incremented after you sent the test certification, your survey triggered the workflow and completed it. 4. Go to the profile of the test user, look for the `automation` event. Double-click it to see the details. If the `status` parameter is `200`, the workflow works.

Event generated on the customer's profile

You can use this webhook response to trigger further campaigns to the user as well as create analytical dashboards with clear information on how many users received their credentials. ## Check the use case set up on the Synerise Demo workspace --- You can check the configuration of use case in Synerise Demo workspace: - [Catalog](https://app.synerise.com/assets/catalogs/200765) - [Workflow](https://app.synerise.com/automations/workflows/automation-diagram/d62c7285-1698-48a7-b5be-a6238679c78e) If you’re our partner or client, you already have automatic access to the **Synerise Demo workspace (1590)**, where you can explore all the configured elements of this use case and copy them to your workspace. If you’re not a partner or client yet, we encourage you to fill out the contact [form](https://demo.synerise.com/request) to schedule a meeting with our representatives. They’ll be happy to show you how our demo works and discuss how you can apply this use case in your business. ## Generated events This use case generates approximately 5 events per profile that completes the flow: `certification.acquired` (~1), [`automation.clientStartPath`](/docs/assets/events/event-reference/automation#automationclientstartpath) (~1), [`automation.clientPathStep`](/docs/assets/events/event-reference/automation#automationclientpathstep) (~1), [`automation.clientEndPath`](/docs/assets/events/event-reference/automation#automationclientendpath) (~1), `accredible.userSent` (~1). ## Read more --- - [Automation Hub](/docs/automation) - [Integration](/docs/automation/integration) # Early Access Discount for a Specific Product Create a buzz around your product and draw attention to your store, while attracting a larger audience by offering significant discount for a limited time. Build anticipation and excitement among your loyalty and future customers with an early preview of the remarkable discount opportunity. This use case describes how to create a high discount promotion for one product with an early preview. The customer will receive a 70% discount for a specific product three days in advance, which can be redeemed only on the weekend. ## Prerequisites --- - Implement promotions in your [mobile application](/developers/mobile-sdk/loyalty), website or through [API](https://hub.synerise.com/api-reference/loyalty-and-engagement#operation/profileLogin) - [Implement transactional events](/developers/web/methods-reference#tracking-transactions). - [Import the product feed to a catalog](/use-cases/import-product-feed-to-catalog). ## Create a promotion --- Create a straightforward weekend promotion for a specific product with a substantial discount rate (for example 70%). The promotion will be previewable three days prior to its activation. 1. Go to

**AI Hub > Regular Promotions > Add Promotion**. 2. Enter a name for the promotion. 3. Select the **For selected items** type of promotion. 4. In the **Audience** section, choose **Everyone**. 5. In the **Content** section: 1. Define the name, descriptions, thumbnail, and image of the promotion. 3. Optionally, you can add tags to the promotion and JSON code with additional promotion parameters. 2. Confirm the settings by clicking **Apply**.

The view of Content configuration — Content configuration

6. In the **Type and limits** section: 1. Leave **General** in the **Type section**. 1. In the **Type section** field, select **General** (default option). 2. In the **Priority**, enter a number that defines the priority of the promotion.

Priority defines the order of display in the customer’s view. 1 is the highest priority. If two or more promotions applicable to a customer have the same priority, the order of display is determined by the date of creation. The one that was created earlier takes the priority over the other promotion.

3. Select the **Single** tab (default choice). 4. In the **Limit per profile** field, type `1`. 5. From the **Discount type** dropdown list, select **Percentage**. 6. In **Discount mode**, leave the default option (**Static**). 7. In the **Value** field, type `70`. 8. Confirm the settings by clicking **Apply**.

Type and limits configuration

7. In the **Schedule** section: 1. In the **Display time** section, choose **Scheduled**. 2. Pick the dates in the **Start** and **End** fields, in this case the promotion should start three days before the weekend and end on Sunday. 3. In the **Activity time** section, deselect **Same as display time**. 4. Set a date range when the promotion can be activated. Pick the dates in the **Start** and **End** fields, in this case promotion should be active on a selected weekend. 3. In the **Lasting** field, you can enter the time (in seconds) that a promotion remains redeemable after it is activated. `0` is interpreted as infinity. 4. Confirm the settings by clicking **Apply**.

The view of Schedule configuration — Schedule configuration

8. In the **Items** section: 1. From the **Source catalog** dropdown list, select a catalog of items. 2. In the **Include items** section, choose **Selected items**. 3. Click **Select items** and select the product you want the discount to apply to.

The view of Items configuration — Items configuration

9. To apply configuration and run the promotion, click **Publish**. ## Check the use case set up on the Synerise Demo workspace --- You can check the [promotion configuration](https://app.synerise.com/campaigns/promotions/90f3a031-7026-4313-af56-8538d7bea0d0) directly in Synerise Demo workspace. If you’re our partner or client, you already have automatic access to the **Synerise Demo workspace (1590)**, where you can explore all the configured elements of this use case and copy them to your workspace. If you’re not a partner or client yet, we encourage you to fill out the contact [form](https://demo.synerise.com/request) to schedule a meeting with our representatives. They’ll be happy to show you how our demo works and discuss how you can apply this use case in your business. ## Generated events This use case generates approximately 4 events per profile that completes the flow: [`client.activatePromotion`](/docs/assets/events/event-reference/loyalty#clientactivatepromotion) (~1), [`transaction.charge`](/docs/assets/events/event-reference/items#transactioncharge) (~1), [`product.buy`](/docs/assets/events/event-reference/items#productbuy) (~2). ## Read more --- - [Catalogs](/docs/assets/catalogs/introduction-to-catalogs) - [Promotions](/docs/ai-hub/promotions) # Automated email campaign performance reports Take your email performance tracking to the next level using the data context Jinjava tag. Automate the delivery of a detailed weekly report summarizing key metrics from your sent email campaigns, ensuring you stay informed and can take timely action. An alert can be sent through any channel, for example as an email, SMS or to an external tool such as Microsoft Teams or Slack. This particular use case shows how to send once a week an alert with data referencing email performance in the form of an email. To streamline implementation, a ready-made email template is included for a quick setup. ## Prerequisites --- - [Implement a tracking code](/docs/settings/tool/tracking_codes). - [Configure email account](/docs/campaign/e-mail/configuring-email-account). ## Process --- In this use case, you will go through the following steps: 1. [Create an email template](#create-an-email-template) with the HTML block with accurate Jinjava tag. 2. [Create a workflow](#create-a-workflow) sending the notification. ## Create an email template --- You can use a [ready-made template with an HTML block](https://app.synerise.com/campaigns/email/content-manager/template/158990) (available on the Synerise Demo workspace) that inserts the data you want to send in a table format. Just copy it and edit according to your needs. 1. Click the table in the template, and then **Configure** on the right panel.

The configuration of the Email notification on email performance template

2. You can provide the name of the node and change the colors of the table in the configuration. 1. Click **Next**. 3. Edit the template according to your needs. 4. Click **Save as**. 5. On the pop-up, you can change the name and select the folder where the template will be saved. **Result**: The template is saved in the selected folder.

If you want to make your own template, you can switch to the html editing mode of this ready-made template, where you will find an example of jinjava syntax using data reference

## Create a workflow --- In this part of the process, prepare a workflow that sends an email message with a weekly report summarizing the key statistics of your sent email campaigns. 1. Go to

**Automation Hub > Workflows > New workflow**. 2. Enter the name of the workflow. ## Define the trigger node --- At this stage, we will configure the conditions that launch the workflow. We will create a scheduled workflow, that starts every week on Monday at 9:45 A.M. 1. As the first node of the workflow, add **Scheduled Run**. In the configuration of the node: 1. In the **Run trigger** section, leave the default **all time** option. 2. In the **Repeat runs** section, choose suitable timezone. 3. To launch the workflow every week at the defined time, click the **Every week** tab below. 4. Select the desired day, in our case **Monday**. 5. Click **Add time** and set it according to your needs, in our case to `9:45`. 5. Confirm by clicking **Apply**.

Scheduled Run Node — The configuration of the Scheduled Run node

## Configure the Get Statistics Node --- As the next node, choose **Get Statistics** to retrieve email campaign statistics from a specified time range. 1. Click **Then** and add the **Get statistic** node. In the configuration of the node: 1. Select the **By time range** tab. 2. From the **Campaign type** dropdown list, select **Email**. 3. In the **Set time range** field, select the time range from which you would like to export the statistics. In our case, in the **Relative time range** section, select the **Last week** option. 5. The default setting includes statistics exclusively for campaigns sent through Experience Hub. If you also want to include statistics for campaigns launched through Automation Hub, enable the **Include automation statistics** option. If this option is selected, the output will include campaigns set up by Automation Hub that meet one of the following criteria: - the date of creation is within the indicated time range, - at least one sending event has occurred in the indicated time range. 6. Optionally, if you want to export variants of one campaign as separate records, enable the **Breakdown by variants** toggle.

By default, if statistics of a campaign selected for export contains more than one version (due to A/B testing), the statistics for each variant are a single aggregated record.

Campaign statistics data retrieved through the **Get Statistics** node before sending can be [transformed](/docs/automation/data-transformation-and-imports/introduction) to better align their format with specific requirements. To simplify building validation rules, you can download sample data in various formats (.csv, .json, .jsonl).

8. Confirm by clicking **Apply**.

Get Statistics Node — The configuration of the Get Statistics node

## Define the Email Alert Node --- 1. Click **Then** and add the **Email Alert** node. In the configuration of the node: 1. In the **Content** section, select [the email template created in the previous step](#create-an-email-template) and in the **Subject** field, enter your message subject. 2. In the **Recipient** section, use the text field to find recipients or enter an email address to add recipients outside the contact base. 3. Confirm the selection by clicking **Add**. 4. Optionally, you can save the list by clicking **Save list**. This way you can use this list in the future. 3. Confirm by clicking **Apply**.

## Add the finishing node --- 5. Add the **End** node. 6. In the upper right corner, click **Save & Run**.

Data Reference Workflow — Workflow configuration

## 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: - [Configuration of the email template](https://app.synerise.com/campaigns/email/content-manager/template/158990), - [Configuration of the workflow](https://app.synerise.com/automations/workflows/automation-diagram/bbb24d8a-f1ae-44ac-a614-36d1f6f37667). If you’re our partner or client, you already have automatic access to the **Synerise Demo workspace (1590)**, where you can explore all the configured elements of this use case and copy them to your workspace. If you’re not a partner or client yet, we encourage you to fill out the contact [form](https://demo.synerise.com/request) to schedule a meeting with our representatives. They’ll be happy to show you how our demo works and discuss how you can apply this use case in your business. ## Generated events This use case generates approximately 5 events per workflow execution: [`automation.clientStartPath`](/docs/assets/events/event-reference/automation#automationclientstartpath) (~1), [`automation.clientPathStep`](/docs/assets/events/event-reference/automation#automationclientpathstep) (~2), [`automation.clientEndPath`](/docs/assets/events/event-reference/automation#automationclientendpath) (~1), [`message.send`](/docs/assets/events/event-reference/email#messagesend) (~1). ## Read more --- - [Automation Inserts](/developers/inserts/automation#data-context) - [Creating email templates](/docs/campaign/e-mail/creating-email-templates) - [Creating workflows](/docs/automation/creating-automation) - [Get Statistics node](/docs/automation/actions/synerise-integrations/get-statistics) # Web push with voucher and promotion for different categories This use case highlights the functionality provided by Synerise through web push notifications - with a keen focus on user engagement and conversion, Synerise introduces a possibility to add two buttons to a web push campaign. These buttons not only act as navigation tools, directing users to the online store, but also serve as triggers, offering a tailored and interactive experience. This campaign focuses on a targeted approach aimed at users, who have visited specific category, but have not yet made a purchase. The web push notification will highlight special active promotions in the women’s category, which, in our case, will include jewelry and watches. However, this targeting can be customized based on various criteria, such as previously viewed categories (e.g., men/women), where dynamic content placed on the page, which the web push button redirects to, adapts to show relevant promotions based on the visited category. It can also be tailored to other specific user segments, offering flexibility to match our needs. The campaign described in this specific use case, involves adding two buttons, each associated with a unique listing of products: "watches" and "jewelry" for women. After clicking these buttons, users will go to a specific category page where dynamic content with the unique voucher will be displayed. What is important you can enrich this use case using personalized recommendations, promotional recommendations or instead add the link to dedicated landing page with personalized promotions.

## Prerequisites --- - [Implement a tracking code](/docs/settings/tool/tracking_codes). - Create [voucher pools](/docs/assets/code-pools) for both promotions. - [Configure web push notifications](/docs/campaign/Webpush/configuring-web-push) - [Import your product feed to catalog](/use-cases/import-product-feed-to-catalog). ## Process --- In this use case, you will go through the following steps: 1. [Create voucher pools](/use-cases/webpush-with-vouchers#create-voucher-pools). 2. [Prepare a web push template](/use-cases/webpush-with-vouchers#prepare-a-web-push-template). 3. [Create a dynamic content campaign](/use-cases/webpush-with-vouchers#create-a-dynamic-content-campaign) for each promotion. 4. [Prepare a workflow](/use-cases/webpush-with-vouchers#prepare-a-workflow) that will send a web push to customers who visited products of specific categories and didn't make a purchase within 24 hours after visiting the products. ## Create voucher pools --- Create a voucher pool in Synerise for the promotion for women watches and jewelry. 1. Go to

**Data Modeling Hub > Voucher Pools > Add pool**. 2. On the pop-up, fill in the following fields: 1. In the **Pool name** field, enter the name of the pool (the name is only visible on the list of the voucher pools). 2. Optionally, from the **Barcode** type dropdown list, select the type of codes which will be imported in the CSV file to Synerise.

The selection in the dropdown has no influence on the further process. It serves only informational purposes for the users.

3. Optionally, in the **Voucher prefix** field, enter a number that will be added to the beginning of each code. 4. In the **Emission start** and **Emmission end** fields, select the dates when the distribution of the codes starts and finishes, respectively. 5. Optionally, to limit the size of the pool, fill in the **Pool limit** field. 7. Optionally, in the **Description** field, enter the internal description of the pool that is visible only on the list of voucher pools. 3. Confirm by clicking **Save**. 4. Enter into the pool. 5. Using the **Import** button on the top of the screen, import the vouchers into the pool. Proceed according to [this instruction from step 3 (selecting the import method)](/docs/assets/imports/importing-vouchers#procedure). **Result**: After importing vouchers, you will be able to see the codes in the pool. You will also see information about whether it is assigned or unassigned to any customer. You can also see the assignment date and the date of use.

6. Repeat all the steps to create voucher pool for the other category.

Learn more how to build a monitoring system for all voucher pools you have in your workspace. The system can alert you when the number of codes in a voucher pool drops below a predetermined threshold (500 codes in a pool). This alert serves as a reminder for the business to replenish the pool with more codes, as well as an alert to customer service teams to communicate with customers to ensure they are aware of the updated balance. We encourage you to read [Voucher pool alert use case](/use-cases/voucherpools) and use this mechanism.

Do the same with the another voucher pool for watches category. ## Prepare a web push template --- In this part of the process, you will create a web push template with two action buttons. Each of them will display different product category for which the voucher code can be used. 1. Go to

**Experience Hub > Web Push > Templates**. 2. Click **New template**. 3. Enter the name of the template. 4. In the **Title** field, define the title you want to display in the web push. 5. In the **Message** field, define the main body you want to display in the web push. 9. In the **Image URL** field, enter the URL of the image you uploaded previously to the **Files** section in the **Data Modeling Hub**. [Image requirements](/docs/campaign/Webpush/creating-webpush-templates#image-requirements) are listed at the top of the article. 1. To get the URL of the image, go to

**Data Modeling Hub > Files**. 2. Find the image on the list. 3. Hover the mouse cursor over the image on the list. 4. Click **Copy URL**. 5. Paste the URL in the **Image** field. 10. If you want the web push to remain visible until the recipient clicks or closes it, switch the **Require an action** toggle on.

The "requireInteraction" functionality used by this toggle is not supported by some browsers. For more details, go to [https://developer.mozilla.org/en-US/docs/Web/API/Notification/requireInteraction#browser_compatibility](https://developer.mozilla.org/en-US/docs/Web/API/Notification/requireInteraction#browser_compatibility).

11. To configure action buttons for your template, switch the **Action Buttons** toggle on. 1. Click **Add item**. 2. In the **Button Label** field, enter the text that will appear on the button. 2. In the **URL** field, enter the address to which a customer is redirected after clicking the button. 3. To add the second action button, click **Add item** and follow steps b and c.

In this scenario, we have two buttons labeled "watches" and "jewelry." Each button corresponds to a specific URL link: - Clicking the "jewelry" button will redirect to: `https://demoshop.synerise.com/women/jewelry` - Clicking the "watches" button will redirect to: `https://demoshop.synerise.com/women/watches` These links will be employed later in the Dynamic Content (DC) configuration when choosing where to display the DC.

12. For saving the template in a folder of your choice, click **Save as** button and select the desired folder. 9. Save the template clicking the button **Save as**, and choose the folder in which template will be saved. ## Create a dynamic content campaign --- Create a dynamic content campaign where you will display items using a predefined dynamic content template (insert object). This dynamic content will be displayed as a part of the site, only for customers who have clicked the web push. 1. Go to

**Experience Hub > Dynamic Content > Create new**. 2. Enter the name of the content. 3. Choose **Insert object** type. ### Define Audience 1. In the **Audience** section, select **New Audience** and click **Define conditions**. 1. From **Choose filter** dropdown list, select the `webpush.click` event, `campaignTitle` parameter, choose operator `Equal (string)` and as the value add the exact title of the [Webpush campaign](/use-cases/webpush-with-vouchers#prepare-a-web-push-template) created in the previous step. 1. Click `+ where` and from the **Choose filter** dropdown list, select the **webpush.click** event. 2. Choose the `actionButton` parameter with the value `1`. It will be visible only for users who have clicked the first button in the webpush campaign. 2. Click the calendar in the right bottom of the page and choose the option **Lifetime**. 3. Click **Save**.

The view of the Dynamic Content Audience configuration — Audience configuration

8. To save the audience, click **Apply**. ### Define content 1. In the **Content** section, click **Create Message**. 2. From the list of template folders, select a folder with the predefined **Insert object templates**. **Result:** You are redirected to the list of predefined templates. 3. You can also create your own template. In our case we choose predefined template: **Small message bar**. 4. In the **Text** field, add the copy for your message. 5. On the upper right side of the screen, click **Inserts**. From the dropdown list, choose **Pool** and select the voucher pool created in the previous part of the process. Click the voucher pool, copy the code and paste to your text box. 6. Additionally add background color, text color or add any other additional changes. 7. Click the **Use in communication** button. 8. Click **Apply**.

The view of the Dynamic Content Content configuration — Content configuration

Create two dynamic contents: the first includes an insert from one voucher pool directing to the watches category, as previously described. For the second dynamic content, use an insert from the second voucher pool leading to the jewelry category.

### Define schedule and display settings 1. In the **Schedule** section, click **Define** and set the time when the message will be active. 2. In the **Display Settings** section, click **Define**. 3. Specify circumstances for dynamic content to be displayed. Optionally, you can also define the Advanced options. You can also define the type of device you want to show your dynamic content. 5. In the **Page targeting** section, choose **Others**, and in the **Display on pages** section, click **Add rule**. 10. Select **Page URL containing** and enter the address of the category page you defined in the first button in the web push template (for example, the main category page). 4. Click **Apply**. 5. Optionally, you can define the UTM parameters for your dynamic content campaign. 6. Click **Activate**. 7. Prepare another dynamic content template. Duplicate this campaign and add three changes: - In the **Audience** section, change the value of the `actionButton` to `2`. - In the **Content** section, add voucher pool for jewelry category. - In the **Display settings**, select **Page URL containing** and enter the address of the category page you have defined for the second button in the web push template. ## Prepare a workflow --- In this part of the process, create a workflow that will be run every 24 hours, and it will be triggered for the group of users who have visited women category in the last 24 hours but did not make any transaction. ### Define the Audience trigger node 1. Start the workflow with the **Audience** node. 2. Click the node to configure it. 3. In the **Run trigger** section, set the option to **repeatable**, every 24 hours.

Automation Hub Audience node configuration with repeatable run trigger set to every 24 hours — Configuration of the Audience node

4. In the **Define audience** section, choose **New audience**. 1. Click **Define conditions**. 2. From the **Choose filter** dropdown list, select **page.visit**. As the parameter, select **URL** and add the URL for the watches category. 3. Click **Choose filter** and from the dropdown list, select **page.visit**. Choose the **URL** parameter and add the URL for the jewelry category. 4. Betwen those conditions choose operator **OR**. 2. Click **Choose filter** and from the dropdown list, select **transaction.charge**. 4. Betwen those conditions choose operator **AND**. 5. Set up time for each conditions as the **last 24 hours**. 6. Change filter from **matching** to **not matching**. 6. Click **Apply**

Automation Hub Audience node configuration with page visit and no recent transaction conditions — Configuration of the Audience node

### Configure Send Web Push node In this part of the process you will define the Webpush message to be sent. 1. Add **Send Web Push**. In the configuration of the node: 1. In the **Content** section, from the **Webpush template** dropdown, select [the template you created in the previous step](/use-cases/webpush-with-vouchers#prepare-a-web-push-template). 2. In the **Schedule** section, set the **Webpush lifespan (TTL)** according to your business needs. 3. You can describe the campaign with [additional parameters](/docs/campaign/Webpush/creating-webpush-campaigns#adding-custom-parameters). 2. Click **Apply**. ### Add the finishing node 1. Add the **End** node. 2. In the upper right corner, click **Save & Run**.

Automation Hub workflow for sending web push notifications with vouchers — The workflow configuration

Product Sets Template — The workflow configuration