What a multi-app review should answer
A good review is short enough to repeat and specific enough to change what you do next. Start with the products that moved, then ask whether the movement came from a release, a campaign, a subscription event or a refund.
Which app moved?
See sales and revenue by product so a quiet day in one app does not hide a useful signal in another.
What changed?
Compare the current period with the previous one and look for a meaningful difference, not noise.
Did refunds alter the story?
Keep reversals visible beside sales so the number you discuss matches the number you can keep.
What is the next test?
Turn the review into one action: improve a store page, publish a guide or tell the right users about a release.
Why a portfolio view matters
Each provider dashboard is designed around its own data model. A portfolio view is designed around the maker's decision: which product deserves attention this week, and what evidence supports that choice? Revenue Bear is a review layer, not a replacement for App Store Connect.
Keep the source data honest
Use App Store Connect as the source of record for reconciliation. Review Revenue Bear regularly, annotate launches or pricing changes and treat refunds as product feedback rather than an accounting footnote.
Have more than one app? Open Revenue Bear for a focused App Store portfolio review.