Google added INSIGHTS_MISSING_FOR_DIMENSION to the Data Manager API error reasons in v1.7. The response should not be treated as a generic retryable outage. It means the requested insight is missing for a dimension in the current account, data, location, or request context.
Use this for WordPress lead and WooCommerce conversion pipelines that call Data Manager API diagnostics or insight services and need to distinguish missing coverage from authentication, quota, or malformed requests.
Quick answer
Store the request ID and exact dimension, verify the account and baseline inputs, then repeat with the smallest supported dimension set. If the dimension remains unavailable, mark that slice as not available and continue with supported diagnostics instead of retrying the same request indefinitely.
What to check first
- Capture the endpoint, API version, operating account, login account, request ID, dimension names, filters, baseline settings, location settings, date range, and full error details.
- Confirm the dimension is supported for the requested insight and destination, with exact enum spelling and no stale client-library mapping.
- Reduce the request to one known supported dimension and remove optional filters, then add one input at a time.
- Verify baseline data volume, account eligibility, location-auto-detection result, and whether privacy thresholds can suppress the requested slice.
- Classify the outcome as supported, temporarily unavailable, insufficient data, invalid scope, or permanently unsupported and expose that state to operators.
Diagnostic table
Use this table to keep the work practical. It connects the symptom to evidence and a verification step.
| Action | Evidence to collect | How to verify |
|---|
| Preserve the request context | Capture the endpoint, API version, operating account, login account, request ID, dimension names, filters, baseline settings, location settings, date range, and full error details. | The same request ID connects application logs to the API response. |
| Validate dimension support | Confirm the dimension is supported for the requested insight and destination, with exact enum spelling and no stale client-library mapping. | A minimal supported dimension succeeds or produces a different, explained error. |
| Reduce the request | Reduce the request to one known supported dimension and remove optional filters, then add one input at a time. | Unsupported slices do not block valid insight results. |
| Check data and baseline | Verify baseline data volume, account eligibility, location-auto-detection result, and whether privacy thresholds can suppress the requested slice. | Operators can distinguish no data, unsupported dimension, permission, quota, and temporary service failure. |
Why this usually happens
- A valid dimension can still lack enough underlying data for an insight.
- A destination or account type can support a different dimension set.
- Automatic baseline location detection can fail and remove expected coverage.
- Client code can retry an unavailable dimension as if it were a temporary transport error.
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
request_id: dm-insight-20260721-004
operating_account: accounts/123456789
insight: audience_overlap
dimensions: [region]
location_auto_detection_enabled: true
error_reason: INSIGHTS_MISSING_FOR_DIMENSION
fallback_dimension: country
Safe fix order
Do the work in a sequence that makes each result easy to prove. Stop if a step produces new evidence that changes the incident scope.
- Preserve the request context
- Validate dimension support
- Reduce the request
- Check data and baseline
- Return a clear fallback state
Decision rule
Retry only when the underlying data or service state can change. Do not retry an identical unsupported dimension. Return a typed unavailable result and keep supported dimensions flowing.
What to tell the client or owner
Share the API version, endpoint, account resource names, request ID, dimensions, filters, baseline and location settings, response details, minimal reproduction, fallback result, and retry classification without customer data.
Production verification checklist
- The same request ID connects application logs to the API response.
- A minimal supported dimension succeeds or produces a different, explained error.
- Unsupported slices do not block valid insight results.
- Operators can distinguish no data, unsupported dimension, permission, quota, and temporary service failure.
Mistakes to avoid
- Do not rename the error in logs so broadly that it loses the dimension context.
- Do not send customer identifiers while testing an insight configuration problem.
- Do not retry the identical request on a tight loop.
- Do not interpret unavailable insight as zero performance.
Questions teams ask during testing
Is INSIGHTS_MISSING_FOR_DIMENSION a permanent error?
Not always. Coverage can depend on dimension support, baseline data, account eligibility, location, and privacy thresholds. Diagnose those inputs before classifying it.
Should the pipeline fail the whole request?
Usually valid results should remain usable. Represent the missing dimension explicitly so reporting does not turn unavailable data into a zero value.
When HandL WP should help
HandL WP can trace Data Manager API diagnostic gaps from WordPress or CRM request construction through account scope, dimensions, baseline inputs, and operator reporting.
If this is active on a production site, fix Data Manager API insight errors.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
Helpful references