Salesforce Account Engagement

Salesforce Account Engagement runs forms, landing pages, prospect scoring and nurture programs against a Salesforce sales database. Einstein adds behavioral predictions, account prioritization, send timing and content assistance. Agentforce Lead Management can review prospects and add them to nurture programs, while the Account Engagement+ bundle also opens access to Marketing Cloud Next. Those are distinct capabilities with edition and consumption requirements. The established automation engine still captures leads, evaluates rules and sends campaigns without generative AI, making AI an extension of a complete marketing product.

Engagement Studio lets marketers test paths, preview assets and then start a program. Administrators and users with the Marketing role control that launch, although warnings can be dismissed. Pausing a program normally pauses a prospect's remaining wait time; changing its time zone is an exception that allows elapsed time to count. Date specific email steps are skipped when the scheduled date has passed. These controls support deliberate testing and interruption, but pausing does not undo messages already sent or reverse completed changes to prospect records.

Einstein separates lead scoring, behavior scoring, campaign insights, attribution and account prioritization into different models and data uses. Lead scoring can use a global model, while the other named Account Engagement features use different, restricted inputs. Einstein Assistant drafts email subjects and bodies, forms and landing page text after an administrator enables it. OpenAI and Microsoft Azure are named generative AI suppliers. Salesforce names no model version or route for a given generated asset, and the generation service remains separate from the models used for lead and behavior scoring.

Vashi uses Account Engagement to score leads and support targeted upselling across a distribution business with more than 40,000 products. Its broader Salesforce implementation includes Sales Cloud, Service Cloud, quoting tools and an ERP connection. Vashi reports doubling its business over three to four years and a 10% increase in opportunity closure. Those results describe a substantial commercial operation, but the closure figure lacks a defined denominator and measurement window. The implementation spans marketing, sales, service and operational changes, so the gain cannot be assigned to Account Engagement alone.

Permission based sending is part of Account Engagement's operating rules. Messages need an accurate sender identity, a physical mailing address, an unsubscribe route and appropriate privacy information. The sender remains responsible for consent and tracking notices. Operational emails are a distinct exception: an administrator can enable them for critical nonmarketing notices, including messages to prospects who opted out of marketing. That capability also works within Engagement Studio. Its availability does not authorize promotional use of a transactional route, and an imported audience still needs its own permission history.

The DPA places Salesforce in a processor role for customer directed processing and requires confidential handling under the customer's instructions. It covers assistance with access, correction and deletion requests, supplier obligations and security incidents. Transfers use current EU standard contractual clauses, with UK provisions and other applicable mechanisms. Named subprocessors have service and location details.

Within Account Engagement, prospects can be permanently deleted after entering the recycle bin, and associated Einstein data is removed through synchronization. The deletion path covers both the marketing record and its associated prediction data, while collection permissions remain with the customer.

Prospect information comes from customer records, form activity and connected Salesforce objects. Einstein Key Accounts adds company information from public websites when account fields such as industry or business size are incomplete. Its recommendations combine those attributes with engagement and historical opportunity creation, and the account tiers are specific to each organization. This is a different input path from a person's submitted form.

Enrichment values carry no field by field rights record, and the customer remains responsible for lawful collection and use of its imported contact data. Browser cookie restrictions affect that history: when third party cookies are blocked, activity tracking, progressive profiling and form prefill do not continue across subdomains. Changing a tracker domain also resets the cookie association.

Account Engagement uses a Salesforce connector and supported APIs to exchange prospect and sales data. Field settings determine whether Salesforce, Account Engagement or the most recently updated value takes priority, and changes apply to future synchronization. Marketing Data Sharing can limit which sales objects enter the marketing system on eligible editions. Connected third party services require their own account permissions and terms.

This integration model avoids dependence on a salesperson's browser session, but it does not provide a blanket guarantee that every installed application or customer data flow meets another platform's conditions.

Salesforce's customer data access setting permits global predictive model training and service improvement by default, except for Government Cloud and organizations that have opted out. Turning it off stops new sharing; collected data used for service improvement can remain for up to 30 days. Global lead scoring uses a different training arrangement from Account Engagement features that do not use a global model. Separate zero retention arrangements apply to third party language models. These controls address different uses, so an external provider restriction is not a universal prohibition on Salesforce's own learning.

AI assistance can create campaign text that a marketer edits before it reaches a prospect. The AI use policy requires disclosure when people interact directly with automated systems unless a human is in the loop, and prohibits misrepresenting automated output as original human content. That policy covers Agentforce and Einstein alongside the ordinary sender identity rules for email. Generated messages get no automatic label, and the product's Article 50 approach is not set out. An editor's AI acknowledgement is separate from information shown to the eventual recipient.

The Salesforce connector moves prospect information into sales workflows with configurable field precedence. Marketing Data Sharing limits eligible Lead, Contact, Opportunity and custom object data on supported editions, rather than requiring every record to synchronize. APIs extend that connection into extraction and custom workflows. The asynchronous export API can return prospect and activity data as CSV, with up to 150 selected fields and downloads that expire after seven days. Exports queue per account and have resource limits, so large migrations need scheduled extraction rather than unlimited simultaneous jobs.

Account Engagement's core service runs on AWS in the United States, while some Einstein processing, including send timing and engagement frequency, runs in the United States and Ireland, and generative AI suppliers add their own locations. Customers are separated logically on shared infrastructure, and Salesforce's broader regional hosting does not move this product's contact database. No setting locks core records, predictions and every AI request to one region. Advanced+ includes two business units and two developer sandboxes and Premium+ five of each, so larger teams can partition data and test changes before release.

Account Engagement carries SOC 2 and SOC 3 reports and ISO 27001, ISO 27017 and ISO 27018 certification within Salesforce's assurance program, with detailed reports and scope materials on request. Product controls include permissions, custom user roles, network restrictions, encrypted transport and retained security logs, and Salesforce requires multifactor authentication for covered user access, including federated sign in. A bring your own key option covers encryption at rest. These protections sit alongside the customer's own configuration of roles and integrations, and a connected third party application stays outside the same audit scope.

Growth+ costs $1,250 per org a month on an annual contract, with 10,000 contacts, 50 automation rules and 25,000 API calls a day. Plus+ is $2,750, Advanced+ is $4,400 with two business units and a dedicated IP, and Premium+ is $15,000 with 75,000 contacts and Premier Success. Extra contacts cost $100 per 10,000 a month, SMS and WhatsApp credits start at $10 per 1,000, and Premier Success on the lower editions adds 30% of net license fees. Marketing Cloud Next access comes with every edition but consumes Einstein, messaging and Data 360 credits, so the full bill depends on usage.

The export API creates CSV files for prospect and activity data, letting a marketing team keep structured records outside Salesforce, with downloads expiring after seven days. Customers can ask for their data back within 30 days after the contract ends, and inactive production data and rolling backups then follow separate deletion periods. Permanent prospect deletion also removes associated Einstein data.

Engagement Studio programs, assets and execution history have no export that would rebuild them elsewhere. Salesforce states it has no end of life or end of sale plans for Account Engagement, which bears on how soon a team needs an exit plan.

Sending requires a verified domain, and DKIM can authenticate mail from that domain. Dedicated IP options give the customer responsibility for its own sending reputation. Dynamic lists can suppress unengaged prospects, while a permission pass can refresh an old list once and cannot be used on a purchased list. Salesforce's reputation team monitors bounce rates above 10% and complaints above 0.1%, with outreach and possible suspension when problems arise. Operational email can bypass marketing opt outs, so that route requires separate discipline from ordinary campaign suppression.

Account Engagement is built for B2B marketing teams that connect prospect activity to a Salesforce sales process. Vashi's distribution operation illustrates lead prioritization and upselling across a large industrial catalog. Higher editions add business units, a developer sandbox and more automation capacity, supporting organizations with separate marketing teams or divisions. Smaller teams still need the relevant Salesforce environment and administration. Access to Marketing Cloud Next broadens the available channels, but it introduces another set of setup and consumption choices rather than removing the underlying Salesforce dependency.