Keypup

Field ID: <code>aggregation_level</code>

Description: What the measurement aggregates over. Possible values are:

<code>USER</code> the measurement covers one actor.

<code>REPOSITORY</code> the measurement covers one repository.

<code>ORGANIZATION</code> the measurement covers the whole account.

- <code>USER</code> the measurement covers one actor.
- <code>REPOSITORY</code> the measurement covers one repository.
- <code>ORGANIZATION</code> the measurement covers the whole account.

Note: Aggregation levels are not interchangeable and must not be aggregated together. See <a href="https://docs.keypup.io/en/articles/16988566-definition-ai-usage-record-structure">Definition: AI Usage Record Structure</a>.

Transformation logic: Assigned from the provider report a record comes from.

The <code>Aggregation level</code> field is one of the two fields that must appear in almost every AI usage filter. It says whose activity a record counts.

Always filter on one value: Mixing levels adds a day's per-user counts to that same day's organization total. A report that does this roughly doubles every figure.

Per-developer reporting: Filter to <code>USER</code>. This is the level that carries an actor, and the one from which active developer counts are derived.

Repository impact: Filter to <code>REPOSITORY</code>. Only GitHub Copilot publishes this level, and it carries pull request measures only - no tokens, no actor, no model.

Organization totals: Filter to <code>ORGANIZATION</code>. These are published by the provider rather than summed from user records, so they will not exactly match the sum of the <code>USER</code> records for the same day.

Beware overlapping organizations: Copilot attributes organization usage by membership, so a person in several organizations is counted in each. Do not sum organization records across several Copilot integrations.

- Always filter on one value: Mixing levels adds a day's per-user counts to that same day's organization total. A report that does this roughly doubles every figure.
- Per-developer reporting: Filter to <code>USER</code>. This is the level that carries an actor, and the one from which active developer counts are derived.
- Repository impact: Filter to <code>REPOSITORY</code>. Only GitHub Copilot publishes this level, and it carries pull request measures only - no tokens, no actor, no model.
- Organization totals: Filter to <code>ORGANIZATION</code>. These are published by the provider rather than summed from user records, so they will not exactly match the sum of the <code>USER</code> records for the same day.
- Beware overlapping organizations: Copilot attributes organization usage by membership, so a person in several organizations is counted in each. Do not sum organization records across several Copilot integrations.

AI Usage > Aggregation level

No tickets or conversations found

Try selecting a different creation date range.

Tickets and conversations you've started through the messenger will appear here.

No tickets or conversations created by you

Try using different keywords or checking for typos.

Try selecting a different update date range.

Find answers and get help from Intercom Support and Community Experts

Conversations you've started through the messenger will appear here.

No conversations created by you

No conversations found

AI title

Title

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Empty Help Center

Uh oh. That page doesn’t exist.

Home

Search results

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

No tickets created by you

No tickets found

Conversations and tickets in {topic}

Conversations and tickets in {topic} // {subtopic}

Volume, creators and topics for your company.

Insights

Top creators

AI topics

Track the progress of all tickets and conversations related to your company.

Customer Portal.

Track the progress of all tickets related to your company.

Tickets portal.

{assigneeName} needs more information from you

Tickets

No access to tickets portal

Search

Skip the search. Describe what you’re trying to do and get a grounded answer.

Browse articles and guides in this topic.

Create your workspace and invite the people you work with.

Set up your account

Build your first workflow and watch it run end to end.

Ship something

Connect the tools your team already uses to bring data in.

Connect your stack

A quick lap of the product so you know where everything lives.

{appName} in 60 seconds

This prototype demo is aware that you are reading “{title}”. It can point you back to the current article, but a production article-aware Fin contract is still follow-up work.

Prototype article-aware answer

Because you already asked about invitations, this prototype demo can add the follow-up: use the role selector before sending each invite to limit access to the teammate responsibilities.

Prototype role-limiting follow-up

This prototype demo suggests starting with your workspace profile, inviting the team members who need access, and then connecting the integrations you use.

Prototype getting-started answer

In this prototype demo, integrations are configured from workspace settings. Choose the integration, connect the account, and review the enabled permissions.

Prototype integrations answer

In this prototype demo, invite teammates from workspace settings, then choose the access each teammate needs before sending the invitation.

Prototype invite-team answer

This prototype demo does not have a scripted answer for that question yet. Try asking how to invite your team or open a source article. No production Fin API was called.

Prototype answer unavailable

I’ve got this page open. Ask me anything about it and I’ll answer from the docs.

GitHub Copilot	`USER`, `REPOSITORY` and `ORGANIZATION` - GitHub publishes a separate report at each level
Anthropic Claude (coming soon)	`USER` for Claude Code usage; `ORGANIZATION` for API traffic that carries no account
Cursor (coming soon)	`USER` only
OpenAI Platform (coming soon)	`USER` where the API key belongs to a person; `ORGANIZATION` otherwise
OpenAI Codex (coming soon)	`USER` for per-user rows; `ORGANIZATION` for workspace rows and code review

AI Usage > Aggregation level

App Mapping

Reporting Use Cases