As you review your analytics, you may see an entity value of
(not set) displayed, including the
parenthesis, for your API Proxies, Product,
Developer, Developer Apps and other dimensions. This
may or may not be an issue.
Oftentimes, (not set) means Apigee doesn't have enough information. For
example, developer apps are associated with developers, API products, and by extension API
proxies. When a developer app makes an API call with an API key or OAuth token, all those
associations are made in analytics. However, if an API proxy is open and doesn't require an API
key, Apigee has no way of knowing if there is a developer, developer app, or product associated
with the API call.
Other times, (not set) could mean doesn't apply. For example, the "Flow
Name on Error" dimension shows the named API proxy flows where errors occurred. In that case, all
non-error calls will be shown as (not set) because there was no error in the
calls.
The following table summarizes possible explanations for why you are seeing
(not set) on a particular
dimensions.
Dimension
Possible Meaning of "(not set)"
API Proxy
A call to an API proxy reached the Apigee routers, but was malformed,
never reached the proxy, and the message processor returned a 404 status code with a
classification error. This means that there are some callers that are making malformed
calls.
API Product
Not all of your API proxies and developer apps are using products. For information about how to get your API proxies and developer apps to use products, see
Managing API products.
Some of your traffic is being generated by unregistered developers. This
traffic may originate with an internal-use or public API. For information about how
to register your app developers, see
Registering app developers.
Developer Apps
Some of your traffic is being generated by unregistered apps. This traffic
may originate with an internal-use or public API. For information about how to register your developers' apps, see
Registering apps and managing API keys.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-26 UTC."],[[["\u003cp\u003eThis content is relevant to both Apigee and Apigee hybrid users, providing insights into analytics and the "(not set)" entity value.\u003c/p\u003e\n"],["\u003cp\u003eThe "(not set)" entity value in Apigee analytics often means that Apigee lacks sufficient information to associate the API call with specific entities like developers or apps.\u003c/p\u003e\n"],["\u003cp\u003eIn some contexts, "(not set)" in analytics may signify that a specific dimension, such as "Flow Name on Error," is not applicable to a given API call if there was no error.\u003c/p\u003e\n"],["\u003cp\u003eThe presence of "(not set)" for dimensions like "API Proxy," "API Product," "Developer," and "Developer Apps" may indicate malformed calls or the absence of proper associations, such as unregistered developers or apps.\u003c/p\u003e\n"],["\u003cp\u003eThe dimensions displaying the "(not set)" entity value can potentially be resolved by registering developers and their apps, as well as using API products.\u003c/p\u003e\n"]]],[],null,["*This page\napplies to **Apigee** and **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\nAs you review your analytics, you may see an entity value of\n(not set) displayed, including the\nparenthesis, for your **API Proxies** , **Product** ,\n**Developer** , **Developer Apps** and other dimensions. This\nmay or may not be an issue.\n\nOftentimes, `(not set)` means **Apigee doesn't have enough information**. For\nexample, developer apps are associated with developers, API products, and by extension API\nproxies. When a developer app makes an API call with an API key or OAuth token, all those\nassociations are made in analytics. However, if an API proxy is open and doesn't require an API\nkey, Apigee has no way of knowing if there is a developer, developer app, or product associated\nwith the API call.\n\nOther times, `(not set)` could mean **doesn't apply** . For example, the \"Flow\nName on Error\" dimension shows the named API proxy flows where errors occurred. In that case, all\nnon-error calls will be shown as `(not set)` because there was no error in the\ncalls.\n\nThe following table summarizes possible explanations for why you are seeing\n(not set) on a particular\ndimensions.\n\n| Dimension | Possible Meaning of \"(not set)\" |\n|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| API Proxy | A call to an API proxy reached the Apigee routers, but was malformed, never reached the proxy, and the message processor returned a 404 status code with a classification error. This means that there are some callers that are making malformed calls. |\n| API Product | Not all of your API proxies and developer apps are using products. For information about how to get your API proxies and developer apps to use products, see [Managing API products](/apigee/docs/api-platform/publish/create-api-products). |\n| AppGroup | Not all of your API proxies and developer apps are using AppGroups. For information on AppGroups, see [Using AppGroups to organize app ownership](/apigee/docs/api-platform/publish/organizing-client-app-ownership#using-appgroups-to-organize-app-ownership). |\n| AppGroup app | Not all of your API proxies and developer apps are using AppGroups. For information on AppGroups, see [Using AppGroups to organize app ownership](/apigee/docs/api-platform/publish/organizing-client-app-ownership#using-appgroups-to-organize-app-ownership). |\n| Developer | Some of your traffic is being generated by unregistered developers. This traffic may originate with an internal-use or public API. For information about how to register your app developers, see [Registering app developers](/apigee/docs/api-platform/publish/adding-developers-your-api-product). |\n| Developer Apps | Some of your traffic is being generated by unregistered apps. This traffic may originate with an internal-use or public API. For information about how to register your developers' apps, see [Registering apps and managing API keys](/apigee/docs/api-platform/publish/creating-apps-surface-your-api). |"]]
