Supermetrics Support Forum

Incompatible fields: IllegalDimensionMetricCombinationException

This article applies to this error message happening with the MailChimp connector for both Supermetrics Google Sheets and Data Studio:

Script error message: DS_USER: Incompatible fields:  IllegalDimensionMetricCombinationException (Supermetrics request ID: xxxxxx).
 Script error cause: USER
 Script error stacktrace:
  getData:119


The MailChimp connector is very finicky about what you can and can't use together. The date range, the campaign/list type, and the combination of metrics (both directly selected for your report data and those used in filters) all can have conflicting effects and lead to the llegalDimensionMetricCombinationException.

If you are consistently getting invalid combinations, try other list types for your query to see if they work. Some fields only work with campaigns, some only work with lists, or automations. If you have the wrong type selected or a combination of types, it can break the query. "No data" errors can also result if you are pulling a date range that is too long for some fields - some only work for current date, some won't work with the current date, some are only last 7 days or last 30 days.


If using Data Studio, make sure your query type matches the type of campaigns/lists you've selected. If your query type is for automations but you're pulling lists, that could cause issues. For example, this causes llegalDimensionMetricCombinationException errors for with some fields meant for automations.

Blue rectangle around 'all lists' with 'all automations' in the same selection.

As soon as the Select campaigns/lists: setting is changed to only pull "all automations", the error clears.

Start with one selected list/campaign/automation, and add one metric or dimension at a time to figure out which one doesn't work with the list-type you selected. Unfortunately, we don't have a comprehensive guide at this time of what doesn't work with each list type or field, so some experimentation will be necessary. If you try this for a while and still cannot get it to work, then please submit a private ticket outlining what list type(s) and what fields you are trying to pull that results in the error so that Support can investigate further.



Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.