source: lead_capture, and a lead_captured event, so a journey can welcome the lead on WhatsApp or
email within seconds, while they still remember you.
Lead Capture is an add-on. If you don’t see Lead capture → Pop-ups in
the Boom app’s left sidebar, ask your account manager to turn it on for your
organization.
Create a pop-up
In the left sidebar, open Lead capture → Pop-ups and choose New pop-up, pick a template, and give it a name and the site it will run on. Templates are finished pop-ups (a big coupon, a newsletter sign-up, a full-screen offer, the wheel and the other games) with their design and text already in English, Spanish and Portuguese; choose Blank to start plain. Either way you only add your prizes and codes. New pop-ups start Paused, so you can design one without it showing to anyone. The pop-up’s page is a live preview with the settings beside it. The left sidebar lists its sections, grouped under Setup, Look, Engage and Results; pick one and its settings open next to the preview. A blue dot on a section means it has unsaved changes, and an orange dot means something there needs fixing. Switching sections keeps your unsaved changes, and Save saves them all at once. On a phone the settings come first. Tap Preview at the top of the settings to see the pop-up, and Back to settings to return.See it live before installing
Above the preview, See it live opens the pop-up in a new tab on a sample store page, working exactly as it will on your site: it opens on its trigger (after the delay, on scroll, on exit), the tab shows, and every step runs, the game included, through to the code. It works while the pop-up is Paused, before you install anything and whatever sites you allowed. The bar at the top of that page has:- Open now: open the pop-up without waiting for its trigger;
- Reset: forget that it was seen, closed or filled in, so it plays again from the start;
- Desktop / Mobile: see it at a phone’s width.
Install
The Install section has a tab for each way to install the pop-up. If your Shopify store is connected to Boom, the Shopify tab comes first; otherwise you start on Script tag. Rotate key sits below the tabs and changes the key in all of them; the confirmation explains what stops working.Shopify
Stores connected to Boom through their own Boom Shopify app do not need to edit any code. The Shopify tab has two steps:- Copy your key (the
blc_live_…value). - Open theme editor. The button opens your live theme on App embeds with Boom Chat Widget already switched on. Paste the key in Lead Capture install key, then click Save.
- Turn the embed on yourself: App embeds → Boom Chat Widget. In a Shopify admin in Spanish, that’s Tienda online → Temas → Personalizar → Incrustaciones de aplicaciones.
- No Lead Capture setting at all? Your app needs updating; ask Boom.
- The same embed has Enable AI Chat (on by default) and Enable WhatsApp. Leave both off unless you use Boom’s chat on your store, or turning the embed on also shows a chat bubble.
Script tag
Copy the tag from the Script tag tab and paste it at the end of the page body on every page that should show the pop-up:https://example.com does not cover https://www.example.com. On any other site
the pop-up does not open, and your browser’s console says why.
Open it from your own button
The Your own button tab has a ready-made sample. Any button or link with the pop-up’s install key indata-boom-lead-capture-open
opens it when clicked, whatever its trigger:
lead_captured event, a repeat one included (repeat is
true), so give a welcome journey a frequency cap or branch on repeat to
avoid welcoming the same person twice. Set the trigger to On click if it
should only ever open this way. That is also the
choice for a page where search ranking matters: a pop-up that covers a page as
soon as it loads on a phone can cost it.
Single-page apps
On a site that changes pages without reloading (React, Next.js, Vue), the pop-up stays mounted across those changes, tab included. To show it on some pages only, take it down when the visitor leaves them and bring it back when they return:Apply the code in your store
Under Form → After the form, add an apply-code link and the prize screen gets a button that opens your store with the code already applied. Write{code}
where the code goes. For Shopify:
Going live
Set Active is refused until the pop-up can keep its promise:- at least one allowed site;
- it asks for an email or a WhatsApp number;
- a game has at least one prize, and its prize odds total 100%;
- if it asks for a WhatsApp number, it has a consent sentence;
- if it plays first, it has a game.
Prizes and games
Each visitor gets one prize, drawn on Boom’s side using the odds you set. The game only shows the result: whichever card or box the visitor picks, the wheel, the ball and the reels land on the prize already drawn, and the scratch card hides it. Nothing on your page can change what a visitor wins, and the promo codes are never sent to the page until a prize is drawn. Odds are percentages, one per prize — 90, 9 and 1, say — and they must total 100% before the pop-up can go live. Two decimals are allowed, so0.1 is one in
a thousand and 0.01, the smallest, is one in ten thousand. A prize at 0 is
still shown by the game and can never be won.
Someone who enters again — same WhatsApp number, or the same email inbox, even
with a +tag or Gmail dots — gets the prize they got the first time.
Play first
By default the visitor leaves their details first and then plays to reveal the prize. Set Order of screens to Play first (in Prizes, once a game is picked) to turn it around: the visitor plays straight away, sees what they won (“You won! 10% off”), and then leaves their details to get the code. The ask first screen and the quiz, when you use them, still come before the game. The line over the form is the Claim message in Content;{prize}
in it becomes the prize’s name, e.g. Leave your details to get your {prize}.
The prize is still drawn on Boom’s side, when the game starts, and the code
still reaches the page only after the visitor has left their details. After the
form they see the code, or the message that it is on its way if you send it by
message. Someone who entered before still gets their first prize, even if the
game showed them another one, and the screen after the form shows the prize
they actually get. If the prize cannot be drawn when the game starts (a network
problem, for example), the pop-up falls back to the form first.
Quiz
Turn on the quiz to ask up to three quick questions before the form, such as “What would you like to work on?” with answers like Stress, Sleep or Energy. Each question has two to twelve answers, one question per screen. One tap or several picks. With Answers they can pick at 1, the visitor taps one answer and moves on. Set it higher, say 3 for “pick up to 3”, and the answers show as tiles two to a row, with a counter (“2 of 3 chosen”) and a Continue button that works from the first pick. Every answer is saved on the person under the question’s Saved as name (filled in from the question; you can rename it), and on thelead_captured
event, so a segment or a journey can branch on it. Answers are saved as written
in English, the base language, whatever language the visitor saw, so a condition
like interest = "Sleep" matches everyone. If the person already answered
before, their first answer is kept.
Saved values. Give an answer a saved value, a short code such as sleep
or hormones (lowercase letters, digits, _ and -), and that code is stored
instead of the English text. A code survives rewording the answer, and a journey
can build a link from it, e.g. /collections/need-{{need_primary}}.
Several picks are saved as a list, in the order the visitor picked them,
e.g. need = ["sleep", "stress"], and the first pick also as
<name>_primary (need_primary = "sleep"). Segments can match any pick in the
list (“need includes sleep”). Journey branches compare single values, so branch
on the _primary one. The lead_captured event also carries
<name>_labels, the picks as the visitor read them, in their language, ready
for a message: {{event.need_labels}} gives “sleep and stress” (or “sueño y
estrés”). A question already live as one tap can’t become
multi-pick under the same name, since its saved answers are text: give it a new
name.
An answer can also have a link, for example the collection that matches it.
The last screen then shows a button to it, with the words you choose for that
answer, and the link reaches your journey as link_url. Use {code} in the link
to apply the code as well, e.g.
https://your-store.com/discount/{code}?redirect=/collections/sleep. When the code
is sent by message, a link that contains {code} is left off the screen and only
reaches the journey.
Consent
When the pop-up asks for a WhatsApp number, it shows your consent sentence beside an unticked box, and the visitor has to tick it to continue. Boom stores, with each lead, whether they ticked it, the exact sentence they saw, the language it was in, and when. A visitor who leaves the box unticked (on a form that asks only for email) is still saved as a lead, but is not enrolled in journeys. The same goes for someone on your Do Not Contact list (in People), even if they tick the box: they are saved, but not opted in and not enrolled, and their event saysconsent: false.
Someone whose email address unsubscribed from your marketing emails is handled
more narrowly: they are saved and enrolled as usual, and their WhatsApp opt-in
counts, but Boom does not opt their email back in to marketing (anyone can type
a known address), so marketing emails still skip them. See
Email deliverability.
A form that asks only for email can show the consent sentence as a notice
instead of a checkbox — submitting the form is then the agreement. Forms that ask
for a WhatsApp number always use the checkbox. Each lead records which of the
two it was.
Progress bar. Turn on Form → Progress bar to show a thin bar on top with one segment per screen (each quiz question, each form step, the game, the code), filled up to where the visitor is.
A form in steps. Under Form → Steps you can split the form into a few
screens, for example your email first and then an optional WhatsApp step with a
link like “I’d rather just use email”. Each step has its own headline, button and
consent sentence. The visitor’s details are sent once, at the end; someone who
skips the WhatsApp step, or closes the pop-up on it, is still saved with the email
they gave. Consent is kept per channel: the email step’s sentence (often a notice)
opts them in to email, and the WhatsApp step always has a box to tick, which opts
them in to WhatsApp. When both were agreed, the lead records both sentences.
To link your terms and conditions, add the page under Form → Terms and
conditions link and mark the words that should link with asterisks in the
consent sentence (Content), for example I accept the *terms and conditions*.
Those words open your page in a new tab, and each lead records the link as
consent_terms_url. A pop-up with a terms link cannot go live until the sentence has marked words in every language you wrote it in.
Use the lead in a journey
Start a journey with thelead_captured event. It appears in the journey
builder as soon as a pop-up is first set Active. Its properties are available as
message variables:
A typical welcome sends the promo code again on WhatsApp, then follows up if no
order arrives.
Before you publish
- Check for a WhatsApp number first.
emailandphoneare only there when the visitor gave them, so some leads arrive with an email and no number. Start the journey with a condition onphoneis set: send WhatsApp on Yes and email on No. A WhatsApp step for someone with no number ends their journey there; an email step for someone with no email is skipped. - One journey hears every pop-up. The trigger is the event name, so a
lead_capturedjourney receives leads from all your pop-ups. To treat them differently, add a condition onform_name(orform_id) right after the start. - Publishing is going live. The journey starts enrolling new leads the moment you publish it, so test the messages first.
- Visitors who left the consent box unticked are saved as leads but never enter a journey.
lead_, and it
carries source: lead_capture), even when the email or number matches a
customer. The same visitor coming back, on any of your pop-ups, is the same lead,
and gets the prize they were first given. To target leads in a segment, use
source is lead_capture.
In the Leads section each person counts once, however many times they submit,
and counts as opted in if any of their submissions was. The People list it opens
is filtered by the leadCaptureForm attribute, which holds the name of the last
pop-up or form the person used. Someone who later signs up through another one
is listed under that one, and renaming a pop-up leaves its earlier leads under
the old name. Seeing the list needs access to People; the counts do not.
See which initiatives a pop-up starts
The pop-up’s Initiatives section (under Results) lists every initiative, campaign or transactional message whose journey starts onlead_captured, with
its journey’s status (Published, Draft or Stopped) and links to the initiative
and to its journey. A journey starts for leads from every pop-up unless
its first step is a condition on form_id (or form_name) whose “no” side
ends the journey: then it is listed only under the pop-ups that condition lets
through. A journey that names this pop-up in a condition is listed as this
pop-up’s; one that names none is marked All pop-ups. The Pop-ups list shows the same count next to each pop-up. Seeing the
section needs access to Initiatives.
From the API or an AI tool
Everything above can also be done over MCP or the REST API, with five tools:config on an update is merged into the current one: objects merge key by key,
while a list (such as prizes) or a plain value replaces what was there. So
{ "copy": { "headline": { "en": "Spin to win" } } } changes only the English
headline, and sending prizes replaces the whole prize list. A field the config does not have, such as a misspelled one, is refused with its path instead of being ignored.
The same rules as the settings page apply. Setting a pop-up Active is
refused, with the reasons, until it is ready, and a change that would leave a
live pop-up unable to deliver what it promises is refused the same way. Rotating
the install key and archiving stay in the app.
Creating and changing pop-ups takes the Owner or Admin role, as they are
organization settings. Listing leads also needs access to customer data. The
tools answer lead_capture_unavailable until Lead Capture is switched on for
your organization.
Your own analytics
After a successful submission the page receives aboom:lead-captured event on
window, carrying the install key and the prize id (no contact details):
The funnel, and what it records
The Leads section of a pop-up shows a funnel: how often the pop-up was shown, how far visitors got through it, where they closed, and how many signed up. It covers whole days — the last 7 — in your organization’s time zone. To build it the pop-up sends Boom a small, anonymous counter as a visitor moves through it, and again when they close it or leave the page. What is recorded:- that the pop-up was opened, and how: by its trigger, by the side tab, or by a button on your page
- which of its screens the visitor reached
- which screen they were on when they closed it
- whether they used an optional step’s “skip” link
- that their details were sent
localStorage entry it already keeps to remember that this browser has seen or
signed up through the pop-up.
If the counter cannot be sent — the visitor is offline, an extension blocks it,
the browser does not allow it — that opening is simply not counted. It never
affects your page or the visitor’s sign-up.
The funnel’s figures are not meant to equal the lead counts above it. The
funnel counts openings of the pop-up, over whole days; the lead counts
count people, over a rolling 7-day window. One person who opens the pop-up
three times is three openings and one lead.
The funnel starts counting from the day this was switched on. A pop-up that
has been live for longer keeps all of its existing lead counts, but its funnel
begins empty.