Context

When the Unify tracking tag is installed on your website but visitor data is not appearing in your Unify dashboard, this is typically due to a Content Security Policy (CSP) configuration issue that prevents the tag from connecting to Unify's servers.

Answer

To resolve this issue, you need to update your website's Content Security Policy to allow connections to Unify's domain.

Verify the Tag Installation

Before updating your CSP, you can verify whether the Unify tag is properly installed:

1. Open your browser's developer console on a page where the tag is installed

2. Check if window.unify exists by typing it in the console

3. If it exists, manually trigger a page event by running: window.unify.page()

If window.unify is undefined, the tag may not be installed correctly on that page.

Add the following directives to your website's Content Security Policy:

• script-src https://tag.unifyintent.com - allows the Unify tracking script to load

• connect-src https://api.unifyintent.com - allows the script to send data to Unify's servers

You can add these in one of two ways:

• As an HTTP response header: Content-Security-Policy

• As a meta tag in your HTML: <meta http-equiv="Content-Security-Policy" ...>

After updating your CSP and deploying the changes, hard refresh the page and verify the tag is working using the verification steps above.

Note: If you need to track activity on subdomains (e.g., app.yoursite.com, blog.yoursite.com), ensure the Unify tag is installed on those pages as well.

Additional Troubleshooting Steps

Verify Unify Reveal is Enabled

Check that Unify Reveal is enabled in the dashboard settings. This setting must be enabled for website tracking to work and can be disabled during initial setup or accidentally toggled off during website migrations or configuration changes:

• Navigate to Settings > Data > Web Intent > Unify Reveal in your Unify dashboard

• Ensure the Unify Reveal feature is toggled on

• This feature can be accidentally disabled during website migrations or settings updates

Check Dashboard Filter Settings First

Before investigating technical issues, verify your dashboard filter settings are configured correctly:

• Change the filter to “page views containing”

• Add your domain name to the filter options

• This ensures you’re viewing data for the correct domain

CSP Wildcard Limitation

If you already have a wildcard CSP entry like https://*.unifyintent.com, you still need to explicitly include the base domain https://unifyintent.com in your connect-src directive for the tracking script to function properly.

Check for Script Conflicts

Look for conflicts with other tracking scripts on your website that might interfere with Unify’s tracking functionality. Multiple analytics or tracking tools can sometimes prevent each other from working correctly.

Subdomain Tracking Requirements

If using subdomains (e.g., app.yoursite.com, blog.yoursite.com), you must explicitly add the Unify tracking tag to those pages as Unify does not automatically track subdomains.

Where to View Tracked Data

Once tracking is working, you can monitor website activity in your Unify dashboard:

1. Navigate to the Activity view in your Unify app

2. Apply filters for Website → Sessions or Page Views to see aggregate website activity

3. Set the timeframe (e.g., last 7 days or last 30 days) to view totals for your desired period

After updating the CSP, Unify should begin tracking website visits and form submissions correctly, allowing you to see visitor data in your dashboard.