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

[Purchase] Analytics requirements #463

Closed
7 tasks done
alloy opened this issue Dec 6, 2016 · 1 comment · Fixed by #573
Closed
7 tasks done

[Purchase] Analytics requirements #463

alloy opened this issue Dec 6, 2016 · 1 comment · Fixed by #573
Assignees

Comments

@alloy
Copy link
Contributor

alloy commented Dec 6, 2016

@1aurabrown @anipetrov Please elaborate on requirements

  • Experiment Viewed: fires when an artwork page qualified for the test is loaded with the appropriate variation params
    • properties: {
      experiment_id: purchase_flow,
      experiment_name: purchase_flow,
      variation_id: [purchase, control],
      variation_name: [purchase, control],
      nonInteraction:1
      }
  • Clicked "Contact Gallery": fired when users clicks on the contact gallery button
    • properties: {
      artwork_id: artwork._id,
      context_type: sidebar
      }
  • Clicked "Purchase": fired when users clicks on the purchase button
    • properties: {
      artwork_id: artwork._id,
      context_type: sidebar
      }
  • Purchase request failed to submit: fired when user clicks on the send request button the the /checkout page but does not successfully submit an inquiry. If we start displaying errors (state not added), we might want to gather those in a property eventually -- we do that for other "fail" events, eg. registration_failed_to_submit for auctions
  • Clicked "Back to Browsing" purchase flow: fires when user clicks the Back to Browsing button on the /thank-you page
  • Sent Artwork Inquiry: send when user successfully sends an inquiry from the purchase flow
    • properties: {
      artwork_id: artwork._id,
      artwork_slug: artwork.id,
      inquiry_id: inquiry_request.id
      user_id: user.id -> grabbed after signup
      }
  • Created account: fires when the user creates an account during the purchase flow
    • properties: {
      context: purchase flow
      user_id: similarly, will have to force the user_id -- this is already done for the account creation events from modals
      }
@anipetrov
Copy link
Contributor

is this all in staging now for me to give it another run?

@anipetrov anipetrov mentioned this issue Dec 16, 2016
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants