Behavior signals in the Connect web library

Behavior signals are events that are typically important to any business, regardless of the industry. You can configure the Connect library to generate them while visitors are interacting with your website.

The Connect Web library exposes a method called logSignal() that receives a JSON payload.

Types of behavioral signals

Here is the list of signals supported by all Connect subscriptions:

Premium and Ultimate license holders can enable additional signals:

Important considerations

The signals are designed to capture all necessary details for each use case. However, there is a chance that some of the available options will not be available for capture, or don't apply to your business. Here are some examples.

  • If an insurance company website asks visitors to submit a quote request, there will be no unit price value for the product view signal. Also, the add-to-cart signal will be irrelevant.
  • If your users are redirected to a third-party service that you cannot add the Connect library to, or if pages from that service are displayed within an iframe, it may be challenging to get required data for the order signal. Typical examples of such third-party websites are payment processing and ticket selling solutions.
  • Until users are asked to identify themselves, for example by logging in, the identification signal cannot be sent. Identification is the key to tying the behaviors to a specific contact. You may want to consider surfacing the email or other unique user identifier in the application (for example, in the data layer once the user has logged in) so that it can be captured more easily by the Connect library.

Testing signal configuration

All Connect subscriptions

If a signal is configured correctly, you will find new data flowing to Connect. For example, the signal will become available for segmentation or the audience will be enriched with new contacts.

Ultimate subscriptions only

Additionally, Ultimate subscription holders have access to the JSON payload generated by the signal. It is convenient for quick verification.

  1. Click around on your website to trigger the signals you have activated.
  2. In your Connect account, navigate to Insights > Sessions > Session search.
  3. Find your test session and select the checkmark next to it.
  4. Click Inspect signals.








  1. Find a JSON object of the following format.
{ "signalType": "identification", "name": "identification from product page", "category": "Behavior", "identifierName": "email", "identifierValue": "name@example.com", "identificationFromLogin": true, "effect": "positive" }

Did this page help you?