Using ValidVisit with Binom

Paste the ValidVisit snippet before </body> on the landing page Binom sends visitors to. Binom setups come in three shapes:

• Click-through. The ad points at your Binom campaign link; Binom records the click and sends the visitor to the lander.
• No-hop, with the LP pixel. The ad points straight at the lander, and Binom’s LP pixel runs on the page beside the ValidVisit snippet.
• Integrated landers. Binom renders the page itself and injects its tokens server-side, so the page can load from your Binom domain.

The script only runs on hosts listed under Allowed domains in your ValidVisit site. Add the lander’s domain, and your Binom domain too if you use integrated landers.

ValidVisit reads the network’s values from the landing-page URL, under its vv_* names. ExoClick fills its macros into your Binom campaign link, and Binom holds them as {t1} to {t10}, as your traffic source’s token settings assign them.

Say your ExoClick traffic source puts {site_id} in t1 and {zone_id} in t2; check the order in yours. Add to the lander URL in Binom:

• clickid={clickid}: Binom’s click ID. Binom’s own lander examples pass it this way, so it may already be there.
• vv_source=exoclick: names the network.
• vv_publisher_id={t1}: the site.
• vv_placement_id={t2}: the zone, the unit ExoClick lets you block.

Start the list with ? and join the pairs with &. With the LP pixel the ad URL is the lander URL, so put ExoClick’s macros on it directly, such as vv_placement_id={zone_id}, as the ExoClick tracking tokens page lists them. ValidVisit’s Link Wizard builds that list; behind Binom, swap each macro for the {tN} that holds it.

Binom’s docs put the click ID on the lander URL as clickid={clickid}, and ValidVisit already reads that key: clickid, click_id and vv_click_id all fill the visit’s click-ID field. One parameter serves both tools.

Send one click ID. With clickid and vv_click_id both on the URL, the one later in the URL fills the field, so don’t add ExoClick’s {conversions_tracking} as vv_click_id beside it.

With the LP pixel, the ad opens your page before Binom has a click ID to put on the URL. Pass ExoClick’s click ID there instead: vv_click_id={conversions_tracking}.

Binom groups stats by its traffic source tokens; ValidVisit shows the same sites under Publisher and zones under Placement. They’re one source seen twice: Binom counts clicks, leads and events, ValidVisit judges each visit that loaded the page Valid or Invalid, with its evidence.

• Zones that convert but are judged invalid. Check the leads before you raise bids; bot traffic that fires events looks like a good zone.
• Sites that are bad throughout. When most of a site’s zones are judged invalid, the cut is the whole site.
• Totals that differ. Binom records the click before the lander loads; ValidVisit counts visits that loaded the page with the script. Compare shares, not raw counts.

Binom Protect is a paid add-on, though its VPN and proxy detection has been free since version 2.27. It runs server-side and JavaScript checks on each click, tags what it flags in reports and the click log, and a Bot rule in your campaign sends flagged clicks down a bot path. Its JavaScript methods add a short browser-check step before the lander.

If the bot path ends on another page, what Protect catches never reaches your lander; ValidVisit grades what it let through, by zone and site. Tracker bot filters vs ValidVisit compares the two approaches.

ValidVisit never changes your Binom campaigns or your ExoClick account, and sends nothing into Binom. It ranks zones and sites worst first and exports the ones worth cutting as a Cut-list CSV. In ExoClick, open campaign Step 5, Zones, set Target Mode to Block and paste the IDs; blacklisting sites and zones in ExoClick walks through it, and blocking bad sources by network covers other networks.

Binom’s Triggers, in open beta since version 2.34, act on Binom’s own metrics and can pause paths, landers or offers; its docs list no action that pauses a network zone.

For visitors you never want on the page, ValidVisit’s traffic rules tag visits by country, data-center hosting or VPN and can send them to another page; whole countries can also be blocked at your own firewall. The verdict itself blocks nothing.

• Integrated landers. Binom injects its tokens into the page on the server. ValidVisit reads the page’s URL, not values written into the HTML, so check the address bar carries the vv_* parameters.
• The allowed domain. An integrated lander served from your Binom domain needs that domain in Allowed domains, or the script won’t run.
• Protect’s browser check. With JavaScript methods on, confirm a test visit still lands with its parameters after the check step.

Test this setup again after changing the traffic source’s token order.