> ## Documentation Index
> Fetch the complete documentation index at: https://help.fanaura.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Glossary

> A comprehensive glossary of every term, concept, and abbreviation used across the Fanaura platform.

This is your go-to reference for every term you will encounter while using Fanaura. Whether you are setting up your first flow or analyzing campaign results, this glossary has you covered. Terms are listed alphabetically.

<Info>
  Click on any term to expand its full definition. Use your browser's search (Cmd + F / Ctrl + F) to jump to a specific term quickly.
</Info>

<AccordionGroup>
  <Accordion title="Asset">
    Any content an artist creates in Fanaura. There are four types of assets:

    * **Music**: A single, EP, album, or any music release.
    * **Tour**: A tour date or series of tour dates with venues and ticket links.
    * **Merch**: A merchandise product synced from Shopify or created manually.
    * **Extra**: Special content that does not fit the other categories -- giveaways, exclusive videos, behind-the-scenes content, contests, and more.

    Each asset gets its own smart link for data collection and fan engagement.
  </Accordion>

  <Accordion title="Blast">
    A one-time broadcast message sent to a targeted audience. Blasts can be:

    * **Email blasts**: Sent to your fan email list or a filtered segment.
    * **SMS blasts**: Sent to your opted-in SMS audience.

    Unlike flows (which are automated and ongoing), blasts are manual, one-time sends.
  </Accordion>

  <Accordion title="Campaign">
    A multi-faceted marketing effort organized in Fanaura. A campaign typically includes one or more assets, a launch container, flows, blasts, and smart links all working together. In the context of SMS, "campaign" specifically refers to a batched sending operation that processes messages at your number's throughput rate.
  </Accordion>

  <Accordion title="Condition">
    A flow node that evaluates a fan's data or behavior and branches into **Yes** and **No** paths. Conditions let you personalize your automation:

    * "Has this fan presaved?" (Yes path: send a thank-you. No path: send a reminder.)
    * "Is this fan Gold tier or higher?" (Yes path: exclusive offer. No path: standard offer.)
    * "Did this fan open the last email?" (Yes path: follow up. No path: try a different subject line.)
  </Accordion>

  <Accordion title="Cycle Stage">
    A phase within a launch that organizes your marketing timeline. For music releases, the three cycle stages are:

    * **Pre-Release**: The build-up before the song drops. Presave campaigns, teaser content, countdown posts.
    * **Release**: The day your music goes live. Streaming links activate, first-day push.
    * **Post-Release**: Sustaining momentum after release. Thank-you messages, playlist pitching, review roundups.

    Different asset types may have different cycle stages.
  </Accordion>

  <Accordion title="Delay">
    A flow node that pauses execution for a set duration or until a specific condition is met:

    * **Time-based delay**: "Wait 2 days" or "Wait 4 hours."
    * **Wait until**: "Wait until Tuesday at 9 AM" (uses your account timezone).
    * **Wait for event**: "Wait until fan opens the email" or "Wait until fan responds."

    Delays create space between flow actions so fans are not bombarded with messages all at once.
  </Accordion>

  <Accordion title="DSP (Digital Streaming Platform)">
    Any platform where fans stream music. Fanaura supports 9 DSPs for presaves:

    * Spotify, Apple Music, YouTube Music, Amazon Music, Tidal, Deezer, Pandora, SoundCloud, Audiomack.

    Additional platforms (iTunes Store, YouTube) are supported for streaming and purchase links.
  </Accordion>

  <Accordion title="Engagement Score">
    A 0-100 score reflecting how active and engaged a fan is. The score is calculated based on the fan's actions: presaves, streams, email opens, email clicks, merch purchases, RSVPs, referrals, and more all contribute. Higher scores indicate more engaged fans. Engagement scores update dynamically as fans interact with your content.

    Use engagement scores for targeting: send exclusive content to fans with scores above 80, or re-engagement campaigns to fans below 20.
  </Accordion>

  <Accordion title="Enrollment">
    When a fan enters a flow. Enrollment happens when a fan takes an action that matches a flow's trigger:

    * Fan presaves your music > enrolled in the "Presave Thank You" flow.
    * Fan sends an Instagram DM with keyword "MERCH" > enrolled in the "Merch Promo" flow.
    * Fan RSVPs to a tour date > enrolled in the "Show Reminder" flow.

    A fan can be enrolled in multiple flows simultaneously.
  </Accordion>

  <Accordion title="Execution">
    A single action running for one fan within a flow. If 500 fans are enrolled in a flow and each fan receives 3 emails, that is 1,500 executions. Executions are logged in your Activity Logs for auditing and debugging.
  </Accordion>

  <Accordion title="Extra">
    A special asset type for content that does not fit Music, Merch, or Tours. Extras are flexible containers for:

    * Exclusive video content
    * Giveaways and contests
    * Fan surveys
    * Behind-the-scenes footage
    * Unreleased demos
    * Any creative content you want to share through a smart link
  </Accordion>

  <Accordion title="Fan">
    Anyone in your Fanaura database who has interacted with your content. A fan record is created when someone:

    * Submits their information on a smart link
    * Presaves your music
    * RSVPs to a tour date
    * Texts your SMS number
    * Engages through an Instagram DM trigger

    Fan records include name, email, phone, location, engagement history, VIP tier, and more.
  </Accordion>

  <Accordion title="Fan List">
    A custom segment of fans for targeting. Fan lists let you group fans based on criteria:

    * Fans in a specific city
    * Fans who presaved a specific release
    * Fans with engagement scores above a threshold
    * Fans at a specific VIP tier
    * Custom combinations of any criteria

    Fan lists are used for targeting blasts and flow enrollments.
  </Accordion>

  <Accordion title="Flow">
    An automated workflow that executes actions when fans trigger events. Flows are built visually in the Flow Builder using nodes:

    * **Trigger**: What starts the flow (presave, DM keyword, RSVP, etc.)
    * **Action**: What happens (send email, send SMS, send DM, add tag, go to another flow)
    * **Delay**: Pauses between actions
    * **Condition**: Branches based on fan data

    Flows run automatically 24/7 once toggled on.
  </Accordion>

  <Accordion title="Go-to-Flow">
    An action node that redirects a fan from one flow to another. Instead of building one enormous flow, you can modularize your automation:

    * Welcome flow > Go to "Presave Reminder" flow
    * Presave flow > Go to "Release Day" flow

    The fan seamlessly moves from one flow to the next.
  </Accordion>

  <Accordion title="Heatmap">
    A geographic visualization of where your fans are located. Fan heatmaps use Fanaura's mapping technology to show concentration of fans by city, state, and country. Heatmaps help you:

    * Plan tour routing based on where demand is highest.
    * Target marketing by region.
    * Understand your audience's geographic distribution.
  </Accordion>

  <Accordion title="ISRC (International Standard Recording Code)">
    A unique identifier for each sound recording. Every professionally distributed song receives an ISRC from the distributor. In Fanaura, the ISRC is used to:

    * Automatically find your song across all streaming platforms on release day.
    * Match presaves to the correct song.
    * Power the automatic link resolution that populates your smart link with streaming URLs.

    Format: `USRC12345678` (12 characters, alphanumeric).
  </Accordion>

  <Accordion title="Launch">
    A campaign container that organizes marketing around a release. Launches bundle:

    * Assets (the content being promoted)
    * Cycle stages (pre-release, release, post-release)
    * Flows (automated workflows)
    * Blasts (manual sends)
    * Smart links (fan-facing pages)

    Think of a launch as the master plan for promoting a release.
  </Accordion>

  <Accordion title="Lead">
    A fan who has not fully verified their identity. Leads might have provided only an email address without confirming other details. Leads can be converted to verified fans through re-engagement and data enrichment.
  </Accordion>

  <Accordion title="Merge Tag">
    A dynamic placeholder that gets replaced with real data when a message is sent. Common merge tags:

    * `{fan_first_name}` -- "Hey Sarah" instead of "Hey Fan"
    * `{artist_name}` -- Your artist display name
    * `{asset_title}` -- The name of the song, tour, or product
    * `{smart_link_url}` -- A link to the relevant smart link

    Merge tags work in emails, SMS, and Instagram DMs.
  </Accordion>

  <Accordion title="Node">
    A single step in a flow. There are four types of nodes:

    * **Trigger node**: The starting point (what kicks off the flow).
    * **Action node**: Something that happens (send email, send SMS, send DM, add tag, go to flow).
    * **Delay node**: A pause (wait X hours/days, wait until a specific time).
    * **Condition node**: A branch point (evaluates a condition, splits into Yes/No paths).

    Nodes are connected by edges in the visual Flow Builder canvas.
  </Accordion>

  <Accordion title="Opt-In">
    A fan's explicit consent to receive marketing messages. Fanaura tracks opt-in separately for:

    * **Email opt-in**: Consent to receive marketing emails.
    * **SMS opt-in**: Consent to receive text messages.

    Opt-in is required by law (GDPR, CAN-SPAM, TCPA) and is collected through smart link data wrappers.
  </Accordion>

  <Accordion title="Pre-Save">
    A fan's commitment to save a song to their streaming library on release day. When a fan presaves:

    1. They authorize Fanaura to access their streaming account.
    2. On release day, Fanaura automatically adds the song to their library.
    3. The fan earns reward tokens and the presave is logged in their profile.

    Presaves are available on 9 platforms: Spotify, Apple Music, YouTube Music, Amazon Music, Tidal, Deezer, Pandora, SoundCloud, and Audiomack.
  </Accordion>

  <Accordion title="RSVP">
    A fan confirming attendance at a tour event. When a fan RSVPs:

    * They are added to the RSVP list for that show.
    * Their location data is captured.
    * They earn reward tokens.
    * They can be enrolled in tour-related flows (reminders, day-of info).
  </Accordion>

  <Accordion title="Smart Link">
    A data-collecting landing page for your content. Smart links are the core of Fanaura's fan engagement:

    * Every asset gets its own smart link.
    * Fans must provide their data (email, name, etc.) to access the content.
    * The data wrapper ensures privacy compliance.
    * After submitting data, fans see streaming links, presave buttons, RSVP forms, or merch.

    Smart links are your primary tool for growing your fan database.
  </Accordion>

  <Accordion title="Throughput (SMS)">
    How many SMS Fanaura can send per minute for your line depends on the **messages-per-minute** setting on your provisioned number and carrier 10DLC rules. New local numbers often start conservative; contact support to align with your approved campaign tier. See [SMS Integration](/integrations/sms).
  </Accordion>

  <Accordion title="Ticket Comp">
    A complimentary ticket offered to a fan, typically as a VIP tier reward or promotional incentive. Ticket comps can be managed through Fanaura's tour features.
  </Accordion>

  <Accordion title="Trigger">
    An event that starts a flow. Triggers are the first node in any flow:

    * Fan presaves music
    * Fan sends an Instagram DM with a keyword
    * Fan comments a keyword on a post
    * Fan RSVPs to a tour date
    * Fan buys merch
    * Fan signs up via smart link
    * Fan sends an SMS with a keyword
    * And more

    Each flow has exactly one trigger.
  </Accordion>

  <Accordion title="Trigger Conflict">
    When two or more flows share the same trigger, causing a fan to be enrolled in multiple flows simultaneously. This can result in duplicate messages (the fan receives two welcome emails, for example). Fanaura warns you about trigger conflicts in the Flow Builder.
  </Accordion>

  <Accordion title="UPC (Universal Product Code)">
    A barcode identifier for a release as a product. While ISRC identifies a recording, UPC identifies the release packaging (the single, EP, or album as a product). Your distributor provides the UPC.
  </Accordion>

  <Accordion title="VIP Tier">
    A fan's loyalty level in your rewards system. There are five tiers:

    * **Bronze**: Starting tier (0 tokens). Everyone begins here.
    * **Silver**: 100 tokens (default). A few meaningful interactions.
    * **Gold**: 500 tokens (default). Consistent engagement.
    * **Platinum**: 2,000 tokens (default). Highly active fans.
    * **Diamond**: 10,000 tokens (default). Your most dedicated superfans.

    Each tier can offer exclusive perks configured in Settings > Fan Rewards.
  </Accordion>

  <Accordion title="Webhook">
    An automated notification from an external service to Fanaura. When something happens outside of Fanaura (a fan texts your number, buys merch on Shopify, or comments on Instagram), the external service sends a webhook to Fanaura so the event can be processed. Webhooks are configured automatically when you connect integrations.
  </Accordion>
</AccordionGroup>

<Note>
  If you encounter a term that is not in this glossary, reach out to Fanaura support and we will add it.
</Note>