Best practices (CJA)
Best Practices for CJA Projects
When building custom demos, itβs often necessary to tailor your Customer Journey Analytics (CJA) project to align with a customerβs brand β adjusting labels, dimensions, and metrics accordingly.
Within the Demo-System-Next (DSN)β ecosystem, there are a few recommended approaches to achieve this efficiently while minimizing any accidental impact on shared demo assets.
- Next, use the DSN datasets to configure "Connection" in CJA. You may choose to use IdentityMap -> Email as stitching attribute across DSN datasets.
- Benefit of this type setup supports Journey Optimizer (AJO), Decisioning (ODE), and Segment (ProfileSnapshot) datasets β allowing you to demonstrate a complete RTCDP-to-CJA workflow.
- β In the connection setup UI, ensure βIngest new recordsβ is enabled for each dataset.
- Use the B2C Data Generatorβ to ingest a few thousand experience events into the instance. The tool supports recursive generation, making it easy to manage volume.
- Benefits include:
- All interaction data will be continuously captured and reflected in your CJA project.
- Audience qualification, journeys, and personalization flows will also contribute to reporting automatically.
- This approach uses Profile-enabled datasets with potentially millions of identities and events β monitor usage to avoid unexpected costs due to identity stitching.
- Since, the tool does not provide option for configuring brands; so, in CJA Data-View, use "Derived field" feature to map existing labels to match with brand.
- Create new datasets based on DSN schemas β each schema represents a distinct data source.
- β οΈ DO NOT enable these datasets for Profile.
- Configure a Connection in CJA using the new datasets. Recommended stitching attributes: _<TENANT>.identification.core.crmId or IdentityMap -> CRM
- β In the connection setup UI, ensure βIngest new recordsβ is enabled for each dataset.
- Use the Experience Event Generatorβ to programmatically create large data volumes. π Note: Basic JavaScript knowledge is required.
- Manually upload the generated output in batch mode to ingest the data.
- Benefits include:
- Full control over eventTypes, branding and data volume.
Public Project Data Views & Derived Attributes
From the data view, any derived fields starting with "ACA"; otherwise, we cannot complete the setup of the content analytics demo. Also, do not modify the original Omni-Channel Multi-Industry data view. Make a copy for yourself and edit that.
Following this method helps preserve the integrity of Demo-System-Next Public Projects for everyone.
This method uses Adobe Demo System Shared org assets and is highly recommended for standard demos: β’ DSN Public Projects are actively maintained with the latest features. β’ Following best practices ensures your customizations donβt disrupt other teams.
PANEL / HEADER RE-LABEL
- In some customer engagements, where we do not demonstrate technical aspect of analysis using CJA and we give the clients an experience of benefits of CJA and show them the experience or environments; we recommend this approach.
- Any marketer can go ahead and make a copy (duplicate) from the available list of DSN public-projects.
- In the copied version of the CJA project, users can edit and re-lable panels or visualization heading (NOT VALUES). User can also re-arrange visualizations as per the presentation plan.
DERIVING BRANDED PRESENTATION
- In this method, you can change the values (dimensions and metrics) of the DSN public projects.
- Make a copy (duplicate) Data-View; then, copy of CJA project. Finally, refer the copied Data-View in all of the visualizations in CJA project.
- Values of dimensions and metrics can be controlled by leveraging "Derived field" and custom/new metrics.
- Please note; that, "Derived fields" are defined at Data-View level and managed at "Connection" level i.e. IF YOU CREATE / MODIFY DERIVED FIELD(S), THE CHANGES REFLECT ACROSS ALL THE DATA-VIEWS, WHICH ARE PART OF CONNECTION.
- DO NOT MODIFY/UPDATE/DELETE EXISTING DERIVED FIELD. ALWAYS CREATE NEW DERIVED ATTRIBUTES (You can refer to existing derived fields in the creation of new derived attributes)
- PREPEND SHORT ABBREVIATION TO NEWLY CREATED DERIVED FIELD LABEL. For example ABC_Page name
- Now, refer to the newly created derived fields in the copied data view and subsequently in the CJA project for your demo.
π£ Need Help or Have Suggestions?
For questions, feedback, or ideas, reach out to the Demo-System-Next development team on Slack: #demo-system-nextβ.
ο»Ώ
ο»Ώ
ο»Ώ