Initialize on a Specific Element

:point_right: Describe the problem

Currently AmplitudeJS binds to the entire page. This can be overkill and needs to be optional. Sometimes you only want to bind events to elements within a certain element.

:busts_in_silhouette: Problem evidence & reach

Any user who wants to narrow down and scope the binding of events to a certain element.
Specific Requests

:smiling_face_with_three_hearts: Describe the “impact” on users?

We can limit the scope of where AmplitudeJS is bound along with opening the door to making re-usable web components.

:trophy: How to solve this problem

Allow the user to pass an element, identifier, etc. when initializing AmplitudeJS.

:100: How do we validate the problem is solved?

Users can bind AmplitudeJS events to a specific element and bind multiple times per page for multiple players.

This has been migrated to Initialize on a Specific Element · Discussion #485 · serversideup/amplitudejs · GitHub