Skip to main content
Start with the symptom below. Check one stage at a time: installation, collection, visitor qualification, then delivery.

​
No visitors are showing up

  1. In Pixels, confirm the domain, verification state, and recent activity. Check whether the pixel is paused.
  2. Open a published page and confirm the pixel script loads using the installation check.
  3. In Visitor Insights, choose the intended pixel and date range. Clear search, filters, and the saved view.
  4. Review page targeting. Include-only rules can leave most of your site untracked.
  5. Check your organization and credits in the account area, or use account status.
A script loading successfully does not guarantee that a particular visit will be identified. Recent activity can also appear after a processing delay. If using the API, inspect historical coverage as described in Visitor data.

​
The pixel is unverified

  1. Confirm the snippet is on the published site, not only in an editor or staging preview.
  2. Confirm the snippet’s pixel ID matches the configured domain.
  3. In browser developer tools, reload with Network open and inspect the script request. A missing request suggests the snippet was not published or is not on that page.
  4. If the browser reports blocking, inspect the blocker or the site’s content security policy with your site administrator. Keep the site’s consent requirements in place.
  5. After correcting installation, return to Pixels and run verification if the action is available.

​
The data looks noisy

Use the control that matches the problem: Suppression still allows identification. It prevents future credits and automation triggers from the next sync cycle; it does not reverse earlier charges or deliveries.

​
A webhook or integration is not delivering

  1. Check that the connection is active and points to the intended destination.
  2. Confirm its pixel, segment, and send frequency. Once per visitor does not send every repeat visit.
  3. Review suppression rules for the expected visitor.
  4. For webhooks, send a test payload and inspect both Leadpipe delivery history and your receiver’s logs.
  5. If the test succeeds but live data does not arrive, compare the test with an actual qualifying visitor and the configured trigger.
  6. If the connection is Auto-disabled, fix the recorded failures before enabling it again.
See webhook receiver checks. Delivery and retry behavior can differ between Identification webhooks and Orbit destinations.

​
The API request fails

If a key was regenerated, update each backend or integration that used the previous key. See Authentication and errors.

​
Orbit results are not ready

A saved audience is a definition. It needs a completed run before results or exports are available. Result reads return 202 while a run is queued or running; 202 is not a completed empty audience. List the audience’s runs and inspect its state. Failed or cancelled runs return a conflict when you request results. Use the bounded polling example, and keep the same run ID across result pages and exports.

​
Before contacting support

Include the page or workflow, expected result, actual result, time with time zone, and organization or pixel ID. For an API issue, include the method, path, status, request ID when present, and a redacted response. For a delivery issue, include the delivery ID and receiver status when available. Use your existing Leadpipe support channel. Remove API keys, webhook secrets, signed download URLs, and personal visitor data before sharing logs or screenshots.