AEM-native product

ContentSync: AEM-Native Interactive Content Platform

An AEM-native product that unified interactive content authoring, asset reuse, personalisation, publishing and measurement in one workflow.

Client: Enautics Group, Inc.
Role: Solution Architect & Lead Developer
Operating flow: Create → personalize → publish → measure → convert

01 / The problem

The content workflow was fragmented across too many tools

Authoring, asset storage, hosting, personalisation, measurement and conversion each created another handoff. Content, brand, measurement and conversion logic drifted apart.

01Authoring toolCreate

02Asset libraryStore

03Hosting / publishRelease

04Adobe TargetPersonalize

05Adobe AnalyticsMeasure

06Oracle EloquaConvert

Fragmented tools · repeated handoffs · no connected authoring workflow

02 / The product experience

ContentSync brought the entire workflow into AEM

Authors could choose a reusable starting point, design, enrich and release from the same AEM workflow.

01CreateChoose an ebook, folder or reusable option

02DesignApply templates and brand controls

03EnrichUse native assets, forms and video

04PublishRelease from the same AEM workflow

Same-domain AEM delivery

03 / AEM-native architecture

The product runs with the platform, not beside it

The product was installed, authored and published as part of AEM rather than operated as separately hosted software.

01AEM PublishSame-domain experience and delivery

02ContentSync UITemplates · brand kit · forms

03OSGi bundle + product logicAEM services

04JCR / DAMContent + native asset reuse

05Enterprise integrationsAnalytics · Target · Eloqua · media

04 / Authoring experience

Marketers build responsive experiences without developer handoffs

Templates, brand controls, native AEM assets, responsive preview and publishing were available inside one marketer-facing product UI.

01Template

02Brand kit

03Responsive view

04AEM DAM assets

05Publish

The authoring surface stayed inside AEM

05 / Integrated experiences

Assets, forms, video and personalisation remain one workflow

Target and video shaped the experience, while Eloqua and Analytics received conversion and engagement signals from the same AEM-centered runtime.

01ContentSync experienceInteractive content · assets · forms · video

02Adobe TargetPersonalize

03VideoEnrich

04Oracle EloquaCapture

05Adobe AnalyticsMeasure

Personalized → published → measured

06 / Technical deployment

Two deployable artifacts support AEM 6.5 and AEM as a Cloud Service

A versioned release moved through Maven as one coordinated backend and UI package pair into the normal AEM deployment pipeline.

01Versioned releaseMaven repository

02.JAROSGi bundle · backend services · product logic

03.ZIPAEM UI / content · editor · templates · DAM content

04Deployment pipelineCoordinated platform release

05AEM 6.5 + AEM as a Cloud ServiceNative DAM and same-domain delivery

07 / Measure

Engagement and conversion become measurable

The reporting layer connected engagement, CTA clicks, form submissions, visitor trends, conversion funnel performance and individual content experiences.

01EngagementRate + engaged visitors

02CTA clicksInteraction volume

03Form submissionsConversion action

04Conversion funnelVisitors → engage → download → CTA → forms

05Video engagementViews + completed plays

06Top experiencesViews · engagement · click rate

08 / Outcome

One AEM-centered workflow from creation to measurement and conversion

Interactive content remained inside AEM while native assets, measurement, personalisation and conversion platforms stayed connected to the same publishing workflow.

01Author

02Personalize

03Publish

04Measure

05Convert

Consolidated authoring · native asset reuse · connected measurement · personalisation + conversion · one publishing workflow