Common Issues

Connection issues

My API key is rejected during setup

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.

The data flow connects but returns no rows

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.

Missing data

GCP incremental insights are missing historical data

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.

Azure metered usage data is empty

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.

Co-sell opportunities are missing deals I can see in Clazar

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.

Permission errors

I get a permission error when pulling analytics entities

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.

Data discrepancies

AWS revenue and disbursements don't match

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.

GCP daily and monthly insights show different totals for the same period

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.

Rate limits

My data flow fails with a rate limit error

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.