This is how I would use Salesforce and Marketing Cloud to build an automated journey that identifies Marketing Qualified Leads (MQL), nurtures them based on engagement, and routes sales-ready leads to the appropriate next step.
The end-to-end path a form submission travels, from lead creation through journey orchestration and sales ownership.
Salesforce Lead IDbecomesContactKey| ContactKey | Lifecycle | Form Source | Opt-In | |
|---|---|---|---|---|
| 00Q...123 | user@email.com | MQL | Website | Yes |
I would start with the data. When someone submits the website form, I would create or update their Lead record in Salesforce CRM. Salesforce would remain the source of truth for information like lead status, form source and email consent. I would then use Marketing Cloud Connect to bring the Salesforce data into Marketing Cloud. In Contact Builder, I would connect the data back to a unique Contact Key so the same person can be consistently identified across their marketing activity.
Use the Salesforce Lead/Contact identifier as the Contact Key rather than email address to maintain a persistent unique customer identity across every attribute group.
Next, I would define exactly who should enter the journey. I would create a sendable Data Extension specifically for qualified website leads. To enter this audience, the lead would need to meet each qualification rule: they submitted the correct website form, their Salesforce Lead Status is MQL, they fall within the appropriate date range, and they have not opted out of marketing emails. This gives me a clean audience before anyone ever enters the nurture journey.
| ContactKey | EmailAddress | FirstName | LeadStatus | FormSource | CreatedDate | EmailOptIn |
|---|---|---|---|---|---|---|
| 00Q...123 | user@email.com | Jordan | MQL | Website Form | 2025-02-04 | True |
| 00Q...481 | lead@company.co | Priya | MQL | Website Form | 2025-02-06 | True |
| 00Q...907 | hello@studio.io | Marcus | MQL | Website Form | 2025-02-09 | True |
I wouldn't want to manually rebuild this audience every time a new lead comes in. I would use Automation Studio to automatically evaluate the Salesforce data on a schedule. A SQL Query Activity would look for leads who meet my qualification criteria and update the MQL Data Extension with the contacts who are eligible for nurture. This keeps the audience current and gives Journey Builder a reliable, controlled entry source.
SELECT
ContactKey,
EmailAddress,
FirstName,
LeadStatus,
FormSource
FROM Lead_Data
WHERE LeadStatus = 'MQL'
AND FormSource = 'Website Form'
AND EmailOptOut = 0Once I have a clean MQL audience, I would use Journey Builder to manage the actual nurture experience. Qualified leads would enter from the MQL Data Extension and receive the first nurture email. From there, I would add wait periods and engagement splits so the next step can change based on how the lead interacts with the campaign. Engaged leads could continue through the primary nurture path, while leads who don't engage could receive a different follow-up. I would also check the lead's current Salesforce status before continuing the journey so the messaging stays aligned with where they are in the sales process.
The journey shouldn't keep nurturing someone once they're ready for sales. I would use updated Salesforce Lead Status data to determine when a lead should leave the MQL journey. If the Lead Status changes from MQL to SQL or the lead converts, they would exit the nurture path. Salesforce could then update ownership, create the appropriate sales task and move the lead into the next stage of the sales process. This prevents qualified leads from continuing to receive outdated MQL messaging and creates a cleaner handoff between marketing and sales.
Right message. Right lead status. Right owner.
Automation Studio manages the data → Journey Builder manages the experience → Salesforce CRM manages the sales process.
Only qualified and marketable leads enter nurture.
Lifecycle progression connects marketing activity with sales follow-up.
SQLs and converted leads are prevented from receiving outdated MQL messaging.
Track movement from Form Submission → MQL → Engagement → SQL → Conversion.