Event as Triggers
Events as triggers are essentially triggers based on customer events which either happen on Shopify or BIK. These triggers are commonly utilised to initiate predefined actions based on user interactions with BIK and Shopify, aiding in the streamlining of processes and enhancement of efficiency.
List of Events Used in Triggers:
The following below events are available to used as triggers:
Sl. No. | Event Name | Typical Event Properties | Description |
1 | Ordered | 1. Order value 2. Order ID 3. Customer ID 4. Payment method 5. Broadcast ID 6. Broadcast Name 7. Billing Address 10. Total number of items | This event gets triggered when a customer places an order. |
2 | Abandoned product | 1. Product ID 2. Product name 3. Cart ID 4. Customer ID 5. Item price 6. Broadcast ID | This event gets triggered when a customer adds a particular product to the cart but doesn't complete the purchase. |
3 | Abandoned a cart | 1. Cart value 2. Broadcast name | This event gets triggered when a customer starts the checkout on the website by adding contact information but doesn't complete the purchase. |
4 | Customer Created | 1. Customer source | This event gets triggered when a new customer is created. |
5 | Purchased a product | 1. Product ID 4. Product price | This event gets triggered When a product is purchased. |
6 | Product delivered | 1. Collection name(s) | This event gets triggered When a product was delivered. |
7 | Line Item Shipping Update | 1. Order ID 6. Variant name(s) | This event gets triggered whenever shipping status of any individual item changes in an order. |
8 | WhatsApp cart | - | This event gets triggered When a cart request is received on WhatsApp |
9 | Order Delivered | 1. Order ID | This event gets triggered when an order gets delivered to a customer. |
10 | Conversation Created | 1. Source type | This event gets triggered When a new message is sent by user via widgets(Chat redirection widgets, QR code, URL generator). |
11 | Customer Acquired | 1. Source URL 12. Widget name 13. Widget/source category 14. Product name 15. Platform 16. Page Url | This event gets triggered When a new customer is acquired via Bik widgets(reward based, non reward based, chat widgets or growth tools). |
12 | Lead generated | 1. Source type 2. Source ID 3. Widget name 4. Product name | This event gets triggered When any customer shares their contact details via 1. lead generator widget 2. CTWA or 3. in journeys where phone number or email block is used |
13 | Reward disbursed | 1. Source ID 6. Coupon description | This event gets triggered When a reward is disbursed for an user via reward based widgets(Spin the wheel, direct reward, scratch card). |
14 | Added to Wishlist | 1. Product name 4. Variant ID | This event gets triggered when a product is added to the wishlist |
15 | Product viewed | 1. Product ID | This event gets triggered when a product was viewed |
16 | Order cancelled | 1. Order ID 4. Product names 5. Number of items 6. Image | This event gets triggered whenever a particular order is marked as cancelled |
17 | Keyword searched | 1. Search term | This event gets triggered Whenever a customer searches for a keyword |
18 | Add to cart | 1. Product ID 4. Variant ID 5. Variant name 6. Collection ID(s) | This event gets triggered Whenever a product is added to cart |
19 | Subscription | 1. Subscription event | This event gets triggered whenever a customer is enrolling in a subscription service, wherein they will receive a product or service automatically on a recurring basis. Currently, this offering includes Loop subscriptions. Please contact us at [email protected] to add support for other subscription apps. |
20 | Payment Link Update | 1. Payment link 7. Payment link ID 8. Purpose 9. Old Order ID 10. New Order ID
| This event gets triggered When payment link was updated |
21 | Review Created | 1. Review ID | This is an event from Judge Me whenever a user adds a review. |
22 | Email received | 1. Customer Mail Id 2. Merchant Email Id 3. Email Subject 4. Email Body | This event gets triggered whenever email received from customer |
23 | Gmail received | 1. Customer Mail Id 2. Merchant Email Id 3. Email Subject 4. Email Body | This event gets triggered whenever gmail received from customer |
24 | Ticket assigned to agent | - | This event gets triggered Whenever ticket gets assigned to an agent |
25 | SLA Breached | - | An SLA breached event gets triggered, when the Service Level Agreement (SLA) for a specific ticket has not been met. |
26 | Chat Session Closed | 1. Content type 2. Is auto closed | This event gets triggered whenever a chat is closed either by agent or via auto close setup by brands |
27 | Ticket Stage Change | 1. From stage 2. To stage | This event gets triggered when every time the ticket stage changes |
How to Configure Events as Triggers:
Follow these steps to configure events as triggers in journey flows:
1. Access the Journey section in the BIK dashboard.
Open an existing flow journey or create a new journey flow to configure events.
Click on "Start Point" and choose "Events" in the triggers.
From the dropdown, select the desired event from the listed options.
Click on "Add Event Property" and choose a property from the available options.
Add keywords and values for the selected property of the event.
Click "Create" to successfully add events as triggers in the journey flow and complete the journey configuration.
FAQs
1) Can I use multiple events as triggers in a single journey flow?
Yes, you can add multiple events by using the "Add Triggers" option in the starting point block.
2) How do I ensure event trackers are enabled for certain events?
For events such as "Product Viewed," "Order Cancelled," and "Keyword Searched," ensure to enable event trackers in the Settings.
Navigate to Settings -> Channel Management -> Shopify ->Others or alternatively use this link.
Enable and disable website events tracker under the channel management settings. This will ensure these events are properly tracked and can be used as triggers.
3) Can I add multiple event properties for events?
Yes, you can add multiple event properties as needed by using the "Add event property" option.
For further assistance or to raise feature requests related to Event as triggers, please contact [email protected]