This article covers the following:
- About Triggers in Wingify
- Classification of Triggers
- Applying Triggers to Your Campaigns
- Managing Triggers in Wingify
About Triggers in Wingify
Triggers in Wingify allow you to configure when your campaign changes should be shown to your qualified set of visitors. Coupled with the power of Wingify Data360, triggers offer you extreme flexibility to configure based on your custom events. Now, you can use any minuscule visitor action or construct complex criteria to trigger your campaign.
Note: Triggers are enabled for Data360 workspaces and can be used in Wingify Web Experimentation, Wingify Personalize, and Wingify Web Rollout campaigns. You can also use them to trigger your Survey campaigns and apply them for triggering widgets in variations/combinations.
While the pre-segmentation in Wingify allows you to define your audience, i.e., to whom the campaign should be served, triggers allow you to decide when your campaign should be served to them. For example, you can run a campaign for a set of visitors that visit from a certain geographical location, configuring it to be triggered when they have browsed more than two pages. Here, you can set up the targeting condition using pre-segmentation to apply for the said geographical location and use the triggers to define the event.
By default, the campaign gets triggered the instant a visitor gets qualified based on your pre-segmentation criteria.
To configure the triggering condition, go to the campaign > Configuration > Targeting > Triggers.
Classification of Triggers
Triggers are classified into the following:
| Standard Triggers | Features the following predefined trigger templates for a quick application: Page viewed - Triggers the campaign when the visitor has arrived at the specified campaign URL. Attempts to close page - Triggers the campaign when the visitor attempts to close the current webpage. Time spent on page > 10 seconds - Triggers the campaign when the time spent by the visitor exceeds 10 seconds. Page scrolled > 50% - Triggers the campaign when the visitor has scrolled beyond half of the webpage. Session time > 60 seconds - Triggers the campaign when the visitor has spent more than 60 seconds in the current session. |
| My Triggers | Features the trigger templates that you have created and saved to be reused across campaigns. To know about a trigger, you can click on it to view its corresponding description. Also, you can quickly edit, delete, or clone a trigger that can be used in situations where you need to replicate a complex one with a slight change. To access these options, just click on the vertical ellipsis (⋮) icon and select the option as required |
| Custom Trigger | Allows you to create custom triggers based on standard and custom events as available under Events in the Data360 module. You can create a customized trigger by combining visitor events such as clicks, page scroll, and form submissions with time periods for additional granularity. For more information on the predefined standard events that Wingify provides for quick application, see Standard Events in Wingify. |
Frequency
The Frequency setting determines how often the targeted segment will see the campaign. You can configure this using the dropdown, which offers the following options:
- Always – The campaign appears whenever the targeting rules are met. Suitable for persistent banners or elements that should always be visible when conditions are satisfied.
- Once per visitor – The campaign is shown only once to each visitor, regardless of how many times they return. Ideal for onboarding flows or welcome messages.
- Once per session – The campaign is displayed once per browsing session. Best suited for promos or pop-ups that should not repeat within the same visit.
- Once per day – The interval resets every 24 hours, making it appropriate for daily messages or time-sensitive offers.
- At regular intervals – The campaign repeats at a set cadence, for example, every few days or weeks, useful for recurring reminders or periodic promotions.
The Settings option allows you to configure how targeting and trigger conditions are checked for a visitor.
Check targeting conditions for a visitor:
- Once - The campaign is triggered once the visitor satiates the trigger conditions. In the subsequent visits, the trigger conditions will not be checked again; the campaign changes will be displayed immediately upon the visitor’s repeat arrival.
- Every time - Here, the trigger conditions are checked on every visit. The campaign is triggered every time the visitor performs the events set for the trigger. This will not get carried over to subsequent visits; the visitor will have to perform the same events on every repeat visit as defined in the trigger conditions to be able to view the campaign changes. For example, if you wish to run a campaign to offer a discount coupon to visitors every time they trigger a certain specific event on their visit to the campaign URL, then you can select Every time from the Settings so that trigger conditions are checked on every visit.
Check trigger conditions for a visitor
Use this dropdown to define how often the trigger conditions are evaluated:
- Once – The campaign is triggered once the visitor satisfies the trigger conditions. In subsequent visits, the trigger conditions will not be checked again; the campaign changes will be displayed immediately upon the visitor's repeat arrival.
- Every time – The trigger conditions are checked on every visit. The campaign is triggered every time the visitor performs the events set for the trigger.
Note: When Every time is selected, the visitor is evaluated for the trigger conditions on all the metric pages as well. This typically means that when visitors click a button or visit a page defined as a metric in your campaign, they must also satisfy the trigger conditions on the metric URL(s) for their conversions to be recorded.
Applying Triggers to Your Campaigns
As far as Standard Triggers and My Triggers are concerned, you can simply click on the required trigger and click the Save button to apply it to your campaigns. When you’re looking to use the Custom Trigger section, you need to roll up your sleeves a bit. It allows you to tailor your campaign triggers based on your requirements. It brings in the entire set of events listed under Data360 > Events to be used as elements of your custom triggers. Plus, you also get the ability to define when to trigger the campaign.
When you enter the Custom Trigger section, you will get to see that the first on the list of your custom events is selected by default, and it is set to trigger the campaign immediately after the custom event is performed.
If you wish to trigger the campaign after a certain amount of time post event execution, you can select After and specify the number of seconds correspondingly.
You can choose an event based on your requirement and also define the conditions for their respective properties by using the following relations:
If it’s a text property:
| Text Property | |
|---|---|
| Is equal to (case sens.) | Triggers the campaign to the visitors that have performed the said event with the specified property that matches the defined text value, regardless of the text case |
| Is not equal to (case sens.) | Triggers the campaign to the visitors that have performed the said event with the specified property that does not match the defined text value, regardless of the text case |
| Is equal to (case sens.) | Triggers the campaign to the visitors that have performed the said event with the specified property that matches the defined text value matching the text case |
| Is not equal to (case sens.) | Triggers the campaign to the visitors that have performed the said event with the specified property that does not match the defined text value matching the text case |
| Matches Regex (case sens.) | Triggers the campaign to the visitors that have performed the said event with the specified property that matches the defined regular expression, regardless of the text case |
| Matches Regex (case sens.) | Triggers the campaign to the visitors that have performed the said event with the specified property that matches the defined regular expression matching the text case |
| Contains | Triggers the campaign to the visitors that have performed the said event with the specified property that contains the defined value |
| Does not contain | Triggers the campaign to the visitors that have performed the said event with the specified property that does not contain the defined value |
If it’s a number property:
| Number Property | |
|---|---|
| Is equal to | Triggers the campaign to the visitors that have performed the said event with the specified property that matches the defined numerical value |
| Is not equal to | Triggers the campaign to the visitors that have performed the said event with the specified property that does not match the defined numerical value |
| Greater than | Triggers the campaign to the visitors that have performed the said event with the specified property that has a value greater than the defined numerical value |
| Less than | Triggers the campaign to the visitors that have performed the said event with the specified property that has a value lesser than the defined numerical value |
| Greater than equal to | Triggers the campaign to the visitors that have performed the said event with the specified property that has a value greater than or equal to the defined numerical value |
| Less than equal to | Triggers the campaign to the visitors that have performed the said event with the specified property that has a value lesser than or equal to the defined numerical value |
| In list | Triggers the campaign to the visitors that have performed the said event with the specified property that is included in the attached attributes list. For more information, see Using the Attributes List in a Campaign. |
| Not in list | Triggers the campaign to the visitors that have performed the said event with the specified property that is not included in the attached attributes list. For more information, see Using the Attributes List in a Campaign. |
If it’s a boolean property:
| Boolean Property | |
|---|---|
| Is equal to | Triggers the campaign to the visitors that have performed the said event with the specified property that matches with the defined boolean value |
| Is not equal to | Triggers the campaign to the visitors that have performed the said event with the specified property that does not match with the defined boolean value |
You can add multiple event properties by clicking on + and where or using the Add another condition to add multiple events to construct the campaign trigger.
While doing so, you can conjoin two conditions by specifying the following conjunctions:
- And - Triggers the campaign when the visitors meet both the specified conditions simultaneously.
- Or - Triggers the campaign when the visitors meet either of the specified conditions.
-
And then - Triggers the campaign when the visitors meet both conditions sequentially, complying with the specified time frame. Upon selecting this option, you can choose from either of the following options:
- after that - Triggers the campaign when the visitor performs the subsequent event right after the previous one.
- within - Triggers the campaign when the visitor performs the event within the set number of seconds. Upon selecting this option, you need to specify the time in seconds in the adjacent field.
As you’re adding another condition, you can also specify the visitors that have performed or not performed a said event by using the perform and do not perform options.
Once set, you can click on the Save Trigger button to save the trigger, which can then be found under the My Triggers section.
Should you require deleting any of the events or an event property, click on the Delete button corresponding to them.
Let’s consider that you’re looking to draw more conversions aiming at the population that has just abandoned the cart by displaying a cashback offer.
To cater to this, you decide to trigger your campaign when the visitors have added a product to the cart and haven’t proceeded to purchase within 30 seconds of time.
Managing Triggers in Wingify
Wingify provides you with a section dedicated exclusively to managing your custom triggers. You can access it by navigating to the main menu panel > Data360 > Triggers. Here, you will get to create your custom triggers and save them to be used across your campaigns in Wingify. The Triggers page features two sections - Standard (standard triggers) and My Triggers (saved custom triggers).
You can click on a trigger to view the following details:
- Definition - Displays the trigger conditions.
- Metadata - Displays the basic information of the trigger, such as its name, description, the user who created it and its date of creation.
You can use a standard trigger to clone it and create a custom trigger out of it. Whereas the saved custom triggers in the My Triggers section can be edited, deleted and cloned. To perform these operations, simply click on the respective trigger and click on the vertical ellipsis (⋮) to access the respective options.
To create a custom trigger, click on the Create button and perform the steps as explained above.