Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Target release

Type // to add a target release date

Epic

Type /Jira to add Jira epics and issues

Document status

DRAFT

Document owner

@ mention owner

Designer

@ designer

Tech lead

@ lead

Technical writers

@ writers

QA

🎯 Objective

\uD83D\uDCCA Success metrics

Success Metrics

Importance

Metric

Description

Current Value

Expected Value

How are we measuring it?

 

Impact on moving user further in the funnel

from: /cart -> / cart/payment (Feature has the biggest impact on this step)

 

SUCCESS METRIC

Overall CVR Rate from / cart to / cart/payment

Overall conversion rate from /cart to /cart/payment.

Out of the total users who land on the /cart how many proceeded to /cart/payment page

 

 

 

 

CONTROL METRIC

CVR Rate of guest users from / cart to / cart/payment

 

Overall conversion rate from /cart to /cart/payment for users with GuestID.

Out of the total users who land on the /cart how many proceeded to /cart/payment page that are Guests

 

 

 

 

CONTROL METRIC

CVR Rate of registered users from / cart to / cart/payment

 

 

Overall conversion rate from /cart to /cart/payment of registered users. Out of the total users who land on the /cart how many proceeded to /cart/payment that are registered

 

 

 

 

Impact on the CVR to purchase $ on the end of the funnel

from / cart to /order-confirmation/[OrderID]

 

SUCCESS METRIC

Overall CVR to an actual purchase from / cart to /order-confirmation/[OrderID]

Overall conversion rate from /cart to /order-confirmation/[OrderID]

Out of the total users who land on the /cart how many end up on /order-confirmation/[OrderID]

 

 

 

 

CONTROL METRIC

CVR Rate of guest users from / cart to /order-confirmation/[OrderID]

 

Overall conversion rate from /cart to success page for users with GuestID.

Out of the total users who land on the /cart how many proceeded to /order-confirmation/[OrderID] page that are Guests

 

 

 

 

CONTROL METRIC

CVR Rate of registered users from / cart to /order-confirmation/[OrderID]

 

 

Overall conversion rate from /cart to success page of registered users. Out of the total users who land on the /cart how many proceeded to /order-confirmation/[OrderID] that are registered

 

 

 

 

Impact on the CVR to purchase $ considering the whole ordering flow
from /menu (page view) with service mode selected to /order-confirmation/[OrderID] (Feature does not have an impact on the whole flow)

 

MONITOR

CVR Rate to purchase of users landing on /menu with service mode selected to purchase

Out of all the users landing on /menu (page view) with service mode selected (meaning the user is at the menu already with a store selected or a delivery address), how many end up purchasing - so end up on /order-confirmation/[OrderID]

 

 

 

 

Clicks

 

CONTROL METRIC

% of users selecting guest checkout at /cart

Out of the users at /cart unauthenticated, how many select guest checkout to continue

 

 

 

 

CONTROL METRIC

% of users selecting sign in at /cart

Out of the users at /cart unauthenticated, how many select sign in to continue

 

 

 

 

Funnel abandonment- where we see people drop off including guest email input and sign in/register pages

 

CONTROL METRIC

abandonment rate

 

 

 

 

 

Time to Place an order from the moment of intent

 

CONTROL METRIC

Average Order Placement Time for

  • registered users

  • guest users

Time from starting ordering process (/menu (page view) with service mode selected (meaning the user is at the menu already with a store selected or a delivery address) to finish placing an order so end up on /order-confirmation/[OrderID]

 

 

 

 

Registration - Cannibalization

 

CONTROL METRIC

Count of opt in originated from the /cart step

% Opt-in database evolution- as it relates to the trade off digital sales increase vs known sales increase. If we increase sales but reduce drastically the opt-in database you are influencing less people with CRM comms which we know has a higher LTV than the normal guest checkout customer

 

 

 

 

Financial Impact

 

MONITOR

MO Sales

Total sales generated by mobile ordering/ mo

 

 

 

 

Overall Experience

 

 MONITOR

App Ratings

DE seeing complaints in App ratings that no guest checkout is available

 

 

 

 

Milestone

Scope/ Outcome

Work Required

Owner

Available on staging

Available on Production

Status

1

  • Add configurable time period of storing the Guest Order data in the database. Configure to 10 year for DE

  • Preventing the guest user from seeing app content dedicated for registered users only

  • Add a security layer limiting actions allowed for the orders with Guest token. Actions allowed for example: priceOrder, validateCommitOrder, commitOrder, getOrder, etc

  • Add a guard that allows to use of the Guest Token only for the allowed actions

  • Creating Guest Token- To place an order as a Guest users require to have be authenticated on our platform/ In order to do that we need to create a Guest Auth token. We can’t follow the current path for collecting it because Guests don’t have accounts in Cognito and in the User DB entries.

  • Save Card Option Removed at the Payment step
    Iden

  • Added Modal to continue as a guest

  • Adjusted data on the confirmation page

TRX-908 - Getting issue details... STATUS F

TRX-949 - Getting issue details... STATUS F

TRX-959 - Getting issue details... STATUS F

TRX-941 - Getting issue details... STATUS M

TRX-947 - Getting issue details... STATUS M

TRX-957 - Getting issue details... STATUS M

TRX-956 - Getting issue details... STATUS M

TRX-912 - Getting issue details... STATUS W
TRX-1010 - Getting issue details... STATUS W

Fagundes, Silvia configure time period for data storage

WORK IN PROGRESS

2

  • Accommodate new transactional email communication with AWS SES instead of Braze

  • Decide and execute when guest token should be removed, so no other order can be made with that token to guarantee anonymity

  • Prevent error appearing on the success page due to loyalty account request which does not exist for guest users

TRX-1006 - Getting issue details... STATUS

TRX-909 - Getting issue details... STATUS

TRX-962 - Getting issue details... STATUS

TRX-1006 - Getting issue details... STATUS

TRX-909 - Getting issue details... STATUS

TRX-962 - Getting issue details... STATUS

TO DO

3

  • Identify areas for authenticated users only that guest users should not have access to

  • Prevent Guests from accessing the aforementioned areas for registered users

  • Change copy to “choose payment' instead of “add payment” at the /cart/payment page

TRX-958 - Getting issue details... STATUS

TRX-948 - Getting issue details... STATUS

TO DO

4

E2E Testing

TO DO


Guest Checkout V2

TRX-910 - Getting issue details... STATUS

TRX-1008 - Getting issue details... STATUS

TRX-1009 - Getting issue details... STATUS

\uD83E\uDD14 Assumptions

\uD83C\uDF1F Milestones

Dec2021Jan2022FebMarAprMayJunJulMilestone 1Milestone 2
Dashboard
Notification

Feature 1

Feature 2

Feature 3

Feature 4

iOS App

Android

\uD83D\uDDD2 Requirements

Requirement

User Story

Importance

Jira Issue

Notes

HIGH

 

 

 

 

 

\uD83C\uDFA8 User interaction and design

(question) Open Questions

Question

Answer

Date Answered

(warning) Out of Scope

  • No labels