-
Notifications
You must be signed in to change notification settings - Fork 21
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
Campaign Creation: Show campaign setup fields immediately during onboarding #2500
Comments
Does it mean the uses of |
No, I don't think there is any reason to remove those methods. We should just remove the |
Engineering complete and approved, moving to UAT for @fblascogarma final approval |
Just tagging @joemcgill and @asvinb to advise this needs to be merged please |
Merge conflicts fixed and assigning to @fblascogarma for final approval. |
Closing this as completed since it was part of the 2.9 release. |
Part of #2459
Currently, the first time someone gets to the Create a Campaign step of the onboarding flow, they are presented with a promotion for PMax campaigns with the option either skip or create a campaign. Choosing to Create a Campaign reveals the forms fields needed to set up your first campaign. This adds unnecessary friction since this step is much simpler than it was when originally introduced.
Instead of showing the Skip/Create buttons in the
PaidAdsFeaturesSection
and hidingPaidAdsSetupSections
components, we will always show thePaidAdsSetupSections
.Acceptance Criteria
When reaching the Create a Campaign step of the onboarding flow:
PaidAdsSetupSections
) no longer show footer buttons.PaidAdsSetupSections
) are always visible.SetupPaidAds
components.Implementation Brief
Whether the footer buttons are shown in the
PaidAdsFeaturesSection
or not is based on thehideFooterButtons
prop of that component, which currently passes! hasGoogleAdsConnection || showPaidAdsSetup
. This entire prop can be removed and the footer buttons removed from the component itself and all the related logic be removed fromjs/src/setup-mc/setup-stepper/setup-paid-ads/setup-paid-ads.js
where this component is being used.Likewise, the
PaidAdsSetupSections
andStepContentFooter
are only shown ifshowPaidAdsSetup
is true. Now that we always want to show that component, we can remove all the logic related toshowPaidAdsSetup
, which is set via auseState()
hook. This includes removing remove theclientSession.setShowPaidAdsSetup
andclientSession.getShowPaidAdsSetup
methods injs/src/setup-mc/setup-stepper/setup-paid-ads/clientSession.js
. The rest of that file should remain since it is also referenced by thePaidAdsSetupSections
component.Test Coverage
Update E2E tests in tests/e2e/specs/setup-mc/step-4-complete-campaign.test.js to match expected behavior and remove unused helpers.
The text was updated successfully, but these errors were encountered: