For advertisers

Install the AdFrolic tag

One snippet on your website confirms a click actually landed, and lets you report conversions back to AdFrolic. A campaign cannot go live until AdFrolic can verify the tag is present on its destination page.

What the tag does

The AdFrolic tag is a small, universal script. It has no per-account or per-campaign configuration — the same snippet works for every campaign in your account. Once installed on a page, it:

Confirms that a visitor who clicked an AdFrolic ad actually reached your page.
Lets you report a conversion (a signup, purchase, or other outcome) from that page, or any later page.

It never collects browsing history, never sets third-party cookies, and never learns anything about the developer who clicked the ad beyond the single click that brought them to your site.

Install the tag

Paste this immediately before the closing </head> tag on every page you want it to run on — at minimum, your ad's destination page.

HTML

<script src="https://adfrolic.com/tag/v1.js"></script>

If your site is built with a framework that has a single shared layout or root document (Next.jsapp/layout.tsx, a WordPress theme header, a Shopify theme.liquid, etc.), add it there once so it covers every page automatically.

Verify it's installed

Near the end of the campaign-creation flow, after your ad clears moderation, you'll be shown the snippet above and a Verify now button. Clicking it makes AdFrolic fetch your destination page and check for the tag.

If the tag is found, your campaign goes live immediately.
If it isn't found yet, you can install it and click Verify now again, or choose to finish setup later — the rest of the campaign (creative and landing-page moderation) stays approved, but it will not serve any ads until the tag is confirmed.

You can come back to finish installing and verifying at any time from the Advertiser tag page in your portal, which also shows an ongoing tag status per campaign — AdFrolic periodically re-checks it as a best-effort signal, not proof, since a page that blocks automated browsers can fail an automated check while working fine for real visitors.

Report conversions

Call window.adfrolic.trackConversion(name) from the page that represents your conversion event — for example, a signup confirmation or purchase receipt page.

JavaScript

window.adfrolic.trackConversion("signup");

You can optionally include a value and currency, for example on a purchase:

JavaScript

window.adfrolic.trackConversion("purchase", { value: 49.99, currency: "GBP" });

Prefer not to run client-side JavaScript for conversions? A server-side Conversion API is available for advertisers who want to report conversions directly from their own backend instead — contact support for details.

Settings

There is nothing to configure on the tag itself — no account ID, no campaign ID, no API key. It reads the click identifier AdFrolic's own redirect already attached to the URL when the visitor arrived.

The only things that affect its behaviour are on your side:

The tag must load on the exact destination URL(s) your campaign points to (including any pages a visitor is redirected through) for the automated check to detect it.
Content security policies (CSP) that restrict script-src must allow scripts from https://adfrolic.com.
Single-page apps that render the <head> client-side should ensure the tag is present in the initial HTML response, since the verification check does not execute JavaScript.

Troubleshooting

Verify now says it can't find the tag, but I've installed it. Confirm the exact URL AdFrolic is checking matches where the tag is installed — check for redirects (e.g. a bare domain redirecting to www., or HTTP redirecting to HTTPS) and make sure the tag is present on the final page, not just an intermediate one.
My page blocks automated browsers or bots. The verification check needs to be able to fetch your page like a normal visitor would. If your site blocks unfamiliar user agents entirely, allow requests that fetch the page's HTML.
I installed the tag after my campaign was approved. Go to the campaign in your portal and click Verify now again — a campaign that finishes moderation without a confirmed tag stays paused (not rejected) until you verify it.
Does the tag slow my site down? It is a small, asynchronously-loaded script with no dependencies.

What the tag does

The AdFrolic tag is a small, universal script. It has no per-account or per-campaign configuration — the same snippet works for every campaign in your account. Once installed on a page, it:

Confirms that a visitor who clicked an AdFrolic ad actually reached your page.
Lets you report a conversion (a signup, purchase, or other outcome) from that page, or any later page.

It never collects browsing history, never sets third-party cookies, and never learns anything about the developer who clicked the ad beyond the single click that brought them to your site.

Install the tag

Paste this immediately before the closing </head> tag on every page you want it to run on — at minimum, your ad's destination page.

HTML

<script src="https://adfrolic.com/tag/v1.js"></script>

Verify it's installed

If the tag is found, your campaign goes live immediately.
If it isn't found yet, you can install it and click Verify now again, or choose to finish setup later — the rest of the campaign (creative and landing-page moderation) stays approved, but it will not serve any ads until the tag is confirmed.

Report conversions

Call window.adfrolic.trackConversion(name) from the page that represents your conversion event — for example, a signup confirmation or purchase receipt page.

JavaScript

window.adfrolic.trackConversion("signup");

You can optionally include a value and currency, for example on a purchase:

JavaScript

window.adfrolic.trackConversion("purchase", { value: 49.99, currency: "GBP" });

Settings

The only things that affect its behaviour are on your side:

The tag must load on the exact destination URL(s) your campaign points to (including any pages a visitor is redirected through) for the automated check to detect it.
Content security policies (CSP) that restrict script-src must allow scripts from https://adfrolic.com.
Single-page apps that render the <head> client-side should ensure the tag is present in the initial HTML response, since the verification check does not execute JavaScript.

Troubleshooting

Verify now says it can't find the tag, but I've installed it. Confirm the exact URL AdFrolic is checking matches where the tag is installed — check for redirects (e.g. a bare domain redirecting to www., or HTTP redirecting to HTTPS) and make sure the tag is present on the final page, not just an intermediate one.
My page blocks automated browsers or bots. The verification check needs to be able to fetch your page like a normal visitor would. If your site blocks unfamiliar user agents entirely, allow requests that fetch the page's HTML.
I installed the tag after my campaign was approved. Go to the campaign in your portal and click Verify now again — a campaign that finishes moderation without a confirmed tag stays paused (not rejected) until you verify it.
Does the tag slow my site down? It is a small, asynchronously-loaded script with no dependencies.