Observing cases where two user ids are tied to same identity but none of the user show up as migrated.
- Any known reason why we would see such cases?
- what is the best way to build an incremental dbt model considering the migrations that take place.
Two users tied to same identity but doesn't show up as migrated user
Userlevel 3
+1
Hi,
Usually, this should not happen; however, in some cases, it has been observed that there are some identities with multiple users. This could occur due to two known reasons; however, for any reason, it should not exceed 0.2% of the total identified users at a given time.
The common reasons for this are:
- Heap uses cache memory to load web reports, making it faster. Therefore, due to a small time lag in cache refresh, recently identified users could be displayed as multiple instead of being merged. This should be temporary, and the users will appear as one after some refreshes.
- The second cause is related to how Heap runs the query to merge the users. Due to query optimization, in some cases, there might be a very small percentage (not exceeding 0.2%) of identities that could have more than one user, as the merging is not performed.
Please check how many identities are affected by this issue. If it is less than 0.2% of the overall identities, it should not be a problem as it won't have a noticeable impact on the reporting. However, if the issue affects a higher number of identities, you should reach out to "support@heap.io" and open a support ticket.
Hope this helps!
Reply
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.