Carsharing Admin Stats: Passengers, Orders, Invite Rewards, and Sign-up Rewards
A platform with more than one campaign and a growing passenger list needs a place to see totals versus people who actually place orders, and whether invite and sign-up rewards are actually paying out. Ptaxi’s carsharing system documents four admin stat screens under data statistics: passenger statistics, order statistics, invite statistics, and registration statistics.
This article stays on those platform-level admin charts. It is not a finance-ledger post, and it is not a driver performance workbook. Invite and registration campaigns already have their own article. These screens are the place that reports the reward data.
What passenger and order statistics actually show
Passenger statistics let staff view total passengers and statistics on passengers who have placed orders, plus related data charts. That split is the useful one: a headcount of everyone on the platform, and a view of the people who actually order. The list does not name the chart types, a date-range control, a conversion formula, or a CSV export. Do not brief a “weekly KPI pack” as a product name. Open the screen in a demo and write down the actual breakdowns. Until then, train it as totals, ordering-passenger stats, and related charts.
Order statistics let staff view total orders and order details. Keep this as a totals-and-details view, not as a finance screen. Order accounts and the payment ledger are different screens. If a buyer wants revenue by company or a payment ledger, schedule that separately. Here, the documented facts are the order total and the order details on the statistics screen. Confirm in a demo which detail fields actually appear. Do not invent them.
The tradeoff is visibility without a packaged report. You can see how many passengers you have, how many of them order, and how many orders exist, with details and charts the build actually draws. You cannot, on the documented facts, download a weekly workbook or quote a built-in conversion rate. If someone on the operations team needs a spreadsheet, they will have to make it themselves after looking at these screens. Do not promise an export the list does not describe.
Use the passenger split in a briefing the way a growth meeting would use it. A rising total with a flat ordering-passenger number is a different problem from a small list where almost everyone orders. The screen gives you both views, plus charts. It does not, by itself, tell you why the split looks that way. Keep the interpretation in the room, and keep the product fact to totals, ordering-passenger stats, and related charts.
The same discipline applies to order statistics. Total orders answer how much work moved. Order details answer what is inside that total. The list confirms both and does not publish the detail schema. A briefing that invents status breakdowns, city splits, or revenue on this screen is already off the facts. Open the details, copy the fields, and only then decide whether this screen is enough for the weekly meeting or whether finance still has to be a second stop.
Invite and registration statistics report on campaign rewards
Invite statistics let staff view detailed reward data for invite campaigns. Registration statistics let staff view detailed reward data for registration campaigns. These are the reporting counterparts to the campaigns already described in referral and sign-up rewards. One pointer is enough. Do not retell how those campaigns are set up.
The hook here is the reward data. A growing passenger list can have an invite campaign and a registration campaign running at the same time. These two screens are where staff look at the detailed reward data for each. The list does not name the columns, the chart types, or an export. Open both screens in a demo, write down the breakdowns, and brief them as detailed reward data until you have those notes.
Do not import designated-driver performance-stats wording. That product has a different post about driver daily, weekly, and monthly earnings. This article is platform-level admin charts for passengers, orders, and campaign rewards, not a driver earnings workbook.
The same caution applies to campaign setup. If a buyer wants to know how an invite reward is configured, or who is eligible to sign up, point at the rewards post and come back. Today’s screens answer a narrower question: what reward data the statistics views actually show once a campaign is running.
Treat invite statistics and registration statistics as two reports, not as one blended reward dashboard. The list gives them separate screens and separate campaign types. If both campaigns paid out in the same week, look at both screens. Do not brief a combined “growth rewards” total the list does not describe. And do not turn the reward data into a retell of how a user joins a campaign in the app. That setup lives in the earlier rewards post.
A practical review can stay short. Open passenger statistics and write down the total and the ordering-passenger stats. Open order statistics and write down the total and the detail fields you see. Open invite statistics, then registration statistics, and write down the reward data on each. That loop uses only what the list confirms. It does not need a packaged weekly report or an export to be useful, and you should not invent either just to make the meeting feel more formal.
What these screens are not
They are not a finance article. Order accounts and the payment ledger remain different screens. They are not a retell of companies, agents, and admin roles. Those already have their own post. They are not a place to invent conversion formulas or a named weekly pack.
Keep the walkthrough on the four statistics screens. If a buyer starts asking about payouts, company structure, or campaign setup, point at the right article and come back to the totals and the reward data.
The other confusion to head off is role-based access. This article does not retell companies, agents, or admin roles, and the statistics list does not say which role can open which chart. If a platform has more than one company, ask in the demo who can see platform-level totals and write that down. Do not import data-scope wording from another product line just to fill the gap. The facts you can already use are the four screens themselves: passengers, orders, invite rewards, and registration rewards. Everything else belongs in a demo note or in another post.
What not to promise on admin stats
Do not invent chart types, date-range controls, CSV export, conversion formulas, or a “weekly KPI pack.” The list confirms totals, ordering-passenger stats, charts, order details, and campaign reward data. Operators should open the screens in a demo and write down the actual breakdowns.
Do not treat these views as driver performance stats. Do not retell referral campaign setup, company and agent roles, or finance ledgers. Do not invent a passenger-facing dashboard.
A short ops checklist before you brief the app
Keep this to one page.
- Open passenger statistics. Note total passengers, statistics on passengers who have placed orders, and the charts the screen actually draws.
- Open order statistics. Note the order total and what the order details include. Do not move into order accounts or the payment ledger on this card.
- Open invite statistics and registration statistics. Confirm each shows detailed reward data for its campaign type. Point at the referral and sign-up rewards post for campaign setup, then return.
- Write down every breakdown you see. Do not brief an export, a date-range control, or a conversion formula unless the build shows one.
- If a buyer compares these screens to driver performance stats in another product, say this is platform-level admin reporting and stop.
If a script starts promising a weekly KPI pack or a downloadable workbook, cut it back to four admin screens: passengers, orders, invite rewards, and registration rewards.
Close
Carsharing admin statistics are four screens: passengers (total versus those who place orders, plus related charts), orders (totals and details), invite-campaign reward data, and registration-campaign reward data. They are totals and campaign reward views, not a driver performance workbook, and the list does not document an export or a packaged weekly report.
That is enough to brief a platform that needs to see whether passengers actually order, and whether invite and sign-up rewards are paying out. It is not enough to sell a KPI pack the list does not describe. Look at the data statistics screens on the carsharing system product page. If you want a walkthrough, ask for a demo and bring the current passenger total, one day’s orders, and one invite or registration campaign, then write down the breakdowns the screens actually show.
Frequently asked questions
What do carsharing passenger statistics include?
Passenger statistics let staff view total passengers and statistics on passengers who have placed orders, plus related data charts. That split is the useful one: a headcount of everyone on the platform, and a view of the people who actually order. The list does not name the chart types, a date-range control, a conversion formula, or a CSV export. Open the screen in a demo and write down the actual breakdowns.
Are order statistics the same as order accounts or the payment ledger?
No. Order statistics let staff view total orders and order details. Order accounts and the payment ledger are different finance screens. This article stays on the statistics view. Confirm in a demo which detail fields actually appear, and do not invent them.
What do invite statistics and registration statistics show?
Invite statistics show detailed reward data for invite campaigns. Registration statistics show detailed reward data for registration campaigns. They report on the campaigns already covered in the referral and sign-up rewards post. The list does not name the columns, the chart types, or an export. Write down the breakdowns you see in a demo.
Is this a driver performance workbook, and can staff export a weekly KPI pack?
No. These are platform-level admin charts, not a driver daily, weekly, or monthly earnings workbook from another product line. The list does not document CSV export, a conversion formula, or a packaged weekly report. Do not sell a “weekly KPI pack” as a product name. Operators should open the four screens and write down the actual breakdowns.