Identify website visitors

No. The flow works at company level: which company, which pages, which topic. Visits without an identifiable company aren't included in the alerts. Clarify tracking and consent on your website with your data protection team beforehand.

No. An alert is only created when your rules apply – such as repeat visits to product or pricing pages, a matching industry or an open sales opportunity. Everything else is bundled into the weekly overview.

Company identification delivers the company; domain matching and CRM matching assign it – including existing customer matching and a duplicate account check, so no account is created twice. ISP and bot filters weed out internet providers and bots, and visits from your own company are excluded. The flow merges several locations of the same company; a domain that cannot be assigned is left out.

Through visit qualification and lead scoring based on your rules: ICP fit (how well the company matches your ideal customer profile), product pages visited, visit frequency and whether someone comes back. If the company is on your target account list or there is already an opportunity, that is taken into account. You control include and exclude lists yourself.

Lead routing follows the account owner assignment in the CRM: if the account already exists, the lead goes to the person responsible; if there is an existing opportunity, to its owner. New companies go to sales according to your rules – with the pages visited as a conversation starter.

Not on its own. A page visit proves neither a specific person nor a definite need – it is one intent signal among several. That is why the flow works at company level, in account-based marketing as a pointer to target accounts, and respects your visitors' consent status.

That's exactly what the flow is built for. Every value it reads stays linked to the original document, and check rules match it against your ERP. Discrepancies, missing data or unclear matches create a task for the person responsible – with the document, the comparison and decision options. The case then continues right where it left off. Values that aren't in the document are never made up.

You decide: in the XFLOWLY Cloud on a dedicated virtual machine at Google Cloud in Frankfurt – or on your own server (on-premises) running Windows or Linux. Stored data is encrypted with AES-256, and credentials for your systems are additionally kept in a separate secret vault. You'll find all the details in the security factsheet on the platform page.

Easily: after a three-month minimum term, you can cancel XFLOWLY monthly with 14 days' notice. When your subscription ends, we provide a full export – documents, results and your flow definitions in machine-readable formats, available for 30 days at no extra cost. After that, your environment is deleted.