Everything the banner does, and who pays for which part.

Bold, italic and underline, plus a placeholder for the discount code and one for the countdown. Everything else prints as the characters you typed.

Enter your website address and OfferBanner takes the palette off your own page. Nothing ships below WCAG AA contrast.

Anywhere from 32 to 96 pixels, with the padding fitted to it — a 36px banner is 36 pixels tall, not 43.

Name a font family, or set it to match and the banner uses whatever font your site is already loading — including the font name your bundler invented.

Give the banner one destination and the entire bar is clickable. There is no separate button, so there is never a second answer to “where does this go?”

Top or bottom of the page, arriving with a slide or a fade. Changing either takes no redeploy.

Put a banner on the calendar and it runs; remove the booking and it stops. There is no status to set.

A campaign starts and ends at the instant the schedule says, in every timezone your visitors are reading from. Free books date windows too, as many as you like.

When two bookings overlap, the higher priority number is the one shown.

Black Friday, Halloween, Diwali, 春节 and 19 more, each with its own date rule, design and list of countries it is a selling season in. A preset arrives with its discount already written into it, and offers are Pro.

Leave the dates off and the banner keeps running, worldwide, until you take it down. It needs nobody to switch it on.

When more than one booking is live, the site can hold a single banner, tick, step, flip, scroll, or split the traffic by weight.

One banner that changes its own design for each holiday window you set — pumpkins in October, snow in December, with nobody logging in between.

Coupon write and promotion code write — the whole of what OfferBanner can do in your Stripe account. You create the key yourself in Stripe’s own dashboard.

Already have SPRING20 in your checkout? Enter it and the banner prints it as-is, on either plan. Nothing is minted and nothing is claimed.

If nothing minted a code, you did not enter one yourself, and the banner text does not name one, the dashboard says so before a stranger reads it.

Each person who unwraps the gift gets their own freshly minted, single-use Stripe code. Handed out by the gift, which is a Pro effect.

Set the hours and a visitor’s code expires that long after they claimed it. The deadline is written onto the Stripe promotion code, so clearing a cookie changes nothing.

Set the date the sale ends and every visitor watches the same clock run down to it.

A code expires on whichever comes first: the visitor’s own hours, or the day the campaign stops.

A per-visitor countdown that does not match the code’s own lifetime is refused with the number to fix it, rather than shipped as a banner that is wrong by four hours.

A visitor’s four hours start when they claim, not when you set it up, so the last person to arrive gets the same deadline as the first.

Sparkle, confetti, lights, disco, balloons, bubbles and the holiday drifts.

Four fires, six falling weathers, fireworks, lightning and the gift.

Eighteen of the 27 can run over the whole page instead of just the banner. The other nine — a full-screen fire, a light string with nothing to hang on — stay on the bar, where they read as intended.

A badge on the banner opens a modal, and the visitor gets a code that did not exist until they clicked it.

Set the odds — say a 60% chance of 5% off and a 2% chance of 40%. The draw runs on the server, so nothing the browser sends can pick a winner.

The default on both plans, and the whole of what Free does: the visitor sees the bar the moment they see the page.

Hold the banner back 1 to 120 seconds, or until the visitor has read from 10% to 100% of the page.

The banner appears when the cursor heads for the tab bar — the last moment you get.

Name a CSS selector on your own page and the banner arrives when a visitor reaches it.

Targeting lives on the booking, so the same banner can run a different week in a different country.

How many people the banner reached, and how many of them clicked it.

How many visitors copied the code — the step between reading a banner and using it.

How many codes the gift actually minted, which is a headcount rather than an impression.

Every figure is shown beside the same length of time immediately before it, so a number has a direction and not just a size.

The end of the funnel, counted where it happens. When Stripe is unreachable OfferBanner says so instead of showing a zero.

Who scheduled what, when a code was minted, and which surface did it. Readable in the dashboard and by an assistant.

Sites, banners, schedules, offers, stats, activity and the install check — the same actions the dashboard performs, in the same words.

Read banners, or change them. Write does not imply read, so a grant does exactly what the consent screen said it would.

For the things that are not a chat window. Every call acts on the account that owns the key and can never reach anybody else’s sites.

A restricted key can only be created inside Stripe’s dashboard, so the assistant sends you a link for that step instead of asking for the key.

One line, pasted once. There is no second snippet and nothing to update when the campaign changes.

Served from the edge. It is the one number you can check yourself in a devtools network tab, so it is the measured one.

Your stylesheet cannot restyle the banner and the banner cannot restyle your page. Neither of you has to know what the other named a class.

It reads the HTML, finds the tag or does not, and names the content-security policy that is blocking it when one is.

Three shops off one login, each with its own live banner. Free runs one banner at a time per site; Pro runs as many as you like.