Category: Live Signals

This integration is only available for Web projects and these are the third parties this integration supports sending signals to:

What to expect

The integration allows for segmentation based on user interactions like rage-clicking, constant hovering, repeated scrolling and fraudulent activity. These signals can also be sent to other 3rd party tools in real-time.

What we collect

Dynamic Variables

Implementation

Implementation Steps

Visit How to request an integration, follow instructions to begin enabling, and return here once completed.

Signal Options

You can choose from these supported signals:

Friction Signals

Fraud Signals

Nudge Signals

Ad Block Signal

Namogoo Signals (for Namogoo clients only)

Each signal has the option of overriding the default threshold values that are set.

Here are the defaults for each which you can request to have changed if need be.

Defining CSS Selectors

Fraud Signals

If you use the fraud signals then you need to define the following:

For the Excessive Reloads module you need to define a part of the URL where you want this module to run.

It is recommended to only set this condition to run on pages that have a credit card or voucher field.

For the Excessive Pastes and Excessive Clicks modules you need to define CSS selectors such as Class Names / IDs / Data Attributes of input fields which you would like to track pasting in or clicking on. It is recommended to use classnames that are unique to these fields. You can put as many comma separated selectors as you need but best to keep it to credit card or voucher input fields as that is where fraud takes place. If your company deals with insurance claims then perhaps all fields in the insurance claim form should be included in this. For the URL conditions please use pipe | separators.

Other Signals

For all signals you have the option of setting CSS selectors or JavaScript expressions to make the scope of the detection more specific and to only apply to certain pages and/or certain elements.

CSS Selector Format

It accepts the standard format that is used by document.querySelector()

So for example the click listener will only detect the selector based on the last node which in this case is the SPAN element which is inside a BUTTON element. So let's say your selector exists on the BUTTON element ([data-testid='configurator-next']) but you want a signal to be detected on the BUTTON and the SPAN inside it, then you need to request that option to be enabled else it will never detect the selector.

Get CSS Selectors

In order to easily define CSS selectors to be provided to Contentsquare for Live Signal tracking, you can install this Chrome extension.

1. Once installed, right-click on the new extension icon in your browser and click 'Options':

2. On the options page change the Get CSS Selectors to 'Enabled' and click 'Save Settings'.

3. Go to the page that you want to get the CSS selectors from (refresh if the page was already open).

4. Click on any element on the page, especially the ones you are interested in tracking with Live Signals and you will see a draggable modal in the top left of the screen showing the element type and the CSS selectors associated with it.

Ex: Clicking a CTA button, as you see in the modal, shows the tag type and the CSS selectors associated with it.

5. Click on the CSS selectors that you want to use and it will copy them to the clipboard.

If for some reason the page redirects after you click it then once the page loads it will automatically show the last detected CSS selectors in blue.

The moment you click on another element it will then show the new element information you clicked on and change back to red and so on.

6. Please then provide the selectors you want to track to the team who will configure this for you in your Contentsquare account and let them know which Live Signals it is for. If the selectors will be the same for multiple signals, then please specify that. Don't forget to disable this option once completed else it will track on all sites you go to.

Alerting Options

With signals you have the option to choose where to send these signals, such as to Contentsquare for segmentation and also to some 3rd party products that we currently support. Should there be another product you would like to send to but don't see it in the list then feel free to request it via support and we can look into developing it.

If you would like to send these signals to Contentsquare then you can choose from sending them as either or both of these:

• Dynamic Variables
• Page Events (these appear in the event stream of playback sessions)

Special Instructions

window.addEventListener(
    "Contentsquare_LiveSignal",
    function (e) {
        //In the event detail property you will find the signal object that was dispatched.
        //Simply push that object to wherever you need.
        
        //console.log(e.detail);
    },
    false
);