Adovo

AEM-native product

ContentSync: Interactive Content Inside AEM

Authors could create and publish interactive ebooks in AEM while reusing managed assets and connected measurement.

The challenge

Interactive content creation and measurement sat outside the AEM workflow.

Business outcome

The product let marketers create, publish and measure interactive content inside AEM.

Engagement context
Anonymized enterprise product engagement
Operating flow
Create → personalize → publish → measure → convert

01 / The problem

Marketers had to leave AEM to create and measure interactive content

Authoring, assets, publishing, personalization and lead capture sat in separate workflows. Each handoff made it harder to keep the experience, brand and measurement connected.

01Authoring toolCreate
02Asset libraryStore
03Hosting / publishRelease
04Adobe TargetPersonalize
05Adobe AnalyticsMeasure
06Oracle EloquaConvert

Fragmented tools · repeated handoffs · no connected authoring workflow

02 / Solution

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 / Business outcome

Content teams could publish interactive ebooks from within AEM

Authors could reuse managed assets and release responsive experiences in their existing AEM workflow. Engagement and lead signals connected to Adobe Analytics and marketing systems for follow-up and reporting.

01Author
02Personalize
03Publish
04Measure
05Convert

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

04 / 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

05 / 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

06 / 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

07 / 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

08 / 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

The work presented in this case study was delivered by members of the Adovo team through Adovo and/or during previous enterprise engagements.

Continue exploring

Adobe Experience Cloud

AEMAssets

AEM Assets metadata form import fails when permission trees grow

Diagnose a metadata form import error caused by an oversized Sling JSON response without making a broad author configuration change first.

Read more

Adobe Experience Cloud

AEMPublishing

AEM Cloud page publish blocked by a default design reference

Investigate an immutable /libs design reference in AEM page publication without normalizing manual unchecking.

Read more

Adobe Experience Cloud

AEMOperations

AEM on Windows needs a network share: test the service identity first

Plan a controlled AEM 6.5 Windows Service identity change from Local System to a gMSA when an external share becomes necessary.

Read more
Explore Adobe services →