If you run Account Engagement, this is your path

This is the route for teams using Marketing Cloud Account Engagement (you may still call it Pardot). We ask your marketing operations person to create one small connector called a Form Handler, and send us the endpoint it produces. We keep the Beacon design exactly as it is, and your leads flow into Account Engagement and on into Salesforce.

Account Engagement (Pardot) admin · About 15 minutes

Two ways to do this inside Account Engagement

We are recommending the one that keeps the Beacon look.

Account Engagement can capture this form two different ways. The difference matters, so here it is in plain terms before you choose.

Recommended

Form Handler

You build a small connector in Account Engagement and send us its endpoint URL plus the field names. We keep our own Webflow form, styled to match Beacon perfectly, and point it at your endpoint. You own the data side, we own the design side. This is what the steps below cover.

Fallback

Hosted form (iframe)

You build the whole form inside Account Engagement and send us an embed code. Least effort for you, but an embedded form cannot be styled to match the page, so it will look like a Pardot form dropped into Beacon rather than part of it. Only if the Form Handler is not workable for you.

Before you start

The fields the form will collect.

The first five already exist on your current Beacon page. The last one is new. In Account Engagement, a form can only use Prospect Fields, so each of these needs to exist as a Prospect Field before you build the handler.

ExistingName

ExistingOrganization

ExistingEmail

ExistingPhone

ExistingTopic dropdown

NewMarketing opt-in

The opt-in must exist as a Prospect Field (a checkbox), mapped through to Salesforce. If it already exists, use it. If not, it has to be created before you build the handler, otherwise it will not be available to map.

This one is not optional

A marketing opt-in that is shown to the visitor but never recorded is worse than no opt-in at all: you would be collecting consent you cannot prove you have. If the field does not exist and you are not able to create it, we need to resolve that before the page can go live. Tell us early and we will help you make the case internally.

How to build the Form Handler

Inside Account Engagement, not Salesforce Setup.

Written for the Account Engagement Lightning app. The menu names shift slightly between accounts, so if your screen does not match, tell us what you see and we will walk through it with you on a call.

Create the two custom Prospect Fields first, if they are not there
In the Account Engagement app, click Account Engagement Settings, then Object and Field Configuration, then Prospect Fields. Click + Add Custom Field for each one:
- Topic (probably already exists): name it "Topic", set the Type to Dropdown, enter the options under Values, then click Create Custom Field. To sync it to your Salesforce Topic field, set the Salesforce.com Field Name too.
- Marketing opt-in (the new one): + Add Custom Field again, name it "Marketing Opt-In", set the Type to Checkbox, then Create Custom Field.
They must exist before the next steps, or they will not appear when you map fields.
Open the Form Handlers screen Switch to the Account Engagement app with the App Launcher (the grid of dots, top-left) if you are not already there. In the top navigation click Content, then Form Handlers. (Older standalone interface: Marketing, then Forms, then Form Handlers.) Click Add Form Handler, usually top-right, and name it "Beacon Campaign Landing Page".
Set the Folder and Campaign Pick any Folder, then set the Campaign. This keeps these leads separate from every other lead you collect. Use or create a campaign named exactly Beacon Campaign DigiVidBio. When it is connected to a Salesforce Campaign, submissions become Campaign Members automatically.
Tick the two settings that make it work Check "Enable data forwarding to the success location" (required, or the handler will not pass data on), and enable "Kiosk / Data Entry Mode" so visitors are not all cookied as the same prospect. For the Success Location and Error Location boxes, paste any URL to get past them. We control what the visitor sees, so those do not matter. (If you want these prospects tracked for web activity, tell us and we will set it up differently.)
Add the seven fields, exactly like the table below Scroll to the Form Fields area. Each time you click Add New Field, a pop-up opens with three boxes and a Required checkbox. Fill it in exactly as each row in the table just below shows, click Save changes, then Add New Field for the next.
Save, then copy the Endpoint URL from the Summary screen Click Save. Account Engagement takes you to a Summary screen that shows the Endpoint URL. That is what we need. It contains no passwords and is safe to email.
Send us the Endpoint URL Paste it into an email to us, along with the few answers in the next section. That is the whole task.

The table for step 7

Exactly what to enter for each field.

Seven fields. Fill each pop-up in exactly like its row, then Save changes.

Type in "External Field Name"	Choose in "Prospect Field"	Choose in "Data Format"	Required box
email	Email	Email	Check it
firstname	First Name	Text	Leave unchecked
lastname	Last Name	Text	Check it
company	Company	Text	Leave unchecked
phone	Phone	Text	Leave unchecked
topic	your Topic field	Text	Check it
optin	your opt-in field	Text	Leave unchecked

Three notes on the table

The email row is the strict one. Type email in lowercase and set Data Format to Email. It is case-sensitive, so Email or EMAIL will fail.

The last two rows point to your own fields, the ones you made in step 1. Pick your Topic field and your opt-in field from the Prospect Field dropdown.

Two name rows are intentional. Your page shows one "Name" box, but Salesforce stores first and last separately, so we send both. Nothing extra for you to do.

When you are done

What to send us, in one email.

Five things. Short answers are fine for the last four.

1. The Endpoint URL From the Summary screen after you save the handler.

2. The opt-in wording, approved by legal The exact sentence that goes next to the checkbox, plus any links it should carry. We use it word for word.

3. The word to use for Company when Organization is left blank Many visitors are individuals, but Salesforce still needs a company. Tell us the placeholder, for example Not Provided or Individual.

4. Confirm the Topic dropdown options Here are the four we have from your current page. If they are right, just say so. If you want any changed, added, or removed, tell us. The four: Learn more about this product, Place an order, Request a test kit, General question.

5. One person who can confirm a test worked We submit a fake lead, they check the prospect landed in Account Engagement and Salesforce with everything intact. Fifteen minutes, once. It is what prevents a silent failure on launch day.

Everything else is yours to decide internally: scoring, automation rules, who gets notified, what happens next. We do not need visibility into any of it.

If you would rather go hosted

The iframe route, in one line.

If the Form Handler is not workable on your side, build the form in Account Engagement's form builder and send us the embed code instead. It handles the opt-in and campaign membership on its own.

The tradeoff, again: a hosted form is delivered as an iframe, which we cannot restyle, so it will not match the Beacon page as closely. We would rather use the Form Handler, but this works if you need it.