SAP B1 and DotDigital
Integration Agency & Consultants
Revenue leakage often begins when marketing campaigns cannot access the transactional data buried in SAP B1. At scale, this disconnect leads to irrelevant customer communications, wasted spend, and inaccurate attribution that prevents finance from trusting marketing reports.
Our approach integrates your ERP data directly with DotDigital to ensure segments are built on actual purchasing behaviour. We focus on bridging the gap between Sales Orders, Business Partner records, and marketing automation to turn your ERP into the system of record for personalised engagement.
Evaluating your current ERP and ESP architecture
Cogent connects your SAP B1 and DotDigital systems efficiently, ensuring your ERP and ESP platforms work in harmony. Our consulting services, including comprehensive system audits, are invaluable for identifying inefficiencies and integration gaps. By addressing these issues, our consultants enable your team to optimise your tech ecosystem, ensuring SAP B1 and DotDigital function smoothly. This results in a more efficient ERP and ESP setup, allowing you to deliver an exceptional customer experience. Our audits provide actionable insights, helping your business operate effectively.
Solution Design
In this integration, SAP B1 typically acts as the system of record for customer data, product catalogues, and order history. A primary design focus is the flow of transactional data from SAP B1 into DotDigital to inform customer segmentation. We often sequence the sync to balance data freshness against ERP performance, usually opting for batch processing for historical data and defined triggers for new engagements. A common trade-off involves the synchronisation frequency of customer profile updates. While real-time updates provide immediate visibility, they can increase system load, so we often recommend interval-based syncing for non-critical attributes. This approach ensures the marketing team can build segments on accurate data without impacting SAP B1 performance. The resulting operating model allows finance to maintain control in the ERP while marketing executes campaigns based on actual purchase behaviour.
Mapping records between SAP B1 and DotDigital
The integration establishes SAP B1 as the authoritative system of record for customer, product, and order data. Business Partner records and transactional history flow into DotDigital to drive segmentation and campaign execution.
To maintain performance, customer updates typically move on a trigger or defined schedule. We recommend restricting the sync of the SAP B1 Item Master to marketing-relevant products to manage database costs and maintain speed. The data flow includes validation checks for common identifier conflicts, such as duplicate email addresses across different Business Partners, ensuring that your marketing automation is powered by accurate, unique records.
Orchestrating the integration via secure middleware
Cogent2 leverages IPaaS to integrate SAP B1 and DotDigital, ensuring secure, efficient connections between ERP and ESP systems. IPaaS platforms offer a centralised framework for data exchange, enhancing security with ISO 27001 and SOC 2 compliance and above. This approach simplifies SAP B1 and DotDigital integrations, providing robust ERP and ESP solutions. The benefits include improved data management, reduced complexity, and adherence to stringent security standards, ensuring reliable and secure operations.
Monitoring data integrity and sync exceptions
Visibility is often lost when teams rely on basic sync status lights that fail to highlight data discrepancies. Hidden issues, such as a customer record failing to update because of a formatting error in SAP B1, can lead to inaccurate marketing segments and missed revenue. We go beyond basic dashboards by surfacing specific data exceptions that require attention. This allows your team to see exactly why a record has not synced and take action in the ERP. By identifying these gaps early, you prevent the gradual erosion of trust in your marketing data and ensure that campaigns reach the entire eligible audience.
Defining daily workflows and data ownership roles
Post-launch, ownership transitions to your internal marketing and operations teams. We provide a clear operating model that explains how customer and order data flows from SAP B1 to DotDigital. Teams learn what to monitor daily, such as sync success rates, and what to check monthly, like data consistency across platforms. We define how to read alerts from the integration layer and establish who owns each exception type, whether it is a data entry issue in the ERP or a segmentation error in the ESP. This handover is supported by operational documentation designed for the staff running your daily marketing activities, not a technical archive. The goal is to ensure your team is confident in the accuracy of the data driving your campaigns.
Maintaining technical reliability and data governance
Ongoing support focuses on preventing operational drift between your ERP and marketing automation. We monitor the health of the sync to identify common failures, such as data mapping conflicts or rejected records, before they disrupt your campaigns.
Our team provides technical oversight for the connection, ensuring that the data flow remains resilient under high volume. You retain ownership of your marketing strategy while we manage the technical architecture required to keep your customer segments accurate and your attribution trustworthy.
Common failures
Identifier mismatch and duplicate records.
Operational impact: Marketing communications may reach the wrong person or be duplicated. This stems from a core database conflict: DotDigital typically uses the email address as the primary unique key, whereas SAP B1 allows duplicate emails across different Business Partner (CardCode) records. Large batches of Contact Persons (OCPR) from B1 can fail to sync if unique identifiers are not handled correctly.
Prevention / Action: Establish a clear logic for handling duplicate emails in B1 before they reach the integration layer. Ensure the mapping recognises the correct contact hierarchy in SAP B1 to maintain a clean subscriber view in DotDigital.
Data type and mapping conflicts.
Operational impact: Customer segments can fail to populate, meaning campaigns reach incomplete lists. This commonly occurs when SAP B1 User Defined Fields (UDFs) are synced to DotDigital fields with mismatched data types. If a B1 field contains Alphanumeric values but the DotDigital target is set to Numeric or Date, the sync will commonly fail.
Prevention / Action: Contrast all UDF data types in SAP B1 against the field settings in DotDigital. Ensure validation is in place to catch format mismatches before they cause sync errors.
Database bloat and inaccurate attribution.
Operational impact: Marketing costs can increase unnecessarily when the entire SAP B1 Item Master is synced into DotDigital Insight Data. Furthermore, if the sync does not account for downstream changes in SAP B1, such as cancellations, marketing ROI reports will overstate actual performance.
Prevention / Action: Restrict the item sync to web-enabled or marketing-relevant products to maintain database efficiency. Ensure the integration logic accounts for status changes in SAP B1 to keep marketing attribution accurate.
Frequently asked questions
Which system holds the master customer record?
For this integration, SAP B1 serves as the definitive source of truth for core customer and transactional data, including Business Partner records and sales history. This information is synchronised to DotDigital to build accurate segments for marketing campaigns based on actual purchasing behaviour. While DotDigital tracks marketing engagement, SAP B1 remains the master system of record.
How does connecting SAP B1 and DotDigital improve our campaign measurement?
By connecting SAP B1 sales data with DotDigital campaign activity, you can build a much clearer picture of marketing ROI. When a Sales Order is created in SAP B1 for a customer included in a DotDigital campaign, this allows for direct revenue attribution. This moves your measurement beyond opens and clicks to see how marketing activity influences actual sales recorded in your ERP.
What happens if contacts in SAP B1 share the same email address?
This is a common failure pattern, as DotDigital requires a unique email address to identify each contact. If multiple Business Partner records in SAP B1 share an email, the integration may only sync one record or consistently overwrite the contact in DotDigital, leading to incorrect segmentation. A robust integration requires a clear rule to either merge, reject, or prioritise these records to maintain data integrity.
We use multiple warehouses in SAP B1. How does this affect stock level synchronisation?
This can cause problems if not handled correctly, as a simple integration might map multiple SAP B1 Warehouses (OWHS) to a single stock figure in DotDigital. This leads to inaccurate inventory levels being used for back-in-stock alerts or low-stock messaging. The integration logic must be configured to correctly aggregate stock from only the relevant SAP B1 warehouses to give DotDigital an accurate total.