Connect Intershop and Act-on

Connecting Intershop and Act-on for a company that uses both could involve enabling the transfer of e-commerce data to marketing automation workflows. This connection could allow customer purchase information from Intershop to inform targeted campaigns or lead scoring in Act-on, supporting more data-driven marketing and improved customer engagement strategies.

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

Contact us

Why connect Intershop and Act-on?

A company operating both Intershop and Act-on could benefit from connecting these systems to enable more efficient and accurate data exchange. Without such a connection, teams may need to manually enter the same information into both platforms, which can lead to errors, duplicated effort, and inconsistencies between records. This situation can result in outdated or mismatched customer and transaction data, making it harder for decision makers to see a complete and current picture of business activity. For instance, sales and marketing teams might act on incomplete or stale information, which could impact campaign effectiveness or customer service quality. If a connection were established, the types of data that could be exchanged would depend on the functions of each system. Intershop is widely recognized as an e-commerce platform, while Act-on is known as a marketing automation solution. In this context, data that could be shared includes product catalog details, customer profiles, order histories, lead information, and campaign performance metrics. This exchange could support coordinated marketing efforts based on real-time sales data or enable personalized communications driven by recent customer activity. Ultimately, the specific data that can be exchanged depends on the capabilities and access provided by each system’s API, and the actual setup is determined according to the requirements of the business and the technical features available in each case.

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 Intershop and Act-on 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.