Collection

One event, collected properly, feeding everything else

A first-party pixel on your own domain, webhooks from any system, and native connectors for the tools you already run. Whatever comes in arrives standardized.

Create a free account Talk to the team

Your own domain

Collection goes to a subdomain you control. Ad blockers take down third-party domains, not yours.

No SDK per tool

One script on the site. No installing a separate pixel per destination and hoping they all fire.

Webhooks for the rest

Homegrown CRM, internal ERP, custom backend: send JSON and it becomes an event with identity already resolved.

Pixel

Install once, collect what matters

The pixel records page views, form submissions, clicks and any event you fire. It keeps a stable session identifier and rebuilds ad-click cookies in first-party context — which is what actually moves your match rate when you send conversions back.

Page views with URL, referrer, UTMs and click identifiers
Forms captured without changing where they already post
Custom events with free-form properties
Video progress on supported players
Ad identifiers rebuilt in first-party context

index.html

<script
  src="https://tag.yourdomain.com/tagPixel.min.js"
  data-project="your-project"
  async
></script>

<script>
  // Fire a custom event whenever you need one
  CrazyLeads.track('checkout_started', {
    product: 'Annual plan',
    value: 1997
  })
</script>

Webhook

Anything without a connector comes in through the front door

The contract is deliberately short: an event name, whatever identity fields you have, and a free-form data block. Whatever lands in that block becomes available for filtering, segmentation and field mapping — no fixed schema, no migration.

POST /webhooks/{your-key}

{
  "event": "crm.opportunity.won",
  "email": "maria@example.com",
  "phone": "+15551234567",
  "ussid": "a3f1...",
  "occurred_at": "2026-08-16T10:32:00Z",
  "data": {
    "product": "Coaching program",
    "pipeline": "Sales",
    "stage": "Closed won",
    "value": 1997,
    "rep": "Ana"
  }
}

Connectors

The sources you already use, syncing on their own

Meta Ads, Google Ads, ActiveCampaign, Zoom, Tally and Hotmart — the dominant checkout in the Brazilian market — have native connectors. Each source knows what is real time and what is history: the webhook delivers the sale in seconds, the sync recovers whatever was missed, and the platform recognizes that both describe the same thing instead of counting it twice.

Real-time webhooks wherever the source offers them
History sync with recovery of anything missed
Deduplication by business identity, not by arrival time
A debugger showing the real payload of every source

Data flow

Pixel
Hotmart
Meta Ads
Webhook
Tally
Zoom

CrazyLeads

identity resolved, event standardized

Meta CAPI
Google Ads
Webhook
BI
IA / MCP

Frequently asked questions

Do I have to remove my Meta and Google pixels?

No. They keep working. CrazyLeads collects in parallel and becomes the source you analyze from and send server-side conversions with — which is exactly where browser data gets lost.

How long does setup take?

The pixel is one script. The first connected source takes minutes. What usually takes time is deciding which events matter, and for that the platform shows you the real payload before you configure anything.

What if I already have a data warehouse?

The platform ships with its own analytical storage and a read API. You can query with SQL, export through the API, or push to your warehouse over webhook.

Keep exploring

Identity and timelineIdentity resolution stitches anonymous sessions, emails, phone numbers and documents into …Delivery and activationDeliveries push conversions back to Meta, Google and your own systems — with identity alre…

Start measuring what actually becomes revenue

Create a free account, connect your first source and see your first lead timeline today. No card required.

Create a free account Talk to the team