# Data 360 Limits Source Precedence

Use this rule whenever a Data 360 answer depends on limits, guidelines,
licensing, billing, feature availability, connector counts, query quotas,
stream volume, or usage calculations.

## Default Source Order

1. Use current **Data 360 Limits and Guidelines** first.
2. When that page points to **Data Services Billable Usage Types for Data 360**,
   follow that path for contract, usage, and billing-sensitive quantities.
3. Use the org's license, Digital Wallet, contract, or Account Executive
   confirmation when the current Data 360 docs route a limit to entitlement or
   billable usage instead of naming a fixed platform number.
4. Use **Customer Data Platform Limits and Guidelines** only when the user
   explicitly says Customer Data Platform, CDP, legacy CDP license, or the
   target org is known to operate under that legacy license.

## Answering Rules

- Do not apply legacy CDP numeric limits to a current Data 360 or Data Cloud
  license by default.
- If both current Data 360 and legacy CDP limits are relevant, label the CDP
  value as legacy and present it as comparison only.
- If the current Data 360 limits page says "See Data Services Billable Usage
  Types for Data 360", do not replace that with an older CDP number.
- For connector and multi-org questions, separate standard CRM connections,
  Data Cloud One companion connections, Data Cloud One Additional Connection
  licenses, and legacy CDP CRM-org limits.
- If the license posture is unknown, answer from the current Data 360 docs and
  call out that a legacy CDP org can differ.

## Proof Habit

For customer-facing guidance, include:

- source used: current Data 360, Data Services usage, legacy CDP comparison, or
  org/contract proof
- whether the limit is a hard platform limit, soft guideline, entitlement,
  billable usage path, or Account Executive-adjustable allowance
- the next proof step when the docs route the answer to license/contract data