Before proceeding, it is important to ensure that “the wishlist price drop” event has been enabled within Swym Admin. To confirm this, after logging in to Swym Admin, navigate to Integrations>Sendlane>Configure. Go on to, locate the Wishlist Plus trigger labelled “The price drops on a product in a shopper’s wishlist”. The trigger threshold is set to 10% by default, which you can change according to your requirement and proceed by clicking on Checkbox.

To confirm that this feature is working as expected, you can test the trigger from the ‘Send a Test Event’ section, which you can find by scrolling down after saving the trigger. Simply input the email address, choose the “Add to Wishlist alert” trigger, and then click on “Send Test trigger” and a test trigger of the event will be sent to Sendlane. Once a trigger has been activated within a Sendlane automation, it will result in an action (activities that take place once a trigger has been activated). One example of such an action is an SMS/ Email to a designated contact, as set by you, i.e. the merchant.

Correspondingly, when a shopper adds a product on the store-front to their wishlist, and assuming that they have already shared their email contact with the store, a price drop email alert will be sent out through Sendlane to the Shopper, straightaway, based on this Swym event.

• The custom events registered for Sendlane<>Swym integration are the ones used as triggers for Sendlane automations.
  ‍
• Select Automations > New Automations > Start from the Scratch. Let’s say you want to set up an Automation for an email message. Choose a name for the automation (say “PD_email” in this case)

Next, the screen shown below will be presented. Click on “Add Trigger”

Select a trigger. Select “Custom”, and scroll down till you see & select “Custom Event”.

A custom event tile gets added to the “map”, and a configuration panel opens up.

You may configure the custom event as required, using the choices presented by the drop-down for the “store”, the limit” and the event per se. For the purpose of this example we have selected “Swym Price Drop”, as the trigger/ custom event. Notice the custom event tile in the map, which gets populated with values selected. Click on “Done”, when satisfied.

The screen shown below is presented. Next, click on the “Plus” sign on the “map” to add an Action or a Timing block.

An “Action-cum-Timing” panel opens up on the LHS. You could choose “Send Message” (Actions> Send Messages); or/ and set up the Automation timing & logic by inserting Timing> Wait, as required.

Proceeding further, let’s say you select “Send Email”.

Click on Create New Email.

Next, configure the email, as shown below. For the purposes of this example the email has been named “MaggieCampaign”. Continue with the configuration as appropriate to your context. Next, select a relevant sender profile. Finally, move on to the email content.

After picking a relevant subject and a pre-header, you may create the email content by picking its design from available templates or by custom designing it.

For this example, we have picked a custom design template and a basic payload. Within that we have narrowed down to a Full Row Layout Block and chosen to drop an HTML element into the custom content space.

We then go about composing the dynamic HTML code block in a contextually relevant manner. Start by editing the HTML Code, save it, and finally save & continue, when you are ready.

Do verify that the destination email id is already added to the Contacts tab of the Audience section of Sendlane. Else, you may add it even now, for automated handling in subsequent iterations.

Next, activate your email and the Automation in any comfortable sequence/ order.

Go to Swym Admin Dashboard, and having selected the right trigger (“Added to Wishlist” in this example) and filled out the selected email id, click on send test trigger – this time from within Swym Admin Panel, to simulate sending of email based on Swym events/ triggers.

Check if you receive the triggered email in the designated mailbox, and satisfy yourself.

• You will recollect that with the Swym<>Sendalane integration, you have the capability to re-engage shoppers in an effective manner with personalised alerts on the products that are of interest to them based on dynamic content generated from the shopper intent captured by Swym.
  ‍
• Setting up of automations in Sendlane is a crucial link to be able to hit up shoppers with more engaging and relevant promotional content, to ultimately drive better results in terms of shopper conversion, from your email/ SMS campaigns.
  ‍
• Please note that different email/ SMS service providers have their own formats and methods for using merge tags. So in this final section we dwell on the how-to of drafting content for a marketing message (Email/ SMS) by leveraging merge tags effectively in a Sendlane-specific context.
  ‍
• You need to start with a declaration, as shown below:
  {% set data = trigger.getCustomEventData() %}

• Currently, Sendlane doesn’t support conditional splits based on custom event properties to select the channel (viz SMS/ Email). This means sending email or SMS based on custom properties from Swym payload is not possible (this would come from the medium field in the payload).
  ‍
• Consequently, if you wish to use the email channel to reach the shopper, you would need to create a separate automation for it (e.g. Add to Wishlist (email)) for each of the Swym triggers separately. However, allowing for conditional split by the user-preferred-medium (email /SMS) is on Sendlane’s roadmap and will be accomplished soon.

• Some of the more complex use-cases relate to sharing information related to a range of wishlisted products with users, when triggered by certain Wishlist Plus or Back in Stock  events such as Share a Wishlist, a Wishlist Reminder or Save of Later (SFL) Reminder. However, the good news is that such events are also supported by the Sendlane<>Swym Integration using arrays (of products).
  ‍
• It is in no way necessary to always use all the listed  merge tags. You may find that a functional subset  can often meet your need quite adequately, e.g. the merge tags used in the Price Drop Email in this playbook are as shown below:-

Hey {{contact.first_name}}

                     {% set name = trigger.getCustomEventName() %}

                     {% set data = trigger.getCustomEventData() %}

                     Click to go to product page

                     Name: {{ data.productName }}

                     Medium: {{ data.user.medium }}

                     Product Name: {{ data.productName }}

                     URL: {{ data.productURL }}

                     Image URL: {{ data.imageURL }}

                     {{ data.productOriginalPrice }}

                     {{ data.productCurrentPrice }}

Immediately Usable HTML Snippet

<p style="text-align: center; font-family: verdana, geneva, sans-serif;">
    Hey {{ contact.first_name }}
</p>
{% set data = trigger.getCustomEventData() %}
<p style="text-align: center; font-family: verdana, geneva, sans-serif;">
    The price of <a href="{{ data.productURL }}">{{ data.productName }}</a> has dropped from {{ data.productOriginalPrice }} to {{ data.productCurrentPrice }}.
</p>
<p style="text-align: center;">
    <img decoding="async" src="{{ data.imageURL }}" alt="Image of {{ data.productName }}" />
Contact Email ID: {{ contact.email }}.
</p>

Issues to be Noted

• To use custom fields from the event, Sendlane uses templating (check here).
• Check the sample events and their templates here.