Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add tags/copy button track for adobe support #357

Closed
hemarina opened this issue Apr 10, 2024 · 4 comments · Fixed by #364
Closed

Add tags/copy button track for adobe support #357

hemarina opened this issue Apr 10, 2024 · 4 comments · Fixed by #364
Assignees

Comments

@hemarina
Copy link
Contributor

Currently adobe is not tracking every button (filter tags, copy button) click on the site.

@kristenwomack
Copy link
Contributor

Thank you, do you know what the effort would be to enable click tracking on:

  • the template name on the main page that opens the panel with more information
  • the copy/paste buttons for the command on each template repo listed on the main page
  • the copy/paste command on the quick use and VS Code commands on the side panel (that opens when you select the template name

@hemarina
Copy link
Contributor Author

The template names are already tracked in workspace, and it shows as the template name. I'll add track on copy/paste buttons for the command on each template repo listed on the main page. However, for card panel, any behaviors on it are not being tracked by Adobe analytics.

@kristenwomack
Copy link
Contributor

Sounds good, thank you Marina! Is it possible to track the card panel elements? Maybe a future item.

@hemarina
Copy link
Contributor Author

Tracking this future issue in #365. I think we might need to make a request with adobe analytics team to enable the tracking on card panel.

@hemarina hemarina changed the title Add button track for adobe support Add tags/copy button track for adobe support Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants