---
title: >-
  Metaobject analytics queryable capability available in the Admin API - Shopify
  developer changelog
description: >-
  Shopify’s developer changelog documents all changes to Shopify’s platform.
  Find the latest news and learn about new platform opportunities.
source_url:
  html: >-
    https://shopify.dev/changelog/posts/metaobject-analytics-queryable-capability-available-in-the-admin-api
  md: >-
    https://shopify.dev/changelog/posts/metaobject-analytics-queryable-capability-available-in-the-admin-api.md
metadata:
  effectiveApiVersion: 2027-01
  affectedApi:
    - displayName: GraphQL Admin API
      handle: admin-graphql
  primaryTag:
    displayName: API
    handle: api
  secondaryTag:
    displayName: New
    handle: new
  indicatesActionRequired: false
  createdAt: '2026-10-09T10:37:26-04:00'
  postedAt: '2026-10-20T16:40:00-04:00'
  updatedAt: '2026-10-20T18:37:03-04:00'
  effectiveAt: '2027-01-01T12:00:00-05:00'
---

October 20, 2026

# Metaobject analytics queryable capability available in the Admin API

DateOctober 20, 2026

Version[2027-01](https://shopify.dev/changelog?api_version=2027-01)

FlagsNew

SurfacesAPI

Affected APIs[GraphQL Admin API](https://shopify.dev/changelog?api_type=admin-graphql)

Starting with GraphQL Admin API version `2027-01`, you can read and configure the `analyticsQueryable` capability on metaobject definitions. This applies to apps that create, update, or inspect metaobject definitions. No action is required unless you want your app to control whether a metaobject definition can be queried in analytics.

## What changed

The GraphQL Admin API now exposes the analytics queryable capability for metaobject definitions.

You can read `MetaobjectCapabilities.analyticsQueryable`, which includes:

* `eligible`: whether the metaobject definition can use the capability. A definition is eligible if at least one of its fields uses an analytics-compatible type.
* `enabled`: whether the capability is currently enabled.

You can also set the capability when you create or update a metaobject definition by using:

* `MetaobjectCapabilityCreateInput.analyticsQueryable`
* `MetaobjectCapabilityUpdateInput.analyticsQueryable`
* `MetaobjectCapabilityAnalyticsQueryableInput.enabled`

The `MetaobjectCapabilityType` enum now includes `ANALYTICS_QUERYABLE`, and `MetaobjectUserErrorCode` includes `CAPABILITY_NOT_ELIGIBLE` for definitions that can’t enable the capability.

## Who's affected

This change applies to apps that use GraphQL Admin API version `2027-01` or later to create, update, or inspect metaobject definitions.

Apps that use earlier versions don’t see the `analyticsQueryable` field, input, enum value, or error code. Existing apps don’t need to make changes unless they want to support analytics queryability for metaobject definitions.

## Why this matters

You can now determine whether a metaobject definition is eligible to be queried in analytics and enable that capability through the public GraphQL Admin API. This brings metaobject definitions in line with metafield definitions, and you get consistent control over which custom data types appear in analytics.

## What to do

No action is required.

If you want to use this capability:

1. Update your app to use GraphQL Admin API version `2027-01` or later.
2. Update your metaobject definition queries or mutations to include `analyticsQueryable`.

For example, to read a metaobject definition’s capabilities, include:

```graphql
capabilities {
  analyticsQueryable {
    eligible
    enabled
  }
}
```

When you create or update a metaobject definition, set `analyticsQueryable.enabled` in the capability input. Check `eligible` first, and handle `CAPABILITY_NOT_ELIGIBLE` in mutation user errors. Use this method to confirm whether a definition supports the capability and give clear feedback when it doesn't.

## Related docs

* [GraphQL Admin API reference](https://shopify.dev/docs/api/admin-graphql)
* [Metaobjects in Shopify apps](https://shopify.dev/docs/apps/build/custom-data/metaobjects)