Contract properties on the Clazar Contract object in HubSpot
Last updated: October 12, 2026
Overview
Until now, the Clazar Contract object in HubSpot did not show who bought a contract, what it is worth or what the buyer entered at registration. That information was only available in Clazar. Clazar now adds 20 properties to the Clazar Contract object for AWS, Azure and GCP contracts, and fills them during its regular writebacks to HubSpot.
Value it drives
Revenue reporting in HubSpot: Total Contract Value, the five revenue properties, and Duration In Days are Number properties. You can sum, average, and filter on them in HubSpot reports and lists.
Buyer context on the contract record: The buyer's name, domain, marketplace account, plan, and registration answers are on the Clazar Contract record, next to your deal data.
Contract terms at a glance: The contract's cloud status, offer type, metering eligibility, duration, and a link to its EULA are on the Clazar Contract record.
Clazar Contract (clazar_contract):
Property label | Internal name | Type | What it contains |
|---|---|---|---|
Buyer Name |
| Single-line text | Name of the buyer's company. |
Buyer Domain |
| Single-line text | Website domain of the buyer's company. |
Buyer Account Id |
| Single-line text | The buyer's account ID in the cloud marketplace. |
External Org Id |
| Single-line text | The ID of the buyer's organization in your own product, when it is set on the contract in Clazar. |
Plan Id |
| Single-line text | ID of the plan the buyer purchased. |
Cloud Status |
| Single-line text | The contract's status, as the marketplace reports it. |
Cloud Offer Type |
| Single-line text | The offer type, as the marketplace reports it. For example, public or private. |
Metering Eligible |
| Single-line text | True when usage can be metered for the contract. Otherwise False. |
Total Contract Value |
| Number | Total subscription value of the contract. It does not include usage-based components. |
Currency Code |
| Single-line text | Currency of the contract's amounts. For example, USD. |
Gross Booking Value |
| Number | Value of all bookings created: Total Contract Value plus Usage Booking Value. |
Gross Billed Revenue |
| Number | The part of the Gross Booking Value that has been billed. |
Usage Booking Value |
| Number | Value from the usage-based (metered) parts of the contract. |
Net Disbursed Revenue |
| Number | Gross Billed Revenue minus marketplace listing fees and similar charges, paid out to your bank. |
Net Undisbursed Revenue |
| Number | Net revenue that has not been paid out yet. |
Duration In Days |
| Number | Length of the contract term, in days. |
Eula Url |
| Single-line text | A link to the contract's EULA. For AWS contracts, it is a Clazar link that does not expire. |
Purchaser Object Id |
| Single-line text | Microsoft Entra object ID of the user who purchased the subscription. Azure only. |
Beneficiary Object Id |
| Single-line text | Microsoft Entra object ID of the subscription's beneficiary. Azure only. |
Registration Details |
| Single-line text | The buyer's answers from your registration page, for the fields you have enabled. If a buyer registered more than once, it contains their latest answer for each field. |
How to get started
You need the Clazar HubSpot integration connected first. If it is not, follow HubSpot integration setup.
Turn on the writeback: This is turned on by Clazar, not from the Clazar app. Reach out to your Clazar support contact to get this enabled. Clazar then adds the 20 new properties to the Clazar Contract object in your HubSpot portal and turns on the writeback for your account. You don't need to update the app or change anything in HubSpot.
To learn more about the Clazar Contract object and the other Clazar objects in HubSpot, see Custom objects.
Things to note
Record view: New properties are not added to the record sidebar automatically. A HubSpot admin can add them with the gear icon on the About this record card, or with the record page's Customize option. You can always find them under View all properties.
Existing records: Existing contracts get the new values during the next regular writebacks. No action is needed in Clazar.
Empty properties: A property is left empty when the marketplace does not provide a value for that contract. For example, Purchaser Object Id and Beneficiary Object Id are only filled for Azure contracts.