---
title: HTTP Requests by Colo Groups to HTTP Requests by Adaptive Groups · Cloudflare Analytics docs
description: This guide shares considerations when migrating from the deprecated httpRequests1mByColoGroups and httpRequests1dByColoGroups GraphQL API nodes to the httpRequestsAdaptiveGroups GraphQL API node.
lastUpdated: 2024-09-11T11:09:20.000Z
source_url:
  html: https://8f4f2dac.preview.developers.cloudflare.com/analytics/graphql-api/migration-guides/graphql-api-analytics/index.md
  md: https://8f4f2dac.preview.developers.cloudflare.com/analytics/graphql-api/migration-guides/graphql-api-analytics/
---

This guide shares considerations when migrating from the deprecated `httpRequests1mByColoGroups` and `httpRequests1dByColoGroups` GraphQL API nodes to the `httpRequestsAdaptiveGroups` GraphQL API node.

For example, if you wanted to see which five data centers had the most number of requests, the total number of those requests, and the total amount of data transfer, in the past you used the `httpRequests1mByColoGroups` GraphQL API node as in the following example:

```graphql
{
    viewer {
        zones(filter: {zoneTag: $zoneTag}) {
            series: httpRequests1mByColoGroups(
                limit: 5,
                orderBy: [ sum_requests_DESC ],
                filter: {
                    datetime_geq: $start
                    datetime_lt: $end
                }
            ) {
                sum {
                    requests
                    bytes
                }
                dimensions {
                    coloCode
                }
            }
        }
    }
}
```

## `httpRequestsAdaptiveGroups` GraphQL API node

With the deprecation of the `httpRequests1mByColoGroups` and `httpRequests1dByColoGroups` GraphQL API nodes, use the `httpRequestsAdaptiveGroups` GraphQL API node to access the same data (`count`, `sum(edgeResponseBytes)`, and `visits`).

**Request**

```graphql
{
    viewer {
        zones(filter: {zoneTag: $zoneTag}) {
            series: httpRequestsAdaptiveGroups(
                limit: 5,
                orderBy: [ count_DESC ],
                filter: {
                    datetime_geq: $start
                    datetime_lt: $end
                    requestSource: 'eyeball'
                }
            ) {
                count
                avg {
                    sampleInterval
                }
                sum {
                    visits
                    edgeResponseBytes
                }
                dimensions {
                    coloCode
                }
            }
        }
    }
}
```

This query says:

* Given the indicated `zones`, `limit`, and `time range`.
* Fetch the total number of requests (as `count`), the total amount of data transfer (as `edgeResponseBytes` of `sum` object), and the total number of `visits` per data center.

A few points to note:

* Adding the `requestSource` filter for `eyeball` returns request, data transfer, and visit data about only the end users of your website.
* Instead of `requests`, the `httpRequestsAdaptiveGroups` node reports `count`, which indicates the number of requests per data center.
* To measure data transfer, use `sum(edgeResponseBytes)`. Note that in the old API this was called `bandwidth` even though it actually measured data transfer.
* `unique visitors per colocation` is not supported in `httpRequestsAdaptiveGroups`, but the `httpRequestsAdaptiveGroups` API does support `visits`. A visit is defined as a page view that originated from a different website or direct link. Cloudflare checks where the HTTP referer does not match the hostname. One visit can consist of multiple page views.
