Set up a project
...
Structure of Dynamic resources
experience.config
5 min
the main configuration for any purple experience is done in a file called experience config json it is located in /storefront/assets within the dynamic content any data you put here is available to your app via the docid\ hh7yttoxelethdlpm 7dl object as it is part of dynamic resources, this configuration is generally also available in offline cases (note that a version of this file is bundled with the app thus, when downloading and app and accessing it in offline mode, upon first start, it might be outdated ) the configuration you may place here is generally ubiquitous, and available on any pxp page so it may also be used to configure custom implementations that are necessary in a project configurations provided by the purple system are defined inside the purple object in the file example config file this code snippet will need to be modified according to the needs of the project { "language" "en", "title" "a title", "purple" { "leandom" true, "analytics" { "ga4" { "configuration" { "measurementid" "provided by google analytics 4" }, "consent" { "vendorid" "customid matching the used cmp", "iabvendorid" "iab id" } } }, "consentmanagement" { "cmpprovider" "consentmanager", "cmps" { "consentmanager" { "configuration" { "codeid" "provided by consent manager", "cmphost" "provided by consent manager", "cmpcdn" "provided by consent manager", "cmpblockignoredomains" \[] } } } } } } available settings version of dom any new project in pxp will use the revisited version of dom, called leandom it is already set up in our boilerplate and also the templates we regularly use preconnects see docid 1e8fgqizp9sc59mdxdij2 website locale for seo and accessibility reasons, we recommend that you set the locale for your website explicitly you can simply do this by adding, i e "language" "de" to the experience config json this will then be added to your website's html as \<html lang="de"> please refer to https //www w3 org/international/articles/language tags/ for further information on locales in general tracking systems most third party tracking systems must be set up in both experience config and purple manager for details, see docid\ cwokg2ejseayqbyzzk8bt and refer to the detailed steps for the individual trackers note that you must set up the tracking config as well, to map events from the purple system to the tracker this setup allows the changing of trackers with limited adjustments in your tracking logics cmp most consent management platforms must be set up in both experience config and purple manager for details, see docid\ iubzrguxkik85qjapwxie