Behavior signal implementation in the Connect Web SDK

Each how-to guide below walks through the configuration, required fields, and a working code sample for firing one specific behavior signal from the Connect Web SDK. Pick the guide that matches the interaction you're instrumenting.

• Enable order signals — capture completed transactions and send order details to Connect.
• Enable page view signals — track page navigation events.
• Enable add-to-cart signals — capture items added to a cart.
• Enable removed-from-cart signals — capture items removed from a cart.
• Enable product view signals — track product detail page views.
• Enable product configuration signals — capture product option or variant selections.
• Enable rich media interaction signals — track video and audio engagement.
• Enable error signals — capture site errors encountered by users.
• Enable on-site search signals — capture search queries and results.
• Enable identification signals — map anonymous visitors to known contacts.
• Enable account registered signals — capture new account creation.
• Enable logged in signals — capture successful logins.
• How behavior signals are processed in Connect — reference for how submitted signals are handled downstream.