Examples
Pages the product actually serves.
These are live pages the product serves in production — starting with 01A, a real artist whose album Hollow is out now. Follow any of them and you land where their fans land, on a page that is counting the visit. This page walks through what each one carries, what to try on it, and what the artist sees on the other side.
What a public page has to survive
Most fans never open your page in a real browser. A link posted to Instagram opens in Instagram’s. The same link in a TikTok bio opens in TikTok’s. These in-app browsers are slower than the real thing, restrict cookies, and can run no JavaScript at all.
So these pages are built not to need it. Every one is rendered on the server, every destination is an ordinary link, and the click is recorded before the redirect rather than after — so a fan who gets thrown out of the webview into the native Spotify app is still counted rather than lost. The test suite exercises that across seven in-app browsers with JavaScript switched off entirely, which is the harshest version of the real thing.
It is an unglamorous constraint and it decides more campaigns than design does. The pages below are what it looks like satisfied.
A real artist’s pages, carrying real traffic
Not a case study anybody commissioned. 01A is an artist whose album Hollow is out, whose pages these are, and whose fans land on them daily — accruing the same analytics any workspace does. Follow one and you are on the live page, not a rendering of it.
Bio page01ADark Alternative Rock · Industrial · Post-Punkdrp.cx/01a/links (opens in a new tab)Carries: Destination buttons (seven real profiles, from Spotify to 01a.rocks) · email signup · social links
Try this: Long-press any button and open it in a new tab. It still lands, and it is still counted — there is no client-side tracking script to lose on the way out.
Release pageHollowThe new album — 20 tracksdrp.cx/01a/hollow (opens in a new tab)Carries: Destination buttons (Spotify, Apple Music, YouTube) · email signup · social links
Try this: Pick Apple Music rather than Spotify — the choice is what gets measured. Each button is an ordinary link through the click-recording endpoint, so the click is counted before the redirect and survives even a browser with scripts switched off.
The page types one catalogue does not exercise
A single artist does not need every kind of page, so these come from the seeded demo workspace. The pages render exactly as a published one does; the artwork is original typographic composition and the traffic behind them is fabricated, which is why they are kept separate from the set above.
- Bio pageNorth StaticEverything in one placedrp.cx/north-static/links (opens in a new tab)
Carries: Hero (featuring Signal Loss) · release list (three releases) · tour dates · social links · email signup
Try this: Tap through to Signal Loss from the hero. A bio page and a release page are one system — the visit to each is counted separately, which is how the demo report below can tell profile traffic from release traffic.
- Pre-release pageAfterimageOut 14 days from nowdrp.cx/north-static/afterimage (opens in a new tab)
Carries: Countdown · destination buttons (all four still pending) · email signup · a notice
Try this: Notice what the page refuses to do. The release does not exist yet, so no destination URLs are invented — the page says they appear on release day — and the signup is labelled a release-day reminder, with a notice stating plainly that it is not a pre-save and touches no music-service account.
- Release pageSignal LossSingledrp.cx/north-static/signal-loss (opens in a new tab)
Carries: Destination buttons (Spotify, Apple Music, YouTube Music, Bandcamp) · email signup · social links — plus a video slot the demo leaves deliberately empty, which is what an artist sees before adding a URL
Try this: Open it again with ?c=poster-qr on the end. The page looks the same, but the visit is now recorded against the Poster QR campaign — one of four seeded variants (TikTok Bio, Instagram Story, Poster QR, Newsletter) — and a signup made on that visit carries the attribution with it. The artist is fictional, so the buttons redirect to catalogue addresses that go nowhere real; the recording works exactly as it does on 01A’s page above.
Every page type the product ships
Eight, as of today. Where a live example exists it is linked; where none exists yet, that is stated rather than papered over with a mock-up — every type is available to build on the free plan.
Release page
One address for a release that is out: every streaming service as a button, the click counted before the redirect.
Pre-release page
The same address before the music exists — countdown, release-day email reminder — which becomes the release page at the moment you set.
Bio page
The one link in your profile: latest release first, then everything else, measured well enough to know what profile visitors want.
Ticket page
A show or a tour on one address, pointing fans at wherever the tickets are sold.
No live example yet — build one on the free plan.
Reward page
Something fans unlock — typically with an email signup, consent recorded — rather than something everyone sees.
No live example yet — build one on the free plan.
Playlist page
A playlist across services, for the artists and curators who live by them.
No live example yet — build one on the free plan.
Podcast page
An episode or a show, with the listen-on buttons podcast apps never agree on.
No live example yet — build one on the free plan.
Content page
Anything else with an audience — a video, a zine, a press kit, merch.
No live example yet — build one on the free plan.
Mechanics you can check from the URL bar
None of this requires an account, a screenshot, or trust. Each behaviour below runs on the pages above, right now.
- Campaign attribution rides a visible parameter
- A campaign link is the page address plus
?c=and the campaign’s slug — nothing hidden, nothing fingerprinted. Open the Signal Loss page with?c=poster-qrand the visit lands in that campaign’s numbers; an email signup made on that visit carries the same attribution. The demo release has four seeded variants:tiktok-bio,instagram-story,poster-qr,newsletter. - Short links for QR codes and print
- Every page also answers at
/r/plus its short code — trydrp.cx/r/meet01a. That is the form printed on posters: it redirects to the full page, carries any campaign parameters through the hop, and marks the arrival as a scan — so a QR code keeps working even after the page behind it changes. - Email capture that says what it is doing
- Every signup block shows its consent wording before the address leaves the form, and the address is confirmed from the fan’s inbox before it counts. On a pre-release page the same block is labelled a release-day reminder — the Afterimage page states outright that it is not a pre-save and touches no music-service account.
- The free plan is visible, not hidden
- Both example workspaces run on the free plan, so every page above ends in a “Made with DropRoute” credit. Paid plans remove it. Showing you the free page seemed more honest than showing you the one you would not start with.
- Rendered fresh for every visitor
- Public pages are never served from a cache, because destinations can be scoped by territory and routing rules can vary a page by country, device, or campaign. These example pages carry no such rules — what you see is what everyone sees — but the per-request rendering they run on is the same machinery.
What the artist sees on the other side
This is the dashboard, not a picture of it: the same components the app renders, reading the same daily rollups, for the demo workspace. Hover the chart for a day’s exact figures, or the information icon beside any metric for what it counts. The traffic behind these numbers is seeded — they are a demonstration, not a customer’s results, and a page arguing for honest measurement should say so.
Inside a workspace, the same rollups break down further: per link, per campaign, per service, and by location, device, and referrer, with exports that hand you the raw figures. The demo’s seeded traffic populates the country, device, and campaign views; every metric’s definition is one click away.
- Human visits
- 26
- Bots and previews excluded
- Destination clicks
- 16
- CTR
- 61.5%
- Clicks ÷ human visits
- Fan signups
- 0
Asked, reasonably
- Are these real pages or screenshots?
- Real pages, served by the product in production. 01A is a real artist whose album Hollow is out; those pages carry real traffic. North Static is a seeded demo workspace for the page types a one-artist catalogue does not use — its pages render identically, but the artist and the analytics behind them are fabricated, and they are labelled as such.
- Can I see the analytics without creating an account?
- The report on this page is the real dashboard component reading the demo workspace’s own daily rollups — not a mock-up. The full dashboard, with per-link, campaign, service, location, device, and referrer breakdowns, requires a workspace, which is free to create.
- Why do these pages say “Made with DropRoute” at the bottom?
- Both example workspaces are on the free plan, and the free plan carries a footer credit. Every paid plan removes it. It seemed more honest to show you the free page than the one most visitors would not start with.