Checked issue with identify - I suppose there was ...
# dev-frontend
a
Checked issue with identify - I suppose there was some confusion when Charles said he will implement User Traits section, so I totally forgot about identify section below that. Also it looks like identify section is a bit obsolete, as we do not have user sign ups and sign in, so we have to use anonymous id, right?
c
trying to remember. sorry this was all so long ago now.
are we doing any tracking in the UI, right now?
yes. dumb question.
does the front ever call identify with the
customerId
returned in
workspaces/get
?
i'm having trouble finding it.
i think we need the UI to call identify with that id so that we can associate what's going on in the UI with what's going on in the backend.
a
Nope we do not call identify at all right now.
c
does it make sense that we should?
a
Looks like identity section in tracking plan was unchanged since dataline initial implementation.
c
👍 yeah. makes sense. probably an oversight on my part.
it seems like we want to do it once at the start of a session, but since there is no log in, i'm not too sure when it should happen.
maybe just everytime
workspaces/get
is called?
a
Yeah. But we want to identify correct users right? But as we do not have users in system ( he is not registering ) we have to use anonymous id.
c
yeah. our goal is to associate the anonymous id with the customer id.
that's as granular as we can get.
a
So like when user enters we assign some Id for him and then we can track correctly. As I understood that’s how it is described in segment docs.
As for association- we can pass customerId along with anonymous id, can’t we?
c
yeah. i think segment assigns the anonymous id automatically. so pretty much we just need to do the part where you pass customer id with anonymous id and then we are all good.
a
Ok. Sounds reasonable.
c
I added one more segment related issue. we'd like to add one more piece of metdata if possible.https://github.com/airbytehq/airbyte/issues/1092
👍 1