Pick a Pardot implementation partner by what you can verify. That means the current Account Engagement certifications on the people assigned to you, delivered projects that look like yours, and a Salesforce partner record that shows both. Pardot has been sold as Marketing Cloud Account Engagement since 2022. The partner's job is your own marketing setup, from the Salesforce connector to scoring, Engagement Studio and reporting.
A SaaS company usually meets a second Pardot question first. Enterprise customers run Account Engagement and want your product's data in it, and no marketing consultant builds that. It is the native integration enterprise customers expect before they buy, and your company owns it. You build the package, pass review and publish the listing, then keep it working in every customer's org. Appnigma covers that side with native Salesforce marketplace apps ("Your product, inside Salesforce or HubSpot."), built by ex-Salesforce engineers. The integration rules come first below, then the partner decisions.
Updated October 2026. Checked against Salesforce's Account Engagement pricing page, the Account Engagement developer guide, Trailhead credential pages and the FY27 consulting partner program brochure. The earlier version listed Plus at $2,500 a month and Advanced at $4,000. They are now $2,750 and $4,400. It labelled Marketing Cloud Next prices as Marketing Cloud Engagement prices, said Premium has the highest API limits (it matches Advanced), and said Account Engagement shares Sales Cloud's data model (prospects are separate records that sync). It also used retired certification names and partner tiers, and named firms under brands they no longer use. This version fixes those and adds the integration side for SaaS vendors.
When your customers run Account Engagement
This is the Pardot problem a consulting partner can't solve for a SaaS company. A customer asks for your webinar attendance, product usage or intent data inside their Account Engagement, so their scoring and Engagement Studio programs can use it. You need an integration that installs in every customer's org, and the developer guide sets the rules for it.
Start with the partner program. "The only partner program that Account Engagement supports is the ISVForce program," and it "doesn't support the other AppExchange Partner Programs, like OEM or VAR" (Get Started as an Account Engagement ISV). A consulting partner who wants to sell an app must also join the AppExchange program. Our post on consultants, product development firms and ISVs explains how those roles split.
Next comes how the data gets in. External activities "feed prospect activity data into Account Engagement where it can be used in automations," and external actions let Engagement Studio trigger something in your app (Work with Extensibility Features). The same page says marketing app extensions "can be packaged," and that a third-party service building a generic integration should "consider creating a managed package with the connected app." Packaging has three rules.
- "External activities aren't available for packaging, but they can be configured using Tooling API." Your setup flow creates them in each customer's org through the Tooling API.
- "Don't create a business-unit assignment for packaged extensions." The customer's admin assigns the business unit after install.
- "External Actions don't automatically retry when there's a response delay from a third-party service," and the guide suggests a 2 second response target (External Actions). Your endpoint has to be fast and your action has to retry.
Submitting an activity is one call to the v5 endpoint, per the External Activity guide. The extension and type values are the DeveloperName fields you created, and the values here are placeholders.
POST /api/v5/external-activities HTTP/1.1
Host: pi.pardot.com
Authorization: Bearer <customer access token>
Pardot-Business-Unit-Id: <customer business unit id>
Content-Type: application/json
{
"extension": "YourProduct",
"type": "trial_started",
"email": "[email protected]",
"value": "Team plan"
}Two things in that request vary by customer. The token comes from the customer's own OAuth grant, and the business unit ID is one of possibly several in their org. Sandboxes use pi.demo.pardot.com instead of pi.pardot.com (Authentication).
Then plan for the customer's edition, because it caps your app. Growth+ customers have no external activity extensions, and Plus+, Advanced+ and Premium+ allow 10, 20 and 30 (pricing page). Your app also shares the customer's daily API budget. Here is a worked example from the documented limits. A Plus+ customer gets 50,000 calls a day. If your app writes 10,000 activities a day with one call each, it uses 20% of that customer's daily calls, and their other tools share the rest. The API also allows "up to five concurrent API requests" (API overview). For 10,000 records or more, the ISV guide points to the import and export APIs.
Two more details cause most first-release bugs. "Account Engagement API requests can only be made against one business unit at a time," and "Any app you create must be able handle multiple business units" (ISV guide). Authentication is Salesforce OAuth, and "the "pardot_api" scope must be one of the selected OAuth scopes" (Authentication).
All of this is product work that lives across every customer org. Appnigma's done-for-you integrations team takes it on ("Build your product. We'll build the integrations."), with a named integration engineer and ongoing maintenance. Our managed package guide covers the packaging and security review steps.
What a Pardot implementation partner sets up
Most of the work is the connector, scoring and Engagement Studio, and the connector decides whether the rest works. Three questions about it tell you more than a case study.
First, ask how the partner handles records that already exist. Account Engagement keeps its own records. Salesforce's developer guide says "A prospect is a record in Account Engagement that represents an individual. Prospects sync with leads, contacts, and person accounts in Salesforce" (Get Started as an Account Engagement ISV). They match on Salesforce ID, with email as a secondary match. Leads and contacts that aren't in Account Engagement yet "don't sync to Account Engagement automatically" (Plan Your Integration). A partner without a plan for those records leaves your first scoring run blind to your existing pipeline.
Second, ask how they connect campaigns. The ISV guide notes that "Account Engagement campaigns and Salesforce campaigns are different objects that don't sync directly by default." Campaign influence reporting depends on that link, so a partner who skips it gives you dashboards that can't credit marketing for pipeline.
Third, ask what the sales team will see and when. The same guide says "Sync does introduce a few minute delay." Alerts and lead assignment rules built for instant data fire late or on stale values.
Which Account Engagement edition should you buy?
Choose the Account Engagement edition before you sign a partner, because the edition decides which features a partner can set up at all. Salesforce now sells the editions as Account Engagement+, and each one includes a Marketing Cloud Next edition. Prices below are list prices from the Account Engagement pricing page, per org per month, and "All per month products require an annual contract."
| Edition | List price per month | Contacts included | API calls per day | What it adds |
|---|---|---|---|---|
| Growth+ | $1,250 | 10,000 | 25,000 | Engagement Studio, 50 forms and landing pages, 50 automation rules |
| Plus+ | $2,750 | 10,000 | 50,000 | Multi-touch attribution, multiple scoring categories, 10 external activity extensions, B2B Marketing Analytics |
| Advanced+ | $4,400 | 10,000 | 100,000 | Custom user roles, 2 business units, Einstein Lead and Behavior Scoring, 20 external activity extensions |
| Premium+ | $15,000 | 75,000 | 100,000 | 5 business units, 5 sandboxes, B2B Marketing Analytics Plus, Premier Success, 30 external activity extensions |
The API figures come from the Account Engagement API overview, which lists "Advanced 100,000" and "Premium 100,000" per day. Premium buys more contacts, business units and support, not more API capacity.
Some gaps are add-ons, not walls. The pricing page lists Advanced Dynamic Content at $400 a month on Growth+. Plus+ can buy Custom Object Integration for $400 a month and a dedicated IP for $500. Extra contacts cost per 10,000, at $100 a month on Growth and $150 on Plus. Here is a worked example from those list prices. A team with 30,000 contacts on Plus+ pays $2,750 plus 2 x $150 a month. That is $3,050 a month, or $36,600 a year before any partner fee. Moving that team to Advanced+ costs $4,400 plus 2 x $300, or $5,000 a month. Price both editions with your contact count before a partner recommends one.
For a SaaS company, the column people miss is external activities. Growth+ has none, so webinar, product usage or intent data from other tools can't feed scoring there. If your marketing plan depends on those signals, Plus+ is the floor.
How to check a partner's Salesforce credentials
Older guides describe badges that no longer exist. The FY27 consulting partner program brochure cut four tiers to two, Select and Summit, and says "28 Competencies Replace 170 Navigator Distinctions." A competency is earned at Accredited or Expert level through certifications, completed projects and customer satisfaction. The tier describes the firm, while the B2B marketing automation competency describes the practice you would hire.
Then check people, not totals. The current credentials are the Marketing Cloud Account Engagement Specialist and Consultant, and firms still count them under the old "Pardot Consultant" name. Ask which named people on your project hold one.
Brands on older lists have moved too. Per each firm's own site, bluewolf.com redirects to IBM's Salesforce consulting page, Silverline is Mphasis Silverline, and CloudKettle redirects to Ateko. Sercante still trades under its own name. Search AgentExchange, which salesforce.com labels "AgentExchange (formerly AppExchange)", by the marketing competency.
What a Pardot implementation costs
Salesforce publishes Account Engagement license prices on its pricing page. It does not publish partner fees, and any range you read online, including the one in the earlier version of this post, is one firm's estimate. Partners quote per project, so you can only compare their quotes against the same scope.
Ask each partner to price the same workstreams separately, from the connector and data cleanup through scoring, Engagement Studio and reporting to post-launch support. Then the quotes line up and you can see which partner skips discovery or support to look cheaper. Add the license and you have the real first-year number. At list price, Plus+ with 30,000 contacts is $3,050 a month. The license line alone is $36,600 a year.
Timelines work the same way. Salesforce doesn't publish an implementation duration. The work that sets the schedule is data cleanup before the first sync and the number of business units, so ask for a plan with dates tied to those two items.
Is Pardot being discontinued?
No. Salesforce answers it on the pricing page. "No, there are no End-of-Life (EOL), End-of-Sale (EOS), or End-of-Roadmap (EOR) plans for Marketing Cloud Account Engagement" (Account Engagement pricing).
The packaging is what changed. "Account Engagement+ allows Account Engagement customers to access Marketing Cloud Next," the newer marketing product on the core platform. Access comes through permission set licenses. Customers "will need to purchase Einstein Request Credits, Messaging Credits, and Data 360 Credits to use Marketing Cloud Next features." If a partner's proposal uses Next features, ask for the credit cost next to the license cost.
For a SaaS vendor the bigger point is the API split. Salesforce's developer guide says "Marketing Cloud Next, Marketing Cloud Engagement, and Marketing Cloud Account Engagement use different APIs that aren't compatible with each other" (Get Started with Marketing Cloud Next). A customer on Account Engagement+ may run campaigns in both products. An integration built on the Account Engagement API keeps working, but it doesn't reach Next, so decide which product your integration supports before you scope it. The $1,500 and $3,250 prices that circulate in Pardot comparisons are Marketing Cloud Next Growth and Advanced Editions (Marketing Cloud pricing). Our Marketing Cloud integration guide covers how the three products differ for an integration.
Mistakes that cost the most after go-live
Each of these traces to documented Account Engagement behavior, not to a survey of projects.
- Assuming the CRM data arrives on its own. Existing leads and contacts don't sync in automatically, so the first scoring run misses them.
- Buying Growth+ and planning on external data. External activities aren't in Growth+, so the scoring model you designed can't use webinar or product signals.
- Paying for Premium+ to get more API calls. Premium+ has the same 100,000 daily calls as Advanced+.
- Hiring by company certification totals. The competency counts the firm, but your project gets specific people.
- Asking a marketing consultant to build your product's integration. That needs an ISVforce app, a managed package and ongoing maintenance in every customer org.
Frequently Asked Questions
How much do Pardot implementation partners charge?
Salesforce doesn't publish partner fees, and partners quote per project. Compare quotes by asking each partner to price the same six workstreams, then add the license, which starts at $1,250 a month for Growth+.
Can a managed package include Account Engagement external activities?
The package can carry the marketing app extension and its action types, but external activities aren't packageable. Your setup flow creates them through the Tooling API, and the customer's admin assigns the business unit after install.
Does Premium+ give more API calls than Advanced+?
No. Both editions get 100,000 Account Engagement API calls per day, with five concurrent requests. Premium+ adds contacts, business units, sandboxes and support.
Can Appnigma build an Account Engagement integration for our product?
Appnigma builds the native Salesforce apps and integrations SaaS teams' enterprise customers ask for, with a named integration engineer and ongoing maintenance. An Account Engagement integration, such as external activities from your product, is scoped as part of that work. It doesn't replace a consulting partner for your own marketing setup.
Related Articles
- Salesforce Marketing Cloud integration guide for SaaS teams
- Salesforce managed package guide
- AppExchange app development guide
- Salesforce integration tools compared
Sources
- Marketing Cloud Account Engagement Pricing, Salesforce
- Marketing Cloud Pricing, Salesforce
- Get Started with Account Engagement API, Salesforce Developers
- Get Started as an Account Engagement ISV, Salesforce Developers
- Work with Extensibility Features, Salesforce Developers
- External Actions, Salesforce Developers
- External Activity, Salesforce Developers
- Authentication, Salesforce Developers
- Plan Your Integration, Trailhead
- Marketing Cloud Account Engagement Specialist credential, Trailhead
- Marketing Cloud Account Engagement Consultant credential, Trailhead
- FY27 Consulting Partner Program brochure, Salesforce
