Pages

Link bundles for a bio

A bundle is a page of buttons, each one a real short link with its own analytics. You choose the order, the labels, the thumbnails and the theme, and the page lives on your own domain rather than on a platform that puts its brand above yours.

Because every button is a link, everything the link engine does applies: geo targeting so an international audience sees the right storefront, device rules so a button opens an app rather than a web page, expiry so a seasonal button disappears on its own, and full per-button click reporting.

• Buttons ordered and themed to match your brand
• Your own domain with automatic SSL
• Per-button click stats rather than one page-level number
• Geo, device and expiry rules on individual buttons

Published pages on a short link

Posts let you write a page in markdown and publish it directly onto a short URL. It is deliberately simple: a heading, text, images, links. The use case is the thing you would otherwise put in a shared document — an event detail page, a set of instructions on packaging, a temporary notice, a landing page for a campaign that does not deserve a full site build.

The page is served from the same fast path as redirects and can be edited at any time without the URL changing.

• Markdown authoring with immediate publish
• Served on your own short domain
• Editable after sharing, with the URL unchanged
• Password protection where the content is not public

Designed to be measured

A bio page usually fails quietly: it gets traffic, but nobody knows which button earned it. Here the page reports its own visits and each button reports its clicks, so you can see the ratio between arriving and acting rather than guessing.

Conversions carry through as they do elsewhere. If a button leads to a signup, the click identifier connects the two, and you can compare buttons on outcomes rather than on taps.

• Page visits and per-button clicks reported separately
• Bot traffic excluded from the human counts
• Conversion attribution per button
• Exportable as CSV like any other link data

Consistent with the rest of your links

Bundles and posts sit inside the same folders, carry the same tags, respect the same team roles and appear in the same search as every other link. There is no separate product to administer and no second place to check permissions.

Folder defaults apply here too, so a bundle created inside a campaign folder inherits its domain and campaign tagging automatically.

• Same folders, tags and search as ordinary links
• Team roles and per-link permissions apply unchanged
• Folder defaults inherited on creation

Building them programmatically

Bundles and posts are available through the REST API, which matters when the content is generated rather than hand-written — a page per event, per store or per product, created by a job rather than a person.

Bulk creation and CSV import cover the same ground when you would rather work from a spreadsheet than write code.

• API endpoints for creating and updating bundles and posts
• Bulk creation from a sheet
• Webhooks on click events for downstream systems

Portability

Because a page lives on your domain, moving it later is a DNS decision, not a migration project. Content exports, links export, and analytics export, so nothing you build here becomes a reason to stay.

That is the intended trade: the convenience of a hosted page without the usual cost of handing your audience's first click to somebody else's brand.

• Your domain, your URLs
• Full export of content and analytics
• No platform branding on the page

Questions

Put a bio page on your own domain, with stats on every button.