Verify the SourceLoop tracking pixel is installed

You’ve added the tracking code to your site. If not, start with Install the SourceLoop tracking pixel. This guide confirms three things: the code loads, visits arrive, and a lead is captured and credited to the right channel.

Step 1: Check the install

1. Open Setup in the left sidebar, then Tracking code.
2. Click Verify. SourceLoop checks your site for the tracking code and reports back in a few seconds.

If you installed through Google Tag Manager or another tag manager, Verify may not see the code in your page’s HTML. That’s fine: Step 2 confirms it with real visits.

Step 2: Watch your own visits arrive

1. Open Setup, then Data health. The Live tab is open by default.
2. Open your website in another browser tab and click around.
3. Your page views appear on the Live tab within a few seconds.

Click any row to see its page, channel, campaign, device, and country. Use Show only this visitor to follow one person, and the search box to find a page path, an event name, or a visitor.

Step 3: Run an end-to-end test lead

The test proves the whole path works: a visit from an ad, a form submission, and the lead credited to that ad’s channel.

1. On Data health, click Run a test lead. You can also start it from the Getting started checklist at the bottom of the sidebar.
2. Click Open my site and start. Your site opens with a test campaign link.
3. Submit any form on that page with an email you can recognise.
4. Back in SourceLoop, the test ticks off each stage: the visit arrives, the form is submitted, and the lead is credited. It should show Paid Search with the campaign sourceloop_test.

The test lead is marked Spam automatically, so it never reaches your reports, CRM, alerts, or ad platforms.

If a stage doesn’t complete, the test says what it saw. “No visit arrived” means the code isn’t on that page. “No form arrived” means the form wasn’t submitted on the page the link opened, or it runs on another domain and needs its own setup.

Step 4: Keep an eye on Data health

Data health also watches everything connected to your website:

• Sources lists the tracking code, leads, ad accounts, CRM, payments, incoming webhooks, and conversion syncs, each marked healthy, quiet, stale, or failing
• Issues at the top flags anything that needs you, such as a source that went quiet or a high share of results with no website visit
• All events lists every event name your site sends, with counts

If tracking still isn’t working

1. Check the page source. View your page’s source and search for t.sourceloop.ai. If the snippet isn’t there, it was pasted in the wrong template or removed by a deploy.
2. Check your security policy. If the browser console reports a Content Security Policy error for SourceLoop, add t.sourceloop.ai to your script-src and connect-src directives.
3. Check your consent banner. Cookie tools such as Cookiebot or OneTrust can hold scripts until consent. Allow SourceLoop in the right category, or turn on cookieless mode on the Tracking code page.
4. Purge your CDN cache if you use Cloudflare, Vercel, Netlify, or similar.
5. Check the website ID. The websiteId in your snippet must match the website selected in SourceLoop. This is the usual cause when you manage several sites.

Still stuck? Email [email protected] with your domain and what the test reported.

What’s next

• Keep staff visits and job applications out: Exclude pages, forms, and IP addresses
• Connect the tools your leads come through: Web form tracking
• See your first channels: Traffic and Revenue report