Build · Create · Data & Research
Build a quarterly pricing-analytics metrics register
I get a quarterly pricing report object carrying all five metrics plus the eight-dimension segmentation, where ASP/median/discount-% recompute correctly from the deal rows I supplied.
You receive: A JSON object {quarter, metrics:{asp, medianSellingPrice, dealsClosed, unitPrice, discountPct}, segmentation:{byProductFamily, byPackage, byAddon, byGeo, bySalesSubteam, bySalesOwner, byClosedQuarter, byOther}, deals:[{amount, units, listPrice,...}]}.
Part of Set My Price
Opens soon
This objective is verified and ready. It opens soon, once sign-in and payments are live.
Deliverable interface
The exact vocabulary the automated check enforces: keys, tokens, entry points, and worked examples. Generated from the verification source.
{
"buyerParamKeys": [
"quarter",
"requiredSegmentations"
],
"checkNames": [
"format_parses",
"quarter_matches",
"deals_valid",
"metrics_present",
"asp_correct",
"median_correct",
"deals_count_correct",
"unitprice_correct",
"discount_correct",
"segmentation_present",
"segmentation_coverage"
],
"constants": {},
"deliverableLabel": "quarterly_pricing_analytics_register",
"documentKeys": [
"amount",
"asp",
"deals",
"dealsClosed",
"discountPct",
"listPrice",
"medianSellingPrice",
"metrics",
"quarter",
"segmentation",
"unitPrice",
"units"
],
"enumLiterals": [
[
"asp",
"medianSellingPrice",
"dealsClosed",
"unitPrice",
"discountPct"
]
],
"submission": "a JSON document (submitted as a string), validated as data; every check below must pass",
"tier": "doc-validator"
}Get early access to STUD the day it goes live.