Website Intelligence
Crawl every page, then watch the things that quietly cost you traffic: SSL expiry, indexability, response latency, and which pages are actually carrying the tracking snippet.
Identity-first marketing intelligenceEvery touchpoint,
Every touchpoint,
resolved to one person.
Your funnel is scattered across ad platforms, forms, WhatsApp threads and call logs — and none of them know they are describing the same human. Demril unifies identity across every channel, attributes the revenue, and syncs it into the CRM your team already uses.
Multi-tenant by design — every customer's data in its own isolated database.
Fragmented signalsOne person
8
channels unified
web, mobile, server, ads, WhatsApp, phone, email, offline
1 DB
per customer
tenant data is isolated at the database level, not by a WHERE clause
2-way
CRM sync
source, campaign and score written back onto the Zoho record
The problem
Six tools each hold a fragment of the same customer
Google Ads knows a click happened. Your form knows an email arrived. WhatsApp knows a conversation started. The CRM knows a deal closed. None of them know it was one person — so the campaign that actually produced the revenue gets credited to whatever touched them last, and the report everyone plans against is quietly wrong.
The platform
Nine modules, one identity graph
Each one is useful alone. Together they share a single resolved person, which is what makes the numbers agree with each other.
Events
One ingest pipeline for every channel — web, mobile, server, WhatsApp, phone, ads. Client SDK or server-to-server, deduplicated on arrival, queryable the moment it lands.
People
Identity resolution. An anonymous visitor, a form fill, a WhatsApp thread and a phone call collapse into one person — across devices, sessions and channels.
Forms
Build a form, or auto-capture the ones already on your site. Either way the submission arrives attached to a resolved person, not an orphan row.
Lead Scoring
Score the person, not the pageview. Behaviour, source quality and channel depth combine into one number your sales team can sort by.
CRM Sync
Two-way Zoho sync. Leads and contacts flow in, and first-touch source, campaign and lead score are written back onto the record your reps already live in.
Ad & Search
Google and Meta spend next to the leads it produced. Cost per lead per campaign — the one number the ad platforms can never show you, because they don't know who your leads are.
Pop-ups
Rule-driven pop-ups with a real funnel behind each one — shown, engaged, submitted — so you can tell a winner from a nuisance.
Warehouse
Your data stays yours and stays queryable — modelled tables, a schema score, and row counts you can point a BI tool at.
How it works
From anonymous click to a name your team can call
- 01
Capture
One snippet on the site, an SDK in the app, or a server-to-server call. Page views, form submissions, ad clicks, WhatsApp messages and call outcomes all land in the same event stream.
- 02
Resolve
Identifiers are matched into a single person — email, phone, click id, anonymous cookie. Weak signals are kept as weak links rather than merged on a guess.
- 03
Attribute & score
First touch is pinned to the person, not the session, so the campaign that actually started the relationship survives every later visit. Scoring runs on top of it.
- 04
Sync
The resolved person, their source and their score are pushed into Zoho, so the team selling never has to open a second tool to see where someone came from.
Integrations
Connects to what you already run
Demril reads from the tools you have rather than asking you to replace them — and writes back only where it earns its place.
Zoho CRMtwo-way sync
Google Adsspend + click ids
Meta Adsspend + lead ads
WhatsAppinbox + delivery
Instagramlead ads
WordPresssnippet + pages
Bland AIcall outcomes
ApolloB2B enrichment
RudderStackevent ingest
n8nautomation
Claude / MCPask your data
Webhooksanything else
Architecture
Built so the numbers still agree at scale
Most analytics stacks are fast until they are real. Demril's constraints are the boring ones that decide whether you can trust the dashboard in year two.
A database per customer
Tenant isolation is physical, not a WHERE clause someone can forget. A bug in one tenant's query cannot reach another tenant's rows.
Bounded by design
Every dashboard figure carries a date window and a row bound, so a query that is fast on day one is still fast at ten million events.
Unattributable stays unattributable
When a lead genuinely cannot be traced to a campaign, it is shown as unattributed rather than smeared across the ones that can. Spend gets compared against an invoice.
Ask it in plain language
An MCP endpoint lets Claude query your own marketing data directly — no export, no BI seat, no waiting on an analyst.
See your funnel as one person at a time
We will connect one site and one ad account, and show you the leads each campaign actually produced — with your own data, not a demo tenant.