The whole customer data path, with BI already inside
CrazyLeads collects your events, works out who is behind every visit and hands the data back ready to use: a query, a dashboard, and the conversion delivered back to Meta and Google. CDP and BI in one product.
No card · Free tier with real data · Answers from the people who built it
- Pixel
- Hotmart
- Meta Ads
- Webhook
- Tally
- Zoom
CrazyLeads
identity resolved, event standardized
- Meta CAPI
- Google Ads
- Webhook
- BI
- IA / MCP
The problem
You do not have a traffic problem. You have a measurement problem.
Almost every team investing in media already has the data it needs. What is missing is having it in one place, tied to the same person.
The data lives in six places
Pixel in one tool, sales in another, email in a third, media in a fourth. Nobody can say where a sale came from without opening four tabs and a spreadsheet.
Conversions go back without value
The browser loses part of the events, and what does get through carries no revenue. The campaign learns from a biased sample and optimizes for the wrong person.
The report arrives too late
On cart day, yesterday’s number decides nothing. And every new question becomes a request to someone who is already busy.
The platform
Collect, unify, analyze and activate — without switching tools midway
Each step is usually a separate product, with a separate contract and a separate name for the same thing. Here it is one path.
Collect
A first-party pixel on your domain, webhooks and native connectors. One standardized event, not one pixel per tool.
- Pixel and forms
- Generic webhook
- Meta, Google, checkouts, Tally, Zoom
Unify
Today’s anonymous visit and the purchase two weeks later become the same person, with a timeline that explains the sale.
- Identity graph
- Timeline per lead
- Attribution through two paths
Analyze
SQL over raw data, dashboards and artifacts you publish behind a link. BI ships with it — the data does not have to leave.
- SQL queries
- Dashboards and artifacts
- A public link that refreshes
Activate
Conversions go back to Meta, Google and your own systems from the server, with resolved identity and a per-delivery audit.
- Meta CAPI and Google Ads
- Business-rule filtering
- Match quality measured
Identity
A person, not a session
Someone clicks the ad on their phone, fills the form on a laptop, watches the session on a tablet and buys ten days later. Without unified identity that is four visitors and zero explained sales.
- Anonymous session claimed by the lead the moment they identify
- Anonymous never merges into known — a shared device does not collapse into one person
- Merges recorded and reversible
- Events leave enriched: by the time they arrive, they know who the person is
ussid a3f1…9c
maria@…
+55 11 9…
HP28624…
Maria S. · identified · 23 events
Fixed rule: an anonymous session never merges into an already-identified lead just because they share a browser.
Activation
The sale goes back to the ad with its real value
The delivery leaves your server carrying email, phone, external identifier and ad cookies pulled from the identity graph — not from whatever happened to be in the payload. You filter by your own business rule and see an audit of every send.
- Filters built on the real payload, tested before publishing
- Approved sales separated from expired payments and renewals
- Match coverage measured on deliveries that actually went out
- A destination going down holds the delivery and reprocesses on reconnect
Checkout · purchase
status = APPROVEDAND product contains “Coaching”AND first purchase
✓ tested: 8 of 30 real events would pass
value ← price_value
em ← lead.email (100%)
ph ← lead.phone (97%)
Purchase delivered · 214 ms
Analysis
The new question does not have to become a ticket
Ad spend, checkout sales, survey answers and pixel events are all available as tables in the same query. And the result becomes a publishable page with live data behind it.
- PostgreSQL dialect, translated to the analytical engine
- Artifacts published behind a link, with a freshness badge
- Refresh triggered by visits, not by blind scheduling
- Or just ask the connected AI assistant in plain language
| Campaign | Spend | Revenue | Return |
|---|---|---|---|
| Retargeting – 7d | 4.110 | 29.350 | 7,1x |
| Remarketing – 30d | 18.240 | 71.980 | 3,9x |
| Topo / Top of funnel | 12.870 | 14.220 | 1,1x |
Ad spend and checkout revenue on the same row — no spreadsheets exported from two places.
What changes
The same operation, measured differently
Without CrazyLeads
With CrazyLeads
Browser pixel alone
Browser + server, deduplicated
Conversions with no value
Sales with the real order value
Loose anonymous sessions
A person with full history
Spreadsheets exported from 4 tools
One SQL query
A PDF report over email
A link showing the current number
A/B tests measured by clicks
Tests decided by revenue
Ask in plain language. Then let it do the work.
Connect Claude, ChatGPT or Cursor to your account. The assistant writes the SQL, shows the number and — when you ask — publishes the dashboard, sets up the experiment and configures the delivery, through the same validations as the interface.
See MCP in actionYou
Which campaigns spent over a thousand and returned less than 2x in the last 14 days?
Claude · via CrazyLeads
Three campaigns. The worst is Top of funnel: 12,870 spent and 1.1x return. The other two are at 1.6x and 1.8x.
Want me to publish this as a dashboard?
Integrations
Sources and destinations that already speak your business
Checkouts, Meta and Google on both sides, and a webhook for everything without a ready connector.
CrazyLeads Pixel
Source
First-party tracking for your site, on your own domain, with identity that survives ad blockers.
View integration
Hotmart
Source
Sales, subscriptions, abandoned carts and member area activity — in real time by webhook plus a history sync.
View integration
Meta Conversions API
Destination
Server-side conversions to Meta, with identity already resolved and no dependency on the browser.
View integrationMCP server (Claude, ChatGPT, Cursor)
Destination
Connect an AI assistant to your data, with scoped permission, and ask in plain language.
View integrationPricing
Start free and grow by volume, not by seat
Unlimited users on every plan. What changes is how much data comes in and what you can activate.
Free
R$ 0
To explore the platform with real data, no card required.
- Events per month
- 10k
- Connected sources
- 2
- History retention
- 90 days
Starter
R$ 297/mo
For teams already running traffic that need conversions back in Meta.
- Events per month
- 100k
- Connected sources
- 5
- Delivery destinations
- 2
Pro
Most popularR$ 897/mo
For launch operations and teams that live by the numbers.
- Events per month
- 1 million
- Connected sources
- 15
- Delivery destinations
- 5
Business
Custom
For high volume, multiple brands and contractual requirements.
- Events per month
- 10 million+
- Connected sources
- Unlimited
- History retention
- No limit
Isolation per project
Each project has its own space in storage. Not a filter on screen: data in one project is unreachable from another.
First-party data
Collection happens on behalf of your site, on your domain. You remain the controller of your audience’s data.
Outbound under your control
You decide what leaves in every delivery, and whatever should not travel is stripped before sending. Every delivery is audited.
More detail in security and privacy.
Frequently asked questions
Which of my tools does CrazyLeads replace?
Usually it replaces the spreadsheet layer and the improvised BI, and coexists with the rest. Your email tool, checkout and ad platforms stay where they are — CrazyLeads becomes the layer that connects them and sends conversions back.
How long until I see the first result?
The pixel and first source take minutes. The lead timeline appears as soon as the first events arrive. Conversion delivery to Meta is usually live the same day.
Do I need a data team?
Not to start. Dashboards and deliveries are configured in the interface. SQL helps with the new question — and for that there is the AI assistant over MCP, which writes the query and shows you the SQL to check.
Does it work with my checkout?
Yes. Hotmart has a native connector because it dominates the Brazilian creator market, but any checkout or system comes in through the webhook, with the same identity resolution and activation.
What if I already use Segment or RudderStack?
They can coexist over webhook. In practice, teams that already have a CDP come here for the built-in BI and the cost — worth reading the comparison before deciding.
Is the data mine?
It is. You export through the API, deliver over webhook and query with SQL at any time. There is no closed format holding your history inside the platform.
Start measuring what actually becomes revenue
Create a free account, connect your first source and see your first lead timeline today. No card required.