pinterest-for-woocommerce
pinterest-for-woocommerce copied to clipboard
Redirect back to integration after user creates new Pinterest business account
Is your feature request related to a problem?
After creating a new business account, users were not redirected back to Wordpress to complete setup.
Half of users (5/10) who participated in our study did not have an existing Pinterest Business account. These users created a new account by either (1) clicking the “Create a new Pinterest account” link in the integration’s Setup flow (2) by connecting with their personal account, then signing out or (3) by going to the Pinterest website directly. Users that clicked “Create a new Pinterest account” were taken to business.pinterest.com, not pinterest.com/business. Additionally, users (regardless of how they initiated account creation) were not redirected back to Wordpress to complete setup after creating a new business account and had to be prompted to do so.
How to reproduce the problem
Describe the solution you'd like
If a user opts to create a new Pinterest Business account from the integration, redirect them back to the setup flow after the creation process is complete.
Describe alternatives you've considered
Additional context
Needs additional investigation into how/where this would be solved (and probably confirmation whether it is still an issue)
A relevant PR was #213 where a detection of the account type was added. When authenticated account wasn't a business account and there were also no other linked business accounts, the user can click "Create business account" and is transferred to Pinterest to create a business account.
From that PR:
Clicking the "Create Business Account" button will sent the user to Pinterest to create a linked business account. That flow in Pinterest doesn't return the user back to the plugin, so to go around that we are refreshing the Authenticated user's Business accounts on window.focus.
We are not aware of a way (for example passing a return URL to Pinterest) on that flow that would send the user back to the plugin. In that sense this can be fixed reliably from the plugin's side.
@niketpins what do you think?