Clarify requirements for displaying Free Ads Credits

[joemcgill]

While working on #2558, it was discovered that the useFreeAdCredit() hook, which is intended to determine whether the Google Ads account is eligible for the $500 free ads credit, was returning false in situations where the credit was expected to be visible (see related conversation).

In order to ensure this hook is working as expected, we need to clarify the requirements of this hook. Right now, it works by selecting the googleAdsAccount object returned from useGoogleAdsAccount() and checking to see if the googleAdsAccount.sub_account value is true and if the googleAdsAccount.created_timestamp value is less than 60 days ago. However, in many cases where this hook is used, those values are not available in the data store because they are only returned by the API during a specific part of the setup process when creating a new Ads ID.

https://github.com/woocommerce/google-listings-and-ads/blob/02537c218b8c0be21c1d5d62f5bb39f3dce71474/src/Ads/AccountService.php#L152-L161

My understanding is that Ads credits should be shown whenever the Ads account was created by the plugin within the last 60 days (i.e. not when an existing account is connected, or when the account is older that 60 days). Are there other requirements that need to be considered before updating this hook so it can be used throughout the admin to determine when the Free Ads Credit should be shown?

[eason9487]

In the v1 version, when linking to an existing account, it was not able to determine whether the account was a sub-account or not, nor to know when it was created. Ref:

• https://github.com/woocommerce/google-listings-and-ads/pull/329

  The data is only added when we create the account, since when we are linking we can't confirm whether it's a sub_account or not. So returning it as false might not be correct. If a user creates a sub_account and then disconnects and then relinks the same sub_account we will lose the created_timestamp and the boolean sub_account. We are accepting this as a limitation in v1.

• https://github.com/woocommerce/google-listings-and-ads/blob/24044c53e4a1e84116086291f02bef8e26af7372/js/src/hooks/useFreeAdCredit.js#L16-L20

Therefore, the implementation at that time could only be narrowly storing those two properties for the account newly created via this plugin. In other words, it was implemented on the basis of avoiding false positives.

The logic in useFreeAdCredit is still working today. The free credit banner was shown correctly in testing with the 90fd7e771ed1158b1b4a2d54981a27cf2b6b1710 revision.

[joemcgill]

Thanks, @eason9487. The current logic does work when creating a new account, but only when you're still in the state where that account was created. If the app is refreshed, or if the hook is used in a different context (like when wanting to display these free ads credit banners on the plugin dashboard #2538, pending designs) then this data can no longer be used.

After talking with @fblascogarma the guidance from Google was that there too many internal factors for us to implement logic to only show these banners when an account is eligible and instead we should show it in nearly all cases as long as we continue including the "Terms and conditions apply" link. See this Slack convo for more context.

Next steps here would be to:

• Remove the 60-day logic since even some accounts created less than 60 days ago are not eligable.
• Try to limit this to only show for accounts that have been created by this plugin vs existing accounts that have been connected. @mikkamp do you know if we have a way of determining that on the API side (i.e., whether the account is a sub account)? If not, then we should essentially always show these banners and remove the hook used as a conditional.

[eason9487]

The current logic does work when creating a new account, but only when you're still in the state where that account was created. If the app is refreshed, or if the hook is used in a different context (like when wanting to display these free ads credit banners on the plugin dashboard #2538, pending designs) then this data can no longer be used.

I'm not pretty sure the meaning of app is refreshed. Does it mean the plugin data is wiped out? Otherwise, if continue using the newly created and connected Ads account, the sub_account and created_timestamp data should keep existing and returning along with the wc/gla/ads/connection API.

• https://github.com/woocommerce/google-listings-and-ads/blob/02537c218b8c0be21c1d5d62f5bb39f3dce71474/src/API/Site/Controllers/Ads/AccountController.php#L64-L68
• https://github.com/woocommerce/google-listings-and-ads/blob/02537c218b8c0be21c1d5d62f5bb39f3dce71474/src/API/Site/Controllers/Ads/AccountController.php#L143-L147
• https://github.com/woocommerce/google-listings-and-ads/blob/02537c218b8c0be21c1d5d62f5bb39f3dce71474/src/Ads/AccountService.php#L80-L96

(I don't/didn't mean to have opinions on the new requirement, but only to explain the current implementation and past considerations in development.)

[mikkamp]

Try to limit this to only show for accounts that have been created by this plugin vs existing accounts that have been connected. @mikkamp do you know if we have a way of determining that on the API side (i.e., whether the account is a sub account)? If not, then we should essentially always show these banners and remove the hook used as a conditional.

No, we don't have a way of doing so. With an Ads account it has a link to an MCC account but this link is established whether it was initially created by one of the MCC's or not. I'm not aware of any account information which shows how the account was created.

[joemcgill]

Thanks, @mikkamp. In that case, I believe we should deprecate the useFreeAdCredit() hook and instead always show the Free Ads credit where applicable. We can include this update in the requirements for #2538, since that will be the first place where the ads credit will be used outside one of the campaign creation flows. @eason9487 does that work for you?

[eason9487]

[...] @eason9487 does that work for you?

I don't have opinions on the direction of requirements. I mostly focus on the implementation and technical things, so sure, the useFreeAdCredit can be removed after confirming no other scenarios need it.

[joemcgill]

Thanks. I'm going to mark this issue as closed now, and we can discuss the implementation details in #2538.