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

Present campaign creation directly on fourth step of onboarding #2383

Closed
mikkamp opened this issue Apr 23, 2024 · 2 comments
Closed

Present campaign creation directly on fourth step of onboarding #2383

mikkamp opened this issue Apr 23, 2024 · 2 comments
Labels
needs investigation type: enhancement The issue is a request for an enhancement.

Comments

@mikkamp
Copy link
Contributor

mikkamp commented Apr 23, 2024

User story

As part of the User Flow Review session we received some feedback on various issues which could be improved. Not all the suggestions have been decided on, and some needed some additional data to backup whether it was a blocker for many people. However I'm logging the issues here so we can determine how we would like to resolve them.

Describe the solution you'd like

When we reach the fourth step of onboarding we are initially presented with the option to connect an Ads account:
gla-step-4

Note

Connecting an Ads account will be moving to step one as part of #2215
With that change implemented any of the screenshots in this issue would no longer show the Google Ads card, the rest of the screen would remain the same.

Once we've connected the Ads account we move on to the next state where the user is now asked whether they want to create the campaign or skip:
gla-step-4-2

If we click on the option to create the campaign it will load the next state where they can enter campaign details, and then once again either create the campaign or skip:
gla-step-4-3

Feedback

The feedback that was given on this multistep process was two fold. Firstly the users need to go through an additional step to be able to start campaign creation. There is no direct need for this to happen, so we could directly present them with the option to fill in the campaign details after connecting the Ads account. Also if the Ads account has been moved to step 2 then there seems to be even less purpose of requiring this intermediate step, so the recommendation was to skip it.

Secondly there was some feedback that the buttons were shown within the section, which isn't consistent with the other onboarding steps (where the action / next buttons were at the bottom of the screen). One comment was that they were initially stuck on the screen as they didn't find the action buttons at the bottom and it wasn't clear enough that the section "Boost product listings with Ads" was a required section to interact with. This could either be resolved by placing the action buttons in the same location as other screens, or the intermediate status could be skipped since that would resolve both feedback comments.

@mikkamp mikkamp added the type: enhancement The issue is a request for an enhancement. label Apr 23, 2024
@mikkamp
Copy link
Contributor Author

mikkamp commented Jun 11, 2024

Just updating this issue as after moving the Ads account connection to step 1, the fourth step looks slightly different and it makes it even more obvious that the extra step is not necessary to start with campaign creation:

image

The expectation would be to directly jump to the screen after "create campaign" has been clicked:
image
The merchant will still be presented with the option to skip campaign creation at the bottom of the screen.

Related issue would be to move the FAQ section lower so the buttons to create / skip are more visible.

@joemcgill
Copy link
Collaborator

Closing in favor of #2459.

@joemcgill joemcgill closed this as not planned Won't fix, can't repro, duplicate, stale Aug 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs investigation type: enhancement The issue is a request for an enhancement.
Projects
None yet
Development

No branches or pull requests

3 participants