yala
← help

the 8 link types.

yala has eight link types, each with its own landing page layout. picking the right one matters because fans tap differently on different pages. this page tells you which one to pick.

every link type uses the same redirect engine and the same scanner. the difference is what the landing page does. choose by what fans should do, not by what you’re promoting.

release.

for the album / track that’s already out.

the most common type. a fan scans your QR code on a poster, taps the link, and lands on a page that says “listen on:” with a list of buttons (spotify, apple, youtube music, bandcamp, deezer, etc). they tap their preferred service. they’re listening within two seconds.

what fans see. palette-themed page, big cover art, title, listen-on rows. each row has a brand-tinted favicon chip + a small CTA color from the palette. mobile-first, edge- cached. no signup required, no popup, no banner ad.

what you fill in. a spotify or apple URL (yala scans the rest), a title (auto-filled from the scan), a slug. that’s the minimum. optional: a fallback URL for territories where no DSP matched, a custom share-card image.

pro tip. upload your real cover art before publishing. yala extracts the palette from it; the landing page themes itself accordingly. a black square gives you a black landing — accurate, but not flattering.

pre-release.

for the release dropping in a few weeks.

same vibe as release, with two extras: a countdown to release day and a pre-save button. fans tap pre-save, grant spotify access, and on release day yala auto-saves the track to their library. no nagging emails, no third-party in the middle.

what fans see. countdown above the listen-on buttons, pre-save CTA on top. on release day, the page silently flips to a regular release landing — the countdown disappears, the pre-save row goes away, listen-on buttons stay.

what you fill in. the pre-save URL (spotify URL of the future track), release date + time, and the standard title + slug. you can also set a subtitle that shows above the countdown — something like “next single from the album.”

follow-me.

one link to all your platforms — for tour posters + email footers.

the artist-profile link. fans see “follow on:” instead of “listen on,” with a list of platforms you publish on. seeded automatically from the artist URLs you save in workspace settings — change those once and every follow-me link in your account updates.

when to use it. tour posters, email signatures, instagram bios. anywhere you want fans to find your artist profile across the world’s platforms in one tap.

what you fill in. a title (usually your artist name), a slug. yala uses the workspace artist profiles for the destinations.

bio page.

your linktree replacement.

a single page that lives at the URL in your social bio. profile avatar + display name at the top, a stack of blocks below. you compose the blocks: links, images, videos, merch cards, release embeds, social icon rows, email capture.

what fans see. a clean, palette-themed feed of whatever you put on it. blocks render in the order you set; drag to reorder.

what you fill in. your display name + a short bio + an avatar (yala uses the artwork upload for this). then click + add block and pick a block type.

the block types.

  • link — a simple labeled URL.
  • image — full-width image, optional caption, optional tap-through URL.
  • video — youtube, vimeo, loom embed.
  • merch — product card with image, name, price, buy button.
  • release embed — pulls one of your own yala links and shows it inline (cover + scrollable DSP buttons).
  • social — a row of platform icons with URLs.
  • email capture — collect emails for broadcasts. consent-banner-aware.

podcast.

for an episode, not a show.

an episode landing. listen-on buttons across apple podcasts, spotify, overcast, pocket casts, plus episode metadata: season, episode number, description, runtime.

what fans see. hero with episode artwork, the episode title, a small “S3 · E12 · 43m” line, the description, then the listen-on rows.

what you fill in. the episode URL (apple podcasts works best for the scan), season + episode numbers, description, runtime, title, slug.

playlist.

a curated set across multiple platforms.

for the playlist that lives on more than one DSP. fans see “open in:” with the platforms you publish on, plus the curator credit and track count.

what you fill in. the spotify or apple playlist URL (yala scans the others), curator name, track count, description, title, slug.

ticket.

for a live show.

an event landing. instead of DSP buttons, fans see a list of ticket vendors (ticketmaster, dice, eventbrite, ra, see tickets, tixel). each one is its own row. above the rows: venue, city, date + time, optional event description.

what you fill in. event name (the title), venue, city (optional), date + time, then a list of vendors. each vendor is “label + URL” — you can label them whatever you want (“ticketmaster — UK”, “dice — EU”).

content.

one URL in, one 302 out.

the plainest type. no landing page, no buttons, no countdown. just a short URL that redirects to one destination. for newsletters, blog posts, sales pages, anything you’d otherwise paste a long URL for.

what you fill in. a destination URL, an optional title (only used for analytics + the share card), a slug.

next upscanner + DSPshow the scan works under the hood. odesli vs direct adapters. when to scan vs add manually.