You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/docs/data-governance/lexicon.mdx
+30Lines changed: 30 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -293,6 +293,36 @@ Once you've made your modifications, you can directly import the CSV file into L
293
293
294
294
Event and property descriptions and metadata (hidden, dropped, sensitive, etc) that are already in Lexicon will be overwritten by descriptions and metadata for matching event and property names. By default, any event and property descriptions for events that are not imported will remain unchanged unless you check the option to overwrite your entire data dictionary during import.
295
295
296
+
### Segment Import
297
+
When importing a data dictionary from Segment Protocols using the Segment Config API, you will be asked for your Segment Token and Segment Workspace. You can find your Segment Token by going to your Segment dashboard: Settings > Access Management > Tokens
298
+
299
+
You can use an existing Token, or create a new token with a Token Role of Workspace Owner.
300
+
301
+
For the Segment Workplace value, we recommend using the Slug name located in the Segment dashboard: Settings > General Settings.
302
+
303
+
Once you have your Segment Token & Workspace, head over to Lexicon and Select Import from Segment.
304
+
- Enter your Token & Workspace
305
+
- Select the Plan you want to import from Segment
306
+
- Review the Events and Profile Properties that will be imported
307
+
-ImportyourSegmentPlanintoLexicon
308
+
309
+
### Avo.app Import
310
+
In order to import your data dictionary from Avo.app, you will need to enable an integration with Mixpanel. The following information would be necessary in order to complete this integration from Avo.app:
311
+
- Mixpanel Project ID (https://mixpanel.com/project/[Mixpanel Project ID]/...)
312
+
- Mixpanel Service Account Username & Secret (Owner or Admin role required)
313
+
To publish your Avo data dictionary to Lexicon, click the "Publish to Lexicon" button in the integration interface.
314
+
315
+
Click [here](https://www.avo.app/docs/publishing/integrations) for more information on integrating Avo.app with Lexicon.
316
+
317
+
### mParticle Import
318
+
When importing a data dictionary from mParticle, navigate to your Data Plan and select Download Plan Version from the upper right menu.
319
+
320
+
- Click Import on the top right hand side of Lexicon
321
+
- Select mParticle
322
+
- Select the downloaded JSON file from mParticle Data Plans
323
+
- Review Events, Event Properties, and User Profile Properties to be imported.
324
+
-ImportdataintoLexicon
325
+
296
326
## Lexicon Schemas API
297
327
298
328
Mixpanel provides a suite of API endpoints for you to Retrieve, Create, and Delete your data dictionary in Lexicon. To use these APIs, check out our [API reference docs](https://developer.mixpanel.com/reference/lexicon-schemas-api).
0 commit comments