Question 1

What is AWS Partner Revenue Measurement (PRM)?

Accepted Answer

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.

Question 2

Is partner revenue management the same as Partner Revenue Measurement?

Accepted Answer

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

Question 3

Who needs to implement PRM?

Accepted Answer

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.

Question 4

How does PRM affect AWS program eligibility and funding?

Accepted Answer

Eligibility for APN funding benefits depends on PRM compliance. AWS checks compliance on your primary Partner Central account. PRM has no fixed tagging deadline of its own, but programs such as Partner Path advancement and ISV Accelerate can set PRM requirements and deadlines. Confirm the rules for your programs with your AWS Partner Development Manager.

Question 5

Is PRM attribution retroactive?

Accepted Answer

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.

Question 6

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

Accepted Answer

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.

Question 7

Should I use resource tagging or the user agent string?

Accepted Answer

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.

Question 8

What is a Revenue Attribution ID?

Accepted Answer

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.

Question 9

How do I validate my PRM implementation?

Accepted Answer

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.

Question 10

Does OPTIMAZE write PRM tags to my AWS accounts?

Accepted Answer

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.

Question 11

What does the OPTIMAZE PRM readiness check not do?

Accepted Answer

It is not an AWS validation. Only AWS validates PRM, through your partner management team or APN Support. It does not guarantee funding or program eligibility, because AWS decides those. It does not change your environment: OPTIMAZE reads your AWS data, returns tag fixes as code for your pipeline, and returns allocations as figures you submit. It does not reveal customer-level AWS revenue. AWS keeps that aggregated, and so do we.

Question 12

What does the OPTIMAZE PRM readiness check cost?

Accepted Answer

Nothing. It is a fixed-scope review that ends in a written report you keep.

Know the return on every feature

Cost, usage and revenue. One return per feature.

Cost

Cost

Cost

Usage

Usage

Usage

Revenue

Revenue

Revenue

Goals and budgets

Goals and budgets

Goals and budgets

Integrations

Integrations

Integrations

Ask the question. Atlas does the heavy lifting.

Slack

MCP

Decisions, answered

Feature margin

Pricing

Margin movement

Board reporting

Feature margin

Pricing

Margin movement

Board reporting

Feature margin

Pricing

Margin movement

Board reporting

Why OPTIMAZE

Works with the stack you already run

Works with the stack you already run

Works with the stack you already run

One number product and finance both trust

One number product and finance both trust

One number product and finance both trust

Fixed pricing, not a share of savings

Fixed pricing, not a share of savings

Fixed pricing, not a share of savings

Enterprise security and finance readiness

See what your own features return

Technology Capital Performance