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

Update Enhanced Conversions onboarding flow #2364

Open
joemcgill opened this issue Apr 11, 2024 · 0 comments · May be fixed by #2361
Open

Update Enhanced Conversions onboarding flow #2364

joemcgill opened this issue Apr 11, 2024 · 0 comments · May be fixed by #2361
Assignees

Comments

@joemcgill
Copy link
Collaborator

joemcgill commented Apr 11, 2024

Overview

This is an update to #2216.

The original definition for that feature were based on processing within the Google Ads which would automatically enable Enhanced Conversions on Google Ads when EC data was added to the gtag config after User Data Terms & Conditions (T&C) were enabled. After testing that implementation, we've concluded that this is not a viable option in the short term.

Instead, we now need to prompt the user to enable Enhanced Conversions directly in their GAFE Settings to enable the feature AND ensure that they have enabled the feature in the GL&A extension to be confident that the user has opted in to sharing EC data from the store with Google.

Previously implemented flow

Success modal

On completion of the setup flow, the user is presented with a success modal with two pages. For new accounts, the second page will prompt the user to set up paid accounts, but if we have determined that the user has already set up paid accounts, then the next page will be a prompt to set up Enhanced Conversions.

Image

If the user has not yet accepted Customer Data Terms & Conditions (T&C) in their Ads account (determined with a request to the Google Ads API) we prompt the user to Accept Terms & Conditions.

Image

When the user clicks the CTA, we leave the modal active and open a new window that links the user to the settings panel for accepting T&C

Image

When the user returns to the original tab after updating this setting, we update the modal to ask them to confirm that they want to enable Enhanced Conversions. This is the same screen that will be shown to the user if we had already determined that they had accepted T&C prior to showing this prompt—skipping the part of the flow described above that links them to the GAFE settings.

Image

Settings panel

If the user has confirmed enabling EC in the success modal above, they will now see a new panel at the bottom of the settings tab that shows that EC has been enabled, and allow them to manually disable the feature. If they had accepted T&C but closed the modal without enabling, then this will show in the disabled state.

Image

If the user has closed the modal without accepting T&C, then the setting will show a button that will open a tab to the same GAFE setting used during the onboarding prompt.

Image

Once clicked, until we can confirm the user has accepted T&C in the GAFE settings, we display the following instructions to remind the user that they still need to complete accepting the terms and conditions.

Image

Once we have confirmed that T&C have been accepted, the setting will show the enable/disable toggle.

Updated flow

Success modal

The success modal still begins with the same first page. This set of requirements only addresses the updates to the second page when we’re showing the prompt for enabling Enhanced Conversions.

Case 1: If Terms & Conditions are not accepted

When Terms & Conditions are not yet accepted for the connected Ads account, we will display a modal with instructions for how to set up Enhanced Conversions, which includes expectations of what steps they will need to take in the GAFE.

Proposed copy

  • Title: “Optimize your conversion tracking with Enhanced Conversions”
  • Body1: “Improve conversion tracking accuracy to gain deeper insights and improve campaign performance.”
  • Body2:
    • Click Enable Enhanced Conversions below to go to Google Ads Settings.
    • Turn on Enhanced Conversions, accept Terms, and then select “Google Tag” as your setup method. Click Save.
  • Body3: For more information, feel free to consult our help center article (link to https://support.google.com/google-ads/answer/9888656)

Proposed CTA

When the user clicks the CTA to confirm they want to enable enhanced conversions, we deep link them to the settings panel in GAFE so they can confirm the Enhanced conversions setting is enabled for the Ads account.

When they return to the open modal, if they have accepted T&C, we will show a success message (described below). If they have not accepted T&C, we remain on this page unless they manually close the modal.

Case 2: If Terms & Conditions were previously accepted

When this modal is reached but the T&C have already been accepted (e.g., in the case of connecting a pre-existing account). We want to confirm that the user wants to enable EC on this Woo store and show the following modal content...

Proposed Copy
Title: “Your Enhanced Conversions are almost ready”
Body1: “We noticed that you have already accepted Enhanced Conversions Customer Data Terms. In order to complete Enhanced Conversions setup on your store, click Confirm below”
Body2: “If you haven’t done so already please ensure that Enhanced Conversions is enabled in Google Ads Settings (add hyperlink), and that the setup method chosen is Google Tag”

Proposed CTA

  • [Close] remove, if possible.
  • [Confirm] – Enables the EC setting in the store and displays the success message

Once the user clicks the “Confirm” button, they will be presented with the success message described below (i.e., the same message shown to a user who successfully enables T&C in Case 1 above).

Success screen

After either case above, when we've been able to confirm that the T&C have been accepted, the modal is updated to show a message confirming that EC has been enabled on their site.

Proposed copy

  • Title: “We’ve successfully set up Enhanced Conversions for your store!”
  • Body1: “We updated your conversion tracking tags. You can manage this feature from your store's marketing settings."

Proposed CTA

  • [Close] Completes the flow and closes the flow.

Settings panel

If we have confirmed that user has enabled Enhanced Conversions during the setup modal, and we can determine that they have accepted T&C, we will display a settings panel with a toggle showing the feature as enabled. If we determine that the user has accepted T&C but they have NOT yet confirmed that they want to enable Enhanced Conversions for their store, then we show the same toggle, but with EC disabled.

In either case, we include instructions that the user also needs to make sure EC is enabled in their Ads account for this feature to work, with a deep link to the Google Ads Settings page. This is necessary because we don’t currently have a way to see if that setting has been enabled on the Ads account via the Ads API.

When we determine that the user has not confirmed Terms & Conditions in their Ads account, we can also infer that they have not enabled Enhanced Conversions, so we show them a settings panel that instructs them to visit their Ads account to enable Enhanced Conversions and accept T&C. Clicking this CTA will open a new window that deep links to the same settings panel in the GAFE that we open from the success modal.

Proposed Copy

  • Title: “Enhanced Conversion Tracking”
  • Body1: “Improve your conversion tracking accuracy and unlock more powerful bidding.This feature works alongside your existing conversion tags, sending secure, privacy-friendly conversion data from your website to Google”
  • Body2: “To properly measure your enhanced conversions, please ensure Enhanced Conversions is enabled in Google Ads Settings (add hyperlink), and that the setup method chosen is Google Tag”

Proposed CTA

  • Option 1: [Accept Terms & Conditions]
  • Option 2: [Enable] / [Disable] toggle
@joemcgill joemcgill self-assigned this Apr 11, 2024
@joemcgill joemcgill linked a pull request Apr 11, 2024 that will close this issue
@joemcgill joemcgill assigned asvinb and unassigned joemcgill Apr 11, 2024
@joemcgill joemcgill assigned joemcgill and unassigned asvinb Apr 17, 2024
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