Introduction
Per-publisher conversion tracking and attribution. A single tag on the advertiser's site measures the conversion and attributes it to the exact source of the click.
Tag ≈7 KB gzip
Zero dependencies
First-party cookies
Tracking layer
One tag, many campaigns#
The same tag serves every campaign the advertiser runs. Configuration lives in the Moclick dashboard — changing how a campaign behaves never requires touching the code installed on the site.Media layer
Premium inventory#
Access to sites and apps selected for qualified audience and brand-safe context, at a fixed cost per click or per acquisition agreed before the campaign goes live.What the integration asks of the advertiser#
Two things, and only two. Everything else is configuration in the Moclick dashboard and never touches the client’s code.-
The global tag, on every page
One<script>withdeferin the<head>. It loads the campaign configuration and captures whatever click identifiers arrive in the URL. -
The conversion object, on the confirmation page
window.MoclickConversionwith the value and the order identifier. From there on, measurement is automatic.
Click tracking is automaticThe platform’s tracking links already deliver the visitor with the right parameters
in the URL. The client’s site does not have to generate, propagate or persist
anything by hand, the global tag does it.
Why it is built this way#
Attribution down to the source site#
You see performance per individual publisher, not per aggregated block. That lets you cut unproductive inventory on real data instead of an estimate.Fixed, negotiated cost#
CPC or CPA agreed before the campaign runs, with no auction swings. You model ROI with the number you will actually pay.One integration for everything#
A single tracking setup for the entire inventory. No separate pixel per publisher and no manual reconciliation between attribution platforms.Fixes reach visitors in 5 minutes#
The tag is served withmax-age=300, must-revalidate. A fix reaches every
visitor within five minutes, with nothing to ask of the client — and with no risk of an
old version stuck in a CDN cache.