Required Minimum Functionality RMF now applies to Internal-Only users?

[Matt Perry]

Hello,

As an agency, we've been developing various tools that we use internally to help us with account creation and management.  We've been very careful to not allow clients, partners, etc to use the API to maintain our status of an "Internal-Only AdWords API Client".  And our intention is to report any use changes when they are developed, as required.

When we began developing these tools, the RMF document said that it didn't apply to "Internal-Only" clients:

"This Section III(2)(f) does not apply to End-Advertiser-Only AdWords API Clients and Internal-Only AdWords API Clients"

See: http://googledata.org/google-adwords-api/changes-to-required-minimum-functionality-for-adwords-api-clients/

But now, the RMF document does not even mention "Internal-Only" clients:

"End-Advertiser-Only AdWords API Clients (each as defined in the Terms & Conditions) are not required to fully implement the required AdWords API features shown in the chart below; all other AdWords API Clients (as defined in the Terms & Conditions) must fully implement the required AdWords API features relevant to their tool type as explained below."

See: https://developers.google.com/adwords/api/docs/requirements

I understand that this forum cannot provide legal interpretation, but I'm hoping I'm missing something.

Since we use the API to manage other business's accounts, we're not End-Advertiser-Only.  But it makes no sense to me that if we've written code to internally use the API to create a campaign, we also need to have code to use the API to create Ad Group Sitelinks.

Was there any discussion around this change?  Do we know when this change occurred?  Are there any other documents that address this besides the RMF and TOS? Am I missing something?

Thanks.

[Oliver]

Google removed the "Internal-Only" keyword from the RMF more than 6 months ago.  There was no discussion on this forum about this change and they didn't make any announcement about it.

Oliver

[Matt Perry]

Update: I contacted the API token team directly about this.  They didn't provide too many details in their response, but it appears to be a case-by-case thing now.   

Although the term "internal-only" has disappeared from the RMF document, it's still a consideration in determining RMF compliance.  In our case, because our use remained internal-only, we were "good to go".