Personal activity views can summarize recorded interaction with a guest entry point for the signed-in person's authorized scope. The metrics, date range, filters, definitions, availability, and freshness displayed in the dashboard are the source of truth for that view. Do not assume every account sees the same funnel, field, device detail, session count, rating, payment, room-charge, or traffic-source measure.
Start with the displayed scope and period
Confirm the signed-in identity, active environment, selected period, and any filter before interpreting a metric. Live, Sandbox, and Demo records are separate. A report or activity result in one environment does not prove the corresponding state in another.
Use only the dashboard controls currently available to your personal scope. A business assignment does not automatically give access to another person's personal activity, Wallet, payment account, or private guest information.
Interpret activity as operational evidence, not settlement
A guest entry, interaction, amount selection, or payment start is not a completed payment. A redirect, thank-you screen, client event, dashboard card, or preliminary report is also not final provider settlement. Treat a payment as final only after the product has recorded the verified provider outcome in the authorized environment.
Recorded activity is useful for asking focused operational questions, such as whether a published entry point is being reached or whether the current flow may need review. Do not use it to promise guest intent, conversion, income, rating improvement, payment method availability, allocation, Wallet balance, or payout.
Protect guest and account data
Use only information available in the authorized view. Do not attempt to identify a guest from analytics or share private guest, payment, bank, password, verification-code, or token data. For a suspected data issue, report the authorized scope, environment, selected period, approximate time, and a non-sensitive error or reference.