Which exit country does an artist merch store need?

The country of the store you are buying from, set with the -cc- token on the username. An artist with a UK store and a US store is two sets of strings: -cc-gb for one, -cc-us for the other. The gateway you connect to only changes latency.

Do I need a city token for a merch drop?

Usually not. A merch store sells to a country, so -cc- is enough. A -city- token narrows the pool, and narrow targeting can answer E20 when nothing matches at that moment. It never falls back to the whole country on its own.

How much data should I buy for a small merch drop?

Start with pay as you go at 1 GB, which never expires. Run the drop, open the statistics page the next morning and read the bytes against the store's domain. That number sizes the next purchase better than any guess.

Sticky or rotating for merch?

Rotating for the monitor that watches the product page, sticky for each checkout task. A checkout task gets its own -sess- id and a -ttl- longer than the checkout takes, so the cart and the payment page see one address.

Artist merch drops: the ticket on-sale playbook, smaller

2026-10-31 · Bazyl

An artist merch drop is a ticket release with fewer moving parts: one store, one country, a handful of products, and usually no seat map. After this post you can set it up with the same three tools a ticket buyer uses, sized down. The mistake people make is copying a ticket setup wholesale, fifty tasks and a city token, onto a store that needs five tasks and a country.

Everything below runs on one login and one port, 2115.

The store's country is the only targeting most merch needs

Merch stores sell to countries, so -cc- does the work. An artist with a US store and a UK store is two sets of strings, -cc-us and -cc-gb, from the same login. You don't need a city unless the store itself is regional, and most aren't.

The gateway is a separate choice. Pick the one nearest the machine running the bot: eu-, us- or ap-residential2.basilproxies.com. Measured from a server in Germany on 1 October 2026, the European gateway answered in 7 to 21 ms and the US one in 113 to 148 ms. So a bot in Europe buying from the US store connects to eu and asks for -cc-us.

A -city- token is worth it only when the store sells something to one city, which is rare. It narrows the pool, and a narrow ask can come back E20 no exit for this targeting. Targeting never falls back to a wider area on its own.

Five tasks, five session ids, one monitor

Size the task list to the products. Say the drop is three items, a shirt, a hoodie and a signed print, and you run two checkout tasks on the print and one on each of the others. That's four checkout tasks and one monitor: five strings.

Each checkout task gets its own -sess- id and its own line. The monitor gets no session token at all, so every request leaves from a new IP.

# Monitor: watches the product page, new IP on every request
us-residential2.basilproxies.com:2115:USER-cc-us:PASS

# Checkout tasks: one id each, held for 30 minutes
us-residential2.basilproxies.com:2115:USER-cc-us-sess-m3rch01a-ttl-30:PASS
us-residential2.basilproxies.com:2115:USER-cc-us-sess-m3rch02b-ttl-30:PASS
us-residential2.basilproxies.com:2115:USER-cc-us-sess-m3rch03c-ttl-30:PASS
us-residential2.basilproxies.com:2115:USER-cc-us-sess-m3rch04d-ttl-30:PASS

Two tasks on one id are one buyer to the store. Five ids are five.

A login starting res2_ predates 27 October 2026 and uses the legacy format: the docs show it.

The ttl is shorter than a ticket queue

A merch checkout is minutes, not hours, so -ttl-30 is plenty. The ttl takes 1 to 1440 minutes; leave it off and the session lasts 15. A ticket queue wants two hours because the queue itself can take an hour and a half. A merch cart doesn't.

If the store runs its own waiting page, size the ttl to the wait you expect plus the checkout, and no further. A session that outlives the task is just parked traffic.

One more timing fact: a tunnel that carries nothing for about 60 seconds is closed. A sticky session keeps its IP across the reconnect, because the same id keeps the same exit, so a task that idles on a product page loses nothing but the open connection.

Buy 1 GB first and let the statistics page size the second purchase

Pay as you go starts at 1 GB and never expires. In euros, as of 1 October 2026, 1 GB is €3.50, 2 to 4 GB €3.25 a gigabyte and 5 to 14 GB €3.00. In US dollars the same rungs are $4.20, $3.90 and $3.60.

We don't publish how much a merch drop uses. It depends on the store's pages and on how often your monitor polls. What we do give you is the statistics page: bandwidth and request charts from 24 hours to 30 days, a success rate, latency, and a per-domain table of your top targets. Read the store's row the morning after. That is your real number.

A worked example on made-up figures: if the store's row says 400 MB for the drop and you plan three drops this month, 2 GB covers it with room, at the 2 to 4 GB rung.

Test the strings an hour before, not at the drop

A brand-new login can answer 407 or E53 login not ready yet for its first minute or two while it reaches every gateway. Test as soon as you generate. Two requests through each sticky string should come back with the same IP, and the country should be the store's.

P="http://USER-cc-us-sess-m3rch01a-ttl-30:[email protected]:2115"
curl -s -x "$P" https://api.ipify.org; echo
curl -s -x "$P" https://api.ipify.org; echo
curl -s -x "$P" https://ipinfo.io/country

Same IP twice and US at the end: the task is ready. A different IP means a new session id. E01 invalid proxy login means the pair is wrong, most often a token pasted onto the password; tokens ride the username only. The pre-drop checklist covers the other eight checks.

What carries over from a ticket setup, and what doesn't

Carries over: one session id per task, a rotating monitor, the nearest gateway, testing early, reading the statistics page afterwards. Doesn't: the hour-long ttl, city tokens by default, and buying 50 GB before you know your number.

What we answer for is the same in both. The proxy is live and reachable from the country you asked for. What the store does with your request is the store's, and we don't promise a checkout on any of them.

For the full-size version of this setup, with cities, teams and longer sessions, start from the ticket drops page.

Common questions

Which exit country does an artist merch store need?: The country of the store you are buying from, set with the -cc- token on the username. An artist with a UK store and a US store is two sets of strings: -cc-gb for one, -cc-us for the other. The gateway you connect to only changes latency.
Do I need a city token for a merch drop?: Usually not. A merch store sells to a country, so -cc- is enough. A -city- token narrows the pool, and narrow targeting can answer E20 when nothing matches at that moment. It never falls back to the whole country on its own.
How much data should I buy for a small merch drop?: Start with pay as you go at 1 GB, which never expires. Run the drop, open the statistics page the next morning and read the bytes against the store's domain. That number sizes the next purchase better than any guess.
Sticky or rotating for merch?: Rotating for the monitor that watches the product page, sticky for each checkout task. A checkout task gets its own -sess- id and a -ttl- longer than the checkout takes, so the cart and the payment page see one address.