Skip to content
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

[Idea] The ability to update a visit, or be able to start a visit programmatically. #75

Open
jmartyniak opened this issue Jun 21, 2023 · 0 comments

Comments

@jmartyniak
Copy link

jmartyniak commented 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:

  • 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?

@jmartyniak 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant