Skip to main content
Before rollout, confirm that Leadpipe supports the people and locations you intend to identify and that your proposed downstream workflow fits your organization’s requirements.

​
Geographic coverage

Person-level location in Visitor Insights is primarily described for the United States. A person’s location and their employer’s location are different fields; a non-US company does not establish support for identifying visitors in that company’s country. These docs do not establish country-by-country availability or a European identification offering. Confirm the specific countries and product area with Leadpipe before planning a deployment outside the documented scope.

​
Review your intended use

Give your privacy or legal reviewer the actual installation scope, contact fields, and destination workflow. Request the current privacy documentation and contractual terms from your Leadpipe contact, including any applicable information about data sources, retention, deletion requests, and subprocessors. Identification and contact availability do not themselves establish permission for every downstream use. Review email, advertising, and sales workflows separately with the responsible team.

​
Product controls

Page targeting limits where the pixel runs. Suppression prevents matching visitors from consuming credits or triggering integrations and webhooks from the next sync cycle. Suppression is not a data-deletion request and does not recall previously delivered records. Use team and account controls to manage access, and keep API keys and authenticated MCP configurations private.