AWS Partner Revenue Measurement (PRM)

No PRM, no more AWS funding.

Q: What is AWS Partner Revenue Measurement (PRM)?

PRM is an AWS capability that attributes AWS service consumption to the AWS Marketplace partner product that drove it. Partners mark resources and API calls with their product code through resource tags, a user agent string or Marketplace metering. AWS reports the result monthly in the Attributed Revenue Dashboard in Partner Central.

Q: Is partner revenue management the same as Partner Revenue Measurement?

Yes, in the AWS context. Both terms refer to the same capability and the same acronym. AWS documentation uses Partner Revenue Measurement.

Q: Who needs to implement PRM?

Any AWS Partner with a product listed on AWS Marketplace (SaaS, AMI, ML or Professional Services) whose product uses supported AWS services, and who wants AWS funding benefits or program incentives.

Q: Is PRM attribution retroactive?

No. Attribution starts on the date the tag or user agent string is applied. Backfilling tags on existing resources only counts consumption from that day forward.

Q: Can AWS or the partner see revenue for an individual customer?

No. The Attributed Revenue Dashboard is aggregated by product, AWS service and billing month, and only shows data once a product meets a minimum number of customer accounts in that month. Deal-level figures from Revenue Attribution IDs stay internal to AWS.

Q: Should I use resource tagging or the user agent string?

Use tagging for static, long-running resources, because attribution continues while the tag is present. Use the user agent string when your product makes regular AWS API calls or the customer restricts tags, noting that each resource needs at least one control plane call per month. Many products use both.

Q: What is a Revenue Attribution ID?

An RA ID, formatted ra- plus 13 characters, links specific Marketplace offers and launched ACE opportunities to your product so AWS can attribute revenue at deal level. It sits on top of product-level PRM. Multi-tenant SaaS products enter a cost allocation percentage per customer per billing month, editable for the prior month until the 7th.

Q: How do I validate my PRM implementation?

Check that your user agent string appears in the userAgent field in AWS CloudTrail, confirm tags on production resources, then send deployment details to your AWS partner management team or APN Support. Revenue for a billing month appears in the Attributed Revenue Dashboard about 45 days after that month ends.

Q: Does OPTIMAZE write PRM tags to my AWS accounts?

No. Tagging outside Terraform, CloudFormation or CDK causes drift, and the next deploy can remove the tag. OPTIMAZE finds the resources your product drives that are missing a PRM tag and returns the change as code. Your team applies it through your own pipeline.

AWS now measures each partner by the AWS consumption its product generates, through Partner Revenue Measurement. Eligibility for APN funding benefits depends on PRM compliance, and that measurement also feeds program eligibility. If your product is not instrumented, AWS cannot see your contribution, and it does not backfill the months you missed.

Get a free PRM readiness check

See what partners need to do

For every AWS Marketplace seller: SaaS, AMI, ML and Professional Services listings.

Input

Your Marketplace product

Identified by its product code

Signal

Tag, user agent or metering

Marks the AWS usage your product drives

Measurement

Attributed AWS revenue

By product, service and billing month

Evaluation

Program eligibility

Funding requests and incentives

Outcome

AWS funding and co-sell support

Earned on measured contribution

What PRM is

Key dates

What to do

Where attribution leaks

How OPTIMAZE helps

Manual versus OPTIMAZE

FAQ

Definition

What is AWS Partner Revenue Measurement?

AWS Partner Revenue Measurement (PRM) is the AWS capability that attributes AWS service consumption to the partner product that drove it. It works across partner-owned and customer-owned AWS accounts. Some teams call it partner revenue management. AWS calls it measurement, and that is the term used in Partner Central.

A partner marks the AWS resources and API calls its product creates with its AWS Marketplace product code. AWS reads those markers, totals the consumption each month, and reports it back in the Attributed Revenue Dashboard in Partner Central, broken down by product, AWS service and billing period.

AWS launched PRM on January 30, 2026. It is generally available in all commercial AWS Regions.

Data is aggregated. AWS does not show partners revenue for an individual customer, and it only reports a product’s figures once a minimum number of customer accounts is reached in the month.

Why it matters now

Eligibility for APN funding benefits depends on PRM compliance.

The account linked to Partner Central is the account AWS checks for PRM compliance, and that compliance determines whether you are eligible for APN funding benefits. PRM itself has no fixed tagging deadline, but programs such as Partner Path advancement and ISV Accelerate can set their own PRM requirements.

Done

January 30, 2026

PRM launched

Generally available in all commercial AWS Regions.

Source: AWS What’s New, January 30, 2026

In effect

September 1, 2026

More services counted

Attribution started for AWS Supply Chain, Amazon GameLift Streams, AWS RTB Fabric and certain Amazon SES features.

Source: AWS PRM onboarding guide

Every month

Your primary account

APN funding benefits depend on PRM

PRM compliance on the AWS account linked to Partner Central determines eligibility for APN funding benefits.

Source: AWS PRM onboarding guide

Attribution is not retroactive

AWS attributes consumption from the date a tag or user agent string is applied. Tagging existing resources today does not recover last quarter. Every month without instrumentation is contribution AWS will never count.

What partners need to do

Six steps to PRM compliance.

This is the sequence in the AWS PRM onboarding guide, in plain terms. Steps 1 and 2 are administrative. Steps 3 to 5 are engineering. Step 6 is the one most partners skip.

Meet the prerequisites

Link your AWS account to AWS Partner Central. This becomes the primary account for all APN activity, the account checked for PRM compliance, and the account billed the annual APN fee. You also need a live AWS Marketplace listing (SaaS, AMI, ML or Professional Services), a product that uses at least one supported AWS service, and Cost Explorer enabled.

Watch for

Several Marketplace seller accounts? Create one primary account and connect the rest through Subsidiary Account Connections after migrating to the new Partner Central experience.

Find your product code

In the AWS Marketplace Management Portal, open Products, select the product and read the Product Summary. The product code is a 25 character string such as 5ugbbrmu7ud3u5hsipfzug61p.

Watch for

Use the product code, not the product ID or the UUID-format ID. The wrong identifier attributes nothing.

Choose a method per workload

AWS offers three methods: Marketplace metering (automatic for AMI and ML products), resource tagging, and a user agent string on API and CLI calls. They can be combined. The right choice depends on where your product runs.

Watch for

Instrument every AWS service your product touches. AWS intends to support all services over time.

Implement through infrastructure as code

Apply tags at the CloudFormation stack, CDK app or Terraform provider level, and set the user agent string in SDK configuration or provider_meta. Tag only resources your product directly uses or influences, and only production workloads count.

Watch for

Tagging IaC-managed resources in the console causes drift, and the next deploy can remove the tag.

Validate with AWS

Confirm user agent strings appear in the userAgent field in AWS CloudTrail. Deploy to production, then send deployment details to your AWS partner management team or APN Support for validation. Attributed revenue appears in the Attributed Revenue Dashboard in Partner Central about 45 days after the billing month ends. There is no real-time check.

Watch for

Below the minimum number of customer accounts in a month, the dashboard shows no data for that product.

Add deal-level attribution and keep it current

Create Revenue Attribution IDs (RA IDs) in Partner Central under Sell, Revenue attribution, to link Marketplace offers and launched ACE opportunities to your product. Multi-tenant SaaS products must enter a cost allocation percentage per customer and billing month. Then monitor coverage every month.

Watch for

Last month’s allocations lock on the 7th of the current month. Historical attribution is not recalculated.

Where attribution leaks

Most PRM gaps are silent.

Nothing errors when attribution stops. AWS processes attributed revenue 17 days after each month ends, so a gap that starts in October shows up in mid-December at the earliest.

Redeploys from old modules

A template without the tag block replaces a tagged resource with an untagged one. Attribution stops with no warning.

Console tags on IaC resources

Tags added by hand drift from the code, and the next apply removes them.

Quiet resources on user agent attribution

A resource with no qualifying API call in a month contributes nothing for that month.

AI workloads left out

Amazon Bedrock and SageMaker AI resources are often created outside the main templates and never tagged.

Wrong identifier or account

Product ID instead of product code, or a tag key carrying an account ID that is not the one linked to Partner Central.

Missed allocation deadline

Multi-tenant SaaS allocations not entered by the 7th are not recalculated later.

Manual versus OPTIMAZE

What PRM costs your team, to get compliant and to stay compliant.

Set the inputs to match your product. The calculator prices the internal effort to reach validated PRM compliance and keep it every month, against the OPTIMAZE annual fee plus the time your team still spends. Every assumption is published below.

AWS accounts your product runs in20

Partner and customer accounts combined. Drives discovery, coordination and validation effort.

Where your product runsBoth

Customer accounts add tag policy and permission work with every customer.

Infrastructure templates to instrument10

Terraform modules, CloudFormation stacks and CDK apps that create resources your product drives.

AWS services your product drives8

Each service needs its own check for tag support or a user agent string.

Multi-tenant SaaS with deal-level allocationYes

Shared infrastructure means a monthly cost allocation percentage per Revenue Attribution ID.

Offers and opportunities to allocate15

Marketplace offers and launched ACE opportunities linked to Revenue Attribution IDs.

Annual cloud spend under managementUp to $50M

The annual fee covers up to $50 million. Above that, OPTIMAZE uses custom pricing.

Period to compare1 year

Implementation, then monthly upkeep for every month in the period.

Manual

Your team implements PRM

Your engineers map resources, instrument every template, coordinate with customers and validate with AWS. Then they check coverage, tag new resources and enter allocations every month.

$69,910

Internal cost over 1 year

Hours to compliance347 hours

Upkeep after compliance28 hours a month

Total hours over the period686 hours

OPTIMAZE feeNone

Weeks to compliance, at half an engineer17 weeks

OPTIMAZE

OPTIMAZE implements PRM

OPTIMAZE maps the resources, generates the code and flags every gap each month. Your team reviews, merges and approves.

$14,090

Fee plus internal cost over 1 year

Hours to compliance16 hours

Upkeep after compliance2 hours a month

Total hours over the period40 hours

OPTIMAZE fee$9,999 a year

Weeks to compliance2 weeks

Your result is ready

Unlock the comparison

Enter your work email to see the manual and OPTIMAZE cost for your product. The method and every assumption stay open below either way.

By entering your email you agree that OPTIMAZE may contact you.

Typical result

Real results vary with the complexity of your environment and business. Typically, customers save up to 90 percent of the hours spent on attribution administration, financial analysis and tagging administration.

Observed with a customer

It took a software business with around $100 million in annual cloud spend two years and two engineers to build its attribution stack in house. OPTIMAZE rebuilt it in one month.

Method and assumptions

Implementation workstream	Manual hours	With OPTIMAZE
Prerequisites and method choice OPTIMAZE recommends the method per workload	24	6
Resource discovery and mapping Read from your existing OPTIMAZE attribution	100	2
Instrumentation in infrastructure as code Code is generated, your team reviews and merges	92	2
Customer account coordination OPTIMAZE prepares the change list for each account	40	0
Validation and AWS submission OPTIMAZE prepares the validation pack	28	4
Revenue Attribution ID allocation method Percentages come from measured usage	31	1
Engineering oversight Scales with the work for the manual route, fixed with OPTIMAZE	32	1
Total to compliance	347 hrs	16 hrs

Upkeep workstream	Manual hours a month	With OPTIMAZE
Monthly Revenue Attribution ID allocations Percentages are calculated from measured usage before the 7th. You submit them.	5.8	0.5
Coverage and drift checks OPTIMAZE flags untagged resources, lost tags and resources with no qualifying call	7	0.5
Tagging new resources and templates Fixes arrive as code for your pipeline	5	0.5
Customer account changes Prepared change list per new or changed customer account	2	0
Reconciliation against the Attributed Revenue Dashboard Expected attribution is already known, so only differences need review	6	0.25
Engineering oversight Scales with the work for the manual route, fixed with OPTIMAZE	2.6	0.25
Total a month	28 hrs	2 hrs

Scenario	Manual	With OPTIMAZE, fee included	Difference	Upkeep hours a month, manual against OPTIMAZE
SaaS in your own account 3 accounts, 3 templates, 4 services, no deal allocation	$22,000 (216 hrs)	$14,100 (40 hrs)	$7,900 saved	9.1 against 2
Mid-size 20 accounts, both patterns, 10 templates, 8 services, 15 allocations	$69,900 (686 hrs)	$14,100 (40 hrs)	$55,800 saved	28 against 2
Scaled 100 accounts, both patterns, 40 templates, 15 services, 60 allocations	$229,400 (2,219 hrs)	$14,100 (40 hrs)	$215,300 saved	90 against 2
Customer-deployed at scale 250 accounts, 60 templates, 20 services, 150 allocations	$530,500 (5,137 hrs)	$14,100 (40 hrs)	$516,400 saved	205 against 2

Role	Base salary	Fully loaded	Hourly rate
Cloud and platform engineer	$130,000	$182,000	$101.11
Senior software engineer	$140,000	$196,000	$108.89
Technical product or alliance manager	$140,000	$196,000	$108.89
FinOps practitioner	$100,000	$140,000	$77.78
Engineering manager	$185,000	$259,000	$143.89

How OPTIMAZE helps

Implement PRM once. Know it is still working, every day.

OPTIMAZE already reads your AWS billing data and resource metadata to attribute technology spend to products, features and customers. The same model shows which of your product-driven AWS consumption carries a PRM signal and which does not.

Coverage

PRM coverage by product and account

The share of your product-driven AWS spend that carries a valid PRM tag or user agent string, by AWS service, account and customer. Untagged resources are listed by spend, so the largest gaps get fixed first.

Drift

Alerts when attribution drops

Without a check of your own, a gap can go unseen for up to seven weeks: the rest of the month it started, plus the 17 days AWS takes to publish it. OPTIMAZE checks coverage continuously, so a resource that loses its tag after a redeploy shows up the same day, not next month.

Allocation

RA ID allocations from measured usage

For multi-tenant SaaS, AWS asks for a cost allocation percentage per customer each month. OPTIMAZE attributes shared infrastructure to customers, so the percentages come from usage rather than estimates, ready before the 7th. OPTIMAZE calculates them. You submit them.

Reconciliation

Your number next to AWS’s number

Compare the consumption your product should drive with what the Attributed Revenue Dashboard reports, and investigate the difference before the partner business review.

Economics

From attributed revenue to return

AWS sees the consumption you drive. OPTIMAZE adds what it costs you to drive it and the revenue you earn from each customer, so the case for co-sell, funding and strategic collaboration is built on volume and margin.

Implementation

Tagging fixes as code for your pipeline

For every untagged resource, OPTIMAZE returns the change in the tool that manages it: a Terraform default_tags block, a CloudFormation stack tag or a CDK Tags.of() line. Your team merges it through your own pipeline, so nothing drifts and nothing changes outside your review.