Dunnhumby - The Complete Journey
Retail focused consumer data
@kaggle.frtgnn_dunnhumby_the_complete_journey
Retail focused consumer data
@kaggle.frtgnn_dunnhumby_the_complete_journey
This dataset contains household level transactions over two years from a group of 2,500 households who are frequent shoppers at a retailer. It contains all of each household’s purchases, not just those from a limited number of categories. For certain households, demographic information as well as direct marketing contact history are included.
Due to the number of tables and the overall complexity of The Complete Journey, it is suggested that this database be used in more advanced classroom settings. Further, The Complete Journey would be ideal for academic research as it should enable one to study the effects of direct marketing to customers.
The following are examples of questions that could be submitted to students or considered for academic research:
CREATE TABLE campaign_desc (
"description" VARCHAR,
"campaign" BIGINT,
"start_day" BIGINT,
"end_day" BIGINT
);CREATE TABLE campaign_table (
"description" VARCHAR,
"household_key" BIGINT,
"campaign" BIGINT
);CREATE TABLE causal_data (
"product_id" BIGINT,
"store_id" BIGINT,
"week_no" BIGINT,
"display" VARCHAR,
"mailer" VARCHAR
);CREATE TABLE coupon (
"coupon_upc" BIGINT,
"product_id" BIGINT,
"campaign" BIGINT
);CREATE TABLE coupon_redempt (
"household_key" BIGINT,
"day" BIGINT,
"coupon_upc" BIGINT,
"campaign" BIGINT
);CREATE TABLE hh_demographic (
"age_desc" VARCHAR,
"marital_status_code" VARCHAR,
"income_desc" VARCHAR,
"homeowner_desc" VARCHAR,
"hh_comp_desc" VARCHAR,
"household_size_desc" VARCHAR,
"kid_category_desc" VARCHAR,
"household_key" BIGINT
);CREATE TABLE product (
"product_id" BIGINT,
"manufacturer" BIGINT,
"department" VARCHAR,
"brand" VARCHAR,
"commodity_desc" VARCHAR,
"sub_commodity_desc" VARCHAR,
"curr_size_of_product" VARCHAR
);CREATE TABLE transaction_data (
"household_key" BIGINT,
"basket_id" BIGINT,
"day" BIGINT,
"product_id" BIGINT,
"quantity" BIGINT,
"sales_value" DOUBLE,
"store_id" BIGINT,
"retail_disc" DOUBLE,
"trans_time" BIGINT,
"week_no" BIGINT,
"coupon_disc" DOUBLE,
"coupon_match_disc" DOUBLE
);Anyone who has the link will be able to view this.