microsoft / microsoft/ApplicationInsights-JS

ClickAnalyticsPlugin extension should have html tag configurability

Open
#2,318 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
685
Forks
261
Avg merge
21h 33m
Merged PRs (30d)
5

Description

**Is your feature request related to a problem? Please describe.**
I'm working on a project where we wanted to use the ClickAnalyticsPlugin to capture all click events for analytics. However, we're using a framework that renames the html tags with custom names, thereby bypassing the extension's filter for 4 specific tags (with 4 different input types allowed) : [extensions/applicationinsights-clickanalytics-js/src/handlers/AutoCaptureHandler.ts#L61](https://github.com/microsoft/ApplicationInsights-JS/blob/master/extensions/applicationinsights-clickanalytics-js/src/handlers/AutoCaptureHandler.ts#L61)
Also, the documentation doesn't explicitly call out the limitations to which types of clicks are to be recorded.

**Describe the solution you'd like**
Can these tags be made to be configurable? If not, add documentation indicating which HTML tags that are clicked that will get recorded.

**Describe alternatives you've considered**
The alternative I'm exploring is to create my own catch-all event handler with my own filter, but I'm not going to implement all of the features the ClickAnalyticsPlugin extension provides. It just seems like this could have been part of the config.

**Additional context**
N/a

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with extensions/applicationinsights-clickanalytics-js/src/handlers/AutoCaptureHandler.ts around line 61 and trace how the ClickAnalyticsPlugin filters tags and exposes configuration. Review the related plugin documentation, then define whether configurable tags or documentation is appropriate; done means the supported tags and click behavior are explicit, with coverage for the chosen change.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
analytics, observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.