Carsharing System

Carsharing Referral and Sign-up Rewards: Campaigns You Can Add and Track

A carsharing marketplace has two growth problems that feel similar and are not the same. You want existing people to invite someone new. You also want a reward sitting on the act of registering, even if nobody issued a personal invitation. If both of those ideas live only in a poster at a depot, you cannot tell which campaign ran, who was supposed to receive a reward, or whether you should stop the campaign next month.

Ptaxi’s carsharing system documents both ideas in the marketing center. Refer and earn lets you add, edit, and delete campaigns for referring new users and drivers. Sign-up rewards lets you add, edit, and delete campaigns for new user and driver registration. On the statistics side, invitation statistics show detailed reward data for invitation campaigns, and registration statistics show detailed reward data for registration campaigns.

That is the working set: two campaign lists you maintain, and two stats surfaces you review. This post stays inside that set. It does not borrow promoter trees from another product line, and it does not invent a prize amount.

Two campaign types, because the trigger is different

Refer and earn is for invitations. The admin can create a campaign, change it later, or delete it. The documented targets are new users and drivers. You can run an activity aimed at bringing in a new rider, an activity aimed at bringing in a driver, or both, as separate campaigns you actually configure. A single campaign is not required to cover both audiences, and a referral is not documented as valid only if the new person completes a first trip. Confirm those details in staging and write them into the campaign rules you show the public.

Sign-up rewards is for registration itself. Again, you can add, edit, or delete activities for new users and drivers. The trigger, as named, is registering, not inviting someone else. That is why this is a second list and not a synonym for refer-and-earn. A person who finds the app in a search result and creates an account may belong on a sign-up campaign. A person who joins because an existing user invited them may belong on a referral campaign. Your policy has to say whether those can stack. The product does not.

The important admin habit is the same on both lists: campaigns are records you maintain. You add one when you want it to run, edit it when it should change, and delete it when it should not run anymore. Do not brief this as a permanent button that always pays a prize. If nobody created a campaign, do not promise a reward at the depot desk.

New users and drivers are both in scope — and that is all the claim

It is easy to over-specify the audience.

The campaigns mention new users and drivers. That is already two sides of a carsharing marketplace: people who will book, and people who will supply or drive the cars, depending on how your operation is staffed. “New user” is not further split into first-time renters versus returning accounts, and there is no documented lock that ties the new person to the referrer after sign-up.

Do not import a downline. Other Ptaxi product lines document account-manager or one-level promoter structures. This carsharing list does not document that structure here. A referral campaign is a marketing activity you add, edit, or delete. It is not a documented permanent promoter tree, and it is not a multi-level plan.

Do not invent an attribution window, a tracking rule, or a lock that prevents a second person from inviting the same new account. If your launch needs those rules, write them as policy and verify them in staging.

Invite mechanics themselves are also thinly specified. A particular messaging channel is not named, and a required invite-code format is not described. In a demo, create one referral campaign and one sign-up campaign, then show whatever invite or registration path the staging app actually presents. Stop at that path. Do not promise a social-network share card the module never named.

Statistics are how you tell whether a campaign is doing anything

Campaigns without a readout become folklore. The product gives you two matching surfaces.

Invitation statistics let you view detailed reward data for invitation activities. Use this when the question is “what did the refer-and-earn campaign actually award?”

Registration statistics let you view detailed reward data for registration activities. Use this when the question is “what did the sign-up campaign actually award?”

The wording is “detailed reward data.” The columns are not itemized. You are not promised a fraud flag, a clawback, or a cohort chart. In staging, open both statistics screens, export or screenshot the fields that exist, and put those field names in your weekly growth review. If a field you want is missing, do not invent it in a board report.

Keep the two readouts with the two campaign types. Invitation stats belong with refer-and-earn. Registration stats belong with sign-up rewards. If your team lumps them into one “growth number,” you will turn off the wrong campaign.

Coupons are a different marketing tool

Operators sometimes want every growth idea to live in one wallet action. Resist that in the briefing.

Passenger coupons are a different marketing tool, with their own configuration. A referral or sign-up campaign might, in your policy, eventually grant a coupon, or it might not. The feature description for refer-and-earn and sign-up rewards does not say that the reward is a coupon, a cash amount, or an in-app balance credit. It says you can maintain the campaigns and later review reward data.

So do not tell a buyer “referral always issues a coupon” or “sign-up always credits a balance.” Decide the reward form after you have walked a campaign in staging, and configure coupons, if you use them, in their own tool. Mixing the two in a script is how support looks for a coupon code on a campaign that never issued one.

What you still have to decide before you print a poster

The module is honest about what it automates, and quiet about what it does not. It does not set a reward amount, and it does not fix the reward form — do not assume cash, balance, or coupons. Confirm the fields in staging. It does not document automatic fraud detection: no duplicate-device rule, no self-referral block, no velocity cap. If abuse would hurt you, write a review habit. Someone looks at invitation and registration reward data on a schedule, and someone can edit or delete a campaign that is being gamed. That is a process, not a documented detector. It also does not document a multi-level plan, a locked referrer, or a downline commission schedule. Do not copy those rules from a designated-driver account-manager briefing into this carsharing page. And it does not name a messaging channel for the invite. Do not promise one.

A short ops checklist before the first campaign goes live

  • One referral campaign and one sign-up campaign are created in staging, then edited, then deleted, so staff know the maintenance path works.
  • Each live campaign states, in your own public rules, who it is for (new users, drivers, or separate campaigns for each) and whether referral and sign-up rewards can stack.
  • Reward form and amount are taken from the fields the staging build actually shows, not from a guess, and are approved as your policy.
  • Invitation statistics and registration statistics are opened, and the reward-data fields that exist are written into a weekly review sheet.
  • Coupons, if you use them, are configured in the coupon tool and are not described as the automatic output of every campaign.
  • No poster, driver leaflet, or sales slide mentions a downline, a locked referrer, an automatic fraud filter, or a named invite channel this module does not give you.
  • Someone is assigned to edit or delete a campaign that should no longer pay.

If you cannot name the person who will turn the campaign off, you are not ready to turn it on.

Close

Carsharing growth is easier to defend when a campaign is a record: added when you want it, edited when it changes, deleted when it should stop, and reviewed in invitation or registration reward statistics. Ptaxi’s carsharing marketing center gives you that for referrals of new users and drivers, and for sign-up rewards for new users and drivers.

It does not choose the prize, and it does not police abuse for you. Look at those campaign and statistics screens in Ptaxi’s carsharing system. If you want a demo, bring one rider-growth idea and one driver-growth idea, and walk each from a new campaign to the matching stats page. The useful test is whether your team can start, change, and retire the activity, and explain the reward only after they have seen the fields in the build.

Frequently asked questions

What referral and sign-up campaigns can a carsharing admin maintain?

In the marketing center, refer and earn lets you add, edit, and delete campaigns for referring new users and drivers. Sign-up rewards lets you add, edit, and delete campaigns for new user and driver registration. Campaigns are records you maintain. If nobody created one, do not promise a reward at the depot desk.

Where do we review what a campaign actually awarded?

Invitation statistics show detailed reward data for invitation activities. Registration statistics show detailed reward data for registration activities. The columns are not itemized in the feature list. Open both screens in staging and write the fields that exist into your weekly growth review.

Are the rewards cash, balance credit, or coupons?

The feature list does not say. It lets you create and maintain the campaigns and later review reward data. Do not tell a buyer that referral always issues a coupon or always credits a balance. Decide the reward form after you walk a campaign in staging. Coupons, if you use them, are a different marketing tool.

Does a referred user stay locked to the referrer, as in a downline?

No such structure is documented on this carsharing list. Other product lines have account-manager or one-level downline tools; do not import those rules here. A referral campaign is a marketing activity you add, edit, or delete, not a documented permanent promoter tree or a multi-level plan.

Related articles

Talk to our team about your platform

Tell us your market and business model. We will reply with a feature plan, a demo of the apps and a quote.