Creator (UGC) attribution
To measure which creators drive installs and revenue, tag their links with a creator_id, or by their name in the link’s path. The creator id is captured on the click and resolved to the installing device, so revenue rolls up per creator in the dashboard.
The short form
The simplest creator link is the creator’s name on the end of your redirect page:
https://app.yoursite.com/jane // creator_id becomes "jane"
Nothing else needed — the snippet already reports the path, so the last segment is read as the creator when no creator_id is present. Use it where a query string would get mangled: a bio link, a QR code, read aloud in a video.
That works when the redirect page sits at the root of its domain. One segment is read as a creator; anything deeper is treated as a page, and ordinary names (privacy, docs, download and the like) are skipped so your own pages never turn into creators.
One piece of hosting setup
The short form is the only part of astronaut that asks anything of your hosting, and it asks once: the page has to answer on paths you never routed.
The snippet cannot do this for you, and it is worth knowing why. Routing happens on your host, before the page is sent — the tag only runs after a page loads. So if /jane returns a 404, the browser never receives your page, never receives the tag, and no click is recorded at all. There is no error to see anywhere; attribution simply stays empty.
If your site is on a builder
Framer, Webflow, Squarespace, Carrd and Wix do not let you serve arbitrary paths, so the short form cannot work there. Use ?creator_id=jane on a page you already have — it attributes identically — or put the redirect page on a subdomain you host yourself.
If you control the hosting
On Vercel, with a static page, a catch-all rewrite:
// vercel.json
{ "rewrites": [{ "source": "/(.*)", "destination": "/index.html" }] }On Next.js, a catch-all route rendering the same page:
// app/[...slug]/page.tsx
export const dynamic = "force-dynamic";
export { default, metadata } from "../page";dynamic is declared rather than re-exported — route segment config is parsed per route and cannot be forwarded. On Netlify the equivalent is /* /index.html 200 in _redirects; Cloudflare Pages uses the same file.
On a subdomain that does nothing but redirect, answering everywhere costs nothing: a mistyped name still reaches the App Store, and records a click with no creator rather than the wrong one. Test with a path you have never used — /zzz-test — and check it returns the redirect page. A 404 can be cached, so use a fresh path when re-testing after a fix.
If the redirect page is not at the root
Hosting it under a path instead? Say where, and the segment after it is the creator:
<script src="https://astronaut.sh/t.js"
data-tracking-id="naut_..."
data-creator-base="/app"></script>
https://yoursite.com/app/jane // creator_id becomes "jane"Declaring the base rather than letting us guess it means everything under that path is a creator link and nothing outside it ever is — so a section of your site called /app-store or /apply cannot be mistaken for one. A nested base (/l/r) works the same way. Either way, if it is unsure it records no creator rather than guessing.
The long form
https://yourpage.com/go ?utm_source=instagram &utm_medium=ugc &utm_campaign=creator_program &utm_content=hero_button // creative variant — NOT the creator &creator_id=jane // explicit creator id (wins)
Order of precedence: creator_id, then the path. The explicit parameter always wins, so adding short links changes nothing about the links you already have.
utm_content is not read as a creator. It means the creative variant, and treating it as a name put placement labels like link_in_bio and demo-header in the Creators table beside real people. It is still recorded, under content, where it belongs.
Give each creator their own value (creator_id=jane, creator_id=mike, …). These links still go through the attribution snippet, so the same click also records source and campaign.
Reading it
The Creators card on the dashboard shows users and revenue per creator, right beside your traffic sources. A creator id is a stored verbatim (lowercased) - so jane and Jane roll up together, while jane.doe stays distinct.