Overview

Partner App Analytics is a feature in iManage Admin Portal that provides marketplace and technology Partners with visibility into how their applications are being used across iManage Cloud customer environments. This feature lets Partners monitor application consumption, understand customer adoption, and analyze usage trends without relying on ad hoc reports from iManage teams.

Partner App Analytics includes tools for viewing request and download activity, identifying which customers are using a Partner's applications, and tracking usage patterns over time. The analytics displayed are based on usage generated by the Partner's applications within iManage Cloud customer environments.

Customer visibility

In iManage Cloud, applications are registered either to customers or to technology Partners. When a customer adds and uses a technology Partner’s application, activity originating from the customer’s environment is displayed to the technology Partner in Partner App Analytics.

This visibility helps technology Partners understand the adoption and usage of their applications across customer environments.

Partner App Analytics components

Partner App Analytics includes the following elements:

Usage analytics

Usage analytics offers a high-level summary of application activity during a selected reporting period. Partners can view:

• Total requests and downloads generated by their applications

• Usage metrics broken down by application

• Usage trends across a selected date range

This view helps Partners understand overall application consumption and identify the applications generating the highest levels of activity.

Customer usage

Customer usage provides insight into how individual customers are using Partner applications. This includes:

• Requests and downloads by customer

• Requests and downloads by application

• A customer-by-application drill-down view showing detailed usage activity

This information helps Partners identify which customers are actively using their applications and understand usage patterns across their customer base.

Usage over time

Usage over time shows request and download trends across a selected period. Partners can analyze historical activity and identify changes in application consumption over time.

Available filters include:

• Customer

• Application

• Metric type (requests or downloads)

• Date range

These filters let Partners focus on specific applications, customers, or time periods when analyzing usage trends.

Understanding usage metrics

Partner App Analytics tracks two independent usage metrics:

• General requests

• Downloads

Monthly allowances for these metrics are tracked and reset independently. Exceeding an allowance for one metric doesn't impact the allowance for the other. Unused allowances don't carry forward to future usage periods.

General requests

A general request is each discrete HTTPS request made to the iManage Universal API by, or on behalf of, a Partner application that is successfully processed and recorded in iManage system logs.

Unless otherwise specified, each successful discrete request counts as one general request.

Downloads

A download is a request made through a document or file retrieval endpoint that successfully returns document, email, attachment, or other file content and is recorded in iManage system logs.

Each successful retrieval counts as a separate download, regardless of:

• File size

• Whether the same content has previously been retrieved

• How many times the content has been downloaded

A download is never counted as a general request.

How requests and downloads are counted

The following rules determine whether a request or download contributes to usage totals.

General request exclusions

The following activities aren't included in general request totals, even when they return a successful (2xx) response:

• Requests used only to issue, refresh, validate, or revoke authentication or access tokens

• Requests made through endpoints designated for uploading content into an iManage product

• Requests already counted as downloads

• Duplicate requests generated solely by internal iManage retry or failure handling and not initiated by the Partner application

Download exclusions

The following activities aren't counted as downloads, even when they return a successful (2xx) response:

• Requests that return only metadata, document profiles, or search results

• Requests used to upload or ingest content

MCP Server usage

Where MCP (Model Context Protocol) Server usage is included as a Partner entitlement, a single request to an iManage MCP Server may generate multiple underlying API operations.

Usage reporting is based on the actual general requests and downloads recorded in iManage system logs, not on the number of MCP Server requests initiated. As a result, a single MCP Server request can produce multiple billable usage events if it results in multiple underlying requests or downloads.

Sandbox environments

Activity generated within a Partner's iManage Cloud sandbox environment is excluded from usage calculations and doesn't count toward general request or download allowances.

Access Policy

The Access Policy page controls who can view the data available on the Partner App Analytics page. From this page, authorized users can add, remove, and manage user access for Partner App Analytics. This helps ensure that portfolio analytics are available only to the appropriate Partner users.

Only users assigned the Partner App Analytics Admin role can open and manage the Access Policy page.

Feature activation

You need to enable the Cloud Partner Analytics upcoming feature in iManage Control Center before you can access the Partner App Analytics section in iManage Admin Portal. For instructions on how to enable this feature, refer to Partner App Analytics feature activation.

Additional information

More information about Partner App Analytics is available in the following sections:

• Partner App Analytics feature activation
• Usage Analytics
• Access Policy