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

# Customers and identity

> How Fanfare creates and matches customer records, what changes when you allow guest access, and how to manage customer profiles.

Every signed-in shopper who interacts with your drops has a customer profile under **Customers** in the Fanfare admin. Each record tracks their email address and phone number, marketing preferences, loyalty balance, and engagement metrics built from their drop activity.

You can also let shoppers join certain drops as **guests** without signing in. Guests don't get a profile under **Customers** and leave no contact details—though their entries and orders are still recorded against the drop. Deciding whether to allow guest access shapes what customers hear from you, whether they can return on another device, and how easily you can recognize and reward them in future drops.

## One person, one record

Fanfare maintains one record per person across your organization: each email address and each phone number belongs to a single customer. If you add or import a phone number without a country code, Fanfare interprets it using your organization's country.

## How customer records are created

A customer record is created whenever:

* **A shopper signs in** — They enter their email or phone number and confirm a one-time code. Because Fanfare creates the record when sign-in starts, your list can include shoppers who requested a code without finishing.
* **You add them manually** — Under **Customers → Add Customer**, using an email address (name, phone, **Status**, and **Lifetime points** are optional). Setting **Lifetime points** here sets only their lifetime total; their spendable **Loyalty balance** starts at `0`.
* **You import a CSV into an audience** — Any row that doesn't match an existing customer creates a new record. See [Build audiences](https://docs.fanfare.io/guide/create/audiences.md) for supported columns.
* **You add them to a waitlist** — Using **Add person** on a sequence's waitlist creates a customer if that email isn't on file yet.
* **Your developers create them via API** — See [API keys and embedding](https://docs.fanfare.io/guide/account/developer.md).

### How CSV imports update existing customers

When you import a CSV, Fanfare matches rows to existing customers by email or phone and updates matched records with any non-empty values in the file:

* **Name, phone number, and lifetime points** overwrite the customer's existing values whenever those cells aren't blank.
* **Metadata** replaces the customer's existing metadata as a whole rather than merging keys.
* **Phone number changes** clear the customer's marketing SMS consent and remove the phone's verified status.
* **Email address** is filled in only if the matched customer didn't already have one.

New customers created via CSV import start opted out of marketing SMS.

> [!WARNING]
>
> CSV imports overwrite existing customer details with no undo. Blank cells leave existing fields untouched, so clear the name, phone, points, and metadata columns for anyone whose current details you want to preserve before importing.

## Signed-in customers vs. guests

Every shopper entering your experience is either **signed in** or a **guest**—there's no intermediate account tier.

| | Signed-in customer | Guest |
| - | - | - |
| **How they enter** | Enters an email or phone number and confirms a one-time code. | Selects **Continue as guest** on the sign-in screen. |
| **Where they can join** | Any distribution and any sequence they qualify for. | Queues, draws, and timed releases with **Allow guest access** enabled, in sequences without an audience. Never auctions, appointments, or waitlists. |
| **Notifications** | Receives Fanfare's automatic emails and texts—like draw results and payment window alerts. | None. Fanfare has no email or phone number to reach them. |
| **Returning later** | Can sign in from any device to check their status. Queue, draw, and timed-release purchases must still be completed in the browser they entered from; auction wins can be completed from any device. | Same browser only. |
| **Loyalty** | Earns points, and their balance counts toward Fanfair loyalty prioritization. | Earns no points and counts as `0` points for loyalty prioritization. |
| **Listed in Customers** | Yes. | No. |

**Allow guest access** (labeled **Anyone, as a guest** in the create wizard) is configured per distribution on queues, draws, and timed releases. A sequence displays the guest option only when every open or scheduled distribution in it allows guests and the sequence has no audience attached. Adding an audience to a sequence automatically turns guest entry off. See [Sequences and routing](https://docs.fanfare.io/concepts/sequences.md), [Add and gate sequences](https://docs.fanfare.io/guide/create/sequences.md), and individual setup guides like [Set up a queue](https://docs.fanfare.io/guide/create/queue.md).

> [!WARNING]
>
> Guests receive no emails or texts—no "you're through" alert, no draw outcome, and no payment window reminder. If a guest closes the page or switches devices, they can miss their turn without knowing. Enable **Allow guest access** only when faster, zero-friction entry outweighs the risk of missed spots and duplicate or throwaway entries.

While a guest participates in a queue, draw, or timed release, Fanfare displays a reminder: *"Keep this page open. As a guest you won't get emails or texts."* See [What your customers see](https://docs.fanfare.io/guide/drop/what-customers-see.md) for the full sign-in flow.

## Verified email and phone

An email address or phone number earns a verified checkmark in **Customers** once the customer signs in using a one-time code sent to it. Customers added manually via **Add Customer** or **Add person**, or created through a CSV import, start unverified.

## Managing customer records

Open any customer's profile to view their contact details, spend, engagement metrics, audiences, and drop history—and to adjust loyalty points if your loyalty program is active on Pro or above. See [Customer profiles](https://docs.fanfare.io/guide/learn/customers.md) for a full walkthrough.

Keep these record rules in mind when managing customers:

* **Editing details:** You can't edit a customer's name, email address, or phone number directly in the admin form. To update a customer's name or phone number, import a CSV that matches their record.
* **Archiving:** **Archive** permanently removes a customer from **Customers**—they can't be restored, and their email or phone number can't be re-added. Archiving doesn't block the person from signing in and entering future drops; it simply hides them from your customer list. See [Customer profiles](https://docs.fanfare.io/guide/learn/customers.md) before archiving anyone.
* **Status (Active / Inactive):** An organizational label you can set when adding a customer manually (all other creation methods default to **Active**). **Status** doesn't block drop entry and can't be used in audience rules.

## Example: a member and a guest at the same drop

Northbound Supply Co.'s "Phantom Stitch Anorak Drop" runs two sequences: **Inner Circle Early Access** (an audience-gated queue from 10:00 to 11:00) followed by **Public Draw** (opening at 11:00 with **Allow guest access** enabled).

* **Signed-in member:** Maya Chen is in Inner Circle. At 10:05, she signs in with her email and one-time code and joins the queue on her phone. When she's admitted, Fanfare emails her that it's time to check out, and she completes her purchase on her phone—the same browser she entered from.
* **Guest shopper:** Another visitor arrives at 10:20. Because only the audience-gated queue is open, they see the sign-in screen with no guest option. They return at 11:15, choose **Continue as guest**, and enter the Public Draw. If they win, they won't receive an email or text—they'll need to revisit the page in the same browser before their payment window closes. They earn no loyalty points and won't appear under **Customers**.

## On Shopify

Customer profiles and archiving work the same way in the Fanfare app in Shopify. On your Shopify storefront, however, visitors start in a guest session automatically: when **Allow guest access** is enabled, they enter directly as guests without seeing a sign-in prompt—and won't receive emails or texts unless they select **Sign In** before entering.

## Related

> [card] [Customer profiles](https://docs.fanfare.io/guide/learn/customers.md)
>
> Explore customer details, metrics, and archiving.

> [card] [Sequences and routing](https://docs.fanfare.io/concepts/sequences.md)
>
> How sequence gates and guest access work together.

> [card] [Build audiences](https://docs.fanfare.io/guide/create/audiences.md)
>
> CSV import steps and supported columns.

> [card] [Loyalty and Fanfair](https://docs.fanfare.io/concepts/loyalty.md)
>
> How loyalty points and Fanfair prioritization work.

> [card] [Announcements](https://docs.fanfare.io/guide/create/announcements.md)
>
> Marketing SMS consent and customer messaging.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.