Skip to main content
An embedded form sits inside a page on your site, where you place it: a test with a score and a result (“test de estrés”), a webinar sign-up, a lead form on a landing page. Each answer is saved in Boom, the person becomes a lead in your CDP people, and the form records an event a journey can start from, within seconds.
Embedded forms are part of the Lead Capture add-on. If you don’t see Forms under Settings → Add-ons → Lead Capture, ask your account manager to turn them on for your organization.

​
Build a form

In Settings → Add-ons → Lead Capture, choose New → Form and start from a template (Lead form, Webinar registration, Short test) or blank.
  • Questions, grouped in steps: one question per step feels like Typeform; several make a classic form. Types: short and long text, email, phone, number, single choice, multiple choice, dropdown, scale (0–10 or 1–5) and plain text with no question.
  • Each question has a key (how it is stored, e.g. sleep) and each answer a value (e.g. badly). Labels can change any time and in any language; keys and values are what your segments and journeys read, so they freeze once the form is published.
  • Scoring: give answers points (a scale scores the number picked) and add results with a score range — “0–3: low stress”, “4–8: high stress” — plus one result for anything else. The visitor sees the result that matches; Boom picks it, never the page.
  • Hidden fields carry values from the page’s address (?campaign=octubre) onto the response; utm_* tags are kept automatically. Constants put a fixed value on every response, such as a webinar’s date.
A form needs a required email or phone question, so every response belongs to a person journeys can reach.

​
Publish, then go live

You edit a draft; visitors only ever see a published version. Publish when the draft is ready: Boom refuses with the reasons if something is missing, and lists the journeys and segments still reading a question or answer you removed. Then set the form Active. Pages already open keep working for an hour after you publish a new version, so nobody loses their answers mid-form.

​
Put it on your site

Paste both tags where the form should appear (the Install tab has them with your key):
Add every site that shows it under Allowed sites — matching is exact, so https://example.com does not cover https://www.example.com. The form takes your accent colour, font and corners from Design, and fits the width of its container. After a submission the page receives a boom:form-submitted event (no answers, no contact details) for your own analytics; turn on Push to dataLayer to send boom_form_submitted to Google Tag Manager for your ad pixels.

​
What each response creates

  • A lead in People (source: lead_capture), never merged into an existing customer by what someone typed. Answers are saved on the person under <form>_<key>, the result as <form>_result and the score as <form>_score, so “everyone who got high stress on the stress test” is a segment with no setup.
  • An event named after the form (for example test_estres_submitted) with every answer by key, the score and result, hidden fields and UTMs. Build a journey on it in the journey builder: the event and all its properties are there as soon as the form is published.
  • A response in the form’s Responses tab, with a CSV export.
Journeys only start for people who ticked the marketing box (or forms that show none). With a phone question, the WhatsApp opt-in box is required.

​
Sensitive questions (health and similar)

Mark a question sensitive when its answer is health data or as private. Then:
  • the answer is stored encrypted and saved on the person as a sensitive field: agents never see it, and only people with access to sensitive data do;
  • the answer, the score and the result are left off the event;
  • the form must ask for consent to process the answers, with a link to your privacy notice, before it can be published;
  • responses are deleted after a retention period (a year by default).
Once published, a sensitive question stays sensitive.

​
When someone asks you to stop or to delete their answers

From a response, an admin can act on a person’s privacy request:
  • Withdraw consent adds them to Do Not Contact (in People), so nothing is sent to them on any channel, turns their WhatsApp and email opt-ins off, and stops the journeys still running for them. Remove them from Do Not Contact to message them again.
  • Erase deletes every form response of theirs, the events those responses created and the answers saved on their profile, right away. The person stays in People with their contact details; delete them there too if they asked for that.

​
Use it from your tools

Everything above is available on the REST API and MCP: lead_capture_embedded_forms_list, …_get, …_create, …_update (edit the draft, sites and status), …_publish, and lead_capture_form_responses_list. Agents always see sensitive answers as [redacted]. An organization API key reads them in full, like the rest of the REST API, so give keys only to systems that need the data.

​
Keep another tool in sync

Moving off another email tool gradually? Build a journey on the form’s event with an HTTP request step that posts the response to the other tool’s API.