Most B2B teams that decide to send website visitors to HubSpot start with the same setup: a tracking script, a CRM connection, and a rule that creates a record for every visit. It works for a week. Then the company list fills with domains nobody recognizes and contacts that were never people.
The noise is not cosmetic. When every anonymous visit lands in HubSpot, reps stop trusting the intent field, follow-ups go to the wrong accounts, and the company that read your pricing page three times gets buried under a recruiting firm on a residential connection.
This guide is about the delivery design behind a clean pipe: which visits you can identify, how to score them, what to write to HubSpot and what to keep out. It assumes Prynt Reveal for identification and Prynt Automate for delivery, and it optimizes for fewer, better records.
Noise starts when a visit becomes a contact
HubSpot has two objects that matter here: companies and contacts, joined by an association. Visitor identification tools often skip that distinction and create a contact per visit, because contacts are the object most marketing tools know how to feed. For B2B traffic that is the wrong default: a company can visit twenty times in a week with no known person behind the session.
Two rules keep the pipe clean:
- The company is the unit of identification. Upsert on the domain, so repeat visits enrich one record instead of creating six.
- A contact requires a known person. Create one from first-party data only — a form submission, a login, a CRM import with a consent record — never from a guessed identity.
Event inflation is the second source of noise. Pushing every page view as an activity makes the timeline unreadable and distorts lifecycle reporting. Send the signals that change a decision; keep full session history in Prynt.
Name the company before you name anyone
Reveal identifies the company behind a visit when the session comes from that company’s own network, and returns a confidence level with the evidence behind the match. That evidence matters: when a rep asks why an account is in the queue, you can point to the network, the enrichment source and the pages that moved the score.

Not every visit resolves, and it should not. Sessions on home broadband, mobile carriers, hosting providers and VPNs stay anonymous. A residential IP usually says nothing reliable about the employer, and guessing produces the wrong records — the failure that teaches a sales team to ignore visitor data.
People follow the same rule. Reveal links a person to a company only from first-party data you already hold, with a consent record attached; it does not buy identities or infer the name of an anonymous visitor. Expect company records without contacts, and design around it.
Score intent so a number means something
A score without a reason is a score reps learn to ignore. Keep two fields instead of one:
- ICP fit — how well the company matches your segments: size, industry, region, signals from its own website. It changes slowly.
- Intent score — what the account did: pages, depth, frequency, recency. It changes daily.
Weight buying work over curiosity. Pricing and plan pages, security and compliance pages, documentation and integration references, and repeat sessions are stronger signals than one homepage visit. Let recency decay, and treat an account that read pricing today differently from one that read it in March.
Store the reasons, not only the number. A rep opening the record should read “pricing, SSO docs, security page — four sessions in nine days” and know what to open with. Reveal keeps the intent score explainable so every point traces back to a page and a session.
Decide the delivery rule before you turn it on
Write the rule down before enabling the connection, because the defaults are where noise comes from.

- Threshold. Send accounts only at the ICP fit and intent levels your team has agreed to work this week. Set the bar where a rep would actually pick up the phone.
- Properties. Map domain, company name, intent score, ICP fit, hot pages, first seen, last seen and confidence — the evidence, not just the verdict.
- Lifecycle and owner. Do not drop every record into a sales-ready stage. Use a stage that reflects reality; assign ownership by segment, or leave it unassigned until the score crosses a higher bar.
- Association. Link contacts to companies on the domain, so a form fill months later joins the existing history.
Prynt Automate runs the handoff: workflows triggered by identification and scoring events, a HubSpot step with retries and a run log, and template variables such as {{trigger.url}} when the triggering page should land in the record; delivery steps are documented at pryntid.com/docs. Add a Slack step above your top threshold so the fastest response is not a CRM refresh.
Keep the pipe clean after week one
Three habits keep it clean: suppress internal IPs and known competitors; honor the public opt-out and suppression lists (how opt-out works) so the same domains do not return; and review thresholds monthly against the accounts reps actually worked. Intent data is not consent to email — contacting a person still needs a lawful basis under your own policy.
FAQ

Does Reveal create contacts in HubSpot, or only companies?
Companies by default. A contact appears only when a person is identified from first-party data you collected, with a consent record.
What happens to visits from home, mobile or VPN connections?
They stay anonymous and are never sent to HubSpot as named companies.
How many companies can I deliver per month?
Reveal’s Free plan covers 100 companies a month on one site with 7-day history. Paid plans start at 250 companies on Starter and go up to 2,000 on Scale, with Enterprise for higher volume.
If you want to see what your traffic actually resolves to before you touch your CRM, start on the Free plan at pryntid.com: 100 companies a month, no card, and you can check the identified accounts against the deals your team is already working. Reveal and Automate run on the same platform, so when the numbers look right, you can connect the pipe the same week.
Try it free
Prynt is device intelligence with a free plan: 5,000 identifications a month, visitor IDs with confidence and bot detection — no credit card. Upgrade to Pro for VPN, proxy, tampering and behavioral signals.