Initialize on a Specific Element

[danpastori]

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.

Problem evidence & reach

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

Initialize a specific element, or initialize in a ShadowRoot

Multi-players loadad by external js

Hi @ErnadoO , As of right now, AmplitudeJS doesn’t support separate Amplitude instances per page. However, I will be adding that soon. In the mean time, you should be able to apply data-attr-song-index to the element and you can control each song individually: Interactive Elements - AmplitudeJS Documentation. I’d also update AmplitudeJS to the newest version since 3.5.2 is older. Here’s an example of how to support multiple songs: Multiple Songs Example - AmplitudeJS Documentation Hope this …

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.

How to solve this problem

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

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.

[jaydrogers]

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