A user (profile) token must have a proxy: without one its requests would leave from the AdFleet server's IP. A System User token needs none — it connects directly.
- The "Proxy" field is required when you connect the token; later you can replace it on the token (not remove it). The proxy is checked together with the token — one request to Meta through it; a proxy that does not answer is not saved. A profile token without a proxy only reads: writes are stopped until a proxy is added.
- Only
http://andhttps://with a public host and an explicit port. SOCKS isn't supported. - With a proxy set, every request with that token goes through it only. If the proxy is down, requests fail — AdFleet never sends them directly instead.
- One proxy, one profile. No rotation, no per-GEO pools, no browser disguise: AdFleet always identifies itself honestly (
adfleet-launcher/1.0).