Skip to content
Knowledge Base

Criteo Error: "Criteo returned 429 Too Many Requests with a non-JSON body"

Last updated

If a report shows "Criteo returned 429 Too Many Requests with a non-JSON body," Criteo briefly turned away a request because too many arrived at once. Your Criteo connection and your data are fine: wait a few minutes, refresh, and use the steps below to keep it from coming back.

What It Looks Like

In Google Sheets, the refresh summary looks like this:

6 report(s) refreshed
The following reports had errors:
Criteo:J1: Criteo returned 429 Too Many Requests with a non-JSON body

The text before the error is where the failed report sits in your spreadsheet: Criteo is the sheet (tab) name and J1 is the report's starting cell. Only the reports listed under "The following reports had errors" did not load. You'll also find the same message in the Error column of the PMA Configuration tab.

The same message can appear on a Data Studio chart, in a Microsoft Excel report, or in an export that includes Criteo data. You may also see a shorter version that starts with "Criteo returned 429 Too Many Requests." The steps below apply to both.

Fix It Now

  1. Wait 2 to 3 minutes.
  2. Refresh the report again. In Google Sheets, open the Power My Analytics sidebar (Extensions > Power My Analytics > Open sidebar), click the three-dot menu next to the Criteo report, and choose Refresh. In Data Studio, reload the report page.
  3. If the report loads, you're done. Nothing was lost: the data simply wasn't fetched on that attempt.

Stop It from Coming Back

If you see this error more than once, Criteo is being asked for too much at the same moment. Pick whichever of these fits your setup:

  • Refresh Criteo reports one at a time instead of refreshing every report in the spreadsheet together.
  • Shorten the date range. A long date range can be sent to Criteo as several separate requests.
  • Stagger your scheduled refreshes so Criteo reports in different spreadsheets or dashboards don't run at the same time.

Important: Reconnecting your Criteo source, re-entering your Criteo credentials, or running a backfill won't fix this error. Your connection isn't the problem, and a backfill sends Criteo even more requests.

What Does "429 Too Many Requests" Mean?

Criteo caps how many reporting requests it accepts in a short period. Every Data Studio chart, spreadsheet report, and export that needs Criteo data sends its own request. When too many arrive together, Criteo answers with code 429 and no data.

Power My Analytics spaces out its requests to Criteo for each set of Criteo credentials to stay under that cap, and automatically tries a refused request again a few times before showing this error. That's also why large Criteo reports can take a little longer to load than reports from other connectors. The error appears when enough Criteo requests still land together, for example when several reports refresh at once.

What Does "with a Non-JSON Body" Mean?

Criteo's 429 reply doesn't come in the data format Power My Analytics normally reads (JSON), and the message notes that so our team can tell this error apart from other Criteo errors. It doesn't mean anything is wrong with your data.

Is This My Power My Analytics Plan Limit?

No. This limit belongs to Criteo. It is separate from the API and MCP request limits on your Power My Analytics plan, and changing your plan or adding capacity doesn't affect it.

I Saw a Different Message Before

Before September 24, 2026, the same situation showed the general message "We were unable to get live data for this component. Please try again in a few minutes." The steps in this article apply to both.

Still Need Help?

If the error appears on two refreshes in a row after you've spaced things out, submit a ticket and include:

  • The time the refresh ran, and your time zone
  • The name of the Criteo source and account in the report
  • A link to the spreadsheet or report

With those details, our team can look up exactly what Criteo reported for that request.

Related Articles