Use Contentsquare Live Signals in a Web Experience

This content is only for clients with a Monetate tag implementation that also have Contentsquare's Live Signals feature.

The integration between Contentsquare's Live Signals feature and Monetate allows you to leverage real-time site visitor behavior—such as rage clicks, repeated scrolling, and time spent on a page—in Web experiences.

Before you can use a behavior signal in an experience, you must set up Live Signals in your Contentsquare account. See the Live Signals documentation in the Contentsquare Knowledge Base for the steps.

Confirming the Integration

After you set up and trigger Live Signals in Contentsquare, verify that they're sending real-time data to Monetate. Launch Monetate Inspector to confirm that the page category and custom variable are being passed to Monetate.

The Track tab of Monetate Inspector, with values for Page Type, Categories, and Custom Variables that show Contentsquare Live Signals data is being sent to Monetate

Using a Signal in a Web Experience

To use a Live Signal visitor behavior signal in a Monetate Web experience, you must create a specific type of action condition. This action condition you can add when configuring a WHAT action for a Web experience, or you can include it when creating an action in Action Builder.

  1. Click ADD ACTION, expand Page category, and then select either Page category contains or Page category =.

    Animated demonstration of a user clicking the ADD ACTION button, expanding the 'Page category' menu options, and then highlighting first 'Page category contains' and then 'Page category ='

  2. Input first _cs_livesignal- and then the signal's event name (for example, _cs_livesignal-returns_intention_signal for the Item Returns Intention signal). Press Enter.

    Animated demonstration of a user typing '_cs_livesignal-returns_intention_signal' into the text field for the action condition 'Page category =' and then pressing Enter to save the value

Available Behavior Signals

This table contains the signals that you can use in a Web experience.

SignalEvent NameDescription
Rage Clicksrage_click_signalClicking rapidly X times in Y ms; default is 4 times in 750 ms
Consecutive Clicksconsecutive_click_signalClicking the same element X times consecutively in Y s; default is 5 times in 5,000 ms
Repetitive Hoveringrepetitive_hovering_signalHolding the pointer over the same element X times in Y s; default is 5 times in 10,000 ms
Repeated Scrollingrepeated_scrolling_signalScrolling to X% of the page and then back up to Y% of the page Z times; default is 2 times with a maximum scrolling threshold of 85% and a minimum scrolling threshold of 10%
JavaScript Errors Caused by Clicksjs_error_signalWhenever a click causes a JavaScript error within X s; default is 2,000 s
Mouse Shakesmouse_shakes_signalAccelerating the mouse left and right or up and down within X ms; default is 350 ms with a 0.01 acceleration threshold
Exit Intentexit_intent_signalLeaving the top document window after X ms of being on the page; default is 10,000 ms
Excessive Load Timeexcessive_loading_time_signalFirst Contentful Paint (FCP) of more than X s and repeats Y times; default is 7,000 s and 5 times
Time Spent on Pagetime_spent_on_page_signalAfter X s have been reached in a single natural or artificial page view; default is 90 s
Excessive Pastingexcessive_pastes_fraud_signalPasting in same defined field and session X times; default is 10 times
Excessive Reloadingexcessive_reloads_fraud_signalReloading one or more defined pages in same session X times; default is 20 times
Excessive Clicksexcessive_clicks_fraud_signalClicking the same defined element X times in a page view; default is 10 times
Item Returns Intentionreturns_intention_signalAdding different SKUs for the same product to the cart X times; default is 2 times
Ad Blocker Detectedadblocker_signalWhenever an ad-blocking extension or application is detected within X ms; default is 2,000 ms