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

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

Signal processing

When the logSignal() method is invoked, a specific message type is created (Type 21) that is then sent to the collectors and stored. Here is an example:

{
  "type": 21,
  "offset": 11938,
  "screenviewOffset": 11925,
  "count": 4,
  "fromWeb": true,
  "signal": {
    "signalType": "order",
    "category": "Behavior",
    "name": "order from product page",
    "orderId": "145667",
    "orderSubtotal": "10",
    "orderShip": "10",
    "orderTax": "5.99",
    "orderDiscount": "10%",
    "currency": "USD"
  }
}

Types of behavioral signals

There are 8 behavioral signal types:

• Identification signals
• Page view signals
• Error signals
• Add-to-cart signals
• Order signals
• Product view signals
• Product configuration signals
• Product purchase signals
• Rich media interaction signals
• On-site search signals

Each of these contain specific data that represents the user action in the form of collected metadata that will be used as the SDK payload, serving as the entry point towards the rest of the signal processing engine.

Testing signal configuration

Here is how you can make sure your new signals are working correctly.

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.

5. Find a JSON object of the following format.

{
  "signalType": "identification",
  "name": "identification from product page",
  "category": "Behavior",
  "identifierName": "email",
  "identifierValue": "[email protected]",
  "identificationFromLogin": true,
  "effect": "positive"
}