Common Issues

Connection issues

Invalid API key or Secret key error

Double-check that you've entered both the API key and the Secret key correctly — these are two separate values in Amplitude's project settings. Go to Settings → Projects → [Your project] → General and copy each key carefully. Make sure there are no extra spaces before or after the keys when pasting.

Connected to the wrong Amplitude project

Each Amplitude project has its own API key and Secret key. If you're seeing unexpected data (or no data), verify that the credentials you used belong to the correct project. Check under Settings → Projects in Amplitude to confirm which project each key belongs to.

Missing data

No data returned for the Events entity

The most common cause is a start date that's too recent or a request time range that's too short to capture events. Try adjusting your start date further back using the date picker. Also check that the Amplitude project actually has event data recorded — verify in the Amplitude UI first.

Active users data is missing or incomplete when grouped by country

Grouping active users by country triggers a separate API call for each country. This can result in partial data or connection failures for projects with many countries. Try disabling Group by country in the advanced settings to pull total active user counts without the country breakdown.

Cohort size shows 0 or cohort is missing

Cohorts in Amplitude must be computed before they can be exported. If a cohort was recently created or hasn't been recalculated, it may appear empty. In Amplitude, trigger a manual recompute of the cohort, then re-run the data flow.

Permission errors

403 Forbidden or access denied error

The API credentials you're using may belong to a user or role without sufficient access to the Export API. Amplitude's Export API requires a project-level API key — organization-level keys won't work. Confirm that the key is a project API key from the correct project's settings page.

Data discrepancies

Event counts in Coupler.io don't match what I see in Amplitude charts

Amplitude charts apply filters, segmentation, and sometimes sampling that aren't reflected in raw Export API data. The Events entity in Coupler.io returns raw, unfiltered event records. Differences are expected — use the Events entity as your source of truth for raw counts, and apply filtering in your destination.

event_properties or user_properties look truncated or malformed

These fields contain nested JSON objects. Spreadsheet destinations like Google Sheets may truncate or display them as plain text strings. If you need to work with nested properties, export to BigQuery where JSON columns are fully supported, or use Coupler.io's transformation layer to extract specific property values.

Rate limits

Timeout errors when pulling Events data

Amplitude's Export API can time out when the requested time range is too large, especially for high-volume projects. Lower the request time range parameter (measured in hours) to break the export into smaller chunks. A value of 1–6 hours is recommended for projects with millions of daily events. See Amplitude's Export API documentation for more detail.