Skip to content
Clarisights Knowledge Center home
InboxAsk a human

Connecting OpenX on Clarisights

OpenX is one of the largest independent ad exchanges, used by publishers and demand partners to manage programmatic supply. Connecting OpenX to Clarisights lets you analyze impressions, ad requests, spend, and revenue at the order level alongside your other paid channels.

At a glance

AuthenticationOAuth 1.0a via OpenX SSO — email + password + realm + domain + consumer key + consumer secret
Permissions neededOpenX user with API access on the OX3 / Ad Server platform and read permission on the orders you want to report on
Account discoveryAutomatic — every advertiser account visible to your OpenX login is offered
Data freshnessDaily
Lookback windowDefault backfill from connection date; older history available on request
Backfill on connectOn request from Clarisights support
TimezoneAccount timezone as configured in OpenX
CurrencyAccount currency as configured in OpenX; converted to your reporting currency by Clarisights
Levels supportedAccount · Order (mapped to Campaign)
Limited rolloutNo

Prerequisites

  • An active OpenX (OX3 / Ad Server) account with API access enabled

  • A user account on your OpenX instance with read access on orders and reporting

  • Your OpenX Realm, Domain, Consumer Key, and Consumer Secret — issued by your OpenX account manager. These together identify your OpenX instance to the OAuth flow.

Steps to Connect

Step 1 — Collect your OpenX OAuth credentials

Ask your OpenX account manager (or check your OpenX onboarding email) for the Realm, Domain, Consumer Key, and Consumer Secret for your OpenX instance. These are required in addition to your normal email + password.

⚠ Don't have a Consumer Key / Secret? → Contact your OpenX account manager. The OX3 API requires OAuth 1.0a credentials issued per OpenX instance — they are not available from the self-service UI.

Step 2 — Add OpenX in Clarisights

In Clarisights, go to Integrations → OpenX → Add Account.

[TODO: Screenshot needed — Integrations page OpenX row with Add Account button]

Step 3 — Enter your OpenX credentials

Fill in:

  • Email — the email you use to log in to OpenX

  • Password — your OpenX password

  • Realm — issued by OpenX

  • Domain — the OpenX UI domain for your instance

  • Consumer Key / Consumer Secret — issued by OpenX

Click Validate. Clarisights performs the OpenX OAuth dance (request token → authorize → access token → session validation) and discovers every advertiser account visible to your login.

⚠ OAuth validation fails → The most common causes are (1) a typo in Consumer Key or Consumer Secret, (2) Realm or Domain mismatched against your OpenX instance, or (3) password reset / MFA enabled on the OpenX account. Re-enter the credentials carefully — they are case sensitive. If the issue persists, ask your OpenX account manager to confirm the OAuth credentials are still valid.

Step 4 — Select accounts to connect

Pick the OpenX advertiser accounts you want to connect, optionally rename them, and click Create Accounts.

Verify the connection

  • Go to Integrations → OpenX. Each connected advertiser should show a "Connected" status.

  • First data appears within 24 hours, after the next scheduled sync.

  • Quick start: create a new report, add OpenX as the data source, and add Account · Order · Impressions · Clicks · Spend.

Data available

Hierarchy

How OpenX's native levels map to the standard Clarisights levels:

Native level (OpenX)

Clarisights level

Advertiser Account

Account

Order

Campaign (OpenX Orders are the primary buying unit; surfaced as Campaigns in Clarisights)

—

Ad Group / Ad (OpenX does not expose lower buying levels in its reporting API; Ad Group and Ad fields alias to Order for cross-channel compatibility)

Dimensions

Dimension

Level

Description

Account / Account ID

Account

OpenX advertiser account name and ID

Order / Order ID

Campaign

OpenX order name and ID

Order Status

Campaign

Active, paused, etc.

Currency

Account

Native reporting currency configured on the OpenX account

Timezone

Account

Native reporting timezone configured on the OpenX account

Metrics

Metric

Description

Impressions

Total impressions served

Clicks

Total clicks

Spend

Total spend in account currency

Ad Requests

Total ad requests

View-Through Conversions

Conversions attributed to a view

Click-Through Conversions

Conversions attributed to a click

Conversions Generated

Total tracked conversions

Gross Revenue

Gross revenue reported by OpenX

Net Revenue

Net revenue reported by OpenX

Publisher Revenue

Publisher revenue share

CTR

Click-through rate (derived from Clicks / Impressions)

Limitations & known constraints

  • Order-level reporting only: OpenX exposes performance at the Order level. Line item / package / creative-level breakdowns are not currently ingested.

  • OAuth 1.0a flow: requires Consumer Key + Consumer Secret in addition to email and password. These cannot be self-issued.

  • Daily granularity: hourly breakdowns are not exposed.

  • No bid / auction-level data: log-level (BIDS / OpenXBuild) data is not part of this integration.

  • Custom tags read-only: tags applied to orders sync from OpenX but are not editable in Clarisights.

Operating notes

  • Refresh schedule: daily.

  • Lookback: ongoing pulls cover the previous day plus a short reconciliation window. Historic backfills are available on request.

  • Multi-account: every advertiser account visible to a single OpenX login can be connected from one set of OAuth credentials. Add additional logins to onboard accounts your primary login can't see.

  • Currency conversion: native account currency is preserved on ingest and converted to your reporting currency by Clarisights.

  • Credential rotation: if your OpenX password or Consumer Secret changes, update credentials from Integrations → OpenX → Edit Credentials. The OAuth access token is refreshed automatically each pull.

Need help?

When contacting support from the in-app messenger, please include:

  • The integration name and account ID (Integrations → OpenX)

  • The exact error message or screenshot

  • The step where the issue occurred

  • When the issue started