Skip to main content
Person-level website visitor identification is built into Swan. If you’re currently paying for a standalone visitor identification tool — RB2B or similar — you don’t need to keep it running alongside Swan, and in most cases you shouldn’t.

​
What’s included

Swan’s tracking script ships identification with it. There’s no separate subscription, no separate contract, and no per-identification fee for the RB2B-sourced matches — see credit costs for how the rest is priced. RB2B is one of the identification sources Swan runs under the hood, so the person-level matches you’d get from them come through Swan. On top of that, Swan runs its own matching layer that resolves visitors independently, and a company-level path that works on traffic RB2B doesn’t resolve at all — including traffic outside the US. See visitor identification for how the paths fit together. Once a visitor is identified, Swan doesn’t stop at the name. It enriches the full contact, checks them against your CRM and target market, and can run the outreach, update the CRM, or route the visit to the right person — see how triggers work.

​
Don’t run two identification pixels at once

If you install Swan’s script, remove your standalone RB2B snippet. RB2B’s pixel only supports one instance per page. With both snippets installed, whichever one loads first wins and the other silently stops reporting — there’s no error, no warning, and no way to tell from the page which one is live. Running both to compare them doesn’t work; you’ll just get one of the two, at random. The same applies to any other identification pixel that loads the same underlying provider. If you want to evaluate Swan against your current tool, run them in sequence rather than in parallel — remove the old snippet, install Swan’s, and compare over a comparable window of traffic.

​
Why your numbers won’t match your old dashboard

Expect a lower count in Swan than the raw resolution count in a standalone visitor identification dashboard. That’s deliberate — Swan filters before it shows you anything, so the list is one your team can act on rather than a raw feed:
  • Known-bad and non-actionable matches are dropped, including companies on a small global blocklist Swan maintains across all customers.
  • Your own exclusions apply — companies on your blocklist or CRM exclude lists, such as existing customers.
  • Repeat matches from the same company inside a short window don’t fire twice.
  • Your trigger settings — country allowlist, excluded paths, minimum session time, and identification mode — filter further, per the tracking script settings.
  • The daily identification limit caps identifications at 1,000/day by default.
One thing worth checking if the gap looks larger than expected: your domain allowlist. Swan only reports visits from domains you’ve explicitly allowed, and a standalone tool may have been resolving traffic on subdomains or landing-page domains you haven’t added yet. Add every domain and subdomain you want identified, including blog, docs, and marketing subdomains.

​
Common questions

Can I keep my RB2B subscription as a backup? You can keep the subscription, but you can’t keep the snippet on the same pages as Swan’s — the two pixels conflict and one will silently win. If you want RB2B running standalone, it needs to be on pages where Swan’s script isn’t installed. Will I see every visitor my old tool showed me? Not one-for-one, and that’s by design — see the filtering above. Swan also identifies visitors your old tool wouldn’t have, including company-level matches on non-US traffic. Compare qualified visitors your team can work, not raw row counts. Do person-level identifications cost extra? RB2B-sourced identifications cost 0 credits. Swan’s own person- and company-level identifications cost 2 and 1 credit respectively when they clear qualification and fire your trigger — see credit costs. What happens if my org runs out of credits? Swan stops serving the tracking script until credits are available again, so identification pauses along with the rest of your automations. See credits. Does Swan work outside the US? Person-level identification is strongest on US traffic, which is a limitation of the underlying data, not of Swan. Company-level identification from IP address isn’t US-restricted, so non-US traffic still resolves to companies.