As long as there are no other elements matching that lead to events you do not want / need, this should be fine. There is no “correct” or even “best” selector, as long as it is not too complex without catching too much. I know: sounds easy but might be hard. This is why I try to get custom data attributes for tracking proposes wherever I can.
A selector like [data-track-type=“xyz”] usually survives a (good) relaunch while IDs and classes might change. However, for the time being your trigger should work as expected.
best,
Markus