Abandoned search scenario

Published July 07, 2022
Modules
Difficulty
Selected Clients
empik logosharafdg logoeobuwie logomodivo logocunipic logominimalism logo

Recover customers who have abandoned their search. When customers conduct a search on your website without adding any items to their cart, this is known as search abandonment. When a customer doesnโ€™t complete a purchase, send an email with products related to the phrase they searched.

This use case describes how to prepare an automated workflow that is triggered by customer searching a specific phrase and sends them an email with an offer based on the abandoned search after 48 hours. One of the challenges addressed in this use case is the use of outgoing integration.

Prerequisites


Prepare a workflow


Create a workflow which sends your customers an email offer with the products from their abandoned AI search. Optionally, you can add additional nodes, depending on your business needs.

  1. Go to Automation icon Automation > 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 item.search event.

  1. As the first node of the workflow, add Profile Event. In the configuration of the node:

    1. From Choose event dropdown menu, choose item.search event.
    Note: item.search is an event that our system generates automatically, when our AI search is implemented somewhere in any of your channels, when customer searches for a phrase. It contains query parameter which stores the phrase entered by customer.
  2. Confirm by clicking Apply.

Configure the Event Filter node

This node will set the workflow to wait for 48 hours for customer conversion (product.buy). If the purchase is made, then the workflow ends. If it doesn’t happen, the workflow moves on because the customer meets the abandoned search scenario. This setting is just an example and can be configured according to your business needs.

  1. As the next node, add Event Filter. In the configuration of the node:
    1. In the Check field, from the dropdown menu choose for period of time.
    2. Set the time range. In our case, it is 48 hours.
    3. In the Define conditions field, from the Choose event dropdown menu, choose product.buy event.
  2. Confirm by clicking Apply.
  3. For the Matched path, add the End node .

Configure the Outgoing Integration node

In this step, we will use the phrase that the customer has searched for (it is stored as a query event parameter in the trigger) to send a request to AI search for products related to this phrase. In further steps, we will use these products in the email which will be added to it through a dynamic insert. You can find the method to retrieve products related to the phrase at this link.
In order to create a request, we configure a custom webhook by defining the Endpoint URL, body request, and so on. This action allows you to send requests from Synerise to external systems.

  1. To the Not matched path, add Outgoing Integration. In the configuration of the node:

    1. Choose Custom webhook.

    2. Name the webhook. In our case get search result.

    3. In the URL section, next to POST, type the endpoint of request: https://api.synerise.com/search/v2/indices/{indexId}/autocomplete, where {indexId} is the ID of your AI search index.

    4. In the Headers section, click add header. In the first field type x-api-key, and in the second an authorization key according to the documentation.

    5. In the Body section add the following JSON frame with Jinjava code:

              {   
              "query": "{{event.params.query}}",
              "limit":6
              }
              

      Where:

      Phrase Explanation
      query this is the phrase the customer used in their search, taken from the event triggering the workflow -

      item.search. To insert this phrase dynamically we used an insert.
      limit this phrase limits how many products the customer will receive.
    6. Leave None as the the method of authorization.

  2. Confirm by clicking Apply.

    Outgoing Integration configuration
    Outgoing Integration configuration

Configure the Event Filter node

This node will allow you to use the products returned by the AI search in the previous step, to send an email with those products. The data of the returned products will be included in the parameters of the webhook.response event.

  1. As the next node, add Event Filter. In the configuration of the node:
    1. In the Define conditions field, from the Choose event dropdown menu, choose the webhook.response event.
  2. Confirm by clicking Apply.

Configure settings for email

  1. As the next node, add Send Email. Configure it according to your business needs.
  2. Configure the sender details section.
  3. Configure the Content section.
    1. In the Subject field, enter your message subject.
    2. In the Template section, choose the template email template prepared earlier.
    3. You can define UTM & URL parameters.
  4. Confirm by clicking Apply.
Important: You need to enrich your email template with products related to the phrase your customer searched. To do so, use Jinjava code and correlate it with parameters from the webhook.response event.

Add the finishing node

  1. Add the End node.
  2. In the upper right corner, click Save & Run.
    Result:
    The workflow configuration
    The workflow configuration

Check the use case set up on the Synerise Demo workspace


You can also check the workflow configuration directly in Synerise Demo workspace.

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

Read more


๐Ÿ˜•

We are sorry to hear that

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

๐Ÿ˜‰

Awesome!

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

Close modal icon Placeholder alt for modal to satisfy link checker