Crisper8 min read11 views

What your developer does to set up Crisper on a custom site

The setup work on a custom-built site: DNS records, two snippets in the site's code, Lead and Purchase events after success, and the checks that prove it.

The short answer

On a custom-built site your developer adds the DNS records, pastes two snippets into the site's code, sends Lead and Purchase after a form or payment succeeds, and opens the health link. Page views and contact clicks need no code. Records and snippets take about 5 minutes with access; the events depend on your form and checkout code.

  • DNS: usually two CNAME records on your tracking subdomain, ctx and load.ctx, set to DNS only.
  • Snippets: the head script high in <head> and the body script after <body>, on every page, in the site's code.
  • Events: generate_lead_crisper for your own forms and purchase_crisper for paid orders, once per action.
  • Events show in Events Manager within about 30 minutes once tracking is installed and firing.
  • Checked against Crisper's setup code and the live tracking container on 6 November 2026.

Ask an assistant

ChatGPTClaudePerplexity

FREE AUDIT

NO LOGIN

Check what Meta and Google can count on your site

  1. Your site
  2. Crisper
  3. Meta and Google count it

Enter your website to see how good its tracking is, and whether Meta is likely restricting it.

Run a free audit

Send this page to whoever builds or manages your website. It lists the whole job, so they can size it before the setup call. On Shopify, WordPress and similar site builders the setup call covers it instead; this page is for sites built in-house or by an agency.

Who does what during setup?

The site owner approves the changes and connects Meta; the developer changes DNS and the site's code.

  • Site owner: Approve the DNS and website changes below. Arrange access for whoever will make them. After installation, confirm the first event in your Crisper dashboard.
  • Developer: add the DNS records, paste the two snippets and add the Lead and Purchase events described below.
  • Connecting Meta: the owner does it with the founder on the setup call. The developer doesn't need Meta access.

Have this access ready before the call:

  • The DNS login, wherever the domain's DNS is managed
  • Full control (formerly Admin) on the Facebook Business Manager
  • The website's CMS or back-end login, where the tracking goes in

Your site's exact records, snippets and health link appear in your Crisper dashboard after you sign up and add the tracking subdomain. Open the site's Domain page, choose Share instructions, then Copy as text or Download PDF, and send that with this page. The button stays unavailable until Crisper has created the records for your tracking subdomain. Until then, your developer can use this page to size the work.

What changes in DNS?

Add every record your instructions show, usually two CNAME records on a tracking subdomain. Your website and email records stay as they are. The tracking subdomain is ctx. in front of your domain unless your instructions name another.

CNAME

Name
ctx
Value
Copy it from your instructions
Cloudflare / CDN
Off (DNS only)

CNAME

Name
load.ctx
Value
Copy it from your instructions
Cloudflare / CDN
Off (DNS only)
Default names. Your instructions list the exact records for your site; add every one of them.

If your domain uses Cloudflare, set each record to DNS only, the grey cloud. Cloudflare explains DNS-only recordsdevelopers.cloudflare.com. Other providers may have a CDN setting on the record; turn it off.

Type

What to do
Choose CNAME, not A, TXT or ALIAS.

Name

What to do
Paste the name exactly as copied.

Name doubled

What to do
If your domain appears twice in the saved name, remove the extra part.

Cloudflare / CDN

What to do
Cloudflare turns its orange cloud on for new records. Click it so it turns grey and says DNS only. With another provider, turn off any CDN setting on the record.

Old records

What to do
Before deleting a DNS record with the same name, check whether anything uses it. If it does, leave it in place and discuss it on the setup call.

Wrong DNS provider

What to do
Records only count where your domain’s nameservers point. Check which provider that is.

Still propagating

What to do
Most changes show within 30 minutes; a few providers take a few hours.
The same checks your Crisper dashboard shows when a record doesn't verify.

If the records verify but the certificate doesn't, check for CAA records on your domain. A CAA record limits which authorities can issue certificates for it, so ask whoever manages your DNS to remove it or allow the issuer.

Where do the two snippets go?

Both snippets go in the site's source code or page templates, on every page. Don't load them through a tag manager.

  • Head script: Paste as high in <head> as you can, on every page.
  • Body script: Paste right after the opening <body> tag.

A shared layout or base template is usually the right place, so new pages get both snippets automatically. Pages that skip the layout, such as a separate checkout or thank-you page, need them too.

Which events does the developer send?

Only the conversions the snippets can't see: your own lead forms and your payment flow. Each one is a single data layer push after the action succeeds.

Your own lead form is accepted

Push this event
generate_lead_crisper
Meta sees
Lead

An order is paid

Push this event
purchase_crisper
Meta sees
Purchase
Other standard events use the same pattern; the custom-events guide lists them.
  • Push after the server confirms success, not when the button is clicked.
  • Send each order once, with a stable ecommerce.transaction_id. A refresh or the Back button must not send it again. Google's ecommerce guidedevelopers.google.com uses the same field.
  • Include the customer's email and phone in user_data, and value and currency on a purchase.

The exact code, field list and a prompt for a coding agent are in the custom events guide, with the order fields under ecommerce objects. This page doesn't repeat them, so there is one version to follow.

What is already tracked without code?

Page views and clicks on phone, email and WhatsApp links are tracked on every page. Embedded GoHighLevel, Typeform, Calendly and ClickFunnels forms are picked up in their usual setups: Typeform when it sends people to a thank-you page on your site, Calendly when the booking returns to your site with its confirmation. Submit one test and check it in Crisper Logs before you skip code for it. In Logs, Typeform shows as Submit Application and Calendly as a schedule event. Don't push events for these, or they count twice.

How do you check that it works?

Check three things in order: the tracking server answers, a test action reaches Crisper, and Meta receives it.

  1. Open the health link from your instructions, by default https://ctx.<your domain>/healthy. A page showing "OK" means the tracking server is reachable over HTTPS. It doesn't prove events are flowing.
  2. Submit one test lead or place one test order, then have the owner find it in Crisper Logs for the site. It can take up to 20 minutes to appear.
  3. Confirm it in Meta with the verification checklist. Events show in Events Manager within about 30 minutes once tracking is installed and firing.

What mistakes slow setup down?

Cloudflare record left orange

What happens
The record is hidden and the certificate is blocked.
Fix
Set it to DNS only, the grey cloud.

An A, TXT or ALIAS record

What happens
The subdomain never verifies.
Fix
Choose CNAME.

Snippets only on the homepage

What happens
Checkout and thank-you pages send nothing.
Fix
Add both snippets to the shared layout.

Snippets loaded through a tag manager

What happens
Setup isn't supported that way.
Fix
Paste both into the site's code.

Event pushed on button click

What happens
Failed or abandoned forms count as leads.
Fix
Push after the server confirms success.

Purchase sent again on refresh

What happens
One order counts twice.
Fix
Send each transaction_id once.
Most delays come from DNS settings and from events fired at the wrong moment.

Who is this developer checklist for?

On a custom-built site, your developer needs to add the tracking code and send events from your own forms and checkout. The new checklist puts the whole job on one page you can forward before your setup call.

What does your developer need to do?

Where to find it: Guides → Crisper → What your developer does to set up Crisper on a custom site

The checklist separates the site owner’s work from the developer’s. It covers the DNS records, where both snippets go, sending Lead after a successful form and Purchase after a paid order, and checking the health link and Events Manager. The FAQ now points custom-site owners to this guide.

When to use it: When you want your developer to size the setup work or prepare for your call.

Fig. 1Sample data: the published developer checklist, showing who does what and the setup steps.

Setup depends on your site

Our team does the setup. Tracking is live within 24 hours of full access. The time needed for custom forms and payments depends on your code. Shopify, WordPress and similar site builders usually do not need a developer.

Read next

Why set up Crisper on a custom-built site?

When Meta restricts a domain's data sharing, Lead and Purchase events stop being usable, and ad sets lose the signal they learn from. Crisper gets those events counting again on the domain you already have. On a custom-built site, the work above is the whole job: records, two snippets and two events.

What changed in this guide

  • 15 November 2026: The page now books a free call; our team does the setup.
  • 12 November 2026: Updated sections to how the product works today and corrected details that were wrong when they shipped.
  • 7 November 2026: Added the section that used to be this checklist's changelog page.

Sources

2 sources
  1. 1Cloudflare explains DNS-only records↩
  2. 2Google's ecommerce guide↩