Salesforce Commerce Cloud and DotDigital
Integration Agency & Consultants
At scale, the gap between a purchase in Salesforce Commerce Cloud and a campaign trigger in DotDigital becomes a source of operational friction. When transaction data lags, marketing segments become unreliable and automated customer journeys fail to convert. This usually happens when the integration cannot handle peak volume or when customer data fails to map correctly across systems. We ensure your customer records and purchase history stay in step, allowing marketing to execute with the precision required for high-volume retail without relying on manual data fixes.
Diagnosing requirements for retail tech performance
Integrate Salesforce Commerce Cloud and DotDigital seamlessly to enhance your multi-channel and omnichannel retail strategy. Our expertise ensures quick connectivity and efficient system utilization. Leverage our consulting and delivery skills to boost operational efficiency and tech stack performance. We provide comprehensive training to help you scale rapidly and achieve a unified retail approach.
Solution Design
Designs for Salesforce Commerce Cloud and DotDigital typically establish the storefront as the source of truth for customer profiles, while segment membership is managed within DotDigital. A primary design decision involves the timing of data syncs. We often prioritise scheduled batch jobs for transaction history to protect storefront performance during high-traffic periods, while using specific triggers for key signals like abandoned carts. This represents a deliberate trade-off: batching ensures system stability and more reliable reconciliation, even if it introduces slight latency in reporting. The resulting operating model allows marketing teams to execute campaigns without risking the performance of the checkout. This approach ensures that high-volume trading does not lead to operational drift between storefront records and marketing segments.
Mapping data flow and record ownership
Salesforce Commerce Cloud acts as the primary source for customer profiles and transaction data. The integration moves this data into DotDigital to power segments and personalised journeys. To protect storefront performance, transaction history is typically synchronised using scheduled jobs, while high-priority events use real-time triggers. We focus on maintaining data integrity for all orders, including guest checkouts, so that marketing segments remain accurate. By explicitly mapping unique identifiers, the system prevents duplicate records from being created when customer details change, ensuring the marketing team works from a single source of truth.
Orchestrating the stack via IPaaS platforms
Cogent2 uses IPaaS to streamline integration between Salesforce Commerce Cloud and DotDigital, enhancing data flow and automation. Benefits include reduced integration complexity, faster deployment, improved scalability, and seamless connectivity, enabling efficient management of customer data and marketing processes.
Monitoring sync health and segment drift
Standard dashboards can hide silent sync failures that impact marketing accuracy. If order data fails to move correctly between Salesforce and DotDigital, customers receive irrelevant automated emails. We surface these gaps by monitoring the actual flow of records rather than just total counts. This ensures that marketing segments are built on current storefront activity rather than incomplete profiles, reducing the risk of sending incorrect messages. By identifying synchronisation lapses before they compound, we help teams avoid the manual work required to fix drifted segments.
Handover for marketing team data ownership
Handover focuses on the ecommerce and marketing teams, ensuring they own the data relationship between Salesforce Commerce Cloud and DotDigital. We document the operating model in plain English, detailing how transactional data triggers specific customer segments. Marketing teams learn to monitor sync status on a defined schedule and identify records that fail to map. We specify who owns common exception types, such as opt-in mismatches or data gaps. Training ensures teams know what to check to maintain segmentation accuracy and how to interpret alerts. Documentation is an operational manual for running the business rather than a technical reference, designed for those managing campaigns and customer loyalty day to day.
Hypercare and technical governance after launch
We provide ongoing monitoring to identify and resolve synchronisation issues before they disrupt your marketing activity. If data flows between Salesforce and DotDigital stall, we work to find the cause and restore the connection. This approach focuses on maintaining data integrity so that your segments remain trustworthy for live campaigns. We ensure the integration continues to perform as your storefront volume and marketing requirements change, preventing the accumulation of manual data work.
Common failures
Fragmented customer profiles from guest checkouts
Operational impact: When a customer makes multiple guest purchases using the same email address, the integration can create several distinct contact records in DotDigital. This fragments their order history, making it impossible to calculate accurate customer lifetime value or build loyalty campaigns. The marketing team cannot reliably distinguish a one-time buyer from a repeat customer, skewing segmentation and reporting.
Prevention / Action: Design the integration to use the email address as the unique identifier for upserting contacts into DotDigital. On each Salesforce Commerce Cloud order sync, the process should first search for an existing DotDigital contact with that email address. If a contact exists, the new order data is appended to that record; if not, a new contact is created, ensuring one unified profile per email.
Marketing consent and suppression mismatches
Operational impact: A customer's marketing consent status, whether updated in SFCC by the customer service team or via a DotDigital unsubscribe link, is not reliably synchronised. This leads to sending campaigns to customers who have opted out, creating a poor experience and a serious compliance risk. This damages email deliverability scores and can result in direct complaints and regulatory scrutiny.
Prevention / Action: Establish a definitive source of truth for marketing consent, or design a bi-directional sync with strict precedence rules to govern which system wins in a conflict. The integration must update the suppression list in DotDigital based on changes to customer records in SFCC, and vice-versa. This process should run on a frequent schedule and include an initial audit to align all historical consent data.
Delayed or incomplete order data sync
Operational impact: Order data from SFCC arrives in DotDigital slowly or with missing details, meaning post-purchase automations are triggered with a significant delay. This prevents the execution of time-sensitive campaigns like 'review your purchase' or cross-sells based on the recent order. The marketing team is forced to work with stale data, reducing the effectiveness of their segmentation and customer journey logic.
Prevention / Action: The integration should be designed to push order confirmations from SFCC as soon as an order is successfully created. Utilise a message queue to handle high order volumes and manage API rate limits without data loss. Implement monitoring and exception alerts to flag any sync delays or failures, so that the operations team can investigate and resolve issues with the order data payload or connection.
Frequently asked questions
What happens to a customer's data after they place an order in Salesforce Commerce Cloud?
When an order is created in Salesforce Commerce Cloud, the integration updates the corresponding customer record and their purchase data in DotDigital. This allows your marketing team to immediately use that behaviour, for example, by adding the customer to a 'first-time buyers' segment. Without this, new purchase data is not reflected in DotDigital campaigns until the next manual data upload.
How does the integration handle guest checkouts to avoid creating duplicate contacts?
This is a common failure point that requires specific logic during implementation. Because Salesforce Commerce Cloud can allow multiple guest checkouts using the same email address, the integration must be configured to check DotDigital for an existing contact first. If a match is found, the new sales order data is appended to the existing contact, preventing fragmented customer records and ensuring accurate segmentation.
How does this integration help us build more valuable segments in DotDigital?
The integration connects transactional data from Salesforce Commerce Cloud to your marketing activity in DotDigital, which is essential for creating high-value segments. It enables segmentation based on actual buying behaviour captured in the SFCC sales order, such as 'customers who bought SKU X more than once' or 'has a lifetime value over £500 but has not bought in 90 days'. This allows for more relevant campaigns compared to segmenting on basic customer record properties alone.
If a customer unsubscribes in DotDigital, is their status updated in Salesforce Commerce Cloud?
This is a critical two-way sync required for compliance and to maintain a trustworthy customer record. A correctly configured integration ensures the opt-out status from a DotDigital contact is synchronised back to the master customer record in Salesforce Commerce Cloud. Failing to sync this status back creates a significant risk of sending marketing communications to customers who have opted out, potentially after another system Interaction re-subscribes them.