Picture this: you are in the
Report Builder, building a
Revenue by State report. You are in the zone. Everything is going well until you go to add a
billing state grouping to your report and you see this:
Unfortunately, a lack of standardization can sometimes lead to messy data and headaches when building reports. In this example, there may not have been a dropdown menu or standardized way for your customers to input their billing state information. This lead to various values -
Pennsylvania - all for the same state, which leads to some strange results in the
It is possible that there is a tech resource that can help you clean up the data or insert the columns you need directly into your database. If not, there is another solution - the mapping table. A mapping table allows you to quickly and easily cleanse and standardize any messy data by mapping data to a single output.
You cannot create a mapping table for consolidated tables without help from the Adobe Support team.
Data formatting refresher:
(YYYY-MM-DD HH:MM:SS)for dates.
Before you dive in, Adobe recommends that you export the raw table data. Looking at the raw data first means you can explore all possible combinations for the data you need to clean up, thus ensuring that the mapping table covers everything.
To make a mapping table, you need to create a two-column spreadsheet that follows the formatting rules for file uploads.
In the first column, enter the values stored in your database with only one value in each row. For example,
PA cannot be on the same line - each input needs to have its own row. See below for an example.
In the second column, enter what these values should be. Continuing with the billing state example, if you want
pennsylvania to simply be
PA, you would enter
PA in this column for each input value.
After you have finished creating the mapping table, you’ll need to upload the file into MBI and create a joined column that relocates the new field into the desired table. You can do this after the file is synced to your Data Warehouse.
This example moves the column that you created on the
mapping_state table (
state_input) to the
customer_address table using a joined column. This allows us to group by the clean
state_input column in your reports instead of the
To create the
joined column, navigate to the table to which the field will be relocated in the Data Warehouse Manager. In this example, this would be the
Click Create a Column.
Joined Column from the
Give the column a name that differentiates it from the
state column in your database. Name the column
billing state (mapped) so you can tell which column to use when segmenting in the report builder.
The path you need to connect the tables does not exist, so you need to create a one. Click Create new path in the
Select a table and column dropdown.
If you are not sure what the table relationship is or how to properly define the primary and foreign keys, check out the tutorial for some help.
Many side, select the table you are relocating the field to (again, for us it is
customer_address) and the
Foreign Key column, or
state column, in the example.
One side, select the
mapping table and the
Primary key column. In this case, you would select the
state_input column from the
Here is a look at what the path looks like:
When finished, Click Save to create the path.
The path may not populate immediately after saving - if this happens, click the
Path box and select the path you created.
Click Save to create the column.
That is it!
After an update cycle completes, you will be able to use your new joined column to properly segment your data instead of the messy column from your database. Look at your grouping options now - no more stress mess:
Mapping tables are handy for any time that you want to clean up some potentially messy data in your Data Warehouse. However, mapping tables can also be used for some other cool use cases, like replicating your Google Analytics channels in MBI.