Create profile-properties.md #794
Conversation
Adding a separate profile props page to outline specs on the new data type
🦙 MegaLinter status:
|
| Descriptor | Linter | Files | Fixed | Errors | Elapsed time |
|---|---|---|---|---|---|
| markdownlint | 1 | 16 | 0.34s |
See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff
MegaLinter is graciously provided by
|
@bgiori @justin-fiedler - I'm not sure I understand why this is failing. Would you be able to help? |
…dev-center into chrisseldo-patch-2
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
|
@justin-fiedler @bgiori can we get this reviewed? |
There was a problem hiding this comment.
Hi @chrisseldo I'm the new Head of Dev Docs, and found this PR in the queue.
If this PR is still valid, please take a look at my edits and we'll also need to figure out where we want this to appear in the nav.
| Customers can now bring in non-behavioral, customer profile data from their data warehouse to merge it with the existing behavioral product data already living in Amplitude. These values will always display the most current value being synced from the customer’s data warehouse. | ||
|
|
||
| ## Setup | ||
| To set up a Profile Property in Amplitude, you must connect Amplitude to your data warehouse. Once connected, and you reach the data configuration section, you must select the “Warehouse Props” data type in the dropdown. From there, there are two minimum requirements for the import: a user identifier (user_id) and a profile property. Note: you may add more than one warehouse property per import, but there must be at least one per import. |
There was a problem hiding this comment.
Need some additional context here, and we should format this in an ordered list.
Adding a separate profile props page to outline specs on the new data type
Amplitude Developer Docs PR
Description
Adding a separate profile props page to outline specs on the new data type
Deadline
ASAP :)
Change type
PR checklist:
mkdocs serve.mkdocs servedidn't generate any failures.@amplitude-dev-docs