Overview
Adobe Experience Cloud implementation, starting with the data underneath
Adobe Experience Cloud is Adobe's family of marketing and customer experience products. Several of them now run on Adobe Experience Platform, Adobe's customer data foundation: Real-Time Customer Data Platform (Real-Time CDP) for profiles and audiences, Adobe Journey Optimizer for triggered and scheduled messages across channels, and Customer Journey Analytics for analysis across web, app, CRM and offline data. Alongside them sit long-established products such as Adobe Analytics and Adobe Target, used for testing and personalisation.
This page is about implementing those products: getting data collected correctly, modelled once and used by every tool that needs it. It suits organisations that have bought Adobe licences but are getting little from them, teams moving from Adobe Analytics to Customer Journey Analytics or from the older AppMeasurement library to the Web SDK, and marketing and data teams adding Real-Time CDP or Journey Optimizer to an existing stack. Content management on AEM is covered on our AEM Sites page.
Most Adobe implementations that disappoint fail on data, not configuration: inconsistent page and event tracking, customer identities that don't match across systems, and consent that isn't passed through. Great Minds is a Sydney-based systems integrator, and we treat an Adobe implementation as a data and integration project first. We design the tracking plan and schema, implement collection, connect CRM and commerce data, and then configure the reports, tests and journeys your teams asked for.
Capabilities
What we implement across Adobe Experience Cloud
Each piece below can be delivered on its own, but they depend on each other. A clean tracking plan and identity design make every later product cheaper to add.
How we deliver
An Adobe implementation, from tracking plan to first results
We start with the data design because it is the hardest part to change later, then build in small releases so each team sees working reports or journeys early.
We review what you already collect, which Adobe products you hold licences for, and the questions each team needs answered. The result is a tracking plan, an identity design and a release order.
XDM schemas, identity namespaces, consent fields and data views, agreed with your marketing, analytics and privacy teams before any production data flows.
Web SDK and tags on site and app, CRM and commerce data brought into Experience Platform, and validation of every event against the plan before reports or audiences use it.
First reports, tests and journeys live, dashboards checked against source systems, and training and documentation so your team can build the next ones without us.
Australian considerations
What Australian teams should check
Hosting location. Adobe Experience Platform, which Real-Time CDP, Journey Optimizer and Customer Journey Analytics run on, has a Microsoft Azure hosting location in New South Wales (region code AUS5), listed in Adobe's Experience Platform hosting locations. Confirm with Adobe which location your organisation is provisioned in before data collection starts, and check where other connected tools store data.
Consent and the Privacy Act. Behavioural and profile data about identifiable people is personal information. We pass each visitor's consent choice through the Web SDK so Adobe products only collect and use what the person agreed to, and we keep identifiers such as email addresses out of analytics variables. If data leaves Australia, APP 8 on cross-border disclosure applies.
Automated decisions. Audience rules and journey logic that significantly affect individuals, such as eligibility for offers, may need disclosing in your privacy policy from 10 December 2026. Our guide to automated decisions and the Privacy Act explains the change. For APRA-regulated entities, check whether any Adobe product supports a critical operation, because that brings it into service provider management under CPS 230.
FAQ
Adobe implementation questions
Should we move from AppMeasurement to the Web SDK?
For most sites, yes, as part of a planned release. Adobe's newer products collect data through the Web SDK, and Adobe documents a migration path that keeps your existing Analytics variables, so reports continue while you move. If Customer Journey Analytics is on your roadmap, Adobe recommends a clean Web SDK implementation with your own schema instead.
What is the difference between Adobe Analytics and Customer Journey Analytics?
Adobe Analytics reports mainly on digital behaviour collected from your sites and apps. Customer Journey Analytics runs on Adobe Experience Platform and can combine that behaviour with CRM, call centre and offline data, keyed on the person rather than the device. Adobe publishes several upgrade paths, and we help you choose one based on how much history you need to keep.
Do we need Real-Time CDP if we already have a CRM?
Not always. A CRM holds customer records and sales activity. Real-Time CDP builds profiles from many sources, including anonymous web behaviour, and sends audiences to other tools quickly. If your use cases are mainly sales and service, a well-integrated CRM may be enough. Our customer data platform page explains how we decide.
Can Adobe Experience Platform keep data in Australia?
Adobe lists a hosting location in New South Wales, Australia, on Microsoft Azure. Confirm with Adobe which location your organisation will use before contracts are signed, rather than after data starts flowing. Check the hosting of any other system that receives the data too, such as an email or advertising platform.
How do Adobe products connect to Salesforce or Dynamics 365?
Through Adobe's source connectors into Experience Platform, product-specific connectors such as Marketo Engage's CRM sync, or an integration layer for anything custom. Our Adobe integration page covers the patterns and the trade-offs.
How long does an implementation take?
It depends on how many products, sites and data sources are in scope. A Web SDK migration for one site is a short project. A Real-Time CDP rollout with CRM and commerce data is a programme delivered in releases. We give you a scoped plan and price after the audit.
People
The people behind the work
Strategists, architects and platform specialists who have delivered 350+ projects since 2009, across APAC and Europe.
Case studies
Results that are real.
One asset library for APAC, EMEA and North AmericaModernising creative storage and operations for a global retailerEnabling global brand consistency through enterprise Digital Asset Management
An accessibility programme to bring a global online store in line with WCAGWCAG compliance for eCommerce giantAccessibility audit, remediation and testing to bring a global online retailer's store in line with WCAG.Insights
Latest thinking
What changed in October 2026: Atlassian, Salesforce, Microsoft, Google and AdobeOctober 2026 changes for Australian IT: Atlassian Cloud price rises, Salesforce SOAP login() deadlines, Copilot licensing, Gemini data residency, OAIC.
Atlassian Cloud pricing in AUD: licences, tiers and metered AIWhat Atlassian Cloud costs in AUD after the October 2026 price rise, plus GST, plan tiers and how Rovo credits and automation are billed from 3 December.
The connected enterprise: integrating Salesforce, Atlassian, Adobe and ERPHow to connect Salesforce, Atlassian, Adobe and your ERP: system-of-record map, architecture options, API limits, APP 8 and CPS 230, and where to start.