Launch Perk
Publish a test perk to a brand's points of sale.
Preview
Live Perks
What the app is pulling right now from /manifest-index.
Create a brand
Publish a brand the feed doesn't have yet — a shop near a tester, for example. It goes live immediately, and a tester standing at one of its points of sale gets an alert exactly like any other brand's.
Brand details
Logo, points of sale and perks belong to one brand. Pick a brand to work on it.
Use transparent PNGs. The square mark is what a perk card shows, next to the brand name; the wordmark stands in for that name on the perk page itself. They appear in different places, so a brand never reads twice in one view.
Taken out of the demo feed but still in the brand's published manifest — restore any of them any time.
+ Add a point of sale / city to this brand
Metrics
What the network is carrying, and the anonymised activity recorded against it. Counts only — claims/redemptions are token references and telemetry is an event id in a time bucket, so nothing here can identify a person. Demo-data build-out for redemption & telemetry comes next.
Installs
How many phones opened the app and how far they got through setup. This is the only panel here that reports on the app rather than on a perk. An install is a phone, not a person: a reinstall counts again, and the key behind these counts changes every day — so nothing here can follow a phone from one day to the next, and no count can be sliced by brand, venue or perk.
| Day | Installs | Opens | Setup started | Setup finished |
|---|
| Build | Installs |
|---|
Transactions
What the recorded outcomes actually are. A redemption reported by the phone is not a verified sale — only a merchant-confirmed outcome counts as one.
| Source | Outcomes |
|---|
| Channel | Outcomes |
|---|
| Elapsed | Outcomes |
|---|
By Perk Type
The analytical record: what a tester actually gets. This is how we learn which types work best for a brand (claims → redemptions).
| Perk Type | Perks | Claims | Redeemed | Conv. |
|---|
By brand
Content coverage (perks, points of sale, logo) plus activity per brand.
| Brand | Market | Points of Sale | Logo | Perks | Claims | Redeemed |
|---|
Top Perks
Ranked by redemptions, then claims. Empty until devices (or the tester simulation) work this server.
| Perk | Brand | Type | Value | Claims | Redeemed |
|---|
Simulate a redemption demo data
Records an outcome without a device so you can demonstrate the loop (perk → presentation → redemption → metrics). Every row created here is flagged simulated and is never presented as a measured result — the brief requires synthetic demonstrations to be labelled. Use it for the demo, then Clear simulated before you capture anything you intend to treat as evidence.
Internal Admin users
People who can sign in to this Internal Admin and publish perks. Add one per demo operator — each signs in with their own name and password.
Account
Set a new password below — no need to enter the old one. It keeps you signed in on this browser.
Get the App
Where the team installs the Perks demo build. TestFlight installs and updates itself — no device IDs, no cables. Share the link below, or send someone this page.
Tester instructions
- Install TestFlight from the App Store (Apple's test-install app).
- Open the install link above on the iPhone — it opens TestFlight.
- Accept the invite, then tap Install.
- Open Perks and allow location ("While Using" is enough for matching).
- For the demo: Settings → Demo mode lets you stand at a store and simulate a redemption indoors. Anything recorded that way is flagged as demo data.
Tester feedback rarely mentions the build number, so the label above is what to quote. TestFlight builds expire after 90 days — re-upload before a demo that matters.
Edit this page
Paste the link from App Store Connect → TestFlight → (external testing)
public link, or an ad-hoc itms-services:// link.
The full tester guide is Docs/TESTERS.md in the repo — the note below is the
short version testers read next to the install button, and CHANGELOG.md is
what changed in the build.