--- title: 7. Data View Administration slug: dominos-cja/7-data-view-administration docTags: createdAt: 2025-08-26T03:06:54.996Z --- Data views control how the data ingested into a CJA Connection is to be interpreted. They specify all of the dimensions and metrics which will be available for reporting within Analysis Workspace and which columns those dimensions and metrics obtain their data from. Data views are defined in preparation for reporting in Analysis Workspace. Each connection can have multiple Data views. In this exercise you'll learn: - How to configure dimensions and metrics - How to create derived fields :::hint{type="info"} Configuring data views requires Administration access to Customer Journey Analytics. ::: # 7.1 Create a data view Rather than starting from scratch we're going to duplicate an existing data view. - Browse to the **Data management -> Data views** tab. Find the **Retail Data View **and click on the 3 dots to view the options. Click to **copy **the dataview. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/WXFpe9ZlO0h9CGW3frr8U_image.png) - Click to open your Data View. Update the name of the data view so you can easily recognize it as yours - eg. add your name. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/M3PP0vzSfZ6IMqLinngIT_image.png) - Click on **Save and Continue **to move to the Components tab. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/IY0v2BkxmWne0cYT6qsq6_image.png) # 7.2 Add a dimension CJA supports three types of data, profile data (attributes about your customer such as loyalty tier, NPS scores, address and age), event data (coming from multiple channels) and lookup data. For this exercise, let's add a lookup attribute as a dimension into our data view. Click into the **Lookup datasets **in the left hand panel. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/zi5cOxZDCZqUeRVxGn24I_image.png) Campaign tracking codes are used for tracking which marketing campaigns a customer lands from, this code is mapped to user friendly campaign names stored in a lookup table. - Click into the **Lookup datasets **in the schema fields panel ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/Rd67wxpoOYilnczCrvfS8_image.png) - Search for **campaign **you'll notice we have different lookup values depending on the industry, drag the **Retail Campaign **attribute into the Dimensions. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/GRwNYSe5YC4UmF8xZX8E4_image.png) - Now, let's update the dimension properties on the right hand side and rename the dimension to **Campaign Name. ** ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/Jf34QbTbr0Ym65vQw2oy2_image.png) - Click **Save and continue** ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/jbbRuhstNBOMj8SVd8cNz_image.png) - On the settings tab we can configure the session timeout and add global filtering if desired. We will leave these as is. Click **Save and finish.** ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/CeoGtlnhtdlvFzmp6MemQ_image.png) :::hint{type="success"} Congratulations, you've created your first Data View in Customer Journey Analytics. Let's create a quick project to test it out. ::: # 7.3 Use your Data View - Click to the **Workspace** in the top navigation and **create a new project**. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/B_o08yULzajJU592sp8lD_image.png) - Ensure that you've selected your Data View in the Data View selector. *Hint: you might need to search for it or do a hard refresh to clear the cache. * ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/mR5uPPexxsfBx659Nz4R__image.png) - Drag the **events, sessions** and **people** metric into your freeform. Change the dimension to **Week **to verify that you have data displaying for your new dataview. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/WXdK2LDJf7CNa-EkmcBml_image.png) - Swap the Week dimension for **Campaign Name** and add the **Calls **metric. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/obl-Mfj8DjyH3FyIZDOiZ_image.png) You'll notice that there are no campaign names aligned to calls! That's to be expected because the campaign name is collected when a customer lands on the website, the calls metric is coming from a completely different dataset coming from the call center! Let's see now how dimension persistence and/or attribution can be used to connect these disconnected events! # 7.3 Set dimension persistence Persistence in analytics tools often needs to be configured up front and is applied at ingestion time. In Customer Journey Analytics we set persistence in the Data View and this is applied at run time, allowing changes to be applied retroactively. - Click to **edit** your Data View, you can do this directly from your project by clicking the edit icon in the Data View selector. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/OwvYUyCQDE75ULKvvLg-S_image.png) - Switch to the **Components **tab and search for the **Campaign Name** in your dimensions. Scroll to the bottom of the properties for this component and enable **Persistence. **Set the persistence to **Original** for the **session**. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/4muslbkZVSFRXgfT8mMU3_image.png) - Click **Save**. Then click **Close **to return to your dashboard. You can see there are now campaigns associated with your calls! This is because the call event was received within the 30 minute session window after the customer landed on the website from the marketing campaign! This is possible because we are connecting the events across datasets in the connection using the person id. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/Ox8oLbNCEyieXVz1wSedE_image.png) # 7.4 Create a metric from a dimension Another advantage to this on-the-fly processing allows us to create new metrics from dimensions. What if we forgot to add a specific event field for the metric we want to report on? For example if we know that the call reason **"callreasonid:337426"** means it was a complaint we can use this to create a new "complaints" metric. - Drag the **callReasonId** field into the metrics, update the component name to **Complaints. ** ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/MyDn5pLF0qY5q74fSBfp4_image.png) - Under the component settings scroll down to **INCLUDE EXCLUDE VALUES **and set the metric to include only values that equal **callreasonid:337426. **We now have a new metric to report complaints separately from other call reasons. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/zaG6yVZ3RXfjpgdxNW6md_image.png) - Save the Data View and return to your dashboard, click to **Refresh Components**. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/3CHNLUPVI5FbzYL7t-MEm_image.png) - Drag the new **Complaints **metric into your freeform and change the dimension to** Call Reason** ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/oCqx8RX3MxOxaRPd3EbO5_image.png) # 7.5 Derived Fields One of the most powerful features of Customer Journey Analytics is Derived fields. These allow you to **instantly and retroactively apply complex data changes on-the-fly**, without the need to rewrite and re-ingest data. Imagine the website team made an error when coding the data layer for the mobile website, and now all of the page names coming from this version of the site are pre-fixed with "**mobile web:**". On your dashboard, change the dimension to **Raw Page Name, **apply a filter on the list to include only page names including the word **category. **You can see that we're reporting mobile web pages separately to desktop which is not the desired state. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/b3lRPxk73t4TiaF6gdooX_image.png) You want to report on category pages across all versions of the website. We can quickly fix this using derived fields. Click to edit your dataview and **create a derived field**. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/OWmRzU7UXtzpb0bXIIFn3_image.png) Adobe provide a number of derived field templates available to help you get started but for this exercise we'll skip this step. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/plAnJ7amJmm1EdBWcwGPc_image.png) You can see there are a number of **functions **available. For this use case, we're going to use the **regex\_replace **function to create a new pagename field that removes "mobile web: " from the start of any value. Drag the **regex\_replace **function into the canvas. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/i00q-CcGb9rgzIPUXNYCo_image.png) In the value field, start typing to find the page name field: **web.webPageDetails. **Select the **Name **field when it appears. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/qnwejqUFFlmesoUuRFxyW_image.png) Set the **regex** pattern to `(mobile web\:\s)(.*)` and the **output format** to `$2`. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/86EJk739cEXOyx0huYw0P_image.png) Now we only want to apply the regex on the problem values, so we need to add a second function to our derived field. Drag the **Case When **function into the rule builder under **Rule 1**. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/HtHW9Ll9QUVos2YUelAwh_image.png) Now update Rule 2, to also look at the **web.webPageDetails.Name **value, set the Criterion to **starts with **and the Value to **mobile web:** ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/tjrkVO8YXLrwC4BNWgSkm_image.png) In this case we want to return the output from our regex, so set the output value to **Rule 1. **Otherwise we want to return the original value for **web.webpagedetails.name**. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/XQD21Mjj74zDs73HR8OQV_image.png) Give your new field a name that's unique to you, eg. ` - pagename derived`. *(derived fields are applied to the connection itself not specifically the data view, so we can't all create the same derived field on this connection). * ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/4jHrMHSO3i9bmV-JOqqyi_image.png) Click **Save. **Then drag your newly created field into your dimensions list. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/S_qEYyeZ6BkzObdHg_rq-_image.png) Click **Save. **Click** Close** to return to your project and **Refresh Components. ** Replace the page name dimension with your new derived field, values are now reported together. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/EXY-MqPTXCRfmyh9eAvAf_image.png) :::hint{type="success"} Congratulations you've completed the exercise on Data View Administration! :::