Uploading your advertising spend data allows you to measure campaign ROI by marrying your advertising cost and the
customer lifetime value (CLV) of users acquired from your campaigns.
The first step in analyzing ad spend data is getting the data. Since most advertising platforms allow you to export reports, Adobe recommends you export the raw data from your ad platform and directly upload it to Commerce Intelligence without any manipulation. You can perform operations on the data in your Data Warehouse, so there is no need to double your efforts.
After you have exported the ad spend data, use the
File Upload feature to bring the data into your Data Warehouse. You can upload new data to the same Commerce Intelligence table over time.
In addition to your online campaigns, you may also have advertisements offline, such as on the radio or a billboard. To account for these cases, you can manually upload a spreadsheet with the cost data to Commerce Intelligence.
The table structure explored below is recommended when creating a
.csv file to record ad spend data. A template file is also attached at the bottom of this topic to serve as example. Recommended columns are:
ID - This is a unique identifier for each data row which is used by the database as primary key. This must be different for every row.
Date - This is the date that the campaign ran, in yyyy-mm-dd format.
Amount - This is the amount that you spent on the campaign.
campaign - This is the campaign name. If you are using Google Analytics to track your other ad spend data, it should match the utm_campaign name.
source - This is the source name. If you are using Google Analytics, this should match the
other (Optional) - You may also incorporate additional columns that help you segment campaigns and cost. It can also be a way to summarize several different UTM Campaign names into a single, coherent campaign for tracking purposes. Rather than set this up manually, it might be good to use a V-Lookup to a second sheet to match each Campaign Name to the Other Name and report it here dynamically.