In December 2025 Google Cloud announced the Google Cloud Partner Network, with a formal rollout in the first quarter of 2026. It replaces Partner Advantage and changes how partners are measured, not just what they are called. If you hold a Google Cloud status alongside AWS and Microsoft, this is the program change most likely to reshuffle your certification priorities this year.
Google’s public announcement does not publish tier thresholds. CRN Australia reports that partners must generate $20 million in partner co-sell ACV to reach Diamond, $2 million to reach Premier, and $250,000 to reach Select. It also reports that Diamond carries further milestones: 20 partner-implemented workloads, 30 co-sell-influenced opportunities, and 200 professional certifications. A GCP-focused analysis cites the same ACV figures. Treat all of these as reported, and confirm them in your own program portal.
| Tier | Reported co-sell ACV | Other reported milestones |
| Select | $250,000 | — |
| Premier | $2 million | — |
| Diamond | $20 million | 20 partner-implemented workloads; 30 co-sell-influenced opportunities; 200 professional certifications |
Source: CRN Australia (2026), corroborated on ACV figures by independent analysis. Not published by Google in the program announcement.
The figure that drew the most pushback from partners was the certification count for Diamond. One consultancy founder told CRN Australia that large systems integrators could reach Diamond on headcount without the skill depth of a smaller specialist team, and that his own firm, at roughly 100 people, expected the climb to take about two years.
Run the arithmetic for a firm of that size: 200 certifications across 100 people is two per head. Now remember that the same engineers are also being asked to certify for AWS (ten foundational certifications for Premier on the Services Path), for Microsoft designations, and for whatever security vendors the firm resells. Certification hours are one finite budget with several vendors drawing on it. Which program gets the next hundred hours is a portfolio decision, whether or not anyone is treating it like one.
Automatic tracking is genuinely useful, and it removes a reporting burden. But it lives inside Google’s portal. It can tell you how you are doing against Google. It cannot tell you how your Google progress compares with your AWS progress, or whether the engineers Google needs certified are the same ones AWS needs certified by the same quarter. The vendor dashboard answers “how am I doing with this vendor?” Only a view across the portfolio answers “where should the next certification hours go?”
One analysis of the new program argues that the competency structure is best read as a map of Google’s priorities rather than a checklist, and that partners who treat it as pure compliance tend to plateau once they have satisfied the requirements. That is worth taking seriously for planning. If the framework rewards validated co-sell and post-sale contribution, then the evidence trail for those contributions is as important as the certifications.
Decision test: If reaching the next Google tier needs certification hours that your AWS or Microsoft renewals also need, name which program loses. Make it a decision instead of an accident.
The Google Cloud Partner Network is separate from the Google Ads Partners program, which keeps its Member, Partner, and Premier structure (Premier being the top few percent of agencies). Marketing agencies that hold both should track them as two programs with two sets of requirements, not one “Google status.”
Google Cloud, like the other hyperscalers, runs a partner program that mixes technical credentials, customer evidence, and commercial performance. Each of those has a different owner inside your firm, which is where problems start. Engineering owns the certifications. Sales owns the customer stories. Finance owns the revenue figures. Nobody owns the picture that combines them.
Keep one folder per vendor program with the same four items inside: the requirements document with the date you read it, the list of credential holders with expiry dates, the customer evidence you have collected, and the next assessment date with the owner’s name. It takes an afternoon to build and saves days when an assessment arrives.
Google Cloud’s own Partner Advantage documentation. Third-party summaries lag program changes, so use them only to know what to look for.
Only after costing it. Use the tier return framework in our post on whether a partner tier is worth it, and apply the half test to the expected benefit.
Letting a requirement lapse unnoticed, usually a certification or a customer-success item that nobody owned.
AltamIQ: AltamIQ gives you the cross-vendor view the individual portals cannot: Google, AWS, Microsoft, and security vendors side by side, with certifications mapped to the people who hold them. It is partner portfolio management for the firm holding the tiers, which is a different job from the PRM a vendor uses to run its program.