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

Breakdown insight by data- attributes #5914

Closed
mariusandra opened this issue Sep 13, 2021 · 5 comments
Closed

Breakdown insight by data- attributes #5914

mariusandra opened this issue Sep 13, 2021 · 5 comments
Labels
enhancement New feature or request stale

Comments

@mariusandra
Copy link
Collaborator

mariusandra commented Sep 13, 2021

Is your feature request related to a problem?

posthog-js autocaptures clicks on links, along with some related attributes:

image

However it's hard to use this data in the interface.

Describe the solution you'd like

I'd like to breakdown an insight by a data-attribute.

Describe alternatives you've considered

  • Exporting a list of events as CSV, and getting the data from there (bad news: elements are missing for postgres)
  • Running a SQL query to get the attributes and get the breakdown that way
select
    event.*,
    element.attributes->'attr_data-attr' as report_id
from posthog_event event
    left join posthog_elementgroup elementgroup on elementgroup.hash = event.elements_hash
    left join posthog_element element on element.group_id = elementgroup.id
where
    event.event = '$autocapture'

Additional context

The need came from a customer who wanted to breakdown clicked links by a data-report-id attribute.

Thank you for your feature request – we love each and every one!

@EDsCODE
Copy link
Member

EDsCODE commented Sep 15, 2021

The breaking down on a data-attr is possible. To clarify, in what context is the breakdown being applied? Would the use case be specifically for $autocapture events/actions defined with $autocapture events and breaking those insights down by the data-attr?

@paolodamico
Copy link
Contributor

+1 on understanding the full context here of the problems they're trying to solve. For instance, would breaking down on other attributes be useful? Depends on the problems they're solving.

@neilkakkar
Copy link
Collaborator

@paolodamico paolodamico removed the UI/UX label Feb 22, 2022
@posthog-bot
Copy link
Contributor

This issue hasn't seen activity in two years! If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in two weeks.

@posthog-bot
Copy link
Contributor

This issue was closed due to lack of activity. Feel free to reopen if it's still relevant.

@posthog-bot posthog-bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale
Projects
None yet
Development

No branches or pull requests

6 participants