This error means that some fields in your query cannot be requested together from the source API. Most often, dimensions are incompatible with each other. Some APIs do not publish a full compatibility map, so the error may not list all conflicting fields.
Typical error text
{"type":"NETWORK_EXCEPTION","message":"An invalid mapping has been set in your request field_1, field_2. Please change your fields or contact us on our live chat for more information.",
"Request ID":"<your-request-id>"}
TL;DR: Remove one dimension at a time until the query runs. Then add fields back one by one to find a compatible set.
Source APIs restrict which dimensions and metrics can be combined.
Not all APIs expose full compatibility rules, so that the exact conflicting fields may be missing from the error message.
The issue can vary by metric scope, date granularity (Day/Week/Month), and breakdowns (e.g., Country, Device, Campaign).
Start with the fields named in the error
If the error lists fields (e.g. device and date, remove one of them and re-run the request.
If no fields are listed, isolate the conflict
Remove one dimension at a time, re-run the query after each change.
Prioritize removing: geographic (Country/Region/City), device/platform, campaign/ad group, and date granularity (Month/Week/Day) dimensions.
Re-add fields gradually
Once the query works, add fields back one by one, re-running after each addition.
If it fails again, the last field added is likely incompatible in that combination.
Keep metric scope in mind.
Some metrics only support specific dimensions. If you recently changed metrics, test with a more straightforward metric first (e.g., Sessions/Impressions/Clicks).
Sometimes the platform UI shows a combination that the public API doesn’t return directly. If you believe the fields should work together, don't hesitate to get in touch with us and include:
Request ID from the error.
Connector/source (e.g., Meta Ads, Google Ads), your date range, and any filters used.
The complete list of selected dimensions & metrics.
A screenshot or a small data extract/CSV from the platform showing these fields combined successfully.
Where applicable: account/property IDs and the exact field labels you used.
With this info, we’ll check if the API can deliver the fields together or if Catchr can safely reconstruct the dataset for you.
Affected products
This guidance applies to all Catchr data fetchers: Looker Studio connector, Google Sheets add-on, Microsoft Excel add-in, and Power BI / Tableau queries.
