Targeting On-site Campaign

Once your on-site content is successfully generated, you can make any necessary changes and save it as a draft for later use. If you’re ready to launch, publish the content to prepare it for your on-site campaigns.

To create a campaign directly on content, click on the Create Campaign button which appears within the dropdown after clicking the three dots button.

After the activations are done, real time on-site is accessible on Campaign / On-site on D-engage Panel side menu.

Campaigns have various configurations divided into 3 steps(Settings, Content, Delivery Control) which can be seen in the New/Edit Campaign Page. Last step is a summary of the first 3 steps.

Settings Step

Show conditions of On-Site Message can be configured on this step.

Duration (Start & End Date)

This section provides date based show conditioning for the On-Site Campaign.

There are 2 types of duration conditioning:

  1. After any specific date: This can be achieved by setting Start Date as ‘Now’ or a chosen date and End Date as ‘Never’. So the campaign is going to be active after the set Start Date.
  2. Between 2 specific dates: This can be achieved by setting Start Date as ‘Now’ or a chosen date and End Date a chosen date. So the campaign is going to be active between set dates.

Website (Application) Selection

Real Time On-Site Campaigns can be delivered to only 1 Website(Application).

Within this section applications with On-Site Messaging Enabled are listed for selection. If you can’t see the Website(Application) that you want to deliver, please check that application’s On-Site Messaging Enabled configuration on the Settings / Applications Page.

Platform

This section provides platform based show conditioning for the On-Site Campaign.

This conditioning is used to diverse end-users by detecting they have entered the website from a smartphone browser or a desktop browser. If the end-user’s browser type cannot be detected by D-engage Web SDK, detection is done by checking the screen width of the device they’re using.

There are 3 types of platform conditioning:

  1. All Platforms(Default)
  2. Mobile Web only
  3. Web only

Note: Since the designs of On-Site messages do not differ on desktop and tablet, tablet browsers are not taken into account.

Whom To Show?

This section provides behavioural and situational show conditioning for the On-Site Campaign.

There are 2 options for this section.

All Visitors

This option includes all visitors and does not include any behavioural and situational show conditioning.

Specific Visitors(Rule Builder)

This option provides a behavioural and situational ruleset and logical grouping(AND/OR).

A ruleset has 3 layers.

  1. Ruleset: Contains rules and logical operators between them. A ruleset can have the same logical operator between its rules. If a ruleset has only 1 rule it has no logical operator.

  2. Rule: Contains criterion/criteria and logical operators between them. A rule can have the same logical operator between its criteria. If a rule has only 1 criterion it has no logical operator.

  3. Criterion: Contains selection of parameter, operator(optional) and value.

    1. Parameter: There are 4 groups of default parameter options(Technology, Visit, Traffic Source and Data Space). These options are the same in every customer. Data Space group includes Segment and Tag options. To use Segments and Tags in the Rule Builder, Real-time Synchronisation must be enabled for the chosen Segments and Tags.
      There are also 3 customizable groups of parameter options(Query String, Cookie, Data Layer). These options provide website-specific conditioning.

      Parameters can have 4 basic data types(TEXT, TEXTLIST, INT, BOOL) and 1 custom data type(VISITCOUNTPASTXDAYS).

    2. Operator: Provides selection of various operators according to selected parameters and their data type. A data type has same operator options across parameters with some exceptions especially for the custom parameters.


      List of operators according to data types without exceptions:

      1. TEXT: Equals, Not equals, Starts with, Not starts with, Ends with, Not ends with, Contains, Not contains.
      2. TEXTLIST: Is one of, Is not one of
      3. INT: Equals, Not equals, Greater than, Greater than or equals, Lesser than, Lesser than or equals, Between
      4. BOOL: No operator.
      5. VISITCOUNTPASTXDAYS: Equals, Not equals, Greater than, Greater than or equals, Lesser than, Lesser than or equals.
    3. Value: Provides input or selection according to selected parameters and their data type.

      1. TEXT: Can have free text value.
      2. TEXTLIST: Can have multiple preset values.
      3. INT: Can have number/integer value(s).
      4. BOOL: Can have boolean(true/false) value.
      5. VISITCOUNTPASTXDAYS: Has visit count and past x day values as numbers. Note: This data type is only used in Visit Count in Past X Days parameter.

Ruleset Limits

  • There can be at least 1 and at most 10 total criteria in a ruleset.
  • There must be at least 1 criterion in a rule.
  • There is no direct limitation for the number of rules in a ruleset. But because of the limitations above there can be at least 1 rule and at most 10 rules.

Testing

In this section, a customer can enable A/B testing to offer the best content among all options for the audience. If the customer opts for A/B testing, you are supposed to select more than contents to essentially understand what is the best one for better customer engagement.

Real-time Segmentation and Tagging

Since real-time segmentation and tagging is a performance-heavy feature. A customer can use at most 10 Segments and 10 Tags in Real-time. To use a Segment or a Tag in Rule Builder, Real-time Synchronisation should be enabled for Segments or Tags to be used.

Custom Parameters

Custom parameters can be added under each custom parameter group in the parameter selection dropdown by clicking the ‘Add Parameter’ button.

The name of the added parameter should match the key of the parameter that wanted to be used. Data type and operators can be managed. For example, if the parameter value you want to use will be a number, using INT(number) data type and adding mathematical operators to parameters should be useful.

Custom parameters are add-only. There is no edit or delete option for them. So be careful when adding new custom parameters.

There are 3 types of custom parameters:

  1. Query String: The parameter name is going to be searched among the Query String keys of the current URL. If the key exists in the query string, value of the corresponding key will be used in conditioning.

  2. Local Storage: The parameter name is going to be searched among the Local Storage keys of the page. If the key exists in the Local Storage, value of the corresponding key used in conditioning.

  3. Cookie: The parameter name is going to be searched among the Cookie keys of the page. If the key exists in the Cookie, value of the corresponding key will be used in conditioning.

Show Triggers (When to Show?)

This section provides the configuration for the On-Site Campaign show trigger. After all conditions(Whom to Show, When to Show etc.) are met and selected trigger action occurs or trigger action occurs then all conditions are met On-site Message will be shown.

There are 3 types of triggers:

  1. On Page Load:

    This trigger has 3 options:

    1. Immediately: Trigger fires exactly on page load.
    2. After Delay: Trigger fires after X seconds.
    3. After Scroll: Trigger fires after X percentage of the page scrolled.
  2. On Custom Event
    Trigger fires when a specific Google Tag Manager(GTM) Data Layer event occurs. Event name must be entered to the input. For example ‘gtm.dom’, ‘gtm.historyChange’.

  3. On Exit Intent:

    When the user moves the mouse cursor outside of the top boundary of the page(Address Bar, Bookmarks Bar, Tabs, Window buttons etc.) trigger fires. Trigger does not fire if the cursor moves slowly. This trigger is only available for mouse users.

Show Location (Where to Show?)

This section provides the configuration for URL path based show conditioning.

There are 2 options for this section:

All Pages

When this option is selected, On-Site Message can be shown on any page of the website.

Specific Pages

This option provides inclusion or exclusion for specific pages of the website. Inclusions or exclusion can be done with URL path conditions. To show On-Site Message all path conditions must be fulfilled. Path condition has a logical operator selection and text input.

Content Step

This step provides content selection and creation for the On-Site Campaign. This step has the same feature set with Content > On-Site page. Contents created in this step can be used in Customer Journey On-Site Node.

Delivery Control Step

This step provides configurations for the On-Site Campaign limitations.

Priority

This option sets the priority of the On-Site Campaign. There are 3 priority options: High, Medium, Low. When conditions are met for a visitor to view more than 1 On-Site message, message with the higher priority will be displayed.

Visitor Based Limitation

This section provides configuration for the On-Site Campaign display limitation per visitor.

There are 2 types of limitations:

  1. Show to each visitor only once: When this option is selected. One visitor can see this On-Site Campaign only once.

  2. Show with limits: When this option is selected 2 limitation options can be configured:

    1. Show to each visitor up to X times: Sets the maximum number of On-Site Message displays per visitor. For example if this is set to 5 times, a visitor can see this On-Site Message at most 5 times. After 5 displays the message won’t be displayed even if all conditions to show the message are met again.

    2. Show to each visitor once in every X minutes: Sets the minimum number of minutes to show the On-Site Message again to the same visitor can be defined. For example if this is set to 3 minutes, this On-site Message can be displayed again at least 3 minutes after the message is displayed.

Summary

In this section, the decisions made in the sections of settings, content and delivery control could be checked before saving the real time on-site campaign. You can go back to each page to edit the decisions from the summary section.

To save the campaign, customers can press the Save button located on the upper right side of the page.