Install reference · ~3 minute read

Pro tracking — auto-capture clicks, downloads, 404s and form submits

Pro tracking is a one-toggle upgrade to the Admaxxer pixel. Enable it from the dashboard install panel and the snippet’s src URL swaps from /js/script.js to /js/script.plus.js — a strict superset of the default bundle that auto-fires five reserved goals for the UX-friction signals every DTC operator wants but rarely takes the time to instrument by hand.

What script.plus.js adds

The Pro bundle is the default bundle plus a thin layer of DOM event listeners that watch for five UX patterns and fire a corresponding goal event automatically. Goal names all share the reserved __admx_ prefix so they can’t collide with your custom goals (and so the dashboard knows to surface them under a dedicated “Auto-tracked” section).

The five goals:

Goal name Label What fires it
__admx_outbound Outbound link clicks Captures clicks on cross-origin <a href=...> links.
__admx_download File downloads Captures clicks on links pointing to downloadable file types (pdf, zip, mp4, csv, …).
__admx_404 404 page views Fires when the page title starts with '404' or carries <meta name="admx-404">.
__admx_form Form submits Captures every <form> submit event on the page.
__admx_rage Rage clicks Fires when 3+ clicks land within 500ms inside a 50px radius — a frustration signal.

Why a reserved namespace? Locking the __admx_ prefix to the runtime means future Admaxxer reports can rely on these names existing across every Pro-enabled site. If you tried to fire __admx_outbound from your own code with a different definition, attribution-quality dashboards would show contradictory numbers across customers. The API layer rejects custom goal events that start with __admx_ for that reason.

How to enable Pro tracking

  1. Open the install panel. Sign in to the Admaxxer dashboard and navigate to Connections → Pixel install.
  2. Toggle Pro tracking at the top of the snippet card. The snippet preview updates immediately — the src= URL changes from /js/script.js to /js/script.plus.js. No other change is required.
  3. Re-paste the snippet on your site (or, if you’re on Shopify Custom Pixel, re-Save and re-Connect from Customer events with the updated snippet body).
  4. Verify in Goals. The five __admx_* reserved goals show up automatically — no manual goal creation needed. Within ~5–30 seconds of real-visitor activity, you should see counts ticking up next to each one.

Querying these goals in the dashboard

The auto-tracked goals are normal goal events for every other purpose — you can chart them, set up alerts, build funnels, segment by source, and feed them into the Claude AI agent. A few starting examples:

Top outbound destinations this week
Open Goals → __admx_outbound and group by the href property — you’ll see exactly which external links your visitors clicked, sorted by volume.
Most-downloaded files
Open Goals → __admx_download and group by filename or file extension. Useful for catalog PDFs, white papers, and lead magnets.
Pages with the highest 404 rate
Build a Funnel report on __admx_404 → bounce — or just sort the goal table by URL desc to find broken-link patterns from a recent migration.
Form-abandonment vs form-completion
Pair __admx_form with your custom thank-you-page-viewed goal in a Funnel chart — the gap is your form-abandonment rate.
Rage-click hotspots
Open Goals → __admx_rage and group by URL. Pages with disproportionately high rage-click counts are usually the broken-button or slow-checkout candidates worth investigating first.

FAQ

Will enabling Pro tracking break my existing pixel install?
No. The Pro bundle is a strict superset of the default bundle — every event the default pixel fires, the Pro bundle also fires. Your existing pageviews, sessions, and custom goals continue to work unchanged.
How big is script.plus.js compared to script.js?
Approximately 3.2 KB gzipped versus 2.0 KB for the default — a 1.2 KB delta for the five auto-fired goal listeners.
Can I customize what counts as a rage click or download?
The thresholds are fixed in the runtime — rage = 3+ clicks within 500ms inside a 50px radius; download = links pointing to common downloadable extensions (pdf, zip, mp4, csv, etc.). If you need custom thresholds, fire your own goal events via the public pixel API (admx.event(name)) instead of relying on the auto-fires.
Do the __admx_* goals count against my tracked-events quota?
Yes. They are normal goal events sent to /api/event and counted the same way. If you want the auto-detection but not the quota cost, swap to the default script.js bundle and only fire your own custom goals.
Are the __admx_* goal names reserved?
Yes. The __admx_ prefix is reserved by the Admaxxer pixel. Custom goals you fire from your own code with a name starting with __admx_ will be rejected at the API layer to prevent collisions.
Can I combine Pro tracking with cookieless mode?
Not in a single bundle today — script.plus.js is the cookie-based variant. If you need both, dual-deploy: script.cookieless.js on EU/UK traffic for compliance and script.plus.js on the rest. Detect the visitor’s region server-side and emit the appropriate snippet.

Install hub (all platforms) · Script variants table · Cookieless mode · Shopify Custom Pixel architecture · Documentation home