Affiliate dashboard isolation

A network dashboard is a login you already joined. Payouts, offer status, creative IDs, compliance tickets. I keep it in a local profile that is not my research tab and not a place I click my own links.

The useful caveat: this is hygiene for programs you already joined. It is distinct from the antidetect-for-affiliate commercial page. Ecommerce accounts on one PC is the pillar. Affiliate self-clicks are fraud.

One network, one profile (when they must not meet)

If two networks must not share pixels or login state, two folders. If one network already expects one login for several offers, match that.

Research looking lives in a cold profile. Affiliate research rooms. Cloaking and "helper" extensions stay out. Affiliate extensions we refuse.

Payouts that use PayPal belong with the entity money split, not with research. PayPal business versus personal rooms.

Storefronts are other folders. Shopify multi-store isolation. eBay seller isolation. Airbnb listing isolation.

MaskWright 0.1: Windows 10/11, per-profile user-data-dir. profiles.json is encrypted. Chromium user data is not. Bring your own HTTP or SOCKS5 if that program already uses an exit. No seats. Invite teammates through the network's official users.

How I set it

Empty cookies. Official dashboard URL. 2FA on a device I hold. No extra Google accounts in the picker. Close it when payouts are checked. Do not "preview" your own offer URL from this profile.

How I run a network dashboard on Windows

The profile is acme-cj or acme-impact, named after the network, not after a geo. I sign in, check payouts, download the report I need, move it to finance ops, and close it. I do not browse landing pages from here. Landing pages are the cold profile without my tracking ID.

Pixels and helper tags that fire for this program install here only. Cloaking extensions do not install anywhere. If I need to see a creative, I use the network's preview or a public URL without my click ID.

Two networks I care about get two folders. Shared cookies are how Network A's pixel rides into Network B's dashboard. PayPal for this entity stays in the money profile, not in research.

Geo check if this program already requires an exit. Sticky. I do not rotate under a payout login. MaskWright does not sell the exit.

Teammates get the network's user invite. Cookie files are plaintext. Not onboarding. 2FA they hold.

If I catch myself about to click my own link, I stop. Isolation will not launder that click.

FAQ

Several networks, one profile?

Only if you accept shared cookies and shared download trays. I default to one folder per network I care about.

Will isolation hide that I clicked my own link?

No. Do not click your own link. Isolation is not a fraud costume.

Cookie dump to a media buyer?

No. Official user access. Cookie files are plaintext.

Cloud dashboard?

The vendor sees payouts. I keep dashboards local. Compare local versus cloud.

Can I keep PayPal in the dashboard profile?

Payouts belong with the entity money split when that is a different login. Do not park personal PayPal next to Network A's pixel.

Keep network logins in their own folders. Look at public pages elsewhere. Never self-click.

I skip cloaking kits, rotating exits under payout logins, and cookie dumps to media buyers. I name the profile after the network. I geo-check only if that program already uses an exit. I empty the download tray so reports do not sit next to a tagged URL I might click by habit.

I bookmark the dashboard inside this profile only. I do not paste offer URLs with my click ID into Slack from this folder. Slack plus a tagged URL is how a teammate self-clicks without meaning to. Stats stay in the dashboard. Looking stays cold.

Two networks I care about still get two folders even if payouts land in the same PayPal. Shared dashboard cookies are the mix. Shared PayPal is a money-profile question, not a reason to merge pixels.

More notes sit under Ecommerce. Download MaskWright for the Windows launcher.