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

Onboarding Improvements Overview #2458

Open
1 of 9 tasks
eclarke1 opened this issue Jul 8, 2024 · 0 comments · Fixed by #2631
Open
1 of 9 tasks

Onboarding Improvements Overview #2458

eclarke1 opened this issue Jul 8, 2024 · 0 comments · Fixed by #2631
Assignees

Comments

@eclarke1
Copy link
Collaborator

eclarke1 commented Jul 8, 2024

Objective

Currently, only about half of users make it past the onboarding process to successfully set up and configure their WooCommerce store to integrate with Google Ads and Merchant Center. Simplifying and streamlining this process will lead to greater customer success.

Background

The first step of the current onboarding process requires a store administrator to successfully create and connect four separate accounts/services

Image

  • WordPress.com
  • Google Account
  • Google Merchant Center
  • Google Ads

Setting up each of these accounts creates opportunities for confusion or uncertainty for users, which can be reduced by consolidating this step into a simpler process. Additionally, there are several places during the configuration and confirming store requirements steps where we can remove redundant or unnecessary actions to create a more streamlined experience for users.

Overview

To streamline the onboarding process, we’re proposing the following adjustments to the onboarding flow steps.

Account Creation

To simplify this screen, we will consolidate account creation from the current four steps, to two:

Image

Connect to WordPress.com

This will only be shown if the store is not already connected. Otherwise, this UI will not be displayed.

Connect to Google

This step will consolidate all of the current steps for connecting to a Google account and creating/connecting to Google services into a single unified flow. Users will be prompted to connect a Google account, accept all necessary permissions scopes, and accept any necessary terms & conditions before either automatically connecting to the most applicable Ads and Merchant Center accounts, or creating new ones if they don’t already exist.

In addition, the FAQ list will be moved below the main “Continue” button to make the next step more obvious.

Configure Product Listings

In this step, we can remove the “Language” settings. This is something that we know, and cannot be edited by merchants so there’s no point of showing it.

Image

Additionally, this step includes selecting whether the store uses destination based tax rates. This does not need to be chosen during initial onboarding, so we’ll remove this step and default to destination-based tax rates and allow this setting to be adjusted after onboarding.

Image

Confirm Store requirements

Currently, merchants have to do three things in this page:

  1. Verify phone number
  2. Edit store address if they haven’t done it already on Woo core product
  3. Confirm pre-launch checklist

Phone verification and Store Address will remain the same:

Image

However, we will remove the Pre-Launch checklist:

Image

We can check these things post onboarding and surface to merchants if they’re missing something, like we currently do with MC issues.

Image

In some cases, we may already have a verified phone number and address set up in the MC account, in which case we can skip this step of the onboarding entirely and move right to the Campaign Creation step of the onboarding process.

Complete Your Campaign

Changes to the campaign creation are out of scope of this initial project and will be handled in a follow-up project.

Requirements

🔗See the Requirements Section of the PRD

Technical Design

The Onboarding Improvements work will be implemented by completing the following set of tasks:

Account Creation

Configure Product Listings

Confirm Store requirements

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants