Skip to content

[Content]: Correlation between group/identify/track/screens tables #7529

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.

Sign up for GitHub

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

Jump to bottom
Open
lhunath opened this issue Mar 27, 2025 · 0 comments
Open

[Content]: Correlation between group/identify/track/screens tables #7529

lhunath opened this issue Mar 27, 2025 · 0 comments
Assignees
@pwseg
Labels
content When the bug is about content that needs to get fixed triage

Comments

@lhunath
Copy link

lhunath commented Mar 27, 2025 •
edited
Loading

What article on segment.com/docs is affected?

https://segment.com/docs/connections/storage/warehouses/schema/

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

It is unclear how to correlate tables, for instance, how to determine what the active group or active screen is at the time of a tracks event. It is also unclear what exactly the anonymous_id is.
More exacting correlations for each data point with other tables and the Segment API would be much appreciated to take out the guess-work.

Additional information

No response
@lhunath lhunath added content When the bug is about content that needs to get fixed triage labels Mar 27, 2025
@lhunath lhunath changed the title [Content]: Correlation between group/identify/track tables [Content]: Correlation between group/identify/track/screens tables Mar 27, 2025
@pwseg pwseg self-assigned this Mar 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pwseg pwseg

Labels
content When the bug is about content that needs to get fixed triage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lhunath @pwseg