How It Works

From checkout to your first identified visitor, in five real steps.

Two minutes on most sites. We will do it with you if yours is one of the awkward ones. Here is the exact flow, and the one sentence that removes the biggest objection to paying before installing.

The seven-day trial starts when the connection test passes, not at checkout. Nothing is live before that point, so you do not lose a single day to setup.

Part one: the flow

01

Checkout

You check out and your card is charged $1. You pick a plan now so the trial converts to the right one on day eight, but nothing is live yet and the seven days have not started.

02

Paste one line before the closing head tag

You copy one line of JavaScript and paste it before the closing head tag on your site. One line, site-wide, in the head. This is the WebNet Pixel.

03

The live connection test

We run a live connection test that confirms the pixel is firing on your real site. The test must pass before the account goes live. If it fails, we show you why and how to fix it.

04

Confirmation

When the test passes, you get a confirmation. The account is provisioned. The seven-day trial starts at this moment, not at checkout. You have not lost a single day to setup.

05

Provisioning and names begin

The account provisions and identified visitors begin flowing into your CRM. Amos starts the hunt on your real traffic. You see your real numbers from your real visitors before you pay anything beyond the $1.

Part two: the install

For the person stuck. The snippet, where it goes on each platform, and why the test fails, in the order it actually happens.

The snippet

Copy this one line and paste it before the closing </head> tag on your site. One line, site-wide, in the head. Replace YOUR-SITE-ID with the ID from your dashboard.

<!-- LeadSpyder WebNet Pixel -->
<script src="https://cdn.leadspyder.ai/webnet.js" data-site="YOUR-SITE-ID" async></script>

Where it goes on your platform

Each platform has a field that injects code into the head site-wide. Find that field and paste the snippet there.

WordPress

  1. Install a header-code plugin, or edit your theme header.
  2. Open the global header or the header-code field.
  3. Paste the snippet before the closing head tag.
  4. Save and clear your caching plugin.

Shopify

  1. Go to your theme settings.
  2. Open the custom code or head injection field.
  3. Paste the snippet into the head field.
  4. Save the theme.

Squarespace

  1. Open settings, then code injection.
  2. Find the header field.
  3. Paste the snippet into the header field.
  4. Save.

Wix

  1. Open your site settings.
  2. Find the custom code or tracking tools section.
  3. Add the snippet as head code, site-wide.
  4. Save and publish.

Webflow

  1. Open project settings, then custom code.
  2. Find the head code field.
  3. Paste the snippet into the head code field.
  4. Save and publish your site.

Generic header-code box

  1. Look for a settings area named header code, custom head, or code injection.
  2. Paste the snippet into that field.
  3. Make sure it applies site-wide, not to one page.
  4. Save and clear any cache.

Why the test fails, in real-world likelihood order

If the connection test does not pass, it is almost always one of these five. Each has a fix.

The connection test fails because the snippet is in the body, not the head.

The WebNet Pixel must sit before the closing head tag, not anywhere in the body. Move the one line up into the head section of your site template, save, and run the test again. Most site builders have a dedicated header-code field that places content in the head automatically.

The connection test fails because a caching plugin is serving the old page.

A caching plugin or a CDN can serve a saved copy of your page that does not yet contain the snippet. Clear your cache, purge your CDN, then open the page in an incognito window and run the test again. The test reads the live page, so it needs the live version.

The connection test fails because the snippet is on one page, not site-wide.

The pixel must be site-wide, not pasted into a single page or post. If you added it to one landing page only, the test on your main domain will not find it. Place it in the global header or the site-wide code injection field so it loads on every page.

The connection test fails because a consent banner is blocking scripts before accept.

A cookie consent banner that blocks scripts until the visitor accepts can stop the pixel from firing on the test visit. If you use a consent tool, allow the WebNet Pixel to load before consent, or run the test after accepting the banner. The pixel is cookieless and does not set tracking cookies.

The connection test fails because you tested a different hostname than the one you entered.

The www and non-www versions of your domain count as different hostnames. If you entered leadspyder.ai but the test visited www.leadspyder.ai, it will not match. Use the exact hostname your site loads on, including or excluding www consistently, and run the test again.

Stuck? Talk to a human.

Two minutes on most sites, and we will do it with you if yours is one of the awkward ones. Call us at 307-222-4603 or start the $1 trial. The clock does not start until your connection test passes.

Start the $1 Trial