-
Notifications
You must be signed in to change notification settings - Fork 0
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
Divolte issue #1
Comments
Hi prk2331, We are handling this at the consumer level; not in divolte. |
@jerome73 thanks for giving me your time to response. Managing that whole session stuff in the consumer by suffixing the original sessionid received from divolte can you please provide me that snippet of code, so that I can implement it and see their all provisions which needs to be handle, It would be really helpful for me, Jerome. Thank you and may you and your family have a lovely Christmas and Happy New Year as well |
I suggest you take a look at logisland on github: https://github.com/Hurence/logisland/blob/master/logisland-components/logisland-processors/logisland-processor-web-analytics/src/main/java/com/hurence/logisland/processor/webanalytics/IncrementalWebSession.java That is the code of the sessionization processor we developed to handle all of this |
Hi @jerome73 as per your guidance last month I created the Incremental web session logic, and its working fine. thanks for your help |
Hi prk2331, We faced the same kind of needs. We solved it out by relying on firebase sdk to push events into GA and then export mobile events to Big Query then write a consumer using kafka connect to retrieve big query tables into kafka topic. |
hi @jerome73 sorry for that I am writing you here actually that Divolte repository has been archived by the owner, and I am stuck in one problem of Divolte of session Id
The problem you have raised this in 2017
divolte/divolte-collector#163
I am facing the same issue
can you please help me out what solution you have applied for this
This would be really helpful for me
Thanks
The text was updated successfully, but these errors were encountered: