SolutionsHeadless sites and apps

Keep your pixelsWe'll run the line

Built your own site or app? The SDKs put the whole drop inside it, in your design. Fanfare runs the queue, the draw and the bot checks behind it.

Get started

What usually goes wrong

You could build a queueThen you'd own a queue

Real posts from real drop days.

01 · Create

Marketing plans it. Your code shows it

The drop is set up in the Fanfare dashboard, with no deploy. Your code reads which phase the drop is in and draws each moment your way, or drops in the ready-made widget.

In your codeTake what you need

drop.tsx

<FanfareProvider
  organizationId="org_123"
  publishableKey="pk_live_123"
>
  <ExperienceWidget
    experienceId="exp_123"
    autoStart
    checkoutUrl="/checkout"
  />
</FanfareProvider>

The ready-made widget. Restyle any moment with slots and a theme.

The phase your screens are told

scheduled
enterable
participating
granted
ended

One line behind every screen

Your site and your apps all read from the same drop. The line, the draw and the bot checks behave the same on every screen, and none of it is your code.

Three ways into your store and one line behind them. Tap to move it on, or just watch it run.More on scale

03 · Learn

Three screens. One fan profile

Whichever screen a fan comes in on, the entry lands on the same profile and the points add up. You learn everything a hosted drop would have told you.

A drop on your own site, start to finish

Set up in the dashboardCreateMarketing picks the way in and the time. No deploy, and your page shows it.

Set up in the dashboardCreateMarketing picks the way in and the time. No deploy, and your page shows it.
Your screen counts downCreateThe SDK says scheduled. You draw it your way.
Fans join from your screenDropTheir place and wait come straight from the queue.
Their turn comesDropThe SDK says granted, and your own checkout takes it from there.
On their profileLearnThe entry and the win land on the fan, as with any drop.