Relewise and DotDigital
Integration Agency & Consultants
Revenue leakage in DotDigital campaigns is often the result of undifferentiated messaging. When Relewise identifies a high-intent customer segment based on real-time behaviour but cannot trigger a corresponding event in DotDigital, the commercial window closes. At volume, generic campaigns reach the wrong people while high-value signals are ignored. We connect Relewise and DotDigital so that customer insights drive automated execution, turning behavioural data into campaign outcomes without manual list imports.
Auditing tech ecosystems and personalisation readiness
Cogent will swiftly connect your Relewise and DotDigital integrations. Our consulting services are invaluable, offering system audits that empower both our consultants and your team to take decisive action. These audits ensure your tech ecosystems, including Relewise and DotDigital, operate smoothly and efficiently. By focusing on personalisation and ESP, we help you deliver an exceptional customer experience. Our expertise in system audits identifies inefficiencies, allowing for improvements that enhance personalisation and ESP capabilities, ultimately benefiting your business and customer satisfaction.
Solution Design
Our design for Relewise and DotDigital treats Relewise as the authoritative source for customer behaviour and DotDigital as the delivery engine. We prioritise mapping the Relewise User Key to the DotDigital Contact ID first to close the identification gap. A core design decision involves using defined triggers to enter DotDigital programs only when specific interest thresholds are crossed, rather than syncing every score change as a flat attribute. This approach is designed to avoid API rate limits and prevent attribute bloat. The trade-off is more detailed initial program setup to gain significantly lower operational latency during peak trading. This ensures the marketing team automates based on fresh intent data while the integration layer handles the logic to protect system performance.
Mapping intent data to automation triggers
This integration establishes Relewise as the source for customer segments and personalisation insights, pushing these datasets to DotDigital to trigger tailored communications. Relewise identifies intent based on customer interactions and updates segment tags on the DotDigital contact record. The data flow is typically sequenced so that segment membership updates occur before campaign cycles, preventing triggers based on outdated behaviour. Monitoring at the integration layer identifies sync latencies or mapping errors between Relewise and DotDigital data fields to ensure messaging remain accurate.
Securing the integration with enterprise middleware
Cogent2 leverages IPaaS to integrate Relewise and DotDigital, ensuring secure personalisation and ESP services. IPaaS platforms offer ISO 27001 and SOC 2 compliance and above, providing robust security. This enables efficient data handling and personalisation for Relewise and DotDigital, enhancing ESP capabilities. The benefits include streamlined operations, improved data security, and compliance with high security standards, ensuring reliable and secure integration solutions.
Monitoring sync health and identity mapping
Standard dashboards show campaign sends but often mask the sync illusion where data appears current but is actually lagging. Effective visibility requires monitoring the link between the Relewise UserId and the DotDigital Contact ID. If this mapping drifts, behavioural triggers stop firing even while dashboards report an 'active' integration. Monitoring for these mapping failures and silent filtration errors in interest profiles ensures that marketing teams are not running campaigns against stale segments or mismatched attributes that undermine personalisation ROI.
Handover protocols for daily segment management
The ecommerce and marketing teams must own the logic that connects customer behaviour to campaign triggers. Handover focuses on the operational model where Relewise manages segment membership and DotDigital executes the send. Your team will learn how to verify that interest profiles in Relewise match the address book names. We define who owns exception alerts, such as mapping errors or stalled syncs. Documentation is operational rather than technical, providing a handbook for daily checks of data alignment and a protocol for resolving identity reconciliation drifts should they occur.
Managing data discrepancies post go-live
Post-launch, Cogent provides ongoing monitoring to help ensure personalisation triggers remain accurate as product catalogues and customer segments evolve. We monitor the integration layer, managing updates and identifying data discrepancies that could impact campaign performance. This allows marketing teams to focus on their core work while the underlying data flows are managed.
Common failures
Fragmented Customer Identity Relewise tracks behaviour against its own user keys, while DotDigital typically relies on an email address or contact ID. If the Relewise UserId is not mapped to a high-level DotDigital data field, the system cannot look up real-time product recommendations during the email trigger phase. This makes browse behaviour invisible to abandoned cart triggers, leaving customers with generic follow-ups instead of personalised recovery emails.
Interest Profile Mismatch When syncing Relewise interest scores to DotDigital, the Interest Profile attribute names must exactly match the Address Book names. Any discrepancy causes dynamic segment filtering to fail silently. Marketing teams believe they are targeting high-affinity segments, but the integration is dropping data because of a naming mismatch in the background.
Attribute Bloat and API Overload Syncing the entire Relewise 'In-Market' interest score as a flat DotDigital contact attribute creates unnecessary API overhead. At scale, this leads to rate limiting and attribute bloat. A more resilient approach uses a webhook to trigger program entry only when a specific score threshold is crossed, ensuring DotDigital only receives the data it needs to execute a campaign.
Frequently asked questions
Our campaigns get low engagement. How does connecting Relewise and DotDigital improve this?
When Relewise identifies specific customer segments like high-affinity shoppers, this integration pushes those insights to DotDigital. This allows you to trigger campaigns based on real behaviours like search history or category views rather than generic schedules. By aligning the message with current customer intent, you reduce undifferentiated marketing and improve conversion.
How do you ensure customer tracking in Relewise matches the right contact in DotDigital?
We synchronise the Relewise User Key to a specific DotDigital data field. A common failure in many setups is a mismatch between the Relewise UUID and the DotDigital Contact ID, which prevents browse behaviour from triggering emails. We map these identifiers to ensure anonymous activity is correctly linked once a user is identified via sign-up or checkout.
Can this integration cause API issues during peak periods?
Yes, if not designed correctly. Syncing every interest score update as a flat attribute can hit DotDigital's API rate limits. We typically use threshold-based triggers or webhooks to ensure only essential segment changes move between systems. This prevents attribute bloat and ensures the integration stays stable during high-volume events.
Why do product recommendations sometimes show out-of-stock items?
This happens when there is a reconciliation gap between your commerce platform, Relewise, and the DotDigital trigger. We ensure Relewise is fed directly from the primary product source of truth. If a SKU is discontinued, the integration signals the removal from the Relewise index so that DotDigital never includes dead links in your automated campaigns.