Skip to Content

Connect Kerridge and Dotdigital

Connecting Kerridge and Dotdigital for a company that uses both could enable the transfer of relevant business or customer data between the two systems. This could facilitate the use of information managed in Kerridge within Dotdigital’s communication or marketing tools, supporting more informed and coordinated customer engagement activities.

You can build this integration on the System2System platform. We design the connection between Kerridge and Dotdigital around the way you work — not as an off-the-shelf connector, but to fit your systems.

Contact us

Why connect Kerridge and Dotdigital?

A company that operates both Kerridge and Dotdigital could benefit from connecting the two systems to allow for more efficient data exchange. Without such a connection, staff may need to enter the same information into both platforms, which increases the risk of errors and consumes valuable time. This manual process can lead to records in Kerridge and Dotdigital drifting apart, so that customer or product data becomes inconsistent between the two. As a result, teams might make decisions based on outdated or incomplete information, which could affect customer communications, sales, and operational planning. If a connection were established, it could enable the transfer of key business data between Kerridge and Dotdigital. For example, customer contact details, sales transactions, and marketing preferences are types of information that might be exchanged between an ERP or business management system and a marketing automation platform. This could support more targeted marketing campaigns and ensure that communications are based on the most current information available. However, what can actually be exchanged depends on what each system exposes through its API, and is determined per situation.

How System2System builds an integration

Connectors

We connect to each system through the interface it offers — an API, a database, a file exchange or a webhook — and handle authentication, rate limits and retries.

Mapping

Fields rarely line up one to one. We map and transform the data so both systems receive it in the shape they expect.

Workflow

We define what triggers an exchange, in which direction data flows and which system takes precedence when the two disagree.

Monitoring

Every exchange is logged. Failures are flagged and can be replayed, so nothing disappears without anyone noticing.

What can actually be exchanged?

That depends on what Kerridge and Dotdigital make available through their APIs, on the licences and modules in use, and on the version each system runs. Which records are synchronised, in which direction and how often, is something we determine together before any work starts.

We are happy to look at your specific situation and tell you what is feasible — including when the answer is that it is not.

About these systems

Read more about each system and what it can be connected to

Looking to connect these systems?

Talk to us about what your setup needs. No obligation.

Contact us