Skip to main content
Talk to an expert
Adobe Campaign marketing automation

Adobe Campaign Marketing Integration Specialists

Customer segments and journeys powered by clean, event-driven data. Adobe Campaign is the marketing automation and engagement layer that runs email, SMS and campaigns triggered by customer events from commerce and order systems. iWeb connects Campaign with your ecommerce platform, ERP and CRM so customer identity, behavioural data, segments and suppression stay synchronised. Works with Adobe Commerce, Magento Open Source, Shopify Plus, BigCommerce and other storefronts.

Adobe CampaigniWeb integration layeryour storefront
Talk to an expertSee the estate map ↓
Works with - Adobe Commerce · Magento Open Source · Shopify Plus · BigCommerce · Other storefronts
On this pageGet a brief reviewed
00 · At a glance

Adobe Campaign at a glance.

Category
Marketing · CRM · CX
Role in the estate
Owns customer, campaign and experience data - where consent, segmentation, lifecycle and channel orchestration live.
Commonly connects with
Commerce platforms · ERP · finance · AI · automation · intelligence · Data · BI
Typical use cases
Send transactional and promotional campaigns triggered by order, browse and cart events from commerce · Synchronise customer consent, unsubscribe and preference changes back to the commerce platform and CRM · Publish segments and audience rules from Campaign into commerce for personalisation, targeting and recommendation engines · Capture browse, cart, product view and purchase behavioural data into Campaign for segmentation and journey scoring
Relevant services
BuildSupportPIM and DataAI for Commerce
01 · What you get

What an Adobe Campaign integration gives you.

Accurate customer segments and journeys

Segments are built from clean, deduplicated customer data with resolved identity across email, phone and customer ID. Journey triggers execute against the correct audience, reducing over-mailing and unsubscribe risk.

Automated and compliant unsubscribe handling

Customer unsubscribes from email, SMS or push automatically flow back to commerce, ERP and CRM systems within SLA. Suppression lists stay in sync, reducing GDPR risk and customer complaints.

Behavioural triggers without manual feeds

Purchase, browse, cart and customer registration events trigger campaigns automatically via streaming or scheduled batch. Campaign execution is event-driven, not manual, reducing operational overhead.

Real-time personalisation and targeting

Segment membership and customer attributes sync to the commerce platform or recommendation engine on schedule or near-real-time, enabling checkout personalisation, product recommendations and dynamic pricing without manual intervention.

Transparent campaign and engagement SLAs

Event latency, segment refresh frequency, unsubscribe sync time and campaign delivery SLAs are defined and monitored. Stakeholders know when and why campaigns execute or fail.

02 · When it's worth it

Where an Adobe Campaign integration earns its place.

If two or more of these are true, the integration usually pays for itself quickly.

Send transactional and promotional campaigns triggered by order, browse and cart events from commerce
Synchronise customer consent, unsubscribe and preference changes back to the commerce platform and CRM
Publish segments and audience rules from Campaign into commerce for personalisation, targeting and recommendation engines
Capture browse, cart, product view and purchase behavioural data into Campaign for segmentation and journey scoring
Reconcile customer identity and GDPR suppression lists across commerce, ERP, Campaign and data warehouses
03 · The limits

Where off-the-shelf connectors fall short.

Vendor connectors are fine for simple cases. Here's where the real ones need more.

Behavioural event schema mapping

Adobe Campaign expects clean, consistent event schemas for purchase, browse, cart and customer actions. If your commerce platform, OMS and ERP emit events with conflicting field names, timestamps or identity keys, the integration must transform and normalise them before Campaign ingestion, or events will fail silently.

Identity resolution and deduplication

Campaign's standard connectors do not automatically resolve customer identity across email, phone, anonymous ID and customer ID fields. If your estate has duplicate or mismatched customer records, segments and journeys will execute against fragmented audiences, leading to over-mailing or suppression gaps.

Unsubscribe and consent workflow automation

Campaign tracks opt-in at the channel and category level, but does not automatically propagate unsubscribes back to the commerce platform, ERP or CRM without manual workflow or custom code. Unsubscribe leakage is common if the reverse sync is not automated and monitored.

Real-time segment membership and personalisation

Campaign's native segment sync is often batch-based (hourly or daily). If your commerce platform needs real-time segment membership for checkout personalisation or recommendation engine input, standard connectors will not meet SLA requirements.

GDPR and suppression list compliance

Campaign does not automatically cross-check suppression lists against multiple data sources or enforce cascading unsubscribe rules across channels without integration logic. If you operate across multiple jurisdictions or have fragmented suppression lists, manual intervention is common.

03b · Honest limits

When Adobe Campaign may not be the simplest fit.

A short, honest list. Not a warning; just where a different shape of system usually costs less to run.

A small marketing surface the ecommerce platform already covers
No agreed source of truth for customer identity
A team expecting the CRM to give a single customer view on its own
Consent treated as a checkbox rather than a data flow
04 · The real work

Organisations often blur the line between transactional identity (in the commerce platform) and marketing identity (in Campaign), leading to unsubscribe leakage and GDPR risk when the two systems drift.

05 · Where it sits

Where this integration sits in your estate.

Adobe Campaign holds the commercial record. The iWeb integration layer manages the rules, mappings, monitoring and exceptions. The commerce platform presents the customer-facing experience. The estate map helps agree ownership before anything is built.

Works across the whole stack. Connect Adobe Campaign to your storefront, ERP and everything between.

System of record
Source / owner
Adobe Campaign
Customer engagement and marketing automation engine that runs campaigns and journeys triggered by behavioural events
  • Campaign definitions and execution logic
  • Email, SMS and push delivery and engagement tracking
  • Segment rules and audience computation
  • Unsubscribe and preference tracking at the channel level
iWeb integration layer
Customer-facing commerce
Commerce platform
Adobe CommerceMagento Open SourceShopify PlusBigCommerceOther storefronts
  • Customer master records (name, email, phone, address)
  • Behavioural events (purchase, browse, cart, registration)
  • Consent and opt-in status
  • Transactional sends (order confirmation, shipping, account alerts)
  • Customer account and pricing data
Connected neighbours
Integration layer
ERP
Provides customer account status, credit limits, order history and lifecycle flags for segmentation and account-based campaigns.
Integration layer
OMS
Emits purchase, fulfilment and return events that trigger campaigns and segment membership updates.
Integration layer
CRM
Shares customer records and support ticket data; receives unsubscribe and preference updates for account management.
Integration layer
Consent Management System
Maintains legal basis for consent; GDPR erasure requests propagate through Campaign into ecommerce and ERP.
Integration layer
Data Warehouse
Receives Campaign engagement events and segment membership for attribution, funnel analysis and customer lifetime value modelling.
Integration layer
Recommendation Engine
Consumes Campaign segments and customer attributes for personalised product recommendations on the storefront.
Two-way sync where relevant
06 · Surrounding systems

Systems this integration usually sits next to.

Examples, not a closed list. iWeb is platform-agnostic on both sides: we wire this integration into whatever ecommerce platform and surrounding systems your estate already runs.

Ecommerce platforms (examples)
  • Adobe Commerce
  • Magento Open Source
  • Shopify Plus
  • BigCommerce
  • Other storefronts
Surrounding systems (examples)
  • ERP (SAP, NetSuite, Sage)
  • OMS (Order Management System)
  • CRM (Salesforce, HubSpot)
  • Consent Management System (OneTrust, TrustArc)
  • Data Warehouse (Snowflake, BigQuery)
  • CDP (Customer Data Platform)
  • WMS (Warehouse Management)
Not sure?

Not sure if this works with your stack?

Tell us what you’re using and what needs to connect. We’ll give you a straight view on what’s possible, what might be awkward, and the safest way to approach it.

Ask us about your stack
07 · Data flows

The data flows we wire.

Each flow has a direction and an owner. We agree both before a line of code is written.

→Into CAMPAIGN
←From CAMPAIGN
↔BOTH WAYS
Customer and behavioural events: Purchase, browse, cart, product view and customer registration events flow from the commerce platform, OMS and ERP into Campaign for segmentation, journey triggers and marketing automation
Identity resolution (email, customer ID, phone) must be accurate and consistent across all touchpoints.
Consent and preference data: Customer opt-in status, channel preferences and unsubscribe flags flow from the commerce platform, CRM and consent management systems into Campaign to enforce suppression rules and channel eligibility before campaign execution.
Campaign execution and triggered sends: Email, SMS, push and other campaign payloads are executed from Campaign based on journey triggers, segment membership and customer attributes
Delivery events and engagement metrics flow back for analytics and journey optimisation.
Segments and audience rules: Segment definitions, rules and audience membership lists are exported from Campaign into the commerce platform, CDP or data warehouse for personalisation, real-time targeting and recommendation engine input.
Unsubscribe and suppression synchronisation: Unsubscribe events from Campaign emails, SMS and push channels flow back to the commerce platform and CRM systems to suppress future campaigns and maintain GDPR compliance
New suppression rules from external systems update Campaign's suppression lists.
Customer master and account changes: Customer name, address, account status and lifecycle changes from the commerce platform and ERP flow into Campaign to keep customer records fresh and enable account-based targeting and lifecycle campaigns.
08 · How we build it

How iWeb configures the integration around your business.

Same method on every integration. The decisions come before the code.

  1. 01
    Design customer identity and deduplication rules

    iWeb defines how email, phone, customer ID and anonymous IDs are resolved and matched across commerce, ERP and CRM systems. Duplicate detection and merge rules are encoded into the integration so segments stay accurate.

  2. 02
    Build event streaming and normalisation layer

    iWeb ingests purchase, browse, cart and customer events from commerce, OMS and ERP, normalises schema conflicts, validates completeness and streams clean events into Campaign for segmentation and journey triggers.

  3. 03
    Automate bidirectional consent and suppression sync

    iWeb routes unsubscribe, opt-in and preference changes from Campaign back to commerce, CRM and ERP systems on schedule or event-triggered. Suppression lists stay in sync and GDPR obligations are met without manual queue review.

  4. 04
    Implement segment publishing and refresh workflows

    iWeb exports Campaign segments to the commerce platform, CDP or data warehouse on schedule or triggered by segment changes. Real-time or batch refresh is aligned with personalisation SLAs and commerce platform capabilities.

  5. 05
    Monitor identity resolution and campaign execution

    iWeb observes customer deduplication success rates, segment membership drift, unsubscribe propagation latency and campaign delivery status. Alerts surface identity mismatches, missing events and suppression failures before they damage campaign performance or compliance.

09 · Ownership

Who owns what.

The single most important table in any integration. One system owns each field; everything else reads it.

Data
Source / owner
Maintained by
Notes
DataContact and customer profile (name, email, phone, address)
Source / ownerCommerce platform and CRM
Maintained byeCommerce operations and customer service
NotesAdobe Campaign reads customer master data from commerce and ERP; changes to contact details propagate back to maintain single customer record.
DataConsent, opt-in and channel preferences
Source / ownerConsent management system (CMS), Campaign and commerce platform
Maintained byCompliance, marketing operations and customer service
NotesOpt-in status flows from commerce/CMS into Campaign; Campaign enforces suppression. Unsubscribe events from Campaign propagate back to commerce and CMS within SLA.
DataBehavioural events (purchase, browse, cart, registration)
Source / ownerCommerce platform and OMS
Maintained byeCommerce and order operations
NotesEvents stream or batch-feed into Campaign for segmentation and journey triggers. Campaign does not own event truth; it consumes and acts on them.
DataSegments, audiences and segment membership
Source / ownerAdobe Campaign
Maintained byMarketing operations and analytics teams
NotesSegment rules are authored in Campaign; membership is computed from customer and behavioural data. Segments export to commerce, CDP or BI for real-time targeting and analytics.
DataCustomer-specific pricing and account flags
Source / ownerERP and commerce platform
Maintained bySales and ecommerce operations
NotesCampaign reads account status for lifecycle and account-based campaigns. Pricing and promotions remain in commerce and ERP; Campaign does not own transactional pricing.
DataCampaign execution, delivery and engagement metrics
Source / ownerAdobe Campaign
Maintained byMarketing operations
NotesCampaign tracks sends, opens, clicks, bounces and unsubscribes. Engagement signals feed back to ecommerce and BI systems for closed-loop attribution and journey optimisation.
DataSuppression lists and GDPR compliance flags
Source / ownerConsent management system, Campaign and compliance registry
Maintained byCompliance, marketing operations and customer service
NotesSuppression lists are maintained in Campaign and sync bidirectionally to commerce and CRM. GDPR erasure and opt-out requests propagate from compliance system through all customer databases.
10 · Experienced integrator

Built this before

iWeb has designed and built Adobe Campaign integrations across retail, e-grocery, health and financial services sectors. We understand how Campaign sits as the engagement and segmentation layer, how behavioural events from commerce and OMS feed into journeys, and how identity resolution and unsubscribe compliance must be governed across multiple systems.

iWeb has resolved customer identity and deduplication across commerce platforms, ERPs and CDPs, preventing segment fragmentation and over-mailing.
We implement bidirectional consent and suppression sync so unsubscribes propagate within minutes and GDPR compliance is maintained without manual intervention.
iWeb normalises behavioural event schemas from multiple commerce and order systems into Campaign, enabling reliable journey triggers and segment computation.
We design the ownership boundary between Campaign (engagement and segmentation) and the commerce platform (transactional data), so overlaps and conflicts are clear.
iWeb monitors segment membership, identity resolution success rates and unsubscribe latency in production, surfacing drift and failures before they affect campaign performance or compliance.

Enterprise digital commerce specialists since 1995

UK-based, employee-owned team

Adobe Gold Commerce Partner

ERP, PIM and operational integration experience

Build, replatform, rescue and long-term support

Platform-led where appropriate, integration-led across the wider estate

11 · Before launch

What we test before launch.

Every one of these is rehearsed before a customer ever sees the integration.

Validate customer identity resolution: confirm duplicate detection rules work across email, phone and customer ID variants.
Test unsubscribe propagation: measure time from Campaign unsubscribe to exclusion in commerce and ERP suppression lists.
Confirm behavioural event ingestion: verify purchase, browse, cart and registration events flow into Campaign and trigger segment updates.
Check segment drift: compare segment membership in Campaign against expected audience size and confirm exports sync to commerce and BI.
Test GDPR erasure: confirm erasure requests propagate from compliance system through Campaign, commerce and ERP within SLA.
Validate consent sync: confirm opt-in changes from commerce flow into Campaign and respect channel eligibility rules.
Monitor latency and error rates: establish baseline event ingestion latency, segment refresh SLA and unsubscribe sync time; alert if exceeded.
12 · Failure points

Common risks and where they bite.

We name these on day one. A risk written down is a risk you can plan around.

Duplicate customer records in segments

If customer identity resolution is incomplete, a single customer may appear multiple times in a segment with different email or phone values. Campaigns execute multiple times against the same person, driving unsubscribes, complaints and engagement damage.

Unsubscribe leakage to suppressed contacts

If the reverse sync from Campaign back to commerce is not monitored, unsubscribed customers may still receive campaigns from the ecommerce platform or transactional system. This violates GDPR and drives CASL or GDPR complaints.

Missing or late behavioural events

If the commerce platform or OMS does not emit behavioural events reliably, journey triggers do not fire and segments go stale. Customers do not receive timely purchase reminders or abandoned-cart campaigns, reducing revenue.

Segment refresh lag during peak seasons

If segment refresh is batch-based (hourly or daily) and event volume spikes during promotions or holidays, the pipeline delays and personalisation rules miss high-value customers. Inventory overstocks or stock-outs go uncommunicated.

Identity resolution failure after platform migration

If customer ID format or email normalisation changes during a commerce platform replatform, the integration logic does not adapt and new customer records are not recognised as duplicates. Segments and unsubscribe rules apply to fragments of the customer base.

Unowned consent and suppression workflow

If responsibility for maintaining suppression lists is unclear between Campaign, commerce, CRM and compliance teams, suppression rules drift and manual intervention becomes normal. This breaks SLA and compliance drift goes undetected.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about Adobe Campaign integrations.

How does iWeb resolve customer identity across commerce, ERP and Campaign?

iWeb defines matching rules on email, phone and customer ID before the integration builds. Duplicate detection logic is encoded into the integration flow so a single customer record in commerce matches to the correct Campaign contact. If email normalisation or ID format changes, the rules adapt so re-platforming does not fragment the audience.

What happens when a customer unsubscribes from an email or SMS campaign?

The unsubscribe event is captured in Campaign, normalised and routed back to your commerce platform, CRM and consent management system. iWeb monitors the sync latency and alerts if unsubscribes are delayed or lost, so suppression stays in step and GDPR compliance is maintained.

How do behavioural events (browse, cart, purchase) trigger campaigns in Campaign?

Events from your commerce platform or OMS are streamed or batch-fed into Campaign via a normalised event schema. iWeb validates event completeness and timing, so purchase reminders, abandoned-cart campaigns and product-recommendation journeys trigger reliably without manual intervention.

Can Campaign segments update the commerce platform or recommendation engine in real-time?

That depends on your commerce platform's API and personalisation engine. iWeb can publish segments on schedule (hourly, daily) or near-real-time via streaming, depending on your SLA. Real-time segment sync is common for checkout personalisation and recommendation engines.

What if our commerce platform and ERP emit customer events with different schemas or ID formats?

iWeb normalises event schema and customer ID formats at the integration layer before events reach Campaign. Transformation rules handle field-name mismatches, timestamp normalisation and identity key deduplication, so Campaign receives clean, consistent data.

How does iWeb monitor consent and suppression list accuracy?

iWeb tracks suppression sync latency (time from unsubscribe to exclusion in Campaign), monitors segment deduplication success rates and alerts if suppression lists diverge between Campaign and commerce. Regular audits compare suppression lists against GDPR erasure requests and opt-out logs.

What happens if the integration fails and Campaign does not receive customer or event data?

Can we segment customers by live order status or account flags from the ERP?

Yes. iWeb imports customer account status, credit limits, order history and lifecycle flags from the ERP into Campaign. Segment rules can then target high-value, at-risk or dormant customers based on ERP data without requiring a separate data warehouse.

How does iWeb handle GDPR erasure and right-to-be-forgotten requests?

GDPR erasure requests flow from your compliance or consent management system through the integration into Campaign, ecommerce and ERP. iWeb ensures requests propagate across all customer databases and are not reversed by a subsequent sync. Audit trails document erasure dates and systems affected.

What SLAs does iWeb define for unsubscribe propagation, event latency and segment refresh?

iWeb agrees SLAs with stakeholders before build: typical targets are sub-5-minute unsubscribe sync, event ingestion within 5-15 minutes, and segment refresh hourly or daily depending on use case. Latency is monitored in production and alerts trigger if SLAs are breached.

How do we ensure campaign execution does not conflict with transactional sends from the commerce platform?

iWeb defines ownership boundaries so Campaign owns promotional and engagement journeys while the commerce platform owns order confirmations, password resets and shipping notifications. Suppression and preference logic prevents overlap, and monitoring detects if a customer receives duplicate messages.

Can Campaign segments be used to drive dynamic pricing or inventory allocation in ecommerce?

Campaign segments export to the commerce platform or BI system, but pricing and inventory allocation stay owned by the commerce platform and ERP. Dynamic rules on the storefront can reference Campaign segment membership (VIP, loyalty tier, geography) to adjust display or offers without Campaign owning the transactional logic.

What tools does iWeb use to monitor Campaign integration health and failure rates?

iWeb implements observability via event counting, latency tracking, error logging and dashboards. Alerts are routed to your ops and marketing teams if event ingestion stalls, unsubscribe sync delays or segment membership diverges. Weekly health reports document integration performance and trend any emerging issues.

How does iWeb prepare for a commerce platform replatform without losing Campaign segment or consent history?

Before replatform, iWeb exports Campaign contact records, segment membership and consent flags to a safe archive. After cutover to the new platform, identity resolution rules are validated and segment sync restarted. Customer history and suppression flags are preserved so the new platform inherits the correct audience and compliance state.

Next step

Have an Adobe Campaign integration brief?

Send the brief, or tell us what is breaking. You will get a written response from a senior expert: the integration boundary, the realistic shape, the risks worth naming, and what it takes to support after launch.
Talk to an expertOr browse all integrations →