> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/sales/clazar.md).

# Clazar

Connect Clazar to Google Sheets, BigQuery, or AI tools via Coupler.io. Pull buyers, contracts, listings, and marketplace analytics from AWS, Azure, and GCP.

Clazar is a cloud marketplace management platform that helps software vendors list, sell, and co-sell on AWS, Azure, and Google Cloud marketplaces. It centralizes your listings, contracts, buyers, and marketplace analytics in one place.

Connecting Clazar to Coupler.io lets you pull all that data into your reporting and analytics tools automatically — no manual exports needed.

**Why connect Clazar to Coupler.io?**

* Track revenue, disbursements, and orders across AWS, Azure, and GCP marketplaces in a single destination
* Monitor buyers, contracts, and private offers alongside co-sell opportunity pipelines
* Send marketplace data to Google Sheets, BigQuery, Looker Studio, or AI tools like ChatGPT or Gemini for deeper analysis
* Combine data from multiple entities using Append or Join transformations to build cross-marketplace reports

## Prerequisites

* An active Clazar account with API access enabled
* A Clazar API key (available from your Clazar account settings)

## Quick start

{% hint style="success" %}
Start with the **Analytics AWS Marketplace Revenue** or **Analytics Azure Marketplace Revenue** entity if your goal is revenue reporting — these give you the most immediately actionable financial data.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** From your Coupler.io dashboard, click **Add data flow** and select Clazar as your source.
{% endstep %}

{% step %}
**Enter your Clazar API key.** In the source settings, paste your API key into the authentication field. You can find this in your Clazar account under Settings > API.
{% endstep %}

{% step %}
**Select an entity.** Choose the data you want to pull — for example, Buyers, Contracts, Opportunities, or one of the marketplace analytics streams.
{% endstep %}

{% step %}
**Choose a destination.** Select where you want the data to land — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like Claude or Perplexity.
{% endstep %}

{% step %}
**Run the data flow.** Click **Run** to execute a manual sync and confirm your data is loading correctly.
{% endstep %}
{% endstepper %}

## Available entities

| Entity                                      | Description                                                                   |
| ------------------------------------------- | ----------------------------------------------------------------------------- |
| Buyers                                      | Companies that have shown interest in or purchased your marketplace offerings |
| Listings                                    | Your products and services published on marketplace platforms                 |
| Contracts                                   | Legal agreements with marketplace partners and customers                      |
| Opportunities                               | Potential deals across marketplace channels                                   |
| Private offers                              | Custom pricing and terms for specific customers                               |
| Analytics: AWS disbursements                | Payment settlements from AWS Marketplace                                      |
| Analytics: AWS revenue                      | Revenue generated through AWS Marketplace                                     |
| Analytics: AWS co-sell opportunities        | Joint sales opportunities with AWS                                            |
| Analytics: Azure revenue                    | Revenue generated through Azure Marketplace                                   |
| Analytics: Azure customers                  | Customer profiles from Azure Marketplace                                      |
| Analytics: Azure orders                     | Purchase orders from Azure Marketplace                                        |
| Analytics: Azure metered usage              | Usage-based billing data from Azure Marketplace                               |
| Analytics: Azure co-sell opportunities      | Joint sales opportunities with Microsoft Azure                                |
| Analytics: GCP disbursements                | Payment settlements from Google Cloud Marketplace                             |
| Analytics: GCP disbursements summary        | Summarized GCP settlement data                                                |
| Analytics: GCP charges and usage            | Billing charges and usage from GCP Marketplace                                |
| Analytics: GCP daily insights               | Daily performance metrics from GCP Marketplace                                |
| Analytics: GCP incremental daily insights   | Daily incremental trends in GCP performance                                   |
| Analytics: GCP monthly insights             | Monthly performance metrics from GCP Marketplace                              |
| Analytics: GCP incremental monthly insights | Monthly incremental trends in GCP performance                                 |

## Clazar 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

{% tabs %}
{% tab title="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
  {% endtab %}

{% tab title="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
  {% endtab %}

{% tab title="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
  {% endtab %}
  {% endtabs %}

## 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

## Clazar common issues

### Connection issues

<details>

<summary>My API key is rejected during setup</summary>

Double-check that you're copying the full API key from Clazar without any leading or trailing spaces. API keys are case-sensitive. If the key still doesn't work, try regenerating it in Clazar under Settings > API and entering the new one in Coupler.io.

</details>

<details>

<summary>The data flow connects but returns no rows</summary>

Some Clazar analytics entities — especially GCP and Azure — only return data once transactions or activity have occurred on that marketplace. If you've never sold on a particular platform, the corresponding analytics entity will be empty. Try a different entity like Buyers or Opportunities to confirm the connection is working.

</details>

### Missing data

<details>

<summary>GCP incremental insights are missing historical data</summary>

Incremental entities (GCP daily incremental insights, GCP monthly incremental insights) are designed to return changes since the last sync, not full historical datasets. If you need historical data, use the non-incremental GCP daily insights or GCP monthly insights entities instead.

</details>

<details>

<summary>Azure metered usage data is empty</summary>

The Azure metered usage entity only contains data if your Azure Marketplace listing uses consumption-based (metered) billing. If your listing uses a flat-rate or subscription model, this entity will always be empty.

</details>

<details>

<summary>Co-sell opportunities are missing deals I can see in Clazar</summary>

Co-sell opportunity entities (AWS and Azure) reflect only partner-referred deals, not all opportunities. Standard opportunities that originated outside a co-sell motion won't appear here. Check the main Opportunities entity for a complete pipeline view.

</details>

### Permission errors

<details>

<summary>I get a permission error when pulling analytics entities</summary>

Analytics access in Clazar may require elevated API permissions. Check that your API key belongs to a user role with analytics access enabled. If you're unsure, ask your Clazar account admin to verify the permissions associated with your API key.

</details>

### Data discrepancies

<details>

<summary>AWS revenue and disbursements don't match</summary>

This is expected behavior. AWS Marketplace collects revenue from buyers and disburses it to vendors on a separate schedule, typically with a delay of 30–60 days. Revenue records the transaction date; disbursements record when funds were paid out. These will rarely match within the same period.

</details>

<details>

<summary>GCP daily and monthly insights show different totals for the same period</summary>

GCP computes daily and monthly insights independently, and rounding or attribution differences can produce small variances. For financial reporting, use monthly insights as the authoritative source. Daily insights are better suited to trend monitoring.

</details>

### Rate limits

<details>

<summary>My data flow fails with a rate limit error</summary>

Clazar's API has rate limits that apply per key. If you're running multiple data flows using the same API key simultaneously, you may hit these limits. Stagger your data flow schedules by at least a few minutes between runs, or reduce the number of entities in a single data flow.

</details>

## Clazar FAQ

<details>

<summary>Can I combine AWS, Azure, and GCP revenue into one report?</summary>

Yes. Add all three revenue entities (AWS marketplace revenue, Azure marketplace revenue, and GCP charges and usage) as sources in a single data flow, then use the **Append** transformation to merge them into one table. Make sure the field names align — you may need to rename a few columns in the transformation step.

</details>

<details>

<summary>What's the difference between opportunities and co-sell opportunities?</summary>

The standard **Opportunities** entity covers all potential deals across your marketplace channels, regardless of how they originated. The **co-sell opportunities** entities (available for both AWS and Azure) contain only deals that involve a cloud provider's sales team — where AWS or Microsoft is actively co-selling with you. Keep both in your pipeline reporting to get the full picture.

</details>

<details>

<summary>How do private offers relate to contracts?</summary>

A **private offer** is a custom pricing proposal sent to a specific buyer. A **contract** is the executed agreement after the buyer accepts. Not all private offers become contracts. Joining these two entities lets you calculate private offer acceptance rates.

</details>

<details>

<summary>Can I send Clazar data to an AI tool for analysis?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. This is particularly useful for feeding GCP insights or cross-cloud revenue data to an AI tool to identify trends, anomalies, or forecasting signals without building a dashboard.

</details>

<details>

<summary>Why does my GCP disbursements summary show different totals than the detailed disbursements entity?</summary>

The disbursements summary entity aggregates and rounds values for high-level reporting. The detailed disbursements entity contains individual transaction records. Use the detailed entity when you need precision (e.g., finance reconciliation) and the summary for executive-level dashboards.

</details>

<details>

<summary>How many entities can I add to a single data flow?</summary>

There's no hard cap, but adding too many entities — especially large analytics streams — can slow down your runs. A good rule of thumb is to group related entities (e.g., all AWS analytics together) and keep each data flow focused on a specific reporting use case.

</details>

<details>

<summary>Do I need a separate API key for each marketplace (AWS, Azure, GCP)?</summary>

No. Clazar uses a single API key that covers all the marketplaces you've connected within your Clazar account. One key in Coupler.io gives you access to all available entities across AWS, Azure, and GCP.

</details>

{% hint style="info" %}
For a full list of available entities and fields, see the [Data Overview](#clazar-data-overview) page. If you're running into connection or sync errors, check [Common Issues](#clazar-common-issues).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coupler.io/sources/category/sales/clazar.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.