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

tracking: Add Mixpanel event on Control clicks #2857

Merged
merged 1 commit into from
Sep 25, 2017

Conversation

dlespiau
Copy link
Contributor

We'd like to gain some insight on how controls are used.

@dlespiau dlespiau requested review from fbarl and leth September 21, 2017 10:39
Copy link
Contributor

@fbarl fbarl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd pass in that extra title property, otherwise LGTM!

@@ -21,6 +22,7 @@ class NodeDetailsControlButton extends React.Component {

handleClick(ev) {
ev.preventDefault();
trackMixpanelEvent('scope.node.control.click', { id: this.props.control.id });

This comment was marked as abuse.

This comment was marked as abuse.

We'd like to gain some insight on how controls are used.
@dlespiau dlespiau force-pushed the 2017-09-21-control-tracking branch from cc557e5 to 802559e Compare September 22, 2017 15:40
@dlespiau dlespiau merged commit 74c0c78 into master Sep 25, 2017
@dlespiau dlespiau deleted the 2017-09-21-control-tracking branch September 25, 2017 11:06
dlespiau added a commit that referenced this pull request Sep 26, 2017
Unfortunately, I forgot to rebase before renaming trackMixpanelEvent() and a PR
adding a new trace point was already in-flight.

More precisely:
  - #2861 renames trackMixpanelEvent()
    to trackAnalysticsEent()
  - #2857 add a new
    trackMixpanelEvent() call.

Each PR is fine, but with the merge of both without rebasing any, we end up
with master having a dandling call to trackMixpanelEvent().
dlespiau added a commit that referenced this pull request Sep 26, 2017
Unfortunately, I forgot to rebase before renaming trackMixpanelEvent() and a PR
adding a new trace point was already in-flight.

More precisely:
  - #2861 renames trackMixpanelEvent()
    to trackAnalysticsEent()
  - #2857 add a new
    trackMixpanelEvent() call.

Each PR is fine, but with the merge of both without rebasing any, we end up
with master having a dandling call to trackMixpanelEvent().
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 this pull request may close these issues.

2 participants