Skip to content
This repository has been archived by the owner on Dec 22, 2023. It is now read-only.

Problem with the documentation #16

Open
casertap opened this issue Dec 9, 2014 · 1 comment
Open

Problem with the documentation #16

casertap opened this issue Dec 9, 2014 · 1 comment

Comments

@casertap
Copy link

casertap commented Dec 9, 2014

Hi, I think your plugin is pretty awesome, I can't wait to use it and see if it is still the case in few weeks ;-)
I have trouble to set up my project using your documentation. I decided to go with the Frontend Events set up and I was misguided by the sentence:

First off, make sure you get this into your layout in a script tag somewhere at the bottom of the page is perfectly fine: <%= meta_events_frontend_events_javascript %>

To make this work, I needed to nest the code inside a jquery ready callback otherwise the registerFrontendEvent method is never fired and event are not registred inside of MetaEvents.

I took a look at the meta_event.js.erb and it seems to only manage the mixpanel.track method.
This is annoying because you need to identify and people.set your user to be able to link the event tracked with a user.

@cpb
Copy link

cpb commented Jan 14, 2020

I took a look at the meta_event.js.erb and it seems to only manage the mixpanel.track method.
This is annoying because you need to identify and people.set your user to be able to link the event tracked with a user.

Maybe this is a job for the backend? people.set works with whatever ID you provide it, and updates the attributes of the user with the data payload... So, I would recommend doing that on the backend incase there is user data you don't want to leak to the client...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants