> 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

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                                 |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
