Amplitude Lookup Table (Beta)
Amplitude's Lookup Table integration lets you import your own data and map it to ingested properties to have an enhanced set of properties.
This feature is in closed beta
This feature is in closed beta. Customers with an Enterprise plan or the Govern add-on can contact their Amplitude Customer Service Manager or Account Executive to get access.
You can also create and manage lookup tables via an API. See Lookup Table API for more information.
Setup¶
Prerequisites¶
To set up this integration, you need the following:
- An event property or user property to create a mapping from.
- A CSV that has the data you want to map to. The first column data must correspond to the mapping property value.
Amplitude setup¶
- In Amplitude Data, click Catalog and select the Sources tab.
- In the Lookup Tables section, click CSV.
- Upload the CSV then click Next.
- . Map your event property.
- When you're done mapping, click Finish.
Update a lookup table¶
If you want to create a new lookup property or that mapped property is wrong, you can update the lookup table.
- In Amplitude, navigate to Data Sources, then find the lookup table in the Sources table.
- Click the Edit Lookup Table Configuration tab.
- Make your changes. You can change the mapping, or replace the CSV by uploading a new one.
- When finished, click Update your lookup table configuration.
Delete the lookup table and its properties¶
When you no longer need a lookup table, you can delete it.
- In Amplitude, navigate to Data Sources, then find the lookup table in the Sources table.
- Click the Edit Lookup Table Configuration tab.
- Click the trash icon.
- Follow the on-screen instructions.
Lookup table use cases¶
With Amplitude's Lookup Table feature, you can import your own data and map it to ingested properties to create an enhanced set of event and user properties. With them, you can:
- Enrich data using ingested property values. You've captured an event called
Purchased
with an event property namedSKU
. TheSKU
value itself doesn't inherently hold a lot of meaning. But with your list of all the SKUs and their corresponding product names, you can use this feature to create a new property calledProduct Name
and have it automatically populate based on that list. - Bulk update property values. You've captured a user property called
Language Code
and passed in language codes (en_US
,fr_FR
,de_DE
, etc.). This is difficult to read, so you want aLanguage
property that maps to friendlier values likeEnglish
,French
, andGerman
. Use this feature to create a new property calledLanguage
that maps the language codes to the language names. - Bulk filter long lists. You want to see user behavior for a specific region and you have a list of all the customers and their regions. Use this to map each customer to a region, creating a new "Region" property. Now you can filter specifically to each region in a chart.
Still have questions? Ask them in the Community.