Add the Page headline here

Pleaes add little bit summery on the page here
We have used here the content wrapper component more like as a glue to hold all other components, texts and images. This helps the page be consistent and same in all devices regardless the screen size. So, it is highly recommended to use the content wrapper component to contain other components.
For any Headline it is also recommended to use this big blue bar, if the content fits

Different levels of tracking granularity

Please use the justified allignment style in case you are planning to insert longer texts in the copy text component. Check below for reference. 
Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.
For Work Package or similar contents, you can use the Vertical Tabs component like below: 
Work Package 01

ARTs Journey Readiness with Tracking 
Ownership: DAS team & relevant ACM/BMP Tribe
Scope: The scope of this work package is to work closely in collaboration mode between ACM/BMP Tribe and DAS team, in order to establish below items.
Result: Journey ready for OE rollout with included tracking for Level1 and Level2.                                                                                                 
Work items
  • DAS team to understand the journey functionality and features from the tribe
  • ART to enable DAS team with access to test environment and data
  • ART to confirm the release readiness of the journey in discussion and share knowledge for that specific journey. Also, announce or share information on update/upgrade for upcoming releases
  • DAS team to create a tracking implementation plan for Level1 and Level2 tracking on this journey
  • ART to follow the tracking documentation and include/integrate tracking into their journey
  • ART to do the QA and update the tracking documents with comments for each tracking ID which have been successfully accomplished
Updates to journey release version                                                                                                                                                                                         
  • For minor updates: ART should be able to follow the tracking ID convention in the original tracking document and add these changes, with comments for journey version and successful QA
  • For major updates or re-structuring: ART should align with DAS team to discuss the changes in the monthly "TechTalk" Community Call

OE Onboardings & Readiness Check  
Ownership: OE
Scope: The scope of this work package is to work closely in collaboration mode between OE and DAS team, in order to establish below items.
Result: Planning for journey rollout can be developed.                                                                                                                                                                                  
Work items
OE to journey onboarding roadmap in terms of                                                                                                                                                                           
  • Planned rollout for which all journeys and versions
  • Key stakeholder/support/rollout team for alignment
  • Key dates
  • Access to test/dev environment along with testing data
  • Rollout method - in AEM environment or custom OE specific setup
  • License to use Adobe Analytics and Adobe Launch from oneMarket
  •      Adobe Analytics Report Suite for data collectio
  •      Adobe Launch Web Property for tracking rules
In case of non-standard AEM rollout from OE                                                                                                                                                                            
  • There might be additional cost involved for additional license
  • There might be need for additional developer effort from OE in making journey go-live ready, for example managing user consent

DAS Tracking Rules Migration
Ownership: DAS team
Scope: The scope of this work package is for DAS team to deliver the tracking rules to OE Adobe Launch environment.
Result: Planning for journey rollout can be developed.                                                                                                                                                              
Work items
DAS team will deliver tracking rules and configurations for the said journey to the OEs Adobe Launch Web Property, in following way:                                                                                                              
  • Level1 tracking is migrated over to the OE Launch Property
    DAS team tests the tracking in development environment using the credentials shared by OE for readiness check and confirms it to the OE
  • Level2 tracking is migrated over to the OE Launch Property
    DAS team tests the tracking in development environment using the credentials shared by OE for readiness check and confirms to the OE

DAS team updates the OE on the status of this migration, possible issues or other dependencies

DAS team will not take care of local dependencies, custom consent management or custom hosting of journey, or things falling in similar areas

OE Quality Check + Go-live
Ownership: OE
Scope: The scope of this work package is to OE to verify, QA and go-live.
Result: Tracking implementation is live in customer-facing environment.                                                                                                                                                            
Work items
Optional but recommended: OE quality check                                                                                                                                                                                              
  • OEs can choose to check their journey for tracking and go-live readiness
Go-live                                                                                                                                                                                                                                                   
  • OEs can publish Adobe Launch Rules to production/customer-facing environment, when it is flagged to be ready by DAS or by OEs QA team
  • In cases where OEs are not familiar with Adobe Launch, DAS team can support here with publishing the rules to production

DAS Analytics Dashboard (Basic)
Ownership: DAS team 
Scope: The scope of this work package is for DAS team to provision Adobe Analytics dashboard.
Result: Analytics dashboard delivered.                                                                                                                                                          
Work items
  • Post rollout to the production/customer-facing environment DAS team will support the OE with an Adobe Analytics dashboard with basic KPIs for the journey tracking
  • DAS team will also help the OE in understanding the dashboard and enable them with sharing/alerting/downloading capabilities
  • If there is a global data sharing contract between OE and AZ Tech, we can then enable the data flow to dashboards reporting global journey performance

OE Customization + Additional Requirements
Ownership: DAS team & OE  
Scope: The scope of this work package is to work closely in collaboration mode between OE and DAS team in a demand based project mode on time and material basis.
Result: Demand story and project plan for OE customization and additional requirements.                                                                                                                                                           
Work items
In cases where there is deviation from standard journey rollout or there are customizations that need additional work or additional requirements are highlighted/discovered:                                                                                                                                                                                                                 
Custom CMS or hosting environment for journey                                                                                               
  • Possible additional license cost for OE
  • Possible implication on data layer and OE developers will have to support here
  • Possible implication on delivery timelines depending on level of deviation and customization
Custom analytics solution                                                                                                                                                                                                                                  
  • OE needs to figure out on their own about using Trackify events for tracking data collection in their analytics solution.
Custom Consent Management Solution                                                                                                                                                                                                            
  • OE needs to develop their own consent sharing configuration
Custom advertising or marketing needs                                                                                                                                                                                                               
  • OE needs to identify their requirements and have them included in the project plan for such a demand