11 Questions to Ask Before Enabling Pardot Features
11 questions to answer before you enable a new Pardot feature, covering prerequisites, permissions, setup and training effort, and timing.
This article gives you 11 questions to ask before enabling any new Pardot feature, so you can prioritize, align stakeholders and implement with confidence. When Salesforce releases a new wave of features for Account Engagement (formerly Pardot), it’s tempting to switch everything on right away.
Without a plan, you risk adding complexity, confusing users or wasting effort on features your team isn’t ready for.
- Before enabling a new Pardot feature, be clear on what it does and why it matters to your business.
- Prioritize “gateway” features such as the Lightning app and Connected Campaigns, since other features depend on them.
- Check prerequisites, setup effort, permissions and whether you need your Salesforce admin or support.
- Plan for changes to the user experience and for training, often the biggest hidden cost.
- Don’t roll out changes during peak campaign periods.
Start with “What” and “Why”
Before you dive into any technical setup, clarify two foundational details:
- What is it? Provide a simple, jargon-free explanation of what the new feature does – so even non-technical stakeholders can understand.
- Why does it matter? Identify the business value. Consider not just your use case, but also Salesforce’s long-term product direction. Many new features signal where the platform is headed.
Take the Pardot Lightning App as an example:
- What: Access and manage Pardot features directly within the Salesforce interface, rather than a separate UI.
- Why: Aligns Pardot with Salesforce’s Lightning experience; a prerequisite for many future enhancements.
This simple framing ensures everyone is aligned on the basics before getting into the operational weeds.
1. Is It a “Gateway” Feature?
Some features unlock access to others. These “gateway” features are worth prioritizing early because they pave the way for future functionality. For example:
- Pardot Lightning App: Required for almost all new Pardot features.
- Connected Campaigns: Enables Engagement History, Snippets, and more.
If a new feature opens doors to broader capability, treat it like a foundation – not a nice-to-have.
2. Are There Prerequisites?
Flip the previous lens: does this feature have other dependencies that need to be implemented first? Hidden prerequisites lead to delays, rework, or roadblocks down the line.
If those dependencies are valuable on their own or required for other initiatives, great. Just make sure they’re factored into your timeline.
3. What Are the Use Cases?
Not all features add value the same way. Build your case by mapping usage to categories that resonate with business stakeholders:
| Category | What It Improves |
|---|---|
| Productivity | Faster or easier execution for users |
| Campaign | Better engagement, personalization, or targeting |
| Reporting | Stronger insights and measurement |
Evaluate whether the benefit is clear and immediate – or if the value is speculative or “nice to have.”
4. What’s the Setup Effort?
Estimate the time and effort it will take your team to get this feature up and running. That includes configuration, testing, documentation, and any necessary cross-team collaboration.
Having a rough idea of workload protects you from midstream surprises – like having to pause work due to limited capacity or shifting priorities.
5. Do User Permissions Need Changing?
Many Salesforce and Pardot features rely on permission-based access. Introducing a new capability may unintentionally give access to users who shouldn’t have it – or block users who need it.
Things to consider:
- Pardot has a limited set of standard permission sets depending on your edition.
- Salesforce has highly configurable profiles and permission sets – far more granular, but also more complex.
Review and plan any changes before enabling the feature, especially if you’re working in a regulated or tightly-governed environment.
6. Do You Need the Salesforce Admin’s Support?
If you’re a Pardot admin without full Salesforce access – or vice versa – make sure your Salesforce Admin is looped in early. Many Pardot features assume deeper Salesforce configuration knowledge and permissions.
This collaboration is especially critical when features cross into areas like custom objects, account hierarchies, or layout customization.
7. Do You Need Salesforce Customer Support?
In most cases, Salesforce support no longer needs to manually enable features. But depending on your org’s history or edition, support cases may still be required. If that’s the case, factor in response time and scheduling into your plan.
8. Are There Any Further Considerations? (“Gotchas”)
Even well-documented features can include gotchas – small issues that trigger big frustrations later. These could be changes in data behavior, user workflow impact, or temporary limitations.
Your best defense:
- Scour documentation for known issues
- Read blogs and guides from community experts
- Test in a sandbox before touching production
Identify and plan for these quirks early, so you aren’t blindsided mid-deployment.
9. Are There Any Impacts on the User Experience?
Think through how this feature will change what users see, click, or do. Will key screens look different? Will their routine tasks shift? Small UI changes can cause larger confusion than you might expect.
Consider customizing page layouts or offering side-by-side comparisons to ease the transition.
10. What’s the Expected Training Effort?
Even intuitive features can derail productivity if training is an afterthought. Before launch, ask yourself:
- Who needs to be trained?
- What’s the learning curve for this feature?
- Do you need guides, videos, or live sessions?
Training can easily be the biggest hidden cost – and the biggest success factor – in any rollout.
11. Have You Checked Your Campaign Calendar?
Lastly, don’t forget timing. Avoid deploying changes right before or during peak campaign activity. The last thing you want is unanticipated disruption during a product launch or quarterly push.
Cross-reference your implementation schedule with your campaign calendar before you commit.
Final Thoughts
Salesforce releases dozens of new enhancements for Account Engagement (Pardot) each year, and adopting them well depends on choosing the right ones rather than the most. These 11 questions help you prioritize by business value, team readiness and implementation effort.
With a structured approach, you’re not only adopting new tools, you’re investing in lasting, scalable performance.
Planning your next Pardot rollout? Get in touch with us and let’s talk about your goals.
