Documentation sections
Flow setup
Step 1. Destinations
Where traffic goes: offers and the White Page.
On this page
Flow mode

- Default
- “Cloaking”
- Recommended
- “Cloaking” for ads with moderation; “Cloaking + Tracker” if you need money tracking
- Plan
- all plans
- Common mistake
- choosing “Tracker” and connecting the site with the JS tag: the connection window for such a flow only offers the PHP file, and visits in the log show “Tracked, not filtered” (
TRACKING_ONLY)
| Mode | What happens | When to choose it |
|---|---|---|
| Cloakingdefault | The filter sorts visitors: bots and moderators go to the White Page, people go to the offer. | Ads where moderation must not see the offer. |
| Tracker | Everyone goes to the offer. Clicks, conversions, spend and profit are counted, and bots are only flagged in reports. | Traffic that doesn't need filtering but does need money tracking. In the connection window, a flow in “Tracker” mode only offers the PHP file: the tag, Keitaro, Binom and site builders aren't shown for it. |
| Cloaking + Tracker | The filter weeds out unwanted visits, and money is counted for the visitors who get through: sources, cost per click, branches, pre-landings. | When you need both protection and full tracking. |
- In “Tracker” mode, platform moderators see the offer too. The White Page block is called “Reserve page” there: visitors only land on it if the flow is paused, the plan isn't paid, the address is on your IP blacklist, review mode is on or the shield is up.
- Branches, pre-landings, visitor pinning, affiliate network, prices and tags are only available in modes with the tracker.

The “On our server” option is available on a paid plan; on the trial it's unavailable.
Traffic source

- A dropdown: “No source” (default) and your sources. The last item, Add a source, lets you create a source right here, and the new source is selected at once.
- Choosing a source:
- spreads its parameters and SubIDs into the campaign tags that make up the ad link;
- tunes protection on step 2 to the source's platform (Facebook, Google, TikTok, native ads or other);
- passes its cost per click to the flow, if the flow has no cost model of its own.
- If you've already changed the protection by hand, the dashboard will first ask whether to replace it (see Check strictness).
Name and project

- Why: the name is how you find the flow in the list, the log and reports. A handy pattern is “platform · offer · countries”.
- Error: an empty field gives “Flow name is required.” and the flow won't save.
- Flow name: required, up to 190 characters. The field's example: “FB — Nutra — Main Flow”. Only you and your team see it.
- Project: appears if you have projects. Projects group flows by client, offer or team and separate access. A team member with access to projects only has to pick a project.
Filter preset

Appears if you have saved presets. Pick a preset and it fills in the form:
- all audience lists with their modes: countries, devices, OS, browsers, languages, time zones, cities, regions, networks, ISPs, referring sites;
- the schedule;
- the ten protection toggles (cloaking and nine checks), the clicks per IP limit, warm-up, minimum time on page;
- platform and strictness; the preset's source, if the flow doesn't have one yet.
A preset is applied once: the flow gets its own copy of the rules, and editing the preset no longer affects it. To pull in a newer version of the preset, pick it again. A preset doesn't carry over shadow mode, and features your plan doesn't include are switched off right away.
Offer pages

- Default
- one offer, “Offer (primary)”, in “Loading” mode
- Recommended
- “Loading”: your address stays in the address bar
- Plan
- offers: Starter, 2; Professional and the trial, 5; Business, unlimited
- Common mistake
- the offer is off or has no address, so visits get “The flow has no offer to send to” (
NO_OFFER_DEST); the offer site didn't respond: “Offer did not load” (OFFER_UNDELIVERED)
This block is always expanded. On the left it says “Offers: X of Y.”; when the limit is reached, the Add offer button is disabled, and the plan with more offers is shown next to it.
| Field | What it is | Default |
|---|---|---|
| Enabled | A disabled offer gets no traffic but stays in the flow. | enabled |
| Name | The offer's name in reports, up to 190 characters. | “Offer (primary)”, the next ones “Offer” |
| Mode | Loading: the offer page opens under your ad address. Redirect (302): the visitor is sent on, and the address bar shows the offer's address. Iframe: the page is embedded in yours. | Loading |
| URL | The offer address with http:// or https://, up to 2000 characters. You can use macros, for example {click_id}. | — |
- A new offer gets “Loading” mode and the link tags of the first offer. Its “Offer link parameters” rules are empty and are set separately.
- You can delete any offer except the first one. It's removed for good when you save.
- Offer shares, the split mode and pinning are set not in the card but in the How visits are split panel below the offers (with branches, How the remaining visits are split). The panel appears when there are two or more offers. To pause traffic to an offer, disable it rather than setting its share to 0.
- The ad link doesn't depend on the number of offers: the offer is chosen for each visit after all checks.
- If you choose “Iframe” mode and the offer site forbids framing, a note appears below the address: our server will show the page anyway, but links inside it will open in the full tab. This doesn't stop you from saving.
- To open an app in Google Play, put the deep link
market://details?id=packagein the offer URL and choose “Redirect” mode. An app store can't be loaded or shown in a frame, and pre-landings and White Pages don't accept such a link.
Offer link parameters

fbclid → sub1, 2 “Set” aff_id = {click_id}, 3 “Remove” utm_source, 4 add buttons.- Default
- no rules: tags go to the offer as they came
- Recommended
- put the click number into the affiliate network's tag: “Set”
sub1={click_id} - Plan
- all plans, up to 20 rules per offer
- Common mistake
- renaming a tag the visit doesn't have: the rule does nothing, the postback can't find the click, and there are no conversions
The ad platform (Facebook, Google, TikTok) appends its own tags to the link: fbclid, gclid, ttclid, utm_source and others. The affiliate network expects its own names: sub1, aff_id, s1, click_id. These names almost never match.
The rules rewrite tags on the way to the offer: they rename, set and remove parameters. Three jobs you can't do without them:
- Get the conversion back. The affiliate network sends a postback with the ID you passed to it. If you put our
{click_id}into itssub1, the postback will find the right click. The platform's tags don't carry our number; only the macro provides it. - Give the network its own names. The platform sent
fbclid, but the network readssub1: rename it, and the value arrives under the right name. - Don't expose extra data. A platform tag that reveals the source (
utm_source=facebook) can be removed so it doesn't reach the affiliate network.
The rules apply only on the way to the offer and the pre-landing. In the click log and on the White Page, tags stay as they came. This matters: a renamed fbclid on the White Page would give the cloaking away.
Each offer and pre-landing has its own rule set: different offers go to different affiliate networks, and their tag names differ. The White Page has no rules.
Actions
| Action | What it does | Example |
|---|---|---|
| Rename | The parameter leaves under a different name, with the same value. | fbclid → sub1 |
| Set | The parameter gets a value: a macro or text. If the parameter wasn't there, it's added. | aff_id = {click_id} |
| Remove | The parameter isn't passed to the offer. Instead of a value field, the row says “won't reach the offer”. | utm_source |
Rules run top to bottom, each on the result of the previous one. So order matters: first rename fbclid to sub1, and only then will a rule on sub1 see that value.
The block is collapsed in the offer and pre-landing card, and its header shows the number of rules. Each rule is a row “visit tag → what to do → result”; the rows are numbered so you can see the order. The action is picked with the Rename / Set / Remove switch. A new rule is added with the buttons in the “Add:” row: Rename a parameter, Set a parameter, Remove a parameter. A set holds up to 20 rules. “Rename” does nothing if the visit doesn't have the tag. The value is written without spaces and without the & character.
A full example
A visitor came through the flow's ad link:
https://your-landing.com/?fbclid=IwAR123&utm_source=facebook&utm_campaign=nutra_de
The flow's offer is https://track.partner.com/click?offer=55. The flow's rules:
- Rename
fbclid→sub1 - Set
aff_id={click_id} - Remove
utm_source
The offer receives this address:
https://track.partner.com/click?offer=55&utm_campaign=nutra_de&sub1=IwAR123&aff_id=C-01JB8Q3Z7XKP4M2R9TVN6WDY5H
Before: fbclid and utm_source. After: fbclid moved to sub1, aff_id appeared with the click number, and utm_source is gone. The rules didn't touch utm_campaign, so it arrived as is. The log still records fbclid and utm_source for this click.
Macros for “Set”
The value can include visit data: {click_id}, our click number; {flow_id}, the flow number; {geo}, country; {city}, city; {device}, device; {os}, OS; {browser}, browser; {isp}, ISP; {ext_click_id}, external click id; {cost}, cost per click; {sub1}…{sub10}, the flow's tags.
The rules work the same whether you connect with the link or with the PHP file. The PHP file needs its latest version: if a new one is out, a banner appears in the connection window.
Branches from Professional

- Default
- no branches: everyone goes to offers without a branch
- Recommended
- split by device or country when the offers differ
- Plan
- Professional and up, modes with the tracker; up to 30 branches, up to 15 conditions
- Common mistake
- a branch with no offers: its visitors go to offers without a branch, not to the White Page
Different visitors go to different offers: by country, device, link parameter or campaign tag. The block is visible in modes with the tracker when there are two or more offers.
- Add a branch creates “Branch N” with the condition “Country is one of”.
- A branch has a name (up to 120 characters), an On toggle, Up and Down arrows and a delete button. Offers of a deleted branch become offers without a branch.
- A condition reads as “If [field] [operator] [values]”. When a branch has several conditions, all of them must be met.
- Fields: Country, Device, OS, Browser, ISP, ASN, City, Region, Language, Referrer, Link parameter, Label (sub). For a link parameter and a label, enter the name, for example
utm_sourceorsub1. - Operators: “is one of”, “is none of”, “contains”, “is set”, “is not set”.
- Values: comma-separated.
- Fields: Country, Device, OS, Browser, ISP, ASN, City, Region, Language, Referrer, Link parameter, Label (sub). For a link parameter and a label, enter the name, for example
- Branches are checked top to bottom, and the first match wins. Visitors who match none go to offers without a branch. If every offer is assigned to a branch, those visitors go to any offer of the flow; the form shows this as “Remaining visits → no free offers — they go to any offer of the flow”.
- Offers are assigned in the branch itself: tick them in the Where to send block. An offer can belong to only one branch; an offer from another branch is shown in grey, with that branch's name. If a branch has no offers, its visitors go to offers without a branch. Pre-landings pick their branch in their own card.
- Limits: up to 30 branches, up to 15 conditions per branch.
Pre-landings

Your page before the offer: a quiz, an article, a review. A visitor who passed the filter sees it first, and its button leads to the offer. The report shows how many reached the offer.
- The block is available in modes with the tracker, on every plan and on the trial. The card is the same as an offer's; the default mode is “Redirect”.
- Pre-landings don't count toward the offer limit, but there can be no more than one per offer. When there are as many pre-landings as offers, the + Pre-landing button is disabled, and next to it you'll see “One pre-landing per offer.”
- Leads to offer: “By weight among offers” or a specific offer. An offer that another pre-landing already leads to isn't offered in the list.
- The button on the pre-landing must link to the
{click_url}macro, for example?go={click_url}. If there are several buttons, append/2,/3to the address to open the second and third offers. - When connected with the PHP file, put a
.htaccessfile with a rule for thestartpath next to ourindex.php; without it, reloading the offer page will give a 404. Thestartpath lives in the ad link's folder, and you can't change it in the flow form. Details are in the PHP file section. - When connected with the JS tag, no files or rules are needed: the button leads back to your ad page, the offer opens on it, and our service parameters are removed from the address bar. On reload, the offer stays if the visitor was active in the last 5 minutes.
- Keep the pre-landing on the offer's domain, in its own folder, for example
your-site.com/folder/lead/. With the PHP file in “Loading” mode, the pre-landing opens via the ad link without a<base>tag: the file itself rewrites the addresses of images, styles and links into root-relative paths, and no other domain appears in the markup. A pre-landing on another domain will open too, with caveats. That domain will be visible in image and style addresses. Fonts from it will only load if it allows other sites to use them (theAccess-Control-Allow-Originheader). And addresses the page builds in a script (for examplefetch('send.php')) will resolve against the ad link, not the pre-landing. - With two or more pre-landings, they get a “Weight” field.
Example. The offer is best-shop.com/promo/offer.php, the ad link is best-shop.com/promo/?utm_source=fb. The visitor opens it and sees the pre-landing; the address in the bar doesn't change. Here's what the file turns the addresses in the pre-landing's markup into:
| In the pre-landing markup | Pre-landing best-shop.com/promo/lead/ | Pre-landing quiz-pages.net/keto/ |
|---|---|---|
assets/style.css | /promo/lead/assets/style.css | https://quiz-pages.net/keto/assets/style.css |
img/photo.webp | /promo/lead/img/photo.webp | https://quiz-pages.net/keto/img/photo.webp |
../privacy.html | /promo/privacy.html | https://quiz-pages.net/privacy.html |
#form | stays on the page | stays on the page |
{click_url} | /promo/start?utm_source=fb with the rule in .htaccess; without it, our click-through address | /promo/start?utm_source=fb with the rule in .htaccess; without it, our click-through address |
After the button, the visitor sees the offer at best-shop.com/promo/start?utm_source=fb in both cases. But in the second case quiz-pages.net is visible in image and style addresses, and fetch('send.php') from the pre-landing's script goes to best-shop.com/promo/send.php, where no such file exists.
White Page

- Default
- none: the field is required
- Recommended
- your own page in “Loading” mode or our ready-made one from the catalog
- Plan
- all plans; the design catalog on all plans, premium designs from Professional
- Common mistake
- a White Page on “Redirect”: the moderator sees a jump to another domain; without a page the flow won't save: “Add at least one enabled White destination”
The page for those the filter didn't let through to the offer. It's required. You can set it in three ways:
- Your own address: the URL field and the “Loading” or “Redirect” display mode. “Iframe” mode isn't used for the White Page. Below the field are buttons with the addresses of your recent White Pages and the Order a White Page from the catalog link.
- Our ready-made page: the Or let us show ours — no address list. The ready site opens at your ad address; you don't need to upload it anywhere. The list shows your last 100 ready pages, plus the one already in the flow. With the PHP file, you need its latest version.
- A status code: the “Status code (200/403/404)” display mode. A filtered-out visitor gets only a response code, with no page: 200, an empty page; 403 or 404, an empty server error page, like a closed or non-existent address. A checking program has nothing to read. Works when you connect with the PHP file or the link; the JS tag can't change the response code and leaves an empty page in place of the landing. Platforms with manual moderation (Google, Facebook) usually reject such ads; this mode is for sources where a program, not a person, looks at the page.
Traffic split

- Default
- weighted rotation, even split; pinning 0 h
- Recommended
- weights for a split test; pinning 24 h if one offer per person matters
- Plan
- weights on all plans; “Priority” on Professional and up
- Common mistake
- weights don't add up to 100%: “Weights must sum to 100”; click “split evenly”
The block appears when there are two or more offers (or pre-landings).
- Weighted rotation: the offer for each click is picked at random, taking the weights into account; on large traffic the shares even out to the set ones. Weights must add up to exactly 100%. The split evenly button splits evenly within each set: offers without a branch, each branch's offers, pre-landings. If there's one offer and several pre-landings, the same button is called Auto weights.
- Priority from Professional: all traffic goes to the first enabled offer, the rest are on standby.
- Visitor pinning, h: from 0 to 720 (modes with the tracker). If a visitor comes back within this time, they see the same pre-landing and the same offer. 0 means no pinning.
Possible errors
- “Flow name is required.”
- “Add at least one enabled Offer destination with a URL.”
- “Invalid URL in destinations: …”: the address must start with http:// or https://.
- “Add at least one enabled White destination — with an address or one of our ready-made pages.”
- “Weights must sum to 100”: click split evenly.
ArtisanClo · Dashboard documentation. Questions — info@artisanclo.com or @artisanclo_support on Telegram.