You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here is the use case:
The app is a ruby rails app, that serves HTML so no real sense of a Javascript application.
I am generating a fingerprint using fingerprintjs, which returns the result with a callback. This callback sometimes returns quickly or slowly, which seems to be based on the browser. For example in chrome it returns quickly, and on Firefox it returns slowly.
And in some cases, the visit has already been created. So when I call ahoy.configure in the callback the visit is already created and the fingerprint is never set.
A couple of thoughts:
whenever configure is called it updates the visit.
createVisit is exposed or a new helper method is created upsertVisit.
Other ideas? Am I thinking about this incorrectly?
The text was updated successfully, but these errors were encountered:
jmartyniak
changed the title
Idea: The ability to update a visit, or be able to start a visit programmatically.
[Idea] The ability to update a visit, or be able to start a visit programmatically.
Jun 21, 2023
Here is the use case:
The app is a ruby rails app, that serves HTML so no real sense of a Javascript application.
I am generating a fingerprint using fingerprintjs, which returns the result with a callback. This callback sometimes returns quickly or slowly, which seems to be based on the browser. For example in chrome it returns quickly, and on Firefox it returns slowly.
And in some cases, the visit has already been created. So when I call
ahoy.configure
in the callback the visit is already created and the fingerprint is never set.A couple of thoughts:
createVisit
is exposed or a new helper method is createdupsertVisit
.Other ideas? Am I thinking about this incorrectly?
The text was updated successfully, but these errors were encountered: