yala
← help

retargeting pixels.

drop a meta pixel on every landing in your workspace, fire standard events when fans tap services, build retargeting audiences from real listener intent. yala does the wiring; you run the ads.

how this works.

pixels are configured at the workspace level — one place, applied to every landing in the workspace automatically. the landing page injects the right script tags with your IDs, fires page_view on load and service_click on every DSP button click. consent-banner-aware: nothing fires until the fan opts in (off by default for EU).

supported pixels.

  • meta (facebook + instagram) — pixel ID + access token. CAPI signed events out of the box.
  • google ads — conversion ID + label.
  • google analytics 4 — measurement ID.
  • tiktok — pixel ID.
  • twitter / x — pixel ID + event ID.
  • linkedin — partner ID.
  • pinterest — tag ID.
  • reddit — pixel ID.
  • snap — pixel ID.
  • amazon ads — pixel ID.
  • plus 12 more — see the dropdown in workspace settings → pixels.

setting up your first pixel.

  • go to workspace → settings → pixels.
  • click + add pixel, pick a platform.
  • paste your pixel ID (and access token if it’s meta or tiktok with CAPI). yala stores tokens encrypted.
  • flip the active toggle. live within a minute (yala invalidates the landing’s edge cache).

what events we fire.

  • page_view — landing page load. once per fan-session.
  • service_click — fan clicked a DSP button. payload includes the service name + the link slug.
  • presave_committed — fan completed the pre-save OAuth flow. fires once per fan per pre-release.
  • email_captured — fan submitted the email form on a bio block or pre-save flow.

each event is fired through every active pixel in the workspace in parallel. meta CAPI events get signed with your access token; de-duplication is handled via the standard event_id between pixel + CAPI.

consent.

the consent banner is the gatekeeper. it’s on for EU IPs by default and configurable per workspace. options:

  • on by default for EU (standard) — banner appears for EU IPs only; rest of the world sees no banner and pixels fire.
  • on for everyone — banner appears for every fan. strict but most defensible.
  • off — no banner, pixels fire for everyone. GDPR-violating in most jurisdictions; your workspace, your legal call.
next upcustom domainsship on lnk.yala.la or wire your own (go.yourband.com). cloudflare SSL-for-saas; certs in minutes.