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

R-2.1a Add a page to the SubmissionSuccessGuide panel to enable Enhanced Conversions #2239

Closed
Tracked by #2216
joemcgill opened this issue Feb 5, 2024 · 1 comment · May be fixed by #2242
Closed
Tracked by #2216

R-2.1a Add a page to the SubmissionSuccessGuide panel to enable Enhanced Conversions #2239

joemcgill opened this issue Feb 5, 2024 · 1 comment · May be fixed by #2242
Assignees

Comments

@joemcgill
Copy link
Collaborator

joemcgill commented Feb 5, 2024

Part of to #2216

When a user completes the onboarding flow, they should see an option to turn on enhanced conversions in the pop-up modal when they are already running campaigns. Turning on enhanced conversions requires that the Customer Data Terms of Service (ToS) has to be accepted, so if it has not been excepted, the modal will direct the user to the settings screen in Google Ads (GAFE) in order to complete this step instead.

Screenshot

Succes Modal width="400px}

Requirements Breakdown

1 – Update the SubmissionSuccessGuide component to include a new CTA modal page based on the following conditions:

Check if the user has (1) an ads account connected and if the user has (2) existing spending campaigns in their account. The modals that are presented to the user would depend on the following scenarios:

  • Option 1: User creates a campaign during onboarding
    • (Modal 1/2) PMax Setup Success Modal
    • (Modal 2/2) Enhanced Conversions Setup Modal
    • Note: Since this user has already setup a campaign, we do not need to prompt them twice with the “Spend $500 get $500 modal”
  • Option 2a: User skips campaign creation during onboarding, but has an existing spending campaign
    • (Modal 1/2) “You have successfully setup Google Listings & Ads”
    • (Modal 2/2) Enhanced Conversions Setup Modal
    • Note: Since the user has a spending campaign, they are not eligible for the “Spend $500 get $500 modal”, so we should not surface that.
  • Option 2b: User skips campaign creation during onboarding, and does not have an existing spending campaign (i.e. user has no campaigns, or user has non-GL&A campaigns that never spent)
    • (Modal 1/2) “You have successfully setup Google Listings & Ads”
    • (Modal 2/2) “Spend $500 get $500 Modal”
    • Note: Enhanced Conversions should still be accessible to this user in settings (to be implemented later), but we should not surface this in the modal.

Note: As of the changes deployed conversion tracking changes deployed in Q1, all users who reach the success modal should have an ads account configured, and conversion tracking enabled (regardless of campaign creation status)

2 – When displayed, the content of the modal should be as follows:

If user HAS NOT accepted ToS

  • Title: “Optimize your conversion tracking with Enhanced Conversions”
  • Body1: “Enhance your conversion tracking accuracy and empower your bidding strategy with our latest feature: Enhanced Conversion Tracking. This feature seamlessly integrates with your existing conversion tags, ensuring the secure and privacy-conscious transmission of conversion data from your website to Google”
  • Body2: “Activating it is easy – just agree to the terms of service on Google Ads and we will make the tagging changes needed for you. This feature can also be managed from Google Listings & Ads > Settings”
  • CTA Buttons:
  • Option 1: [Close] – isSecondary, should use the handleGuideFinish event.
  • Option 2: [Sign terms of service on Google Ads] – isPrimary, should open link to Google Ads settings page and set Enhanced Conversions status to pending in TBD API endpoint.

Implementation note: To improve the deep linking workflow, capture the OCID for newly created accounts by parsing the returned response from CreateCustomerClientResponse.invitation_link and store it so it can be used as a parameter for the deeplinking. Using the parameter will remove the account selection step and make it easier for users to get to the ToS page

If user HAS accepted ToS

  • Title: “Optimize your conversion tracking with Enhanced Conversions”
  • Body1: “Enhance your conversion tracking accuracy and empower your bidding strategy with our latest feature: Enhanced Conversion Tracking. This feature seamlessly integrates with your existing conversion tags, ensuring the secure and privacy-conscious transmission of conversion data from your website to Google”
  • Body2: “Clicking confirm will enable Enhanced Conversions on your account and update your tags accordingly. This feature can also be managed from Google Listings & Ads > Settings”
  • CTA Buttons:
    • Option 1: [Close] – isSecondary, should use the handleGuideFinish event.
    • Option 2: [Confirm] – isPrimary, should set Enhanced Conversions status to true in TBD API endpoint.

3 – Add appropriate data handling to the app that will be connected to future REST API endpoints to be developed separately:

  • There should be appropriate hooks and supporting selectors to retrieve the ToS status for step 2, above.
  • There should be appropriate hooks and supporting actions for dispatching updates to update the status of Enhanced Conversions based on descriptions above.
@joemcgill joemcgill changed the title R-2.1a Develop post-onboarding pop-up modal panel to configure enhanced conversions R-2.1a Add a page to the SubmissionSuccessGuide panel to enable Enhanced Conversions Feb 5, 2024
@joemcgill joemcgill linked a pull request Feb 12, 2024 that will close this issue
@asvinb asvinb assigned joemcgill and unassigned asvinb Feb 14, 2024
@joemcgill
Copy link
Collaborator Author

This has all been completed as part of #2242, which now includes all of the functionality required for #2216, so I'm closing this as complete while waiting on final review for the main feature branch.

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

Successfully merging a pull request may close this issue.

2 participants