RedTrack Tracking Platform.

1. 1Ad click
2. 2Capture in the browser
3. 3Checkout with origin
4. 4Webhook: validate, classify, store
5. 5Server-to-server postback
6. 6Conversions API

1. 1RedTrack

   Ad click

   The RedTrack tracking domain records the click and generates a 24-character click id.

   Hands overclick id in the URL
2. 2This projectRedTrack

   Capture in the browser

   Own script reads the click id (query and cookies), fires InitiateCheckout and video milestones (play, 1, 3, 5 and 10 min) with deduplication. A network failure never blocks the checkout.

   Hands overevents + checkout click id
3. 3Checkout

   Checkout with origin

   The click id travels in the checkout platform origin parameters up to the purchase. Hotmart is the integration that is ready today.

   Hands oversale webhook with the click id
4. 4This project

   Webhook: validate, classify, store

   Token compared in constant time, schema validated with Zod, personal data redacted, event classified and stored idempotently before anything is sent.

   Hands overclassified event
5. 5This projectRedTrack

   Server-to-server postback

   Conversion sent to RedTrack with value, type and transaction id. Timeout, network errors, 429 and 5xx go to retry with exponential backoff. 4xx errors are not retried.

   Hands overconversion attributed to the click
6. 6RedTrackMeta

   Conversions API

   RedTrack forwards the event to Meta. Purchase, order bump and upsell arrive as distinct purchases, one per transaction, without one erasing another in deduplication.

Retry in detail: by default up to 3 attempts per send, an 8 second timeout and a wait that doubles from 500 ms. Only timeouts or network errors, 429 and 5xx are retried. If the send fails, the webhook answers 502; when the checkout platform redelivers the same event, the send is redone on the same row, without duplicating.

• 01

  Webhook, idempotency and classification

  A duplicate is never stored twice, approval and refund of one transaction are two rows, a renewal never reaches RedTrack, 5xx is retried and 4xx is not.

• 02

  Offer mapping

  CRUD with expected version, audit, Postgres and SQLite drivers, a snapshot that refuses invalid rows and a boot that aborts if the database is unreachable.

• 03

  Panel and authentication

  Rate-limited login, expired sessions, CSRF required on mutations, security headers and pages that never contain the token.

• 04

  Recurrence enrichment

  Lookup only after the response, a merge that only fills blanks, conflicts without overwriting and sending blocked while recurrence is pending.

• 05

  Finance and reconciliation

  Fixtures kept out of real finance and a reversal without the original sale leaving net null.

• 06

  Unknown offer and reprocessing

  No mapping returns 409, reprocessing twice sends once, a sent event is never reinterpreted and the preview changes nothing.

• 07

  Browser scripts

  A double click does not duplicate the send, each video milestone fires once and a failure or timeout still leads to checkout.

• 08

  Infra and integrations

  Postgres transactions, a readiness check that answers 503 without leaking driver errors, and the suggestion model client.

Security, item by item

Webhook

Token compared in constant time. In production without a configured token, it answers 503 instead of accepting. Events outside the allowlist are ignored.

Personal data

Buyer name, email, phone, document and address are redacted before storage. Logs use a field allowlist and the panel never returns the payload.

Panel session

HttpOnly, SameSite cookie valid for 12 hours that never carries the admin token. A per-session CSRF token on every mutation.

Rate limit

60 requests per minute per IP on admin and 10 login attempts every 5 minutes. Without a token in production, the panel answers 503 and never opens.

Headers

CSP restricted to the same origin, no framing, nosniff, no-referrer and no-store on every admin response.

Public surface

An opaque 404 that does not echo the route, and a readiness check that does not expose error text. Secrets live only in environment variables.

How it works

1. 1

   Call and review

   Page, VSL, checkout, offers, order bumps and upsells, traffic sources and whatever pixel and Conversions API setup already exists.

2. 2

   Event map

   For every event in your funnel: whether it exists, whether it counts in finance, whether it goes to RedTrack and to Meta. Only with your confirmation or a real payload.

3. 3

   Minimum access

   Invites in the official panels, always with the lowest permission needed. No password or token over chat.

4. 4

   Setup with a way back

   Tracking domain, webhook, offers and the page script. DNS or webhook changes only with the exact record confirmed and the rollback defined beforehand.

5. 5

   Test purchase

   A real test purchase goes through the whole funnel. It only goes live after every point below is checked.

6. 6

   Maintenance

   Monitoring the panel and adjusting as the funnel changes.

Stack

• Node.js
• TypeScript
• Fastify
• Zod
• PostgreSQL
• SQLite
• Vitest
• Render
• RedTrack
• Meta CAPI
• Hotmart API