Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There are ways to make this work. But what you are really asking for is a feature called distinct id aliasing, which would allow you to reference one distinct_id ID to another. Unfortunately, we don't offer that right now. This turns out to be a much harder issue than you'd expect due to the unique nature of the data-store we wrote for mixpanel.</p> <p>In the meantime, I can give you a few strategies to get around this limitation:</p> <ul> <li><p>When a user first comes to your website, set a distinct id for them which you generate internally. Once they register for an account, reference that distinct_id in your user detail table, and then continue to register subsequent events with that id. Each subsequent time a user auths, use the stored value as the distinct id. Hopefully when they return the cookie will still be around, and you will capture all the events without a hitch.</p></li> <li><p>You could, also, let mixpanel give them an auto-issued distinct_id value, and then grab that at the time of registration by using mixpanel.get_property() then add that to your users table, and use that when you identify them in the future.</p></li> <li><p>But what if they auth from one machine and then come on from another, or a different browser, or from a mobile device? Then the time in between when they hit your site and when they auth they'll be issued a new distinct_id by your site... and there is no way to alias! The solution here is a bit hackier. The only way to get that data is to log those events that were sent before the authentication (maybe server-side) and then send them via HTTP specification to the rest API with the correct distinct_id once the user auths. As long as you keep the correct time stamps, it will all appear correctly, chronologically within mixpanel. If the user never auths, then you can have the logged events time out and send them anyways.</p></li> </ul> <p>Would either of these work for you?</p>
    singulars
    1. This table or related slice is empty.
    1. POMixpanel anonymous user converts to identified user tracking
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USphillee
    1. USWoody Schneider
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI presumed there was not a way to alias distinct id's together; i was just hoping I was wrong. We implemented the internally generated distinct id solution, and it should work for most cases - it's just more management and overhead to keep track of a second distinct identifier. Anyway, thanks for the response. I assume the "we" in your response means you work @ mixpanel, and you have mixpanel.com listed in your profile - so I'll award the answer here - as it's authoritative (:
      singulars
      1. PO
      1. USJim Rubenstein
    2. COAnd now the feature exists: https://mixpanel.com/docs/integration-libraries/using-mixpanel-alias
      singulars
      1. PO
      1. USraylu
    3. CO@WoodySchneider - is there any better solution for #3 yet or still best to log and post after the fact with the correct ID?
      singulars
      1. PO
      1. USdsldsl
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload