Define the business unit
Confirm the intended business unit, authorized connection and prospect data scope during implementation discovery.
- Receives
- Marketing and Salesforce account context
- Produces
- Connection and ownership specification
Marketing Cloud Account Engagement integration.
Coordinate prospect and campaign operations within an agreed Salesforce marketing and sales model.
Let’s connectProspect operations aligned with Salesforce ownership
Assess Account Engagement and its native Salesforce synchronization together so two update paths do not compete over the same prospect data.
Map prospect context
Agree how prospect identity, lists and campaign references relate to Salesforce lead or contact records.
- Receives
- Approved prospect attributes
- Produces
- Prospect to CRM crosswalk
Verify synchronization
Inspect the resulting records on both sides and ensure external automation does not compete with native synchronization.
- Receives
- Prospect update and CRM state
- Produces
- Reconciled marketing and sales context
Step 1 of 3
Inspect the data contract.
Select a field to examine its owner, permitted changes and conflict handling. Clear ownership keeps updates consistent across systems.
| Field or object | Accountable owner | Mapping and control |
|---|---|---|
| Marketing administrator | Scopes the intended marketing environment. | |
| Account Engagement | Mapped to the relevant Salesforce relationship. | |
| Marketing and sales operations | Documents which process may update each shared field. |
Resolve the important decisions.
Native and custom paths
Review the existing connector behavior before introducing an additional write path.
Configuration verification
API access and supported resources must be checked against the customer’s selected environment.
Validate before handover.
Select the scenarios to discuss with your implementation team.
0 of 3 selected
Test an example workflowPlatform documentation
A connection with a clear purpose.
Account Engagement APIs and native Salesforce synchronization assessed together to avoid competing update paths.
We begin by identifying the business process this connection supports. Source ownership, permissions and the expected update behavior are documented before data starts moving.
The data behind the workflow.
ProspectsListsCampaignsActivities
Object and field availability depend on the platform edition, API permissions and the agreed use case. Mapping defines which system owns each value and how changes are reconciled.
Decisions worth making early.
Scope & access
Validate business unit access, supported objects and the relationship with Salesforce records.
Data & behavior
Define which application owns prospect fields and communication eligibility.
From mapping to a maintainable connection.
Discover the workflow
Agree the trigger, source of truth, receiving system and the person accountable for exceptions.
Validate the contract
Confirm permissions, object mappings, identifiers, consent and API behavior using a representative test environment.
Test real scenarios
Exercise expected updates, duplicates, missing data, access failures and vendor rate limits.
Document and enable
Hand over field mappings, credentials ownership, monitoring guidance and recovery procedures.
The engineering detail.
Read the contracts, controls and failure behavior behind a maintainable implementation.
What could work better, together?
Tell us where your operations are today. We’ll help you see what comes next.