Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Content]: Minor improvment to Profiles Sync Tables and Materialized Views #6954

Open
seanhan-segment opened this issue Aug 20, 2024 · 1 comment
Assignees
Labels
content When the bug is about content that needs to get fixed stale triage

Comments

@seanhan-segment
Copy link

What article on segment.com/docs is affected?

https://segment.com/docs/unify/profiles-sync/tables/

What part(s) of the article would you like to see updated?

The article does a nice job of describing raw vs materialized tables, but it doesn't explain that there's a relationship between raw and materialized which is a useful thing for customers to understand. E.g. in classic warehouse destination, the docs page clearly defines identifies as "A table with your identify method calls" and users as "A table with unique identify calls." A similar comparison would be helpful for Profiles Sync raw vs materialized tables.

Here's a simple chart I made for myself to remember how the raw vs materialized tables are related:
https://docs.google.com/spreadsheets/d/1ABeK4sA8iNsf8IV6jAbbuQJbXC0JbFUh7N3IfzZup_E/edit?gid=0#gid=0

Additional information

No response

@seanhan-segment seanhan-segment added content When the bug is about content that needs to get fixed triage labels Aug 20, 2024
@pwseg pwseg self-assigned this Aug 22, 2024
Copy link
Contributor

This issue is stale because it has been open 60 days with no activity.

@github-actions github-actions bot added the stale label Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content When the bug is about content that needs to get fixed stale triage
Projects
None yet
Development

No branches or pull requests

2 participants