4. Targeting Your Campaign

Rooster can be targeted to both specific visitor segments and/or specific pages within your website.

To target your exit overlay, select an exit overlay from your Dashboard, and select the Targeting tab.

Targeting Specific Pages (URL filters) 

URL filters allow you to isolate or exclude certain pages on your site. You can add as many URL filters as you like, but you must add at least one URL filter in order for Rooster to identify your site.

Here are Rooster's standard rules for applying URL filters:

 Using these rules, use the dropdown menu below the URL rules table to specify which URLs you would like Rooster to run on, and which URLs should be excluded:

If your website sells dog and cat grooming services for example, but you only wanted to run Rooster on pages that sell dog grooming, you would:

1. Select Include URLs that contain, and then enter dog.

2. Select Exclude URLs that contain, and then enter cat.

If you wanted to include only your homepage, for example, and your homepage URL was http://www.mypage.com, you would:

1. Select Include URLs that exactly match, and then enter http://www.mypage.com

**Once you've set an exactly match rule, you do not need to add exclusion rules. All other pages will be automatically excluded.

 

Targeting Visitor Segments

Targeting visitor segments requires creating "Rules" for your Rooster Exit Overlay.

Creating a rule will either isolate or exclude specific visitor segments.

To begin, select a standard rule from the drop-down menu. An example rule is "All Visitors | Seen only once per visitor"

This rule means a visitor will only see your exit overlay once.

Advanced Targeting

If none of the basic segments cover your target visitors you can work with our Advanced Targeting. Advanced Targeting allows you to build new segments from a boolean combination of properties.

To create an advanced targeting rule simply select "Advanced Targeting" from the "Visitor Targeting and Segmentation" dropdown when editing your overlay targeting.

You'll see a text box that allows you to enter a JSON string describing the targeting you want.

The JSON string must be of the following format: { "categories": {"CATEGORY_TYPE": {PROPERTY_MATCHER} } } where CATEGORY_TYPE is one of the available property types listed below and PROPERTY_MATCHER is a substring consisting of the following terms:

  • "or": [PROPERTY_MATCHER, ...] - if any of the PROPERTY_MATCHER rules listed are true, the "or" property matcher will be true.
  • "and": [PROPERTY_MATCHER, ...] - if all of the PROPERTY_MATCHER rules listed are true, the "and" property matcher will be true
  • "not": { term } - if the term returns true, applying "not" around it will make it return false.
  • "PROPERTY": {"OPERATOR": VALUE} - returns true if applying OPERATOR (full list of operators below) to the PROPERTY (full list of available properties listed below) and the target value returns true.

The Advanced Targeting segment includes only those visitors for whom all listed categories have true property matchers.

Available Property Categories

The popup category allows you to target visitors based off how they have previously interacted with this overlay.

Available properties for the popup category are:

  • viewed - the number of times this overlay has been displayed to the user
  • interacted - the number of times the user has clicked the mouse or hit the keyboard while this overlay is shown
  • engaged - the number of times the user has clicked on the cta

visitor

The visitor category allows you to target visitors based off how they've used your site.

Available properties for the visitor category are:

  • has_previous_session - false if the visitor is a new visitor to your site. True if they are a repeat visitor.

cookies

The cookies category allows you to match all visitors who have a cookie present or those who have a target cookie value.

Use the cookie value you want to check as the property. For example if your cookie is returning=true use the property "returning". If your cookie is stored as an encodedURIComponent the property will be run through decordURIComponent first.

Available Operators

  • "eq" - property and value exactly match.

    Example: {"categories": { "popup": { "interacted" : {"eq": 1} } } }

  • "not" - property and value do not match.

    Example: {"categories": { "popup": { "interacted" : {"not": 1} } } }

  • "lt" - property is less than value.

    Example: {"categories": { "popup": { "interacted" : {"lt": 1} } } }

  • "lte" - property is less than or equal value.

    Example: {"categories": { "popup": { "interacted" : {"lte": 1} } } }

  • "gt" - property is greater than value. Example: {"gt": 1}

    Example: {"categories": { "popup": { "interacted" : {"gt": 1} } } }

  • "gte" - property is greater than or equal value. Example: {"gte": 1}

    Example: {"categories": { "popup": { "interacted" : {"gte": 1} } } }

  • "exists" - property exists - this is most useful for the cookies category

    Example: {"categories": { "cookies": { "logged_in" : {"exists": true} } } }

  • "matches" - property matches regular expression - this is most useful for the cookies category Example: {"categories": { "cookies": { "level" : {"matches": "\d{2}"} } } }

 

Time-Based Targeting

Rooster's advanced targeting rules allow you to target visitors at specific times of the day (or even on specific days). Only showing an overlay during office hours can be especially powerful when you are driving visitors to phone customer support or sales.

To implement time based targeting rules takes 3 steps.

Figure out what hours you want to target. You can use 3 types of time targeting here.

  1. **UTC time** 

   UTC is Coordinated Universal Time and is basically the same as GMT. To target utc times you can use the following properties:

   * `utc_hours` - Ranges from 0 - 23 based off the current time in UTC

   * `utc_day_of_week` - Ranges from 0 (Sunday) - 6 (Saturday) based off the current day of the week in UTC

   * `utc_date` - Ranges from 1 - 31 based off the current day of the month in UTC

   * `utc_month` - Ranges from 0 (January) - 11 (December) based off the current month in UTC

   * `utc_full_year` - The full 4 digit year (e.g. 2015) in UTC

 

  1. **Office time**

By setting `_GT_config.utc_offset_in_minutes` to your office's time zone offset (in minutes) in your Rooster script you can specify time targeting using your office's time. This is very similar to UTC time but can be a bit more intuitive to set up. To target office times times you can use the following properties:

   * `hours` - Ranges from 0 - 23 based off the current time in your office's timezone

   * `day_of_week` - Ranges from 0 (Sunday) - 6 (Saturday) based off the current day of the week in your office's timezone

   * `date` - Ranges from 1 - 31 based off the current day of the month in your office's timezone

   * `month` - Ranges from 0 (January) - 11 (December) based off the current month in your office's timezone

   * `full_year` - The full 4 digit year (e.g. 2015) in your office's timezone

  1. **Visitor local time**

   If you want to target users at a specific time in their day (for instance you might mention corporate account options during a visitor's workday) you can use this.

   * `local_hours` - Ranges from 0 - 23 based off the current time in the visitor's timezone

   * `local_day_of_week` - Ranges from 0 (Sunday) - 6 (Saturday) based off the current day of the week in the visitor's timezone

   * `local_date` - Ranges from 1 - 31 based off the current day of the month in the visitor's timezone

   * `local_month` - Ranges from 0 (January) - 11 (December) based off the current month in the visitor's timezone

   * `local_full_year` - The full 4 digit year (e.g. 2015) in the visitor's timezone

 

  1. Build a targeting rule for the times you want the overlay to be available. All time based rules use the property category `time`.

 

Here's a simple starting rule for targeting 9am to 5pm in your own office's timezone:

       {

         "categories": {

           "time": {

             "and" :[

               {"hours": {"gte": 9}},

               {"hours": {"lte":17}}

             ]

           }

         }

       }

 

And here's a simple extension of that rule to target only 9 to 5 M-F

       {

         "categories": {

           "time": {

             "and" :[

               {"day_of_week": {"gte": 1}},

               {"day_of_week": {"lte": 5}},

               {"hours": {"gte": 9}},

               {"hours": {"lte":17}}

             ]

           }

         }

       }

Of multiple categories can be combined to build even more complex rules. Here's one for showing to each visitor between 9 to 5 M-F until they've interacted with the overlay once.

       {

         "categories": {

           "popup": { "interacted":{"lte": 1}},

           "time": {

             "and" :[

               {"day_of_week": {"gte": 1}},

               {"day_of_week": {"lte": 5}},

               {"hours": {"gte": 9}},

               {"hours": {"lte":17}}

             ]

           }

        }

       }

  

  1. Set the advanced targeting rule under the targeting tab for your overlay. Simply select "Advanced Targeting" from the Visitor Targeting and Segmentation dropdown and paste your targeting rule in the text box.

 

## Setting up office time.

To set up the office time you need to specify the number of minutes between your office's timezone and UTC - find this here: http://en.wikipedia.org/wiki/List_of_UTC_time_offsets. This can be done by adjusting your Rooster script to set `_GT_config.utc_offset_in_minutes`. Here's an example for setting your offset to PST time (-5 hours utc offset).

       <script>

         <!-- Start Rooster Code -->

         ... Your Rooster Code Goes Here ...

         <!-- End Rooster Code -->

       </script>

       <script>

         <!-- Set the utc_offset in minutes for your office -->

         _GT_config.utc_offset_in_minutes = -5 * 60;

       </script>

 

Have more questions? Submit a request

Comments

Powered by Zendesk