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
The Snowplow package has two first-class outputs: snowplow_sessions and snowplow_page_views. Both should include the stitched user identity, inferred_user_id, that is the product of snowplow_id_map.
We frequently find ourselves building reports on top of both tables, and we should be able to perform counts of distinct visitors that agree between them.
The text was updated successfully, but these errors were encountered:
Really good idea! Can we additionally try to set the user_id field more appropriately for snowplow_page_views? Right now, it's only set if the user's persistent id was known at the time of that page view. If we're going to join to the id map, are we also able to set the snowplow_user_custom_id field if it was known in the scope of the session?
Rationale
The Snowplow package has two first-class outputs:
snowplow_sessions
andsnowplow_page_views
. Both should include the stitched user identity,inferred_user_id
, that is the product ofsnowplow_id_map
.We frequently find ourselves building reports on top of both tables, and we should be able to perform counts of distinct visitors that agree between them.
The text was updated successfully, but these errors were encountered: