What the Attributed Revenue Dashboard Is
AWS launched the Attributed Revenue Dashboard inside Partner Central in April 2026 as the visible layer on top of a broader initiative called Partner Revenue Measurement (PRM). The short version: AWS now has a way to automatically track the AWS consumption that your product drives across customer accounts, and partners can see that data themselves through a new dashboard in Partner Analytics.
Before this, partner impact was largely self-reported or estimated. A partner would tell their PDM that their product drives significant AWS ARR, and the PDM would factor that in. Now AWS measures it directly. The dashboard shows monthly attributed revenue by product, AWS service, and billing period, pulling together data from all three PRM implementation methods in a single view.
Partner Revenue Measurement is now how AWS measures partnership success across partner programs and benefits, creating a direct line between partner impact and AWS investment. What the dashboard shows is increasingly what drives funding decisions, co-sell prioritization, and tier assessments, not what you tell your PDM.
What the Dashboard Shows
Once you have implemented Partner Revenue Measurement and migrated to the new Partner Central console experience (PC 3.0), the Attributed Revenue Dashboard is accessible through Partner Analytics. It provides three headline metrics at the top of the page:
Below those metrics, the dashboard provides three views: month-over-month attributed revenue by product, revenue broken down by AWS service (so you can see which services your product is driving), and a detailed table showing revenue by product, AWS service, and billing month.
A few important constraints worth knowing: revenue data is refreshed monthly and reflects the prior billing month's consumption. Revenue is only shown when a product reaches a minimum threshold of unique customer accounts in a given month. If volume drops below that threshold in any month, no data is displayed for that period. And critically, AWS only shows aggregated data: no individual customer names, account IDs, or per-customer revenue figures are ever surfaced.
Partners with multiple AWS Marketplace seller accounts can connect subsidiary accounts to see aggregated revenue across their full product portfolio in a single view.
The Three Implementation Methods
Partner Revenue Measurement is implemented through one of three methods, or a combination of them depending on your product architecture. The right method depends on how your product is built and how it interacts with AWS services.
You apply standardized tags to AWS resources using the product code from your AWS Marketplace listing. When tagged resources generate AWS consumption, that consumption is attributed to your product. Revenue attribution continues until the tag is removed or the resource is terminated.
Good for: Partners whose product provisions or manages AWS resources in customer or partner accounts. Works across most AWS services.
You embed a unique product code in your application's AWS SDK configuration as a user agent string, using the format APN_1.1/pc_<YOUR-PRODUCT-CODE>$. When your application makes AWS API calls, the user agent identifies them as driven by your product.
Good for: SaaS products that make AWS API calls on behalf of customers. Can be implemented by updating application code directly or setting an environment variable, with no changes to individual API calls.
For partners with AMI or ML products listed on AWS Marketplace, EC2 and SageMaker consumption is automatically measured when customers purchase through Marketplace. No additional implementation is required beyond the standard Marketplace listing setup.
Good for: Partners with AMI or SageMaker products already listed on AWS Marketplace. This is the lowest-effort option if it applies to your product type. You can also combine this method with Resource Tagging or User Agent String for broader attribution coverage.
You can implement multiple methods simultaneously. For example, an AMI product can use AWS Marketplace Metering for EC2 attribution and User Agent String for attribution on additional AWS services the product uses beyond EC2. AWS recommends instrumenting PRM on all AWS services and resources your solution consumes, not just the primary ones.
What You Need Before You Can Access the Dashboard
The dashboard is not available to every partner by default. Three things need to be in place before you can see any data:
- Partner Central console migration (PC 3.0): You must be on the new AWS Partner Central experience, not the legacy console. If you have not migrated, this is the first step.
- A public AWS Marketplace listing: Your product code, which drives the revenue attribution, comes from your Marketplace listing. Without a listing, there is no product code to track.
- AWS account linked to Partner Central: Your AWS account must be linked to your Partner Central account. This is the same account linking requirement that gates ACE eligibility and APN fee billing.
Once those three elements are in place, implement at least one of the three PRM methods for your product. Revenue data will begin appearing in the dashboard the following month, reflecting the previous billing period's consumption.
The Deadline That Changes the Urgency
July 31, 2026: Access to new fund requests inside the AWS Partner Funding Portal (APFP) is contingent on PRM implementation by this date. Starting January 1, 2027, Partner Revenue Measurement will be the foundation for all partner funding benefits, including co-sell incentives. Partners who have not implemented PRM before these dates will be blocked from new funding requests and will lose access to funding benefits that depend on accurate revenue attribution.
This is not a soft recommendation. It is a hard cutoff tied directly to APFP access and MDF eligibility. If you have been deferring PRM implementation because it felt optional, that calculation changes on July 31, 2026.
The practical timeline: PRM takes time to implement and validate, and revenue data only shows monthly. If you implement in late July, you will have data from August onward, but your July 31 compliance status is what gates APFP access. Getting started now gives you time to implement, verify the tracking is working, and have data in the dashboard before the deadline arrives.
Why This Changes How AWS Measures Partner Value
The deeper shift here is not the dashboard itself. It is the underlying philosophy it represents.
Previously, a lot of partner impact was self-reported or inferred. PDMs had a general sense of which partners were driving AWS ARR, but the data was indirect, often based on ACE pipeline and anecdotal customer conversations. Partners who were doing meaningful work but had not built strong PDM relationships were underrepresented in AWS's internal view of their value.
Partner Revenue Measurement changes that. It creates a direct, automated measurement of the AWS consumption your product is driving across customer accounts. Your PDM can see it. The funding team can see it. The field reps evaluating whether to bring you into a co-sell deal can see it. The data speaks for your program without requiring you to narrate it in every conversation.
The partners who are most at risk are those with real Marketplace traction who have not implemented PRM. Their impact is real, but it is invisible to AWS's measurement system. When funding decisions get made or tier advancement is reviewed, the dashboard shows nothing, and that gap will increasingly be interpreted as low partner impact rather than a measurement gap.
Your PDM can now see the Attributed Revenue Dashboard too. Partners who have implemented PRM come into PDM conversations with data already visible: the dashboard shows which products are driving AWS consumption, which services are being used, and how that has trended over time. Partners who have not implemented PRM show up to those same conversations with nothing to point to. The disparity will compound as AWS leans harder on PRM data for program decisions in 2027 and beyond.
What to Do Right Now
If you have a Marketplace listing and have not implemented PRM, the sequencing is straightforward:
- Confirm your Partner Central console migration. If you are still on the legacy console, migrating to PC 3.0 is the first prerequisite. This also unlocks ACE API access and the new account linking requirements.
- Link your AWS account to Partner Central if you have not already done this. This is the same account linking step required for ACE eligibility and the Marketplace-to-Partner-Central connection.
- Get your product code from AWS Marketplace Management Portal. This is the identifier that drives all three PRM implementation methods.
- Choose your implementation method based on how your product is architected. AMI/SageMaker products on Marketplace get AWS Marketplace Metering for free. SaaS products typically use User Agent String or Resource Tagging depending on whether your product makes direct API calls or provisions AWS resources.
- Implement and verify. Revenue data appears the month after implementation. Confirm the tracking is active in the dashboard before the July 31 deadline.
If you are a Grnmrk managed operations client with a Marketplace listing, this is on our radar. Reach out if you want to walk through implementation status and confirm what needs to be done before the deadline.
The Bottom Line
The Attributed Revenue Dashboard is one part of a larger shift in how AWS defines and measures partner value. The manual, self-reported world of partner impact is being replaced by automated measurement tied directly to AWS consumption. Partners who get ahead of this come into every PDM conversation, every funding application, and every tier review with data that speaks for them.
Partners who do not implement PRM by July 31, 2026 lose APFP funding access. Partners who do not implement it by January 1, 2027 lose access to co-sell incentives and funding benefits that depend on revenue attribution. The window to do this before it becomes urgent is closing.
If you want help working through PRM implementation or understanding how it connects to your broader AWS partner program, reach out to Grnmrk Group. This is exactly the kind of operational work we manage for clients who want their AWS relationship to reflect what they are doing.