Skip to main content

​
Overview

Use Pixels to control where Leadpipe collects data and how each tracked site behaves. Pixels Each pixel gives you a place to manage:
  • Domain coverage
  • Verification state
  • Active or paused status
  • Allowlist or denylist path filters
  • Created and updated history
The page also gives you search, status filtering, and a top-level Create Pixel action for adding new sites quickly.

​
Core tasks

Use Create Pixel when you want to start tracking a new site or domain.
Open the pixel code, copy it, and place it in the header of the site you want to track.
Verification confirms the pixel is installed and collecting from the intended site. Pixels can verify automatically after installation, and the page also gives you a manual verify action.
Pause a pixel when you want to stop collection without deleting the setup.
Use exclusions to prevent unwanted paths from being tracked for a given pixel, such as blog content, demo paths, or other pages you do not want included in the workflow.
If you want the pixel to fire only on a short list of paths, use include-only mode instead of exclusions.

​
Basic install flow

  1. Create the pixel for the site or domain you want to track.
  2. Open View code.
  3. Copy the snippet.
  4. Paste it into the site header.
  5. Return to Pixels and confirm the pixel verifies.
If you only want to track part of the site, add exclusions for the paths you do not want included.

​
Add attribution to a pixel

Add query parameters to the end of your pixel script URL when you need to associate identified visitors with a client, campaign, source, or another internal label. When Leadpipe identifies a visitor, it includes these attribution values in the webhook payload and the Data API’s customAttribution field. The dashboard continues to show all visitor activity.

​
Basic format

The standard pixel does not include attribution parameters:
Standard pixel
Add ?key=value after .js to include the first attribution value:
Pixel with attribution

​
Track a single client

Use a client parameter to identify which client’s website produced the visitor.
The webhook payload includes client = bigco.

​
Track a client and campaign

Use & to add another parameter.
The webhook payload includes client = acme and campaign = spring2026.

​
Track multiple attributes

Add more parameters when your routing or reporting workflow needs additional context.
The webhook payload includes client = acme, source = facebook, and vertical = ecom.

​
Use custom parameter names

Parameter names are flexible. Use labels that match your workflow.
The webhook payload includes account = demo123 and rep = john.

​
Attribution parameter rules

  • Start the first parameter with ? and separate each additional parameter with &.
  • Use short, URL-safe parameter names and values. Prefer letters, numbers, hyphens, and underscores.
  • Do not use spaces. Use my-client instead of my client.
  • Choose parameter names that match your routing and reporting workflow.
  • Use attribution labels only. Do not put API keys, secrets, or sensitive personal data in the pixel URL.
See Passing partner-specific data through the pixel for the customAttribution response shape and Data API availability.

​
Path filters

Leadpipe supports two path-filter modes for pixels: These two modes are mutually exclusive. A pixel should use one or the other. Use allowlist mode when only a few high-value paths should be tracked. Use denylist mode when the pixel should fire broadly but skip low-value areas like blogs, careers pages, or support content.

​
What the table columns mean

If you are working through the API, the pixel list also includes pausedReason, which explains why a pixel is paused.

​
When to use multiple pixels

Use separate pixels when you need to split tracking by:
  • Brand
  • Domain
  • Team ownership
  • Automation routing
This keeps reporting and downstream automations easier to reason about.

​
Keep your pixel setup clean

  • Name pixels clearly
  • Match each pixel to the correct domain
  • Review paused and unverified pixels regularly
  • Add exclusions when internal or irrelevant paths distort the data
  • Use separate pixels when different sites need different routing or reporting