for lead generation
Optimize on leads, not page views.
Send Calendly bookings and Typeform submissions to Meta, Google Ads, GA4 and TikTok server-side, matched to the ad click, so campaigns optimize on real leads.
the problem
What goes wrong today.
The conversion happens somewhere else.
A booking is confirmed on Calendly's page, a form is submitted on Typeform's. Your pixel never sees it.
Thank-you page tracking leaks.
Visitors close the tab, blockers stop the pixel, or the redirect never happens. Every miss teaches the ad platform the wrong audience.
Lead counts don't match the ad account.
Your CRM shows one number, the ad platform another, and there's no way to tell which is broken.
with tracerkit
How it fits.
Conversion webhooks, no code.
Point Calendly or Typeform at a TracerKit webhook. Zapier, Make and n8n cover any other form or CRM.
Matched to the ad click.
TracerKit joins the lead to the visitor's landing visit by hashed email or visitor id, so the click ids from that visit travel with the conversion.
Forwarded server-side.
Each lead reaches the Meta Conversions API, Google Ads, GA4 or TikTok from TracerKit's servers, with email and phone hashed before storage.
where to go next
questions
Asked and answered.
Which form and booking tools work?+
Calendly and Typeform have native presets. Anything that can send a webhook through Zapier, Make or n8n works through the generic webhook.
Do I still need the pixel?+
Keep it for page views and click ids. The server-side event shares an event id with the pixel where both fire, so platforms that dedupe count one lead.
What does it cost?+
Server-side forwarding is the Server-side tier, $149 a month per site, flat, with no per-lead metering.
tracerkit for
Stop guessing whether your tracking works.
Tag management is free forever. Paid tiers start with a 14-day trial, no card.