cloakingx@guard:~
man cloaking-x.integrations.binomIntegration Guide

Binom

A landing-page-level integration — Binom has no drop-in filter/module API for external services, so this file owns the pass/block decision and serves your money/safe page, exactly like Binom's own documented Traffic Armor integration does for its equivalent Fail URL script.

Note
Why this isn't a native filter like KeitaroBinom's only native third-party filter is Adspect, and it's a locally-installed engine bundled with the Binom tracker itself (see docs.binom.org/adspect.php and docs.adspect.ai/en/latest/binom.html) — not something an external API-based service can replicate. Binom's own documented pattern for a service like Cloaking X is landing-page-level (docs.binom.org/traffic-armor.php): the filtering service's script is uploaded to the campaign's Fail URL and owns serving/redirecting, while a Binom LP Pixel snippet on the real landing page keeps click tracking working.

1. Download the landing-page filter file

In your dashboard, go to Integration, select the stream you want to protect, choose the Binom tab, and click Download cloaking-x-binom.php. Your Stream ID and API URL are baked into the file at download time — one file per stream.

2. Upload it to your web server

Anywhere reachable over HTTP(S) works — this file is a standalone PHP script, not something that needs to live inside Binom itself.

3. Set it as your campaign's Fail URL

In your Binom campaign settings, set the Fail URL to wherever you uploaded cloaking-x-binom.php. This mirrors exactly how Binom's own Traffic Armor integration guide sets it up: the filtering script lives at the Fail URL and decides what every visitor sees.

4. Add your campaign's LP Pixel to your real landing page

Copy the LP Pixel code from your campaign's Additional settings and paste it into the <head> of your real landing page (the Allowed Visitors / "Insert HTML" target). This file only makes the pass/block decision and serves content — Binom's own LP Pixel is what keeps these clicks counted and attributed in Binom's reports, independent of which path actually got served.

5. Customize the safe/reviewer-facing page — done

Edit the placeholder HTML at the bottom of the downloaded file with whatever you want ad reviewers or blocked visitors to see. It only renders when there's no Fallback Page configured on the Cloaking X stream, or the /api/check call failed — passed visitors are served your money page in place before that point is ever reached.

Warning
Without the LP Pixel snippet on your real landing page, Binom won't count these clicks at all — this file only decides and serves; it never reports anything back to Binom's own stats on its own.
Note
If the Cloaking X API is ever unreachable, times out, or returns something unexpected, this file fails open — it renders the safe/reviewer-facing page you configure so a temporary outage never black-holes your campaign.