FYI, we still have rollbar because of the JS #3240. I'm going to move this issue to Business as usual

Hmmm, this is not working well, if you check the latest events from ahoy_events table they are without visit_id nor site_id (I'm generating them visiting Getafe staging site). Please review that

-[ RECORD 1 ]---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------------------------------------
id         | 605
visit_id   |
user_id    |
site_id    |
name       | gobierto_people/people#show
properties | {"slug": "rafael-garcia", "action": "show", "locale": "es", "method": "GET", "controller": "gobierto_people/people"}
time       | 2022-02-17 05:01:23.547261

I made a change to not use bounce, and by mistake it was not saving the site correctly for visits with not authenticated users, but the schema of events and method to name them (controller#action) are the same. The only difference is that instead of using an organization_id gobierto events use a site_id, I can change it.

After talking with Victor I am using a different way of associating visits and events that I think can also be useful in contratos: At the moment of enqueuing the job to create the event from the controller there is a current_visit available which is passed to the job

@entantoencuanto thanks, now ahoy_events are tracking the site_id properly.

Would it be possible to add the site_id also to the field ahoy_visits? If we want to give the metric unique visitors to a single site right now it's not possible (please confirm @furilo).

Yes, it's possible, but currently the same visit can use different site_ids. For example, currently if I change in staging of site from the same browser the visit remains the same. I can investigate if a different visit can be generated for each site

Or may I do the same as I did with the user_id field, I can update the site_id when it changes

If the same user visits two sites it should be tracked as two visits, because sites should be independent. Customers don't care if the application is multitenant or there are N applications.

@entantoencuanto there's something I missed in the acceptance that is broken. Your PR doesn't work when a customer has a google analytics key setup (the first point of your PR description). See that you are removing the ga function, while it's necessary: https://rollbar.com/Populate/gobierto/items/6057/?utm_campaign=exp_repeat_item&utm_medium=email&utm_source=rollbar-notification&utm_content=control