Skip to content

Identified people are only useful where your team already works. Connect a destination in a few clicks.

Available now

IntegrationWhat it doesPlan
SlackPosts each identified person or company to a channel through an incoming webhook, with the pages they viewed. Add several Slack destinations with different filters to post to different channels.All plans
HubSpotCreates or updates a contact by email with name, job title, company, and website, using a private app token.All plans
KlaviyoCreates or updates the shopper's profile and records a "WhoLayer Shopper Identified" event, so your browse and cart flows can trigger on it.All plans
WebhooksSigned JSON events (visitor.identified, shopper.identified) to any HTTPS endpoint, verified with an HMAC-SHA256 signature.All plans

Through webhooks or the API

IntegrationWhat it doesPlan
ClaySend identified visitors into a Clay table with a webhook destination, or call the Data API from an HTTP API column.All plans
Zapier and MakeUse a "Catch hook" trigger with a webhook destination; call the Data API with an HTTP action.All plans
n8nUse the Webhook trigger node; call the Data API with the HTTP Request node.All plans
ShopifyPaste the tag into your theme (Online Store, Themes, Edit code, theme.liquid, before </head>).All plans

Coming soon

IntegrationWhat it doesPlan
Microsoft TeamsChannel alerts, like Slack.Planned
Salesforce and PipedriveLead, contact, and account sync.Planned
Meta Custom Audiences and Google Customer MatchHashed audience sync for retargeting.Planned
Shopify appOne-click install with cart value on shopper events.Planned

Filters and routing

Every destination can have its own filter: identity type (person, company, or shopper), job title keywords, minimum company size, and the pages viewed. A common setup sends visitors with "VP" or "Head" in their title who viewed pricing to Slack, every identified person to HubSpot, and companies nowhere.

Don't see your tool?

Use webhooks or the API, or tell us what you need.