Part of milestone 5 · Every channel coming in

In two lines: a lead source is what turns a contact into a lead; without it, a form is just an email that reaches you. And the pixel is what makes that lead bring the campaign that brought it, instead of showing up as direct traffic.

When you finish you'll have: your form and your ads creating leads on their own in the CRM, each with its source campaign identified.

How long it takes: about seventy minutes — fifteen per source, twenty for the pixel and thirty for the form.

Milestone 5 is two articles and most businesses need both, in whichever order they prefer: this one and Connect WhatsApp to the CRM: number, line and source. They are independent chains: neither depends on the other. If you don't use WhatsApp, this article is your whole milestone 5.

What do I need before starting?

Your pipelines and stages created: every source points to a Pipeline and an Initial stage that must already exist.
Access to the ad accounts you're going to connect.
Someone who can paste a code snippet into your site. You don't need to get their access: from the product itself you can email them the instructions.

How do I connect my ad platforms?

Just once, in Settings > Integrations: connect the ones you use. That connection is what later lets you pick the page or the account when creating a source.

See Integrations: what you can connect and how they work.

What do I decide in each lead source?

Sources are created in CRM > Settings > Lead sources with New source, and there's one per channel. The types you'll see in that menu: MB Suite Form (your web form), MB Booking (your booking page), Facebook Lead Ads, TikTok Lead Gen, LinkedIn Lead Gen Forms, Google Ads Lead Forms, WhatsApp Business, Generic webhook and Manual source.

For each one, three decisions:

1. Destination.

Prospect inbox — the lead goes into review before becoming a deal.
Direct deal — the lead is created as a deal in the Pipeline and the Initial stage you choose.

Your starting configuration already tells you which one applies, and in several businesses the answer depends on the source: someone who already left their details in a form shouldn't wait in an inbox, whereas raw WhatsApp is worth reviewing first so it doesn't muddy your conversion by origin.

If you already created a source in milestone 1, open it again now: there you chose Prospect inbox for everything, and your starting configuration may ask for a different Destination for that channel.

2. Field mapping. Pair each form field with its field in MB Suite, including your custom fields. What you don't map is lost.

3. Deduplication strategy (in some sources it appears simply as Deduplication), for when the contact already exists: Merge with existing, Create activity, Notify duplicate or Skip duplicate.

Detail per platform, advanced mapping and how to bring historical leads from a source: Lead sources: mapping, webhook and historical-lead backfill (without duplicates).

How do I publish my site's form?

The short path avoids the most common mistake, which is leaving it unlinked. From CRM > Settings > Lead sources > New source > MB Suite Form, use Create new form in Web Forms: you build the form and come back on your own with it already selected in the source. Close with Save and link.

When building it you define the fields, who receives the email notification and the allowed origins.

The form's Allowed origins are required and the match is exact: https://www.company.com and https://company.com are different. Load the exact form in which your site is served and, if it responds on both, load both.

An unlinked form still sends the email notification and saves the submission, but creates nothing in the CRM. It's the classic cause of "the form works but the lead doesn't show up".

See Turn responses into CRM leads (with their source campaign) and Create your first web form and define its fields.

What does the person who filled in the form receive?

Today, by default: nothing. The email notification you set up when building the form goes to your team, not to the person who completed it. On the other side there's someone who left their details and doesn't know if they arrived. It's fixed with two things in the form itself.

The Auto-responder to the visitor is a confirmation email that goes out as soon as they submit the form. You turn it on right there and it has four fields that decide how it turns out:

Sender — from which address it reaches them. It comes from the senders you have in Settings > Branding.
Subject and Message — they accept variables, so you can address them by name.
Reply-to (optional) — where the reply lands if that person answers that email. By default it uses the form's first internal recipient; if nobody reads that mailbox, your lead's reply falls into the void.

The message that comes preloaded promises something concrete: "We'll reply within 24-48 business hours". Change it to your real time. If you answer in five minutes you're selling yourself short; if you take three days, your first contact with that person is already a broken promise.

The Thank-you page (optional) is what they see on screen when submitting. If you leave it empty they see a success message on the same page; if you load a full URL, you take them wherever you want — a page with next steps, a video, your catalog. It can be changed whenever you want without touching your site's code again.

The auto-responder can't be turned on without a verified email domain and at least one sender configured in Settings > Branding (and the form needs an email field, so it knows who to reply to). That's the real reason your own domain isn't an optional formality: without it, whoever contacts you receives nothing and you have no way to give it to them. See Configure your sending domain so your emails arrive.

How do I make leads arrive with their campaign?

Two pieces, both in Settings > Tracking. Without them, all your leads show up as direct traffic and you can't tell which campaign brings you sales.

The pixel.

Use Enable tracking: the code doesn't exist until you enable it.
Copy the Pixel code — it already comes with your identifier — and paste it before the closing of your site's head tag. In a tag manager it goes as a custom HTML tag fired on all pages.
If someone else manages the site, use Send to developer: it emails the code, the steps and your note.
Check with Installation verification: you paste the URL of a page on your site, press Verify and it tells you whether the code is there.

The pixel's Allowed domains are optional, and leaving them empty means accepting any origin, which is what you want at the beginning. If you load them, they have to match exactly the way your site is served: loading company.com when your site responds on www.company.com breaks tracking that was working. It's exactly the opposite of the form, where origins are indeed required.

The campaign tags. On that same screen, the URL parameters for your ads block gives you the text ready to copy into each platform. Use it instead of writing it by hand: without those parameters, the leads the pixel detects show the platform but not the campaign name.

Full detail: Install the MB Suite Pixel to attribute your web traffic and Attribution: which campaign generated each sale (real ROAS).

How do I check it turned out right?

Use an email address that does not exist in your base.

You submit your form from the site: the email notification arrives and the lead is created in the CRM.
That lead brings the custom fields you mapped, with data.
You enter your site with an address carrying your campaign parameters and generate an inquiry from there: the lead shows its source campaign, not direct traffic.
Every source appears as Active in CRM > Settings > Lead sources.

What if nothing comes in?

What you see	What's missing
The form sends the email but doesn't create the lead	It isn't linked to a source, or the allowed origin doesn't exactly match how your site is served
The lead comes in with empty fields	Those questions weren't mapped in the source. What isn't mapped is lost
All leads show as direct traffic	The pixel is missing on that page, or the campaign parameters are missing in your ads
The pixel stopped recording after touching the settings	Allowed domains were loaded that don't match how the site is served. Empty the list
The ads source doesn't offer your page or your account	The platform isn't connected in Settings > Integrations, or that account doesn't have you as an administrator

The symptoms in more detail: Leads don't come into the CRM or don't sync.

What's next?

If you use WhatsApp and haven't connected it yet, complete the milestone with the other half: Connect WhatsApp to the CRM: number, line and source.

With milestone 5 closed, the next step is for those leads to have an owner and for someone to find out: Distribute leads and get your team operating the CRM every day.

From this moment on real leads are coming in and there is still no notification to the rep. It's a consequence of the order, not a mistake: distribution and notifications are configured in milestone 6. Until you close it, the form's email notification is all you have, and someone has to open CRM > Prospects every day.

Still have questions?

Ask MIA, the MB Suite AI assistant: open it with the MB AI button (⌘J) in the top bar. MIA knows the section you're in, so you can ask it about what you see on screen — and it can also answer how-to questions about using MB Suite.

Connect forms and ads, and know which campaign each lead came from