Documentation

Traffic

Platform recipes

Ready settings for the most common sources. We recognize the platform in two ways: by the traffic source chosen on step 1 (it tunes protection to the platform; see Check strictness) and by the click tag in the link: fbclid, gclid, ttclid, msclkid, twclid and others. The rule is one campaign, one flow. That way decision reasons and reports relate to a single ad and don't get mixed up.

On this page

How to apply a recipe

  1. Create a source for the platform

    Sources → Add a source → the platform template, for example “Facebook / Instagram (Meta)”. Details in Traffic sources.

    «New source» window: name Facebook Ads, «face» typed in the template search, the «Facebook / Instagram (Meta)» template found and the «Add a platform» link
     1 name, 2 template search, 3 platform template, 4 «Add a platform» if it is not on the list.
  2. Pick it in the flow

    Step 1 of the flow form, the Traffic source block. Protection on step 2 adjusts to the platform, and the values from the table below are filled in automatically. If you've already changed the protection toggles by hand, the form shows what will change and asks whether to apply it. In “Tracker” mode, protection isn't filled in.

  3. Connect the site using the method from the table

    The “Connection” column; how to install the tag or the file is in Connecting your site.

  4. Turn on protection before moderation

    Warm-up, the shield or review mode; see Before moderation below.

Settings by platform

PlatformConnectionOfferWhite PageProtection
Google Search, GDN, YouTubePHP file or JS tag“Loading”: the address from the ad stays in the address bar“Loading” or our ready-made page, no redirectGoogle Ads source: required JS, a 30-click warm-up, 2 clicks per IP per day. The shield lets through by gclid, wbraid, gbraid, gad_source.
Facebook, InstagramPHP file or JS tag“Loading” or “Redirect”“Loading” or our ready-made pageFacebook Ads source: a 50-click warm-up, the referrer check off, since Facebook's in-app browser often drops it. The shield lets through by fbclid.
TikTokPHP file or JS tag“Loading”“Loading” or our ready-made pageTikTok Ads source: blocking visits with no ISP is off, a 50-click warm-up. The shield lets through by ttclid.
Microsoft Ads (Bing)PHP file or JS tag“Loading”“Loading” or our ready-made pageThe Bing.com template uses the “Another source” protection settings: required JS, 3 clicks per IP per day, warm-up off (turn it on by hand). The msclkid click tag is recognized, and the shield lets through by it.
X (Twitter)PHP file or JS tag“Loading” or “Redirect”“Loading” or our ready-made pageThe X (Twitter) Ads template uses the “Another source” protection settings: required JS, 3 clicks per IP per day, warm-up off (turn it on by hand). The shield lets through by twclid.
Taboola, Outbrain, MGID and other native adsPHP file“Redirect” or “Loading”“Loading” or our ready-made pageA source made from a native network template (MGID, Taboola, Outbrain, Revcontent and others) gets the “Native and push” protection: 5 clicks per IP per day and a 100-click warm-up, since native ads show to the same people a lot. Push and popunder network templates get “Another source”: set the limit and warm-up for them by hand. The shield lets through by tblci (Taboola), ob_click_id (Outbrain). MGID has no click tag of its own, so the shield doesn't suit it.
An app asks what to show (SDK, a store placeholder)The flow link ending in /a or the PHP file with ?ac_app=1“Redirect”; for Google Play, market://details?id=…any: the app never shows itThe response is an HTTP code (as with Adspect): 200 with the offer address as a single line in the response body means “open the offer”; 403 means “show your own placeholder”. There's no waiting page, so the JavaScript check, time on page and live interaction are off for these requests, and the decision is made by network and request signals. The tag doesn't fit here: it needs a browser.

Warm-up and the clicks per IP limit work from Professional and on the trial. The clicks per IP number is for “Balanced” strictness: “Soft” has no limit, “Strict” allows 2 at most.

Before moderation

  • White Page for everyone during the review. Turn on review mode from Professional for the flow in “Diagnostics” (the “Ban risk” tab): all visitors see the White Page with no filtering. Turn the mode off after approval. Another option is to pause the flow: everyone will see the White Page too.
  • The review is on, and the campaign is already running. Raise the shield from Professional: only visitors with an ad click tag reach the offer, and reviewers without one see the White Page. The auto-shield raises it on its own when it sees signs of a review.
  • Warm-up from Professional: the flow's first N clicks go to the White Page with no checks. The first visits after launch are most often reviews.
  • Don't change the White Page in a running campaign: a new page gives the platform a reason to review the ad again.

In-app browsers and WebView

The in-app browsers of Facebook, Instagram and TikTok and WebView in apps are recognized. In these browsers, automation signals are often false, so on their own they don't cut the visit; they're only weighed in the trust score, along with network, time and referrer. For campaigns where almost all traffic comes from an in-app browser, choose “Balanced” strictness and don't turn on no-referrer blocking.

Native ads and platforms with bots

Pass the placement (zone, site) number into a campaign tag, for example sub1={zoneid}, and look at the “Money by slice” report by that tag. Turn off placements where the filter cuts almost everything in the network itself, so you stop paying for them.

ArtisanClo · Dashboard documentation. Questions — info@artisanclo.com or @artisanclo_support on Telegram.