Skip to main content
Set up one website first. You have finished when the pixel is verified, you can review visitor data, and you have checked one downstream output.

​
Before you start

You need access to a Leadpipe organization, permission to create a pixel, and a way to edit your website’s HTML or shared header. If someone else manages the site, send them the installation steps below and the snippet from Pixels.
1

Create a pixel

Open Pixels > Create Pixel. Enter a recognizable name and the website domain without a protocol or path, such as example.com.
2

Copy the installation code

Open the pixel’s View code action. Copy the complete snippet generated for that pixel.
Example structure — use the snippet from your account
The pixel identifier comes from Leadpipe. It is not your API key.
3

Publish the snippet

Add the snippet inside the site’s <head> element. A shared header lets it load on the pages you want to track. Publish the website change.For WordPress or another site builder, use your site’s supported header-code mechanism. The exact control depends on your theme, host, and plugins; your site administrator can install the same snippet.
4

Check that the script loads

Open a published page on the configured domain. In browser developer tools, open Network, reload the page, and search for your pixel ID or leadpipe.aws53.cloud.Confirm the script request succeeds. If it is missing or blocked, follow pixel troubleshooting.Return to Pixels and check verification and recent activity. Use the verify action if available.
5

Review visitor data

Open Visitor Insights, choose the correct pixel and date range, and clear saved filters for the first check.A successful script load confirms installation; it does not guarantee that your test visit resolves to a person. Recent events and enrichment can take a short time to appear. See No visitors are showing up if the view remains empty.
6

Control traffic and verify one output

Add suppression rules for internal traffic and known customers before enabling delivery. Use page targeting if only selected pages should be tracked.Save a focused segment, then choose an integration, webhook, API, or CSV export. Inspect a delivered or exported record in the destination and confirm the audience, fields, and owner are correct.

​
Verify your setup

  • The pixel belongs to the intended domain and shows as verified.
  • The published pages load the correct pixel script.
  • Visitor data appears under the intended pixel and date range.
  • Suppression and page targeting match your requirements.
  • One output contains the expected records, and someone owns the next step.
Use the trial scorecard to measure results after setup.