Proxies for PetSmart complete the pet-retail trio beside Chewy and Petco, and its door is a layered one on a modern stack. On 24 August 2026 we sent petsmart.com a plain request from a home connection and from a datacenter server. Both returned the homepage, HTTP 200, with Akamai's _abck and bm_sz sensor cookies and an F5 Shape marker, served through a modern hosting layer (Vercel), with Bazaarvoice for reviews. The homepage loading is not the catalog opening; Akamai gates the product data and Shape scores the session.
PetSmart is a national pet retailer with the same subscription economics as its rivals plus store-level services, so its data is one-time and subscription prices, store stock, and services like grooming. That makes the proxy job a store-level read behind an Akamai-and-Shape defense, and it benchmarks directly against Chewy and Petco.
What proxies work best for PetSmart?
US rotating residential proxies behind a real browser, region-matched, one consistent exit per session. A static ISP proxy for a logged-in Treats account with a subscription. Datacenter proxies are for testing only.
Akamai gates the request, Shape scores the session
The homepage returning 200 is Akamai admitting a first look, not opening the catalog. Akamai's sensor sets _abck only after its data validates and reads the TLS fingerprint before any HTTP, so a bare client fails the request-level check (how the _abck cookie works, what is JA3/JA4 fingerprinting). F5 Shape then scores the session's behavior over time (how to handle F5 Shape). The working combination is a residential IP to pass Akamai's reputation gate, a real browser to satisfy the sensor and Shape, and one consistent exit per session, because a mid-session IP swap is a Shape tell. It is the Akamai-plus-Shape pattern of Uniqlo, on a pet catalog. The modern hosting layer underneath does not change the proxy approach; the Akamai edge in front is what a request meets first.
Subscriptions and Treats make the price a subscription
PetSmart's Treats rewards earn points on purchases, and it offers repeat-delivery subscriptions with a discount off the one-time price, so, as with Chewy's Autoship, there are two prices for a product and they differ by a meaningful margin. A benchmarking dataset has to record which state it captured, because comparing PetSmart's one-time price to Chewy's or Petco's subscription price compares different things. The subscribed and member views show in a logged-in session on a static ISP address. Stock is the second axis: availability keys to a selected store, and services like grooming are store-specific, so pin the store, match the exit to its region, and record it.
Selected store
stock and services key to it
Akamai sensor
product data gated
Shape score
session behavior
One-time vs subscription
Treats and repeat delivery
Which proxy type fits which job
| PetSmart job | Proxy type | Why |
|---|---|---|
| One-time price and stock monitoring | US rotating residential, region-matched, one exit per session | Akamai gates the request, Shape scores the session |
| Subscription and Treats price capture | Static ISP, logged in | Member pricing shows behind a login |
| Store-level stock and services | Sticky residential per store | Availability and grooming key to the store |
| Cross-retailer pet comparison | Rotating residential | PetSmart, Chewy and Petco in one pipeline |
| Treats account, cart | Static ISP | The session must keep one address |
| Parser tests against saved HTML | Datacenter or free | The homepage allows the read; only proves plumbing |
Rotating residential IPs pass Akamai and match a store's region, and ISP proxies hold one address for a subscription account. The two are compared in rotating vs static residential proxies.
Setup
Drive a real browser so the sensor sets _abck, keep the cookies, and behave, because Shape is watching (proxies for Playwright). Set the store, match the exit to its region, and record the store with every row. Capture one-time and subscription prices separately, logging in on a static ISP address for the subscribed view. Read reviews from the Bazaarvoice surface separately. Hold one exit per session.
Sizing
Size by store-SKU pairs times refresh frequency, then by sessions, because Shape scores the session: decide how many pages one session reads before the score tips, and add exits, with a sticky exit per store. Budget browser-level bandwidth (headless browser proxy bandwidth cost). Accounts are one static ISP address each, and our pricing is pay-as-you-go with a balance that does not expire.
Free versus paid for PetSmart
A free datacenter IP loads a PetSmart page, so it is fine for testing your parser, but Akamai's sensor and Shape's scoring cut a shared datacenter address off. Our free proxy list and proxy checker cover the parser test; the monitoring wants residential from $0.44/GB pay-as-you-go with no KYC behind a real browser. The line is in datacenter vs residential proxies.
Staying unblocked
- Do not rotate mid-session. Against Shape, an IP swap inside a session is a bot tell.
- Keep the sensor cookies. Discarding
_abckrestarts the Akamai layer. - Pin the store and match the exit. A blended-store price is a wrong number.
- Separate one-time and subscription prices. A one-time price labeled as the real price misleads.
- Watch where the session turns. Note when challenges begin; that is your per-session budget. The full list is in avoiding IP bans while scraping.
What a proxy does not do here
A proxy gives a browser a region-correct residential address and keeps accounts apart. It does not run Akamai's sensor, does not make a headless client behave for Shape, and does not turn the one-time price into the subscription price. Scraping petsmart.com runs against its terms of use, a risk that stays with you regardless of the IPs. What a residential exit does is let a well-behaved browser session look like a local shopper so Akamai admits it and Shape trusts it, after which capturing both price states and the store stock is the work. Test with the free proxy list, then compare PetSmart, Chewy and Petco on the same price state with residential from $0.44/GB.
Sources
- Akamai, Bot Manager: the request-level layer on PetSmart.
- F5, Shape / Distributed Cloud Bot Defense: the session-scoring layer whose marker we observed.
- HProxy test on 24 August 2026: plain GET requests to petsmart.com from a residential connection and a datacenter server, both returning HTTP 200 with Akamai sensor cookies (
_abck,bm_sz) and an F5 Shape marker, served through a modern hosting layer.