SDKs
Help centerCommunityDevelopersAcademyStatus

Behavioral signals in the Connect web library (Pro)

Guide for Connect Pro customers

Suggest Edits

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.

Types of behavioral signals

If you have a Connect Pro subscription, you can capture key user behaviors on your website and map them to contacts in your audience. Three signals are available:

  • Identification. You can instruct the library to capture visitors' emails or client/contact IDs as they are browsing your website and feed the data to your audience in Connect.
  • Add-to-cart. This signal notifies your marketing team that a contact has added products to their cart. The names, IDs, prices and quantities of the products are provided.
  • Order. The order signal comes each time a contact places an order on your website. For each order, there is the total amount and a detailed breakdown by the product.

Not sure what your license type is?

You can quickly check what type of Connect license your company is using. Log in to your Connect account and check the label in the upper-right section of the home screen.

Acoustic Connect home page

Sample Connect Pro subscription

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, 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.

Prerequisites

During the onboarding process, our provisioning team has registered your application with Connect and sent your team an application key and endpoint URL. You'll need these values when installing the Connect library.

Instructions

Step A: install the Connect library

To implement behavior signals, you must first add the Connect library to your web application.

  1. In your webpage template, add the following code snippets anywhere within the <head> tag. 
<!-- version 6.4.157 is the latest version at the time of writing -->
<script src="https://cdn.goacoustic.com/connect/6.4.157/acoconnectLite.min.js"></script>
<script>
    (function () {
        const tlAppKey = "YOUR APP KEY";
        const endpoint = "YOUR ENDPOINT URL";
        // Configures SDK for Acoustic Pro. Do not modify this config object.
        const config = {
            core: {
                buildNote: "Acoustic Connect Pro",
                blockedUserAgents: [{ regex: "(Google|Bing|Face|DuckDuck|Yandex|Exa)bot|spider|archiver", flags: "i" }, "PhantomJS"],
                inactivityTimeout: 1000 * 60 * 29, // 29 minutes
                replay: { events: [{ name: "load", target: window }] }, // to capture TLTDID
                modules: { TLCookie: { enabled: true } },
            },
            services: {
                queue: {
                    asyncReqOnUnload: true,
                    queues: [{
                        qid: "DEFAULT",
                        endpoint: endpoint,
                        maxEvents: 3,
                        timerInterval: 10000,
                        maxSize: 100000,
                        checkEndpoint: true,
                        endpointCheckTimeout: 3000,
                        encoder: ""
                    }]
                }
            },
            modules: {
                TLCookie: {
                    appCookieWhitelist: [{ regex: ".*" }],
                    tlAppKey: tlAppKey,
                    secureTLTSID: true
                }
            }
        };
        function afterInit () {
            // Recommended: add your logSignal code here. Running it in this afterInit
            // function ensures it will be executed after the SDK has initialized.
        }
        window.TLT && window.TLT.init(config, afterInit);
    }());
</script>
  1. Replace YOUR APP KEY and YOUR ENDPOINT URL with the values provided by our provisioning team.
  2. Push the changes to the server.

👍

Tip

  • Add the <script> tags to the <head>of the page to have them executed as early as possible.
  • Do not change the order of the two <script> tags; the SDK file must be loaded first.

Step B: enable behavior signals

Now you can implement the behavior signals. Here are instructions for each signal:

Before a signal can be sent, the SDK must be loaded and initialized. One way to ensure that is the case is to add your signals code inside a callback function like the afterInit function in the example above.

📘

Migrating from Acoustic Campaign?

You must replace the Silverpop Web Tracking pixel with the new, flexible logSignal-based tracking method in Acoustic Connect.

Step C: verify signal capture

To confirm that signals are implemented correctly and data is flowing, do the following:

  1. Click around on your website to trigger the signals you have activated. The identification signal is required because it maps users to behaviors.
  2. Log in to your Acoustic Connect subscription.
  3. Go to Data management > Audience.
  4. On the All contacts tab, select the contact you used for testing the signal.
  5. In the activity feed, view the activity associated with the selected contact.
Activity feed in Connect

Maintenance note

As your website receives updates or gets redesigned, these changes may affect signal configuration. It is important to include signal verification into your regular quality assurance routine.

Updated 2 days ago