Lab Resources
7 min
Feedback Survey
https://forms.office.com/r/pYdGARa8cF?origin=lprLink

HOL Presentation
HOL Recording
Completed Workspace
Password for CJA project export PDF:cja-mc-hol1
Resources
Q&A
- What is the architecture of AEP and what database structures does it use (nosql, relational, etc.)?
- It's not either but a distributed platform storing data in an append-only data lake, managing customer entities as a profile store, and offering SQL querying through a query service. You may want to talk through it to ensure you get the clarity you need, so I suggest asking your CSM or other Adobe account team member about having a quick conversation with someone in the product team.
- Blog post by Adobe consultant
- What happens with CJA, stitching, identities, etc. with shared devices or householding (one device ID, multiple authenticated IDs)?
- In field-based stitching, each record stitches to the authenticated ID most recently seen.
- In graph-based stitching, each record stitches to the graph results at the time of stitching processing (initial and replay).
- Because graph-based depends on the identity graph, your identities and identity linking rules will impact the id graph results. CJA stitching is a consumer of however you build your identity graph.
- How can we address reliance on AA data feeds in moving to CJA? What are the related options?
- There is no 1:1 corresponding feature in CJA for AA data feeds. AA data is heavily processed in advance and uses a static schema for all instances, while CJA / AEP architecture is flexible and built differently.
- Great blog post from Adobe on all types of data egress options related to CJA/AEP. The use case of getting data out of AEP/CJA can be addressed through those methods.
- You can have AA and CJA active simultaneously, getting AA data feeds delivered while adopting and building CJA, but consider any licensing impacts with your account team.
- How does Content Analytics handle personalized and dynamic content?
- Content Analytics can capture and report on engagement for content that’s rendered on-page (even when the page is dynamic), because on-page content interactions are logged as distinct content-interaction events and then enriched for reporting in CJA.
- If the URL stays the same while content changes, reporting can roll up under the same Experience ID.
- For detailed experience payload capture (texts/CTAs/styles), the tracking-library spec explicitly excludes personalized content from some fields (notably texts and CTAs), so Content Analytics is not intended to surface user-specific personalized copy as reportable dimensions.