Splits the Ads & analytics Working Group into two WGs

[mrjoro]

Although ads and analytics have some overlap, there are areas where they differ and in thinking about upcoming efforts it makes sense to create a more focused Working Group for each.

This also renames the "Ads" WG to "Monetization" since ads aren't the only way AMP pages are monetized.

Since this is modifying the Working Groups it requires approval from the TSC.

/cc @lannka @jeffjose @jasti

[cramforce]

CC @ampproject/tsc

We should discuss in our next meeting how to decide on proposals like this one.

[davidstrauss]

This also renames the "Ads" WG to "Monetization" since ads aren't the only way AMP pages are monetized.

We also have a working group for "Access Control and Subscriptions." Would subscriptions also move to the "Monetization" WG?

[jasti]

Hi @davidstrauss, I'm a product manager working on Core AMP @ Google.
The Subscriptions & Access control work is large and orthogonal enough compared to ads based monetization that we could consider keeping them separate.

The renaming of the WG from ads to monetization is to accomodate other ads work that doesn't strictly involve the mechanics of fetching and rendering the ad but more broadly around publisher audience targeting, content recommendation, audience development, etc. (e.g. email collection using a form on an AMP page) which don't strictly rely on display ads but help increase overall publisher revenue in a sustainable way.

Let me know what you think.

[davidstrauss]

Let me know what you think.

I was just curious about the intended scopes of the groups and where there might be overlaps. Please carry on if this makes sense for the people involved. :-)

[cramforce]

@jasti I kind of agree that making the different to subscription based monetization would make sense. What non-ad monetization is in scope? Stuff like affiliate links?

[jasti]

@cramforce sorry, not sure I understand your question. Although subscriptions could fall under the new monetization working group, we are recommending the structure below because of how different the type of work is. Today, they have no work in common except they both deal with 💵.

As a net result of this discussion, we will have:

1. Analytics WG
2. Monetization WG (previously known as ads) which could cover affiliate links, publisher audience targeting, content recommendation, publisher audience development.
3. Access Control and Subscriptions WG

[mrjoro]

Per ampproject/meta-tsc#4 it sounds like the TSC moved discussion about the process for updating WGs to a future meeting.

In the meantime I'll create the wg-analytics and wg-monetization repos/teams so that we can start keeping track of Status Updates/etc. in these areas since it'll be easier to combine them if the TSC decides not to go with the split than to split them apart later. (The main question seems to be about whether it's "ads" or "monetization" rather than rather the split is okay, and changing the name of the repos/teams is straightforward.)

[jasti]

I'm fine either way but think it makes sense to call it "Ads" WG here since "Access Control and Subscriptions" WG is separate.

[cramforce]

Approved by TSC for two working groups

1. Ads (no rename to Monetization)
2. Analytics

[mrjoro]

I've updated the PR to change Monetization back to Ads.

[mrjoro]

I realized we never got this change in. @cramforce can you approve?