Skip to main content

Testing and verifying a listener

How to test a listener in the Simulator, confirm the profile ID, read Last activated, and what to collect before you contact Support.

Confirm the listener with one visit you control, on the profile that visit created. A segment count or a similarly named property will send you to the wrong conclusion.

Test one visit

  1. Turn the listener on and click Save. A new listener stays off until you do both.

  2. Open the Simulator from the listener, or open the real page in a private window. If you use the BlueConic Chrome extension, turn it off for this test. The extension injects the script and can make a missing tag look installed. If you do use the extension, its script host must be the tenant you mean to test.

  3. In the browser console, run window.blueConicClient. If that is undefined, the script is not on the page. Then run blueConicClient.getHostname() and confirm it is your tenant. www and the bare domain are different channels.

  4. Do the action the listener is built for: load the path, submit the form, or start a second visit. Some listeners write at the start of a visit, so one pageview is not enough. End the visit and come back, or load a second page.

  5. Run blueConicClient.profile.getProfile().getId() and open that ID under Profiles. Check the property named in the listener, including its data type. A number property rejects text, and Set if empty will not replace a value that is already there.

What Last activated means

On the listener, Last activated is the last time this listener ran for a visitor. If it is empty or older than your test, the listener did not run on that page. Check Where, the on/off toggle, and consent objectives.

If Last activated moved and the property is still empty, the listener ran and did not write. Typical causes are visitor Write turned off on the property, a rule that does not match the page (word filter, form trigger, interest term, threshold), or Set if empty finding a value already there.

On a mobile app, Last activated can move when the app next opens, because offline updates are sent then. See Listeners in mobile apps (iOS / Android SDK).

Before you contact Support

Send these with the request. Cases that include them are the ones that can be checked against a profile instead of a guess.

  • Tenant hostname

  • Listener name, and the URL of the listener in BlueConic

  • Listener type (Visit, Funnel, Form, Interest Ranker, Campaign Tracker, Behavior)

  • Whether it is on, and the Last activated time

  • The Where rules

  • The profile property name, its data type, and whether visitor Write is allowed

  • The profile ID from blueConicClient.profile.getProfile().getId() on the test page

  • The page URL you tested

  • What you expected to see, and what is on that profile

  • A screenshot of the rule (form selector, funnel step, parameter table, or interest terms)

  • For an app: iOS or Android, app version, BlueConic SDK version, and whether the phone was offline during the test

Did this answer your question?