adorable-planet-58025
09/01/2021, 12:12 AMhandsome-animal-43816
09/01/2021, 12:52 AMrough-alligator-32210
09/01/2021, 6:33 AMrudderlabs/rudder-server:1-alpine
image on AWS ECS since Sunday (29/08).rough-alligator-32210
09/01/2021, 6:33 AMrough-alligator-32210
09/01/2021, 6:37 AMgray-baker-21956
09/01/2021, 8:28 AMadorable-gold-9667
09/01/2021, 1:25 PMwindow.rudderanalytics.identify("userId1234", { email:"<mailto:foobar@gmail.com|foobar@gmail.com>", ph: "+11234567890", "zip": "75001" }); /* here make sure Amplitude doesn't get the *traits* since that will be violating PII */
window.rudderanalytics.track("Performed this event") // when this event is tracked make sure the identified user's traits are not sent here
flaky-lamp-59978
09/01/2021, 1:47 PMflaky-lamp-59978
09/01/2021, 1:48 PMquick-engineer-78417
09/01/2021, 1:55 PMhandsome-animal-43816
09/02/2021, 12:43 AMrhythmic-pizza-93292
09/02/2021, 5:22 PM"Version":"23022021.065348"
not sure what it meansbulky-noon-15156
09/02/2021, 10:05 PMthankful-hair-24699
09/02/2021, 10:39 PMnarrow-petabyte-24274
09/03/2021, 4:31 AMgorgeous-application-3887
09/03/2021, 9:02 AMrapid-engineer-48799
09/03/2021, 2:06 PM.track
events automatically include user traits under context_traits
I’m not sure if I’m doing something wrong but all .track
events seem to use the traits
from the most recent .identify
call.
e.g.
1. In node: .identify('User A', {email: '<mailto:a@a.com|a@a.com>'})
2. In node: .track('action', 'User A')
-> In WH: context_traits_email=<mailto:a@a.com|a@a.com>
3. In node: .identify('User B', {email: '<mailto:b@b.com|b@b.com>'})
4. In node: .track('action', 'User A')
-> In WH: context_traits_email=<mailto:b@b.com|b@b.com>
😱rapid-engineer-48799
09/03/2021, 2:06 PMUser A
but appears with the traits for User B
in the warehouse (and all destinations)narrow-petabyte-24274
09/03/2021, 6:11 PMicy-exabyte-53668
09/04/2021, 2:24 PMfancy-answer-79663
09/05/2021, 7:33 AMshy-ghost-70319
09/05/2021, 4:07 PMidentity
, groups
and userId
for our particular use case.
We're a two-sided marketplace – there are both buyers and sellers on our platform (gigsalad.com). An individual person can have different user types associated with them (buyer and seller accounts) but they're all tied together with a singular accounts
table. The configuration looks like this:
• accounts
table – every user has a singular account and ID associated with them
◦ Not much information is stored here
• buyers
table – some accounts have buyer IDs associated with them
◦ One account
can only have one buyer
ID associated
◦ More information, but only buyer-focused information, is stored here
• sellers
table – some users seller IDs associated with them
◦ One account
can have many seller
IDs associated – if they create a listing for different things
• Each table has unique ID within itself, but they're not unique between unique between them – an accounts
ID of 12345
exists that is not related to the buyers
ID of 12345
. A single account
could have up to 20 seller
IDs associated with it.
My question is... what would you all recommend we use for userId
on pageviews, tracking events, etc.? The accounts
ID? Or should we use the individual buyers
and sellers
IDs? Should we then associate all of their Identity entries together together with Groups? The buyers
and sellers
IDs aren't unique between them, so we would need to prepend them with b-12345
or s-12345
and similar.echoing-minister-6344
09/05/2021, 7:51 PMechoing-minister-6344
09/05/2021, 7:51 PMechoing-minister-6344
09/05/2021, 7:52 PMechoing-minister-6344
09/05/2021, 7:52 PMpowerful-forest-14749
09/06/2021, 12:00 PMpowerful-forest-14749
09/06/2021, 6:45 PMuser_id
vs userId
powerful-forest-14749
09/06/2021, 7:04 PMsession_id
from server-side sources?
Here's a link to the Segment docs that explains the feature but essentially this is so session events can be tied together even if some are sent from the serverfamous-artist-36900
09/07/2021, 1:56 PM