Microsoft Dynamics Business Central and DotDigital
Integration Agency & Consultants
At scale, disconnected ERP data leads to untargeted marketing and wasted budget. When Microsoft Dynamics Business Central financials are not aligned with DotDigital, marketing teams lose the ability to segment by real lifetime value or purchase frequency. Cogent connects these systems to ensure your Sales Order history and customer records drive measurable revenue growth through accurate personalisation. We focus on the operational integrity of the data flow, ensuring marketing builds off a verified system of record.
Auditing inefficiencies in the ERP landscape
We connect Microsoft Dynamics Business Central and DotDigital, integrating your ERP and ESP platforms for efficient operations. Our consulting services are invaluable, with our system audit uncovering inefficiencies and integration gaps between Microsoft Dynamics Business Central, DotDigital, and your wider ERP and ESP landscape. This enables our consultants and your team to take decisive action, ensuring your technology ecosystem runs smoothly and efficiently. As a result, you can deliver an outstanding customer experience, leveraging the full potential of both your ERP and ESP investments.
Solution Design
Our design for Business Central and DotDigital prioritises the ERP as the system of record for all customer financials and purchase history. We implement a specific design choice to push financial summaries via Insight schemas rather than direct table mapping. This protects Business Central performance during high-volume syncs, a critical trade-off that trades minor intra-day latency for system stability.
We sequence the sync to validate email uniqueness in the ERP before records reach DotDigital, preventing primary key failures. While marketing activity lives in DotDigital, consent changes must propagate back to the Business Central Marketing Setup table to maintain a unified financial trust boundary. This opinionated design ensures finance closes the month off verified ERP data while marketing executes campaigns based on the most recent, validated transaction history.
Synchronising customer financials and transactional history
The integration between Microsoft Dynamics Business Central and DotDigital synchronises customer financials and transactional history to drive segmented marketing. Business Central acts as the system of record for Sales Orders and customer status, pushing data to DotDigital for campaign execution.
To maintain data integrity, the sync uses the Customer email as the primary link, though logic must be applied when multiple account numbers share an email address. Transactional data such as Sales Invoices and Credit Memos are pushed to DotDigital's Insight data schemas. This avoids direct database contention on the Business Central Customer table while providing marketing teams with accurate lifetime value and order frequency metrics.
Automations usually trigger based on order status changes. When an order is posted as shipped in the ERP, the integration signals DotDigital to fire post-purchase campaigns. This ensures customer communications remain anchored in real operational events, avoiding the risk of sync illusion where customers receive messages for orders that have not yet been processed.
Securing data flow with compliant orchestration
Leveraging IPaaS with ISO 27001 and SOC 2 and above security accreditations enables secure, efficient integration between Microsoft Dynamics Business Central (ERP) and DotDigital (ESP). This approach simplifies connecting ERP and ESP systems, ensuring data integrity and compliance. Using an IPaaS platform for Microsoft Dynamics Business Central and DotDigital integration reduces risk, supports scalability, and guarantees that sensitive information is protected to the highest standards, making complex integrations straightforward and secure.
Monitoring field mismatches and operational drift
Dashboards often mask the silent decay of customer data. In typical Microsoft Dynamics Business Central and DotDigital setups, a sync might report success even when field-level mismatches are corrupting your segments. A change to a customer record or a missing required email field in Business Central can prevent a record from reaching a marketing list, but these gaps often only surface when a campaign fails to deliver.
We focus on surfacing the specific failures that occur between your ERP and marketing automation: - Sync exceptions where Business Central customer records fail to map to DotDigital contact fields due to shared email addresses or missing parent company links. - Latency issues that delay the flow of transactional data, such as recent Sales Order history required for post-purchase triggers. - Data integrity gaps that identify when changes in the ERP Marketing Setup are not reflected in customer contact preferences.
Monitoring these specific triggers allows the team to fix operational drift before it impacts the accuracy of your marketing segments or financial reporting.
Defining ownership for customer data integrity
Handover ensures ecommerce and marketing teams own segment logic while finance maintains data integrity in Business Central. We guide your teams through the operating model, specifically how contact records and Sales Invoice headers map into DotDigital. Marketing learns to monitor sync alerts for shared email address conflicts, while finance manages the Marketing Setup table in the ERP.
We define clear exception ownership to prevent data drift, such as who manages 'Recipient Not Found' errors when records are deleted in only one system. Documentation is provided as a practical operational reference for daily and weekly checks, not a technical archive. It is written for the people running the business to ensure they can maintain segmented campaigns without ongoing technical dependency.
Managing sync exceptions and business continuity
Post-launch support provides ongoing monitoring of the data flow between Business Central and DotDigital to identify sync exceptions before they skew your marketing metrics. We manage the technical relationship between the ERP and ESP, handling issues where customer record updates or transactional triggers fail to fire.
Our team focuses on business continuity, ensuring that as your ERP data evolves, the connection remains stable. We provide an escalation path for operational failures so your ecommerce and marketing teams can focus on campaign execution rather than troubleshooting data gaps.
Common failures
Duplicate email primary key failures
Operational impact: DotDigital requires a unique email address as the primary record key. If Business Central customers share an email across different account numbers, the sync fails silently or overwrites data. This leads to inaccurate lifetime value reporting and fragmented customer history, making reliable segmentation impossible.
Prevention / Action: Implement logic to handle shared email addresses before the push to DotDigital. Ensure the integration identifies existing contacts and uses an 'upsert' pattern that respects the unique email constraint without corrupting the ERP account mapping.
Failed sync of orphaned contact records
Operational impact: Contacts in Business Central that are not explicitly associated with a 'Company' record often fail to sync to DotDigital. This occurs because DotDigital's B2B sync logic frequently requires a parent account relationship. High-value contacts are missing from campaign lists, leading to revenue leakage and incomplete B2B outreach.
Prevention / Action: Audit your Business Central contact hierarchy. The integration must be configured to either enforce the parent company relationship or use a specific data schema that allows individual contact sync without a parent record.
Database contention on financial mappings
Operational impact: Directly pulling 'Total Sales' or 'Last Order Date' from the Business Central Customer table to DotDigital can cause high database contention and system slowdowns. This impacts ERP performance for other users while often resulting in time-out failures that leave marketing segments stale.
Prevention / Action: Protect ERP performance by pulling financial insights from the Sales Invoice Header instead of the main Customer table. Use a dedicated Insight data schema in DotDigital to store transactional summaries, ensuring marketing data stays current without creating operational latency in Business Central.
Frequently asked questions
How does DotDigital handle shared email addresses from Business Central?
DotDigital uses the email address as a unique primary key. If your Business Central setup allows different account numbers to share an email, the integration must include logic to deduplicate or combine these records. Without this, you risk corrupted profiles or failed syncs. We configure the logic to ensure the marketing data correctly represents the customer relationship.
Why do you sync to DotDigital Insight data instead of the contact table?
Directly mapping high-volume transactional data like 'Total Sales' to the Customer table can cause database contention in Business Central. We typically push this data to DotDigital Insight schemas. This allows marketing to perform complex segmentation on Sales Invoice history without impacting the ERP performance that your finance team depends on.
What happens if a contact is deleted in DotDigital?
If a contact is deleted in DotDigital but remains in the Business Central Marketing Setup, the integration may trigger 'Recipient Not Found' errors during the next sync. We implement workflows to ensure deletions or suppressions are handled across both systems, maintaining data integrity and reducing log errors.
Can the integration handle B2B contact hierarchies?
Yes, but DotDigital's schema often requires contacts to be linked to a parent company record for effective B2B segmentation. We ensure the Business Central contact search and mapping logic respects these relationships so that individual contacts are correctly categorised within their account structures.