Revenue analytics

Separate revenue for apps that share a payment provider.

One payment account can serve several projects. Organize its products into apps so you can see which project is growing, without losing the view of your whole portfolio.

Organize your apps Read the setup steps ↓
Revenue (1m)USD · All portfolio
Revenue (1m)$6,842.00After $198 in refunds

Apps

GROSS$7.04K
  • Focus Timer$4,220
  • Daily Notes$2,820
Product example · illustrative data
THE PROBLEM

Does this sound familiar?

  • Revenue from several apps is mixed together in one account.
  • You cannot tell which project deserves your next week of work.
  • Every new app adds another report to maintain manually.

Separate results for each app. One place to review the portfolio.

THE SETUP

How to make it work.

  1. Let incoming events discover your products.

    Connect your provider and receive events. Products without a real app assignment remain under Unassigned app. You can start organizing the data already collected without inventing a new payment flow.

  2. Create an app for the project.

    Open Apps and start Create app. Give the project a unique name and select the products that belong to it. The configuration flow includes a preview of matching data already received.

  3. Keep prices with their parent product.

    Assign the app at product level. Monthly, annual and other prices inherit that assignment; they cannot belong to different apps. Each price can still have its own notification label.

  4. Apply readable labels and save changes.

    In Manage products, review the provider → product → prices hierarchy. Use search, app/source filters and bulk selections to prepare edits. Save changes applies the assignments together; Discard removes unsaved edits.

  5. Compare each app with your portfolio.

    Use the dashboard App selector to inspect an individual project, then switch back to All portfolio. Filter by source and period to compare like for like. Matching historical revenue and subscriptions already collected follow product reassignment.

IN PRACTICE

Organize once, use the same app context across the product.

Compare the projects you actually run.

Keep web and mobile products together when they represent the same app, or separate unrelated projects even if they share a Stripe account.

Recognize products in Telegram.

Product labels are inherited by prices unless you set a price-specific label. Notifications use the app and label rather than forcing you to interpret a technical identifier.

Reorganize without resending old alerts.

Changing a product assignment moves matching local revenue, subscription projections and MRR history. It does not send the old Telegram notifications or forwarding deliveries again.

Questions about this setup.

Can two apps share the same Stripe account?

Yes. Assign distinct Stripe products to their respective apps. The Stripe account can remain the same.

Can monthly and annual prices go to different apps?

Not when they belong to the same product. Prices follow the product’s app. You can use different price labels for readable notifications.

What happens to data received before I assign products?

Matching data already in PushTheSales is reattributed when you save the assignment. This does not fetch older data from your payment provider.

Will reassignment duplicate revenue?

It changes the app attribution of matching local records rather than creating another copy of the payment. Your portfolio total is not increased by moving a product.

PUT IT INTO PRACTICE

Separate results for each app. One place to review the portfolio.

Start in PushTheSales, then follow the setup for your provider.

Organize your apps