-
Notifications
You must be signed in to change notification settings - Fork 283
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Retrospective user recognition #25
Projects
Comments
Hi guys, this feature is really interesting and much needed, when are you planing to add it for PostgreSQL? |
Hi @clementgalopin ! Once it will be available, it will work for most destinations, including postgres. It's currently in the making, the ETA is mid-Jan |
Hi @clementgalopin! We are happy to announce that this feature has already been released (v1.27.0)! Read more about configuration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have different ways to identify user. The way that always works relies on cookies. For some users, other ids can be known (through id() call). Example:
Right after event3 we can amend event1 and event2 and add email=a@b.com
Proposed architecture (highlevel):
Possible ideas for state manager and queue:
The text was updated successfully, but these errors were encountered: