Ripe Docs
  • Welcome to Ripe Docs
  • Getting Started
    • Connect your product data
    • Connecting your CRM
  • Connect Product Data
    • Connect with Segment
    • Connect with Tag Manager
    • Connect with Ripe SDK
      • Install the Ripe SDK Script
      • Ripe.identify
      • Ripe.track
      • Ripe.page
      • All Ripe SDK Calls
    • Connect with Ripe API
  • Sync CRM
    • Connect Salesforce
      • Key Concepts Overview
      • Timeline data
      • Automatic entity creation
    • Connect HubSpot
      • Key concepts Overview
      • Sync Modes
      • Automatic entity creation
      • Workflows & Automation
      • Timeline data
  • Widget customization
    • Page targeting
    • Widget visibility
    • Widget position & offset
    • Personalization Variables
  • Ripe Concepts
    • Leads
    • Companies
    • Workflows
    • Videos
      • Profile videos
      • Sending videos
    • Sessions
  • How-to
    • Whitelist Ripe in your CSP
    • Identity resolution
Powered by GitBook
On this page
  • Enabling page targeting
  • Allowing or disallowing the widget on specific pages
  1. Widget customization

Page targeting

How to customize which pages the widget appears on

PreviousTimeline dataNextWidget visibility

Last updated 5 months ago

By enabling page targeting, you can choose which URL paths to hide the widget on or which URL paths to show it on. By default, page targeting is disabled, meaning that the widget will be able to appear on all your pages. Enabling page targeting without any excluded or included paths means that we will match all paths, which is the same behavior as when disabled.

Enabling page targeting

Navigate to your widget settings in the Ripe App and toggle 'Page targeting' in the 'Advanced' section.

Allowing or disallowing the widget on specific pages

Once enabled, you input a list of URL paths to either allow or disallow the widget on. The URL path patterns can be simple path names or regular expressions if more complex patterns are needed. The following are all valid patterns:

  • /start

  • start

  • *

The list of allowed and disallowed paths are not mutually exclusive and you can combine both to create narrower inclusions of URL paths, for instance:

  • Exclude all by default: *

  • But include /start: /start

Exact matches are required for the page targeting to take effect. Consider a disallowed path /companies, that filter will not be applied to the path /companies/companyId. Use regular expressions to enable page targeting on all sub-paths of a path, something like this for the above case: /companies/.*.

The widget page targeting options