Only create an enrichment table when the activity needs many features that CANNOT be associated with another activity
Enrichment tables should be used sparingly because they can slow down your queries when you need to use them in a dataset.
If you are creating an activity and find yourself wanting more features, first consider if the features you want can be added to a related activity instead. It's very easy to borrow features(#how-to-borrow-features-from-other-activities-when-building-a-dataset) from another activity when constructing a dataset.
Enrichment tables are only needed when a specific activity has many features that cannot be associated with another activity. The activities that need enrichment are often commonly used in datasets and need to be sliced and diced by their various dimensions.
viewed_page (or started_session)
Columns from the enrichment table: utm_medium, utm_source, utm_content, utm_campaign, ip_address, screen_width, ad_source, device_type, referral_url, referral_domain, fbclid, gclid, etc
Columns from the enrichment table: product_name, product_description, sku, manufactured_by, volume, weight, etc.
Our data team is here to help! Here are a couple ways to get in touch...
💬 Chat us from within Narrator
💌 Email us at [email protected]