Trip.com Data Scraping

Why we raise the data-landing question here

Trip.com is an internationally operated platform. Our China platform page sets out why the constraint on China-linked data collection is cross-border transfer rather than collection, and why the question that decides feasibility is where your data lands rather than which platform it came from.

We raise it here for one reason: it costs nothing to ask and a great deal to discover late.

• If your recipient is outside China and the data is commercial listing data from an international platform, the position is likely straightforward — but likely is not a basis we will assert on your behalf.
• If your programme also covers China-domestic platforms, the question applies directly and the China page answers it properly.
• If you already hold a transfer position for your own data, say so on the first call. It settles the conversation immediately.

We collect no personal data in any market, which removes the heaviest category from the analysis. What remains is a question for your counsel rather than for us, and cleared_by_actowiz is false on any route assessment we issue, as it is on every China-adjacent engagement.

What this is not

This is not a reason to avoid the platform. It is a question we would rather ask before quoting than have you find in a compliance review afterwards.

Beyond that, it is standard OTA discipline

The mechanics are the ones our Agoda and Expedia pages set out, and we apply them unchanged rather than restating them at length.

• The record is a rate plan, not a hotel. Refundable and non-refundable are different products, and a single hotel price averages things a guest chooses between.
• Both dates travel with every record. Stay date and observation date, with lead time derived — because the same night costs different amounts seen 90 days out and 3 days out.
• Member and app-gated rates are null with a reason where gated, with gated_share reported. The public rate is never substituted.
• Currency depends on the market observed from, so it is recorded with FX stamped at the observation.

Where it is strongest

Asian property coverage, particularly outside the markets where the Western OTAs are deepest. For a hotel group or an analyst working across Asia-Pacific, it covers properties that a Western-OTA-only panel will miss — the same coverage argument our regional aggregator page makes about delivery.

What we do not produce

• Occupancy or bookings. Not published, and not inferrable from rate availability.
• Guest or reviewer identity. Review counts and ratings only.
• A rate behind a signed-in session. No account creation, no client credentials, no app emulation — the same boundary as on Agoda.
• A legal position on your behalf. We state the constraint; we do not tell you it does not apply to you.

On struck-through prices

Where a reference price is displayed alongside a rate, it is captured as reference_price_displayed and not treated as a prior price. Building a discount series from displayed reference figures manufactures history out of marketing copy.

Genuine rate history comes from our own repeated observation of the same stay dates, which is the only source that knows what a rate actually was.