Data Overview

Clazar surfaces data across two main categories: operational records (buyers, listings, contracts, opportunities, private offers) and marketplace analytics broken down by cloud platform — AWS, Azure, and GCP.

Entities and report types

Entity	Type	Best used for
Buyers	Operational	CRM-style buyer tracking
Listings	Operational	Marketplace product management
Contracts	Operational	Contract lifecycle tracking
Opportunities	Operational	Sales pipeline reporting
Private offers	Operational	Custom deal tracking
AWS revenue	Analytics	Financial reporting
AWS disbursements	Analytics	Cash flow tracking
AWS co-sell opportunities	Analytics	Partner pipeline reporting
Azure revenue	Analytics	Financial reporting
Azure customers	Analytics	Customer analytics
Azure orders	Analytics	Transaction reporting
Azure metered usage	Analytics	Usage-based billing analysis
Azure co-sell opportunities	Analytics	Partner pipeline reporting
GCP disbursements	Analytics	Payment settlement tracking
GCP disbursements summary	Analytics	High-level financial summaries
GCP charges and usage	Analytics	Billing and consumption analysis
GCP daily insights	Analytics	Day-over-day performance
GCP incremental daily insights	Analytics	Daily trend analysis
GCP monthly insights	Analytics	Month-over-month performance
GCP incremental monthly insights	Analytics	Monthly trend analysis

Available data fields

Buyers

Field	Description
Buyer ID	Unique identifier for the buyer
Company name	Buyer's organization name
Marketplace	Which cloud marketplace the buyer came from
Status	Current relationship status
Created date	When the buyer record was created

Listings

Field	Description
Listing ID	Unique identifier for the listing
Product name	Name of the listed product or service
Marketplace	AWS, Azure, or GCP
Status	Active, draft, or inactive
Listing type	SaaS, AMI, container, etc.

Contracts

Field	Description
Contract ID	Unique identifier
Buyer reference	Associated buyer
Start date	Contract start date
End date	Contract end or renewal date
Value	Contract value
Status	Active, expired, or pending

Opportunities

Field	Description
Opportunity ID	Unique identifier
Stage	Current pipeline stage
Source marketplace	Channel where opportunity originated
Expected value	Projected deal value
Close date	Anticipated close date

Marketplace analytics — revenue and disbursements

Field	Description
Period	Reporting period (month, day)
Gross revenue	Total revenue before fees
Net revenue	Revenue after marketplace fees
Disbursement amount	Amount paid out
Currency	Transaction currency
Marketplace	AWS, Azure, or GCP

Azure marketplace orders and metered usage

Field	Description
Order ID	Unique order identifier
Customer ID	Linked customer
Quantity	Units ordered
Usage quantity	Metered consumption amount
Billing period	When usage was billed
Meter ID	Meter dimension identifier

GCP insights (daily and monthly)

Field	Description
Date	Reporting date
Active customers	Count of active subscribers
New customers	New sign-ups in period
Churned customers	Cancelled subscriptions
MRR	Monthly recurring revenue

Common metric combinations

• Revenue vs. disbursements: Join AWS revenue and AWS disbursements to reconcile earnings with payouts
• Pipeline to closed: Join opportunities with contracts to track conversion rates from deal stage to signed contract
• Cross-cloud revenue: Use Append to combine AWS, Azure, and GCP revenue entities into a single unified revenue table
• Buyer to contract: Join buyers with contracts to understand which buyer segments generate the most contract value

Use cases by role

Finance

• Pull AWS and GCP disbursements into Google Sheets or Excel to reconcile marketplace payouts against internal records
• Append Azure and AWS revenue entities to build a single cross-cloud P&L view
• Use GCP monthly insights to track MRR trends over time in Looker Studio

Sales ops

• Export opportunities and contracts into BigQuery to analyze pipeline conversion rates by marketplace channel
• Monitor private offers alongside contracts to see how custom pricing affects deal close rates
• Use co-sell opportunity entities (AWS and Azure) to report on partner-sourced pipeline performance

Growth & strategy

• Feed GCP daily insights and incremental monthly insights into ChatGPT or Gemini to surface growth trends and anomalies
• Combine buyer data with Azure customer analytics to understand acquisition patterns across cloud channels
• Track listing status across marketplaces to identify which products drive the most contract activity

Platform-specific notes

• GCP has two insight cadences — daily and monthly — each with an incremental variant. Use incremental entities for ongoing refreshes to avoid reprocessing the full dataset
• Azure includes a metered usage entity that is only relevant if your Azure listing uses consumption-based billing
• Co-sell opportunity entities are separate from standard opportunities and reflect partner-referred deals specifically
• AWS disbursements and revenue are separate entities and may not match on a 1:1 basis due to marketplace fee timing differences