Confirm the snippet is live on your site

Open your published site (not a draft or preview), view the page source, and check that the Admaxxer snippet is present inside the . If you edited a theme or template, make sure you saved and published the change so it's on the live URL your visitors actually load.

Test in an incognito / private window

This is the most common reason a brand-new install looks dead. Ad-blockers and privacy extensions (uBlock Origin, AdGuard, Brave Shields, Ghostery) block analytics requests, so when you visit your own site to test, your event never gets sent. Open a clean incognito or private window with no extensions, visit a page, and check again. If events appear there, your install is working perfectly — real visitors without blockers are being tracked.

Give the first event a minute or two

The very first pageview can take a couple of minutes to appear while your site is registered. Visit a page, wait 1–2 minutes, then refresh your dashboard before assuming something is wrong.

Make sure the right website is selected

If you manage more than one site, double-check that the dashboard is showing the same website whose snippet you installed — and that the snippet's website ID matches it. Events for one site won't show up while you're viewing a different one.

First-party (CNAME) setup is optional

You do not need a custom subdomain or any DNS change to start collecting events — the standard snippet works out of the box on any domain. First-party setup is a purely optional upgrade that improves resilience against ad-blockers for a slice of privacy-heavy traffic. Skip it while you get started; add it later if you want maximum coverage.

Install Admaxxer — 36 Platform Guides | Admaxxer AI Analytics Docs

Install Admaxxer

Pick your platform. Every guide has a copy-paste snippet, the right place in that platform's UI to paste it, and a verification step so you can confirm events are flowing before you leave the page.

The pixel works on any domain. Paste the snippet into your site's <head> and you're done — there is no DNS change, no first-party subdomain, and no CNAME setup required to start collecting events. First-party setup is an optional upgrade you can add later.

E-commerce

Shopify Custom Pixel via Customer events — 5-min install. ~5 min

WooCommerce WP plugin — revenue automatic. ~4 min

BigCommerce Script Manager → Head → All Pages. ~3 min

Stripe Paste a restricted key (rk_*). ~3 min

Paddle API key + transaction.completed webhook. ~3 min

Lemon Squeezy API key + order_created webhook. ~3 min

Polar API token + order.created webhook. ~3 min

Frameworks

NPM Package Install via npm for bundled frameworks. ~3 min
Next.js npm install @admaxxer/pixel — call initPixel() in layout. ~3 min
Nuxt Register a .client.ts plugin. ~3 min
React (Vite / CRA) Call initPixel() in main.tsx. ~2 min
Vue Call initPixel() in main.ts. ~2 min
Gatsby onClientEntry in gatsby-browser. ~3 min
Astro Drop into src/layouts/Layout.astro. ~2 min
React Router Call in root.tsx (v7 / Remix). ~3 min
React Native / Expo Mobile apps: track via the API (the pixel is browser-only). ~3 min
Django Drop into templates/base.html. ~2 min
Laravel Drop into app.blade.php. ~2 min

No-code builders

Webflow Project Settings → Custom Code → Head. ~2 min
Framer Settings → Custom Code. ~2 min
Wix Settings → Custom Code → Head. ~3 min
Squarespace Advanced → Code Injection → Header. ~2 min
Carrd Embed → Type=Code, Style=Head. ~2 min
Bubble Settings → SEO/metatags → Header. ~2 min
Notion (via Super/Potion) Via Super, Potion, or Feather. ~3 min
Podia Site Settings → Code → Head. ~3 min
Kajabi Site Details → Head Scripts. ~3 min
Lovable Ask the AI to paste the snippet. ~2 min
Vercel v0 Ask v0 to patch layout.tsx. ~2 min
Replit Paste into index.html or ask Agent. ~2 min
Bolt Ask Bolt to inject the snippet. ~2 min

Not seeing events yet?

Fresh installs almost always come down to one of these five things. Work top to bottom.

Confirm the snippet is live on your site

Open your published site (not a draft or preview), view the page source, and check that the Admaxxer snippet is present inside the <head>. If you edited a theme or template, make sure you saved and published the change so it's on the live URL your visitors actually load.
Test in an incognito / private window

This is the most common reason a brand-new install looks dead. Ad-blockers and privacy extensions (uBlock Origin, AdGuard, Brave Shields, Ghostery) block analytics requests, so when you visit your own site to test, your event never gets sent. Open a clean incognito or private window with no extensions, visit a page, and check again. If events appear there, your install is working perfectly — real visitors without blockers are being tracked.
Give the first event a minute or two

The very first pageview can take a couple of minutes to appear while your site is registered. Visit a page, wait 1–2 minutes, then refresh your dashboard before assuming something is wrong.
Make sure the right website is selected

If you manage more than one site, double-check that the dashboard is showing the same website whose snippet you installed — and that the snippet's website ID matches it. Events for one site won't show up while you're viewing a different one.
First-party (CNAME) setup is optional

You do not need a custom subdomain or any DNS change to start collecting events — the standard snippet works out of the box on any domain. First-party setup is a purely optional upgrade that improves resilience against ad-blockers for a slice of privacy-heavy traffic. Skip it while you get started; add it later if you want maximum coverage.

Still stuck after all five? Send us your site URL from Support and we'll confirm the snippet is loading and events are reaching your dashboard.