For the complete documentation index, see llms.txt. This page is also available as Markdown.

FAQ

Can I combine AWS, Azure, and GCP revenue into one report?

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.

What's the difference between opportunities and co-sell opportunities?

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.

How do private offers relate to contracts?

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.

Can I send Clazar data to an AI tool for analysis?

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.

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

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.

How many entities can I add to a single data flow?

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.

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

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.

For a full list of available entities and fields, see the Data Overview page. If you're running into connection or sync errors, check Common Issues.

Last updated

Was this helpful?