Skip to content
GridRouterhome

Search

Search providers, capabilities and pages

Identify a website visitor API

signals.visitor_id

The company, and where lawful the person, behind a website session.
providers document it
15

Providers

15 providers document identify a website visitor in their own API docs. None routes it through GridRouter yet. Scores appear as calls are routed.

Show all 15 providers
  • Dutch B2B website visitor identification platform.

  • Ecommerce visitor identity resolution for email/SMS retargeting.

  • UK B2B website visitor identification software.

What counts as a hit:
A company or person is resolved for the session.

API

Same input for every provider. Set provider.sort to route by price, reliability or latency, or provider.only to pin providers; X-Grid-Max-Cost caps what one call can spend.

Inputs for signals.visitor_id
InputDescription
session_id*Visitor session or pixel event id (required)
Request
curl https://api.gridrouter.io/v1/run/signals.visitor_id \
  -H "Authorization: Bearer $GRID_API_KEY" \
  -H "Content-Type: application/json" \
  -H "X-Grid-Max-Cost: 0.05" \
  -d '{"input":{"session_id":"s_8Hq2c1"},"provider":{"sort":"price"}}'

Fields

The normalized output every provider maps into. Suppliers come from integrated endpoint mappings (verified) or field names in each provider's API docs (claimed by the provider).

Every capability's fields
Output fields for Identify a website visitor
FieldTypePIIDescriptionSupplied by
session_idstringIdentifierVisitor sessionNot mapped yet
company_domainstring · domainNoneResolved companyRB2B
company_namestringNoneResolved company nameCommon RoomVector
person_emailstring · emailPersonal contactResolved person email (where lawful)Vector
linkedin_urlstring · linkedin_urlIdentifierResolved person profileDealfront (Leadfeeder)
pages_viewedarray<string>NonePages in the sessionNot mapped yet
visited_atdatetimeNoneSession timeDealfront (Leadfeeder)Snitcher