Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
- Item 1
- Item 2
- Item 3
Unordered list
- Item A
- Item B
- Item C
Bold text
Emphasis
Superscript
Subscript
The decision is the order of work. Most accounts switch on more features than they govern. Automation rules run in the background, dynamic content multiplies versions and nurture programmes branch, and each one depends on the prospect data your forms collect. Get the capture layer right and the rest has something to work with.
Forms decide the quality of every prospect record
Pardot (Marketing Cloud Account Engagement) offers two ways to capture prospects. Its own forms are built and hosted in the platform, with features such as progressive profiling, which asks returning visitors for new fields instead of the ones you already hold. Form handlers connect the forms already on your website, so your web team keeps control of the design while Account Engagement receives the submissions. Form handlers give up some of those built-in features, and every change to the website form has to be mirrored in the handler.
Whichever route you take, define the fields first. Every later feature, from dynamic content to grading, reads from them. A job title typed as free text cannot drive grading reliably; a picklist can. We challenge the field list early on B2B Sales Cloud projects, because a field nobody fills is a field no feature can use.
Automation rules, segmentation rules and completion actions do different jobs
All three change prospect records automatically, and picking the wrong one causes most of the surprises. A completion action fires once, when a prospect submits a form, clicks a tracked link or downloads a file. A segmentation rule runs once, when you trigger it, on the prospects that match at that moment. An automation rule keeps running in the background and acts on every prospect who matches, now or later, until you pause it.
That continuous behaviour is useful and risky. An automation rule that adds prospects to a list or notifies a sales representative will keep doing so for months. Set the criteria tightly, decide whether a prospect may match more than once and give every rule an owner. Salesforce's platform-native product handles this kind of logic in Flow, as Marketing Cloud Next and its editions describes, and the distinction between one-off and continuous rules carries over.
Engagement Studio turns capture data into nurture programmes
Engagement Studio is the Account Engagement tool for nurture programmes: sequences of emails, waits and conditional steps that branch on what each prospect does or on the data you hold. It compares to Journey Builder in Marketing Cloud Engagement, with a narrower set of channels and a focus on the handover to sales. You can pause and edit programmes while they run.
The design choice that matters most is where a programme ends. It should hand prospects to sales at a defined point, usually a combination of score and grade, and stop mailing them while the sales conversation runs. Programmes without an exit keep mailing prospects a sales representative is already calling.
