Insight Tag won’t connect

You installed the tag and Settings → Domains still does not show Connected. Three causes cover nearly every case:

• Hostname mismatch — the script must be on pages served from the exact hostname you added. www.yoursite.com and yoursite.com are different hostnames; so is a landing-page subdomain like go.yoursite.com. Add the hostname your QR destinations actually use.
• No real traffic yet — Connected means a real page ping arrived within the last 48 hours. The tag only reports on visits that came from a Boxli QR redirect, so an installed tag with no scans yet stays unconnected. Scan a code from one of your own sends to generate a ping.
• The script never loads — tag managers and site builders sometimes strip or defer custom scripts, and a strict Content-Security-Policy can block the request. View the page source to confirm the script tag is actually in the served HTML, and make sure your CSP allows app.sendaboxli.com.

The fastest end-to-end check: confirm the snippet is in the served HTML on the exact hostname, scan a code from a real send, wait a moment, then use Test connection on Settings → Domains. If that passes once, dwell will flow for every future scan — and until it does, scans still track fine; only time-on-page is missing.

Related articles

• Install the Boxli Insight Tag
• Why isn’t an engagement showing up?
• Total Attention, explained
• Why did my send fail?
• The address says undeliverable