Skip to main content
Use the @bijection/connectors/adobe-analytics entrypoint to declare Adobe Analytics resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Ranked reports

daily: One ranked report per report-suite day

The following example matches configuration pages.

Configuration: pages

Case: adobe-analytics/reports/daily/pages. Connection and resource configuration are declared by this exact case. Credential kind: adobe-analytics. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: report
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. Ranked reports from Adobe Analytics 2.0 POST /api/{globalCompanyId}/reports, one report-suite day per request (a half-open dateRange global filter in the suite’s time zone), paged by settings.page until lastPage. Rows are keyed by (day, dimension itemId); the item’s display value is published beside it. Only counting metrics are offered and each is an exact integer: Adobe sends every metric as a JSON number, so fractional metrics (revenue, rates) are not published. Adobe processes hits with latency and can reprocess data later, and states no per-row finality or restatement bound; restatementDays defaults to three days, a recipe choice, and settled is that window’s basis. Reprocessing an administrator starts after the window is not observed. The connection holds an adobe-analytics OAuth Server-to-Server (client credentials) envelope for https://ims-na1.adobelogin.com/ims/token/v3 (adobeAnalytics.credential); JWT service-account credentials reached end of life on June 30, 2025. Setup names globalCompanyId, clientId (sent as x-api-key) and reportSuiteId. One sliding budget admits twelve requests per six seconds, Adobe’s per-user limit. Nothing here has run against Adobe or been qualified.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.