Patient records for a hospital. Wire fraud for a bank.
A B2B security vendor’s home page, four visitors. An unknown visitor gets the whole platform. A hospital network, identified through an ABM integration, sees patient-record protection and a healthcare case study; a regional bank sees account takeover and audit evidence. An existing customer gets the module they do not own yet and the customer community — and no “Book a demo”. Switch the visitor below to see all four.
Every login, device and data store, on one console
Detection, identity and data protection in one place — so a 3am alert arrives with the context to act on it.
One security site, four buyers.
Connect firmographics and the CRM
An ABM integration supplies industry and size for anonymous business visitors; the CRM supplies lifecycle stage and modules owned for known ones. Both become targeting conditions.
Write one version per industry
A hero, a resource row, a proof and a call to action for healthcare, and another set for financial services — each an audience with its own content, built in the visual editor.
Take customers out of the sales funnel
A customer audience swaps the demo request for the module they lack and the community, so the site stops selling people what they already bought.
How Personyze personalizes this security vendor’s site.
Industry arrives with the IP, not with a form
An ABM integration resolves the visitor’s company before the page paints: a hospital network with 6,200 staff, or a regional bank with 1,800. No field was filled, and no earlier visit is needed.
Each industry gets its own hero, resources and proof
The hospital network sees patient-record access, a healthcare case study and a CISO from a health system; the bank sees account takeover, an audit evidence pack and a bank’s head of IT risk. The modules and the navigation are the same — only the framing changes.
An unknown visitor gets the platform, not a guess
When nothing resolves, the page shows all four modules and a broad headline. It is the page as built, and it stays broad on purpose: the wrong industry is worse than none.
Customers are recognized from the CRM, and the demo button goes
A customer’s CRM record — lifecycle stage and the modules on the contract — is synced as customer attributes. The page leads with the one module they do not own, points to the community, and suppresses every “Book a demo”, including the one in the navigation.
The resource row is filtered per audience
The row under the hero is a content recommendation with a rule on the industry tag, so a hospital gets hospital material and a bank gets bank material. For a customer the rule switches to their account: a walkthrough of the missing module, the community, and release notes.
Questions about this example
How does the page know a visitor is from a hospital or a bank?
An ABM integration such as 6sense, ZoomInfo, Leadinfo or Albacross resolves the visitor’s company from the IP address before the page paints, including its industry and headcount. Those values are targeting conditions, so each industry can have its own hero, resources and proof.
How are existing customers kept out of the sales pitch?
Customer attributes from the CRM, such as lifecycle stage and the modules on the contract, are synced to Personyze. An audience of customers can then see the module they do not own and the community instead, with every “Book a demo” suppressed.
What does a visitor who cannot be identified see?
The default page: the whole platform and a broad headline. Nothing is guessed, and the industry versions only appear when the company has actually been resolved.
Speak to each buyer’s risk.
Resolve the industry before the page paints, write one version per market, and stop asking customers to book a demo.