Proxy field notes Response codes Pool sizing Choosing an address

Choosing an address by task

Requirements for scraping and for account work point in opposite directions. Here is the difference across four parameters.

Parameter	Data collection	Accounts and dashboards
Permanence	changing addresses helps spread the load	the address stays pinned for the life of the profile
Quantity	a pool at triple the calculated minimum	one address per profile
Region	matches the storefront you collect	matches the region in the profile
Neighbours	someone else's history spends the allowance first	someone else's block drags your profile with it

Checks before launch

• Headers carry no trace of the real IP. Verified before any profile touches the address.
• The region of the address matches the profile or the job.
• The address answers steadily for an hour with no session drops.
• No other activity runs through it against the same platform.

Long-lived profiles run on addresses rented by the month, background jobs on datacenter addresses with a steady channel, and jobs that need no session on a pool with automatic rotation.