CarGurus Proxies for Deal Rating Research

CarGurus is distinctive because it does not only show asking prices. It labels each listing with a deal rating against its own estimate of market value, and it shows how long a car has been listed and how its price has moved. For pricing analysts, dealers watching their market and researchers studying how algorithmic price labels shape buyer behavior, those labels are the interesting data. This page explains what to capture, how the rating changes over a listing's life, how to collect it at a considerate pace, and where a WeProx dedicated US mobile line fits in.

The fields that make CarGurus different

Each listing carries a deal rating on a scale from great deal through fair to overpriced, an instant market value estimate for that vehicle configuration and mileage, days on the site, price history, dealer rating and the usual vehicle facts including VIN. The rating is a function of the asking price against the estimate, and both move. A car can shift from fair to good without any price cut because the market value estimate for its segment rose. If you only record the label, you cannot tell those two stories apart. Record the asking price, the estimate and the label together on every observation.

Why observation timing matters

The most useful CarGurus datasets are longitudinal: the same VIN observed on a schedule until it disappears. That gives you days to sale, the price path, and whether a rating improvement preceded the sale. It also means your job cares about consistency more than speed. Check each tracked listing at the same rough time each day, from the same metro if you are comparing localized views, and treat a missing observation as missing rather than as sold. A listing that vanishes and returns under a new listing ID with the same VIN is a relist, and relists reset the days-on-market counter the site displays, which is why your own first-seen date is more reliable than the site's number.

Searches are defined by zip and distance. Build discovery sweeps from overlapping zip centers and deduplicate on VIN, then move each found VIN into a tracking list.

How to run it on a WeProx line

Run discovery and tracking as separate jobs. Discovery walks search results for each zip slice in one sticky session, with a moderate page size and varied pauses, rotating the line between slices. Tracking visits known listing pages in small batches, again one sticky session per batch. Keep one or two concurrent sessions per line and add lines to scale. The line is a single dedicated carrier device; its IP comes from the carrier's regional pool, where CGNAT puts many real phones behind the same addresses, so the site judges the traffic by conduct rather than by the IP alone. Conduct is what you control.

CarGurus's web app loads search results from JSON requests that the page makes after load. Reading those responses in a browser session is sturdier than scraping the rendered cards, but the formats are undocumented and change, so validate every record before storing it.

• Discovery: daily per zip slice, deduplicated on VIN.
• Tracking: daily per VIN until the listing is gone for several days.
• Store price, market value estimate and rating on every observation.

Metro and localization

Results follow the zip in the search. The visitor's location mainly affects default searches and the homepage. If you want to see what a shopper in Houston or North Carolina sees without entering anything, use a line in that metro. WeProx lines can move between our eight US metros free from the dashboard, which makes it easy to repeat a localized check in several regions.

Limits and troubleshooting

CarGurus's terms govern automated access; keep to public listing facts and do not copy dealer photos or descriptions. If rating fields come back empty while prices are present, the market value estimate may not exist for that configuration, which happens with rare trims. If a line starts getting challenge pages, slow it down and rotate less often rather than more. Errors immediately after a rotation are the re-attach window; wait and confirm the new exit IP.

Setting up a CarGurus proxy on WeProx

1. Order a WeProx line and copy host, port, credentials and rotation URL.
2. Build discovery sweeps from overlapping zip centers.
3. Deduplicate on VIN and move new VINs to a tracking list.
4. Track each VIN daily in small sticky-session batches.
5. Record asking price, market value estimate and deal rating together.
6. Rotate between batches and alert on missing fields.

CarGurus proxy questions