On this page
TrafficID helps your team review identifiable website visitors, submitted forms and company context in the BrandWell portal. It gives a portion of your existing website demand a useful next step; it does not identify every visitor or prove that someone is ready to buy.
This updated product overview replaces the original launch announcement. For the current demo, packages and allowances, see the TrafficID product page. Historical launch wording is not a current offer.
What TrafficID does
TrafficID connects available person and company information with website visit context. Review the audience by person or company, distinguish submitted inquiries from passive visits and inspect the available details before routing a record.
Identification coverage and available fields vary. A record should retain its source so the team can distinguish an identified visitor, a form submission and an additional decision maker at the same company.
Keep observed visitors separate from stakeholders
A Stakeholder ICP can help find relevant decision makers at represented companies. Those additional contacts are useful account context, but they should remain clearly marked as added stakeholders rather than people observed visiting the site.
Likewise, several visits from one company do not prove an internal buying discussion. Treat that pattern as a reason to review the account, not a statement about what employees said to each other.
Set up the collection and suppression path
- Connect the site. Use the Company Project’s site-tag setup and reported installation state to check the configured collection path.
- Review the audience. Inspect identifiable visitors, form completions and the company context attached to them.
- Apply exclusions. Keep customers, ineligible contacts and other suppressed people or companies out of the proposed next action.
- Check the role and need. Use the available evidence to decide whether the person or account fits the offer.
- Assign an owner. Keep the reason for review and the next-step responsibility visible.
Configure the website’s disclosures, permissions and collection behavior for the intended use. A contact field appearing in a record does not establish permission for every communication channel.
Use AIMEE for research and a reviewed handoff
TrafficID includes AIMEE for the initial user under the current product offering. AIMEE can help research an account, summarize relevant context and prepare a message or task through configured tools. Confirm the permissions, usage and approval process for the workflow you choose.
The owner should decide whether follow-up is appropriate. Avoid messages claiming you know a person’s private intentions. A useful account brief can explain the business fit without treating a passive visit as a submitted request.
Fictional workflow: a payroll-software team reviews a returning visitor from a suitable company. The account owner checks the role and existing customer status, then asks AIMEE for an account brief. Any added finance stakeholder remains labeled as an added contact, not the original visitor.
Choose the next action deliberately
With the appropriate access, TrafficID supports exports of the first-party or stakeholder view to CSV or a formatted Excel workbook. Reviewed audiences can also inform an Outreach or Direct Mail workflow, with the relevant product, permission and fulfillment requirements.
Do not send texts to an enriched mobile number merely because it is available. Keep channel-specific permission, opt-outs and suppression separate from identity enrichment. Audience export is a data operation, not evidence of consent or a guaranteed advertising match.
Measure the audience and the actual outcome
Track identified visitors, form completions, qualified accounts, reviewed handoffs and resulting outcomes separately. Record duplicates and exclusions. Do not label every identified person a sales-ready lead.
Hypothetical review: 100 identified records yield 30 accounts that fit the agreed criteria and ten reviewed handoffs. Report those three counts separately. Ten handoffs do not mean ten customers, and the example is not an expected TrafficID identification or conversion rate.
Compare periods with the same definitions and note changes to traffic, tagging, exclusions or follow-up. A rise in identified records can come from more visits without any improvement in sales conversion.
Common questions
Will TrafficID identify every website visitor?
No. Coverage varies. Review what is actually available in your workspace rather than assuming complete identity or contact details.
Are added stakeholders observed visitors?
No. Keep the source distinction visible when reviewing, exporting or preparing follow-up.
How does it differ from MarketPulse?
TrafficID focuses on your website audience. MarketPulse provides topic-research intent data, with standard plans starting at $500/mo. Choose the signal relevant to your workflow.
Explore TrafficID and watch the current demo. Begin with a defined audience review and measure the usefulness of the next action.
Reviewed and updated October 3, 2026.
Written by
Justin McGill is the founder of BrandWell, growth automation software for inbound and outbound teams. BrandWell brings together MarketPulse intent data, TrafficID website audiences, RankWell content workflows, Visibility research and AIMEE execution through configured tools.
Julia McCoy