Request additional scope when connecting Ads via PAX

[aaemnnosttv]

Feature Description

The Ads module requires a new OAuth scope when connecting via PAX for the purpose of providing in-product support/feedback.

---

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

• The Ads module should request an additional OAuth scope under the same conditions that it requests the adwords scope:

  https://www.googleapis.com/auth/supportcontent
  

Implementation Brief

• Update \Google\Site_Kit\Modules\Ads::get_scopes to include the additional scope

Test Coverage

• Update coverage for the method

QA Brief

• Ensure the paxAds feature flag is enabled.
• Reset Site Kit or set up a new site and proceed to connect the Ads module. Check that the additional scope (Support Content) is requested within the Google Auth screen.

Changelog entry

• Add new OAuth scope to Ads module.

[aaemnnosttv]

This needs a follow up since the implementation only requires the scope when Ads does, but this misses the scenario when the Ads scope is first requested which is invoked on the client here

site-kit-wp/assets/js/modules/ads/components/setup/SetupMainPAX.js

Line 77 in 1c40b02

additionalScopes: [ ADWORDS_SCOPE ],

Sending back for a quick follow-up 👍

[wpdarren]

QA Update: ✅

Verified:

• The additional scope (Support data) is requested within the Google Auth screen.
• The error reported previously for the scenario when the Ads scope is first requested does not occur. I am able to complete the oAuth and no errors appear on the setup screen.

Screenshots