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

Implement KPI setting on conversion #21

Merged
merged 3 commits into from
Jul 2, 2015
Merged

Implement KPI setting on conversion #21

merged 3 commits into from
Jul 2, 2015

Conversation

Valve
Copy link
Contributor

@Valve Valve commented Jul 2, 2015

No description provided.

@zackkitzmiller
Copy link
Contributor

👍

zackkitzmiller added a commit that referenced this pull request Jul 2, 2015
Implement KPI setting on conversion
@zackkitzmiller zackkitzmiller merged commit 65d361b into sixpack:master Jul 2, 2015
@zackkitzmiller
Copy link
Contributor

I'll tag a release today

@Valve
Copy link
Contributor Author

Valve commented Jul 2, 2015

@zackkitzmiller, btw, when I try to set a KPI on a participation call, it takes no effect. It only works on conversion. Is it by design?

@zackkitzmiller
Copy link
Contributor

Yes. You cannot assign a KPI to a participation.

@Valve
Copy link
Contributor Author

Valve commented Jul 2, 2015

OK, here is a scenario:

We need to track AB conversions separately for logged-in vs anonymous users.
A logged in user makes a participation and then a conversion.
Then 9 anonymous users make a participation and then a conversion.

I tag logged in users with 'loggedin' KPI, and anonymous users with 'anonymous' KPI.
In the end I expect the numbers on the dashboard to be:

1/1 for logged in KPI
9/9 for anonymous KPI,

but in reality they're:

1/10 for logged in KPI
9/10 for anonymous KPI, i.e. they don't convey the picture at all.

Please let me know if I"m misusing it and if it's possible to achieve this w/out setting up two experiments for anonymous/logged-in users.

@Valve
Copy link
Contributor Author

Valve commented Jul 3, 2015

I'll ask it on the project repo itself, I think it'll be more appropriate there.

@valo valo mentioned this pull request Feb 9, 2016
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