Proxies for Ulta cover the other half of the beauty market from Sephora, and the site is built a little differently. On 24 August 2026 we sent ulta.com a plain request from a home connection and from a datacenter server. Both returned the homepage, HTTP 200, behind Akamai (the AKA_A2 cookie and Akamai transform headers were present) with PowerReviews serving the ratings layer. Unlike Sephora, Ulta did not redirect by country or refuse the homepage, but the Akamai sensor still stands between a bare client and the product data, and the review data lives on a third-party surface. Both facts shape the proxy setup.
Ulta is a US beauty retailer with roughly 1,400 stores and a loyalty program, Ultamate Rewards, that stages its biggest sales by tier. The data people want from it is price, stock, launches and reviews, and each has a wrinkle: Akamai on the reads, PowerReviews on the reviews, and tiered early access on the launches.
What proxies work best for Ulta?
US rotating residential proxies behind a real browser for reading price, stock and reviews, and a static ISP proxy for a logged-in Ultamate account. Datacenter proxies are for testing only.
Akamai on the door, PowerReviews on the reviews
The homepage loading is not the same as the catalog being open. Akamai Bot Manager runs a sensor script that sets _abck only after its data validates, and every protected product and search request has to carry a valid one; a bare client that skips the sensor loads a cached homepage and then fails (how the _abck cookie works, how to scrape past Akamai). Akamai also reads the TLS fingerprint before any HTTP, which is why a real browser matters as much as a residential IP (what is JA3/JA4 fingerprinting).
The review layer is a separate story. Ulta serves ratings and reviews through PowerReviews, a third-party platform, so review data has its own endpoints, its own structure and its own rate limits. For a project that wants review sentiment or volume, that surface is the target, and it should be read and paced on its own budget rather than scraped out of the product page. This is the same architecture Bazaarvoice gives Costco, and treating the review layer as a distinct surface is what keeps the read efficient (proxies for Costco).
Ultamate Rewards stages the sale
Ulta's signature event is 21 Days of Beauty: a rotating set of 50 percent off Beauty Steals, a different one each day, with Platinum and Diamond members getting early access before the public opens (Ulta, 21+ Days of Beauty). Points multipliers and free shipping also skew toward the top tiers.
For a monitoring project this splits the work. Watching the public daily Steal, its price and whether it sells out is anonymous reading. Watching what a Platinum or Diamond account sees during early access is a logged-in session with a tier attached. The first wants rotating residential; the second wants a static ISP address per account, because a tier is an identity and the account has to persist.
Which proxy type fits which job
| Ulta job | Proxy type | Why |
|---|---|---|
| Price and stock monitoring | US rotating residential behind a browser | Akamai scores the session past the homepage |
| Review and rating collection | Rotating residential, PowerReviews surface | Reviews are a separate third-party endpoint |
| 21 Days of Beauty and launch tracking | Sticky residential per session | Frequent reads of a rotating deal, shopper pace |
| Ultamate account, early access, cart | Static ISP | Tier is an identity; the session needs one address |
| Comparison against Sephora | Rotating residential | Two beauty catalogs in one pipeline |
| Parser tests against saved HTML | Datacenter or free | The homepage allows the read; only proves plumbing |
Rotating residential IPs are real home connections that pass Akamai's reputation check, and ISP proxies hold one address for a tiered account. How the two differ is in rotating vs static residential proxies, and the other half of the beauty market is in proxies for Sephora.
Setup
Drive a real browser so the sensor sets _abck, and persist cookies across the run (proxies for Playwright). Point review collection at the PowerReviews surface directly rather than parsing it out of the page, and pace it separately. Keep a sticky residential window per session, behave like a shopper, and rotate between sessions. For accounts, one static ISP address each, held for the account's life, so an early-access session is coherent and unlinked.
Sizing
For reading, find how fast one residential IP reads behind a browser before Akamai challenges it, and add exits, budgeting the PowerReviews surface on its own rate. Because a browser is mandatory, budget bandwidth for full page loads (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 Ulta
A free datacenter IP will load a Ulta page, so it is fine for testing your parser, but Akamai's sensor and per-IP limits score a shared datacenter address down quickly. 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
- Keep the sensor cookies. Discarding
_abckrestarts the sensor and reads as a bot. - Read reviews from the PowerReviews surface. Scraping them out of the product page is slower and noisier.
- Pace launches from many exits. One address polling the daily Steal is the pattern a launch page catches.
- Isolate tiered accounts. One address, one device per Ultamate account.
- Watch the challenge rate. A rising 403 share means slow down or widen the pool. The full list is in avoiding IP bans while scraping.
What a proxy does not do here
A proxy gives a browser a clean residential address and keeps accounts apart. It does not run Akamai's sensor, does not raise an Ultamate tier, and does not open early access before the tier's window. Scraping Ulta runs against its terms of use, a risk that stays with you regardless of the IPs. What a residential exit does is let a real browser look like a US shopper so Akamai admits it, after which reading the review surface and the tiered sale correctly is the real work. Test with the free proxy list, then read price, stock and reviews with residential from $0.44/GB.
Sources
- Ulta Beauty, 21+ Days of Beauty: the daily 50 percent Beauty Steals and Platinum/Diamond early access.
- PowerReviews, ratings and reviews platform: the third-party review layer on Ulta.
- Akamai, Bot Manager: the vendor gating the product data.
- Cloudflare, JA3/JA4 TLS fingerprinting: fingerprinting before the first HTTP request.
- HProxy test on 24 August 2026: plain GET requests to ulta.com from a residential connection and a datacenter server, both returning HTTP 200 behind Akamai with PowerReviews present.