Configure auto-load tracking
Simplify your workflow by letting Wistia automatically load a Marketing Automation Platform (MAP) tracking script when one isn't already present.
To enable auto-load tracking for your supported MAP integration, head to the Integrations page, connect or reconnect your integration, and opt in to auto-load tracking.
Note
Supported MAP integrations include HubSpot, Marketo, Klaviyo, Eloqua, and ActiveCampaign. Automatic script loading is not available for Pardot.
How auto-load tracking works
Note
Auto-load tracking works in conjunction with other integration requirements, so make sure you've got those configured as well. Check out our Integrations article to find your integration and learn all that's required for setup.
When auto-load tracking is enabled, Wistia first checks whether the tracking script is already present when a Wistia video, webinar, or webinar registration form loads.
If a tracking script is found:
Wistia detects the existing tracking script.
Wistia respects the existing installation and does not load another script.
Engagement continues to sync through the existing integration.
If no tracking script is found:
Wistia automatically loads the supported MAP tracking script.
Engagement can now be associated with visitors recognized by the MAP.
This works for embedded videos, webinars, and registration forms as well as Wistia-hosted pages.
Note
Auto-load tracking is not currently available for channels.
Identifying visitors across domains (webinars)
Since the Wistia webinar page and your website exist on different domains, your MAP may treat the same person as two different visitors. Whether the MAP can eventually reconcile those identities varies by MAP.
| Does it recognize visitors across domains? |
HubSpot | Sometimes. It depends on whether the viewer’s browser allows HubSpot to recognize the same visitor across both domains. |
Marketo | No. Marketo creates a separate visitor identity when the viewer moves to the Wistia-hosted domain. |
Pardot | No. Pardot creates a separate visitor identity when the viewer moves to the Wistia-hosted domain. |
Eloqua | Sometimes. This requires Eloqua’s third-party tracking and a browser that allows Eloqua to recognize the visitor across both domains. |
ActiveCampaign | No. ActiveCampaign creates a separate visitor identity when the viewer moves to the Wistia-hosted domain. |
Klaviyo | No. Klaviyo creates a separate visitor identity when the viewer moves to the Wistia-hosted domain. |
Disable auto-load tracking
Disable auto-load tracking for an account
Auto-load tracking can be disabled account-wide, per video, or per webinar. To disable the setting at the account level, reconnect the integration and, in the final step, opt out of auto-load tracking.
Disable auto-load tracking for a single video
To disable auto-load tracking at the video level, navigate to the video's Manage page, scroll down to the video settings, and click the gear icon to open the "Tracking scripts" setting.
In the modal that appears, toggle the setting to the off position and click "Confirm."
Disable auto-load tracking for a single webinar
To disable auto-load tracking for an individual webinar, navigate to the webinar's Overview page. Under Webinar info, click the gear icon next to "Tracking scripts."
In the modal that appears, toggle the setting to the off position and click "Confirm."
