Showing Revision 3 created 05/25/2016 by Udacity Robot.

1. Title:
   Checkout steps code
2. Description:

3. 1140 0:01 - 0:06
   As your user progresses through
   the steps in the checkout process,
4. 7400 0:07 - 0:11
   your app needs to send
   an analytics hit for each step.
5. 13140 0:13 - 0:15
   However, you only need one checkout hit.
6. 16965 0:17 - 0:22
   So subsequent steps in the checkout
   process, send checkout option hits.
7. 23200 0:23 - 0:26
   So that you don't over report
   the number of checkouts.
8. 26140 0:26 - 0:31
   And use the setCheckoutStep
   method to set the step number.
9. 30860 0:31 - 0:34
   And you can set the number
   to whatever you want, but
10. 34370 0:34 - 0:38
    it only shows up in the checkout
    behavior analysis report in
11. 37580 0:38 - 0:43
    the google analytics dashboard
    if you set a funnel step for it.
12. 42540 0:43 - 0:47
    If i set the step in the code to 99, but
    I've only labeled 4 checkouts steps in
13. 47310 0:47 - 0:51
    the admin console, I will never see
    the 99th step in the dashboard, so
14. 51250 0:51 - 0:53
    that's just not a good idea.
15. 53650 0:54 - 0:54
    That's better.
16. 55460 0:55 - 1:00
    So go ahead and add a second step to
    the checkout process for the dinner app.
17. 59760 1:00 - 1:01
    For that you're going to
    need a payment button.
18. 62840 1:03 - 1:07
    So add another button to the order
    dinner screen labelled payment.
19. 67970 1:08 - 1:13
    And in the order dinner activity,
    add the method to get the payment info.
20. 73290 1:13 - 1:16
    Then send a step two hit to analytics.
21. 76870 1:17 - 1:21
    Make sure to set the action
    to an ACTION_CHECKOUT_OPTION.
22. 81433 1:21 - 1:25
    Show the payment button
    only when relevant and
23. 85250 1:25 - 1:29
    hide the other buttons when
    the payment button appears.
24. 88870 1:29 - 1:31
    Test your app and try it out.
25. 92115 1:32 - 1:35
    And in the analytics dashboard,
    look for the realtime activity.
26. 96355 1:36 - 1:39
    And in the realtime activity,
    check for the events.
27. 99085 1:39 - 1:42
    See, here's the Get payment step.
28. 101795 1:42 - 1:46
    It might take a good amount of time
    after you see the realtime hits for
29. 105535 1:46 - 1:48
    the checkout behavior
    analysis page to update.
30. 108715 1:49 - 1:52
    But when it does,
    you should see your new payment step.
31. 112025 1:52 - 1:55
    Oh, something went wrong.
32. 114535 1:55 - 2:00
    I got a hit for getting the address,
    but not forgetting the payment details.
33. 119550 2:00 - 2:01
    That's not what I wanted.
34. 121230 2:01 - 2:05
    Okay that happened because step
    one is starting checkout and
35. 125280 2:05 - 2:07
    step two is getting the address.
36. 127950 2:08 - 2:11
    Step three is getting
    the payment details.
37. 130824 2:11 - 2:13
    That's easy to fix for now.
38. 132815 2:13 - 2:16
    Go to Admin > Ecommerce, and
39. 136495 2:16 - 2:20
    I'm just going to remove
    the Get address final step.
40. 139585 2:20 - 2:22
    Yep, I'll delete this rule.
41. 143320 2:23 - 2:29
    And submit, and go back to Reporting,
    and look at that.
42. 149460 2:29 - 2:33
    The get address step is gone,
    and I've got my payment details.
43. 153220 2:33 - 2:37
    And I know that that is correct,
    in this case.
44. 157100 2:37 - 2:43
    An alternative would be to change
    the step number to three in the code.
45. 162910 2:43 - 2:45
    But then we would be
    skipping over step two.
46. 164910 2:45 - 2:48
    So we would have values here,
    nothing here, values here.
47. 169340 2:49 - 2:53
    So when you set your check out step in
    the code, you need to make sure that it
48. 173420 2:53 - 2:57
    mapped the correct final step
    in the analytic dashboard.
49. 178310 2:58 - 3:04
    So make sure step two is in fact
    the payment step, and if not, fix it.
50. 186410 3:06 - 3:10
    So go ahead and do these steps and
    check the boxes when you're done.