Connecting Kayzen on Clarisights
Kayzen is a mobile-first programmatic DSP for in-house user acquisition, retargeting, and brand campaigns. Connecting Kayzen to Clarisights lets you analyse impressions, clicks, bids, wins, and spend across your campaigns and creatives alongside your other paid channels — and answer questions like "which creative size and orientation drives the most efficient installs?" or "how is video resume affecting delivery and spend?".
Note: The Kayzen integration is currently admin-managed by Clarisights. There is no self-serve flow on the Integrations page — onboarding happens through Clarisights support.
At a glance
| Authentication | OAuth2 password grant (Kayzen username + password) plus a Clarisights-managed client ID and client secret |
| Permissions needed | A Kayzen user with read access to the advertiser(s) and to a saved Kayzen report |
| Account discovery | Manual — each advertiser ID is registered with its own credentials and Kayzen report ID |
| Data freshness | Daily (non-periodic ingestion managed by Clarisights) |
| Lookback window | 30 days |
| Backfill on connect | Last 30 days |
| Timezone | Set on the Kayzen report (default time_zone_id is configured in Kayzen) |
| Currency | USD (advertiser_spend is reported in USD) |
| Levels supported | Account · Campaign · Ad (no Ad Group) |
| Limited rollout | Yes — admin-managed integration. Contact Clarisights support to onboard. |
Prerequisites
An active Kayzen DSP account with at least one advertiser
A Kayzen API user (username + password) with read access to the advertisers you want to connect
A saved Kayzen Report for each advertiser — Clarisights uses the Report ID to pull results. If you don't already have one, your Kayzen account manager can create a daily report grouped by day, campaign, and creative.
The advertiser ID(s) you want to connect (visible in the Kayzen UI under each advertiser)
Steps to Connect
Because Kayzen is an admin-managed integration, the steps below describe what you need to provide to Clarisights support and what happens behind the scenes. There is no self-serve UI on the Integrations page.
Step 1 — Gather your Kayzen credentials
Collect the following from Kayzen for each advertiser you want to connect:
Kayzen username and password for the API user
Advertiser ID (the numeric ID of the advertiser)
Report ID of the Kayzen report Clarisights should pull (a daily report grouped by day, campaign, and creative)
(Optional) A dedicated Client ID and Client Secret if your account uses advertiser-specific OAuth credentials. If not provided, Clarisights uses the shared client credentials configured for the integration.
Treat the Kayzen username and password like any other production credential. The API user only needs read access — do not share an admin user.
Step 2 — Share the credentials securely with Clarisights
Open a request from the in-app messenger or with your Customer Success contact and ask to enable the Kayzen integration. Clarisights will share a secure channel for transmitting the username, password, advertiser ID, and report ID.
[TODO: Screenshot needed — in-app support messenger entry point]
Step 3 — Clarisights configures the channel
The Clarisights team will:
Create the Kayzen channel for your company
Store the API user credentials encrypted
Register each advertiser ID with its corresponding Kayzen report ID and (optionally) advertiser-specific client ID / client secret
Validate the connection by issuing an OAuth token and fetching a sample report
⚠ Authentication failure during validation → Most often caused by an incorrect username/password, a disabled API user, or a client ID/secret pair that does not match the advertiser. Clarisights will reach back out for corrected credentials — please re-issue the credential rather than reusing one that has been flagged as compromised.
⚠ "Report ID not present" or "Could not create Kayzen report" → The advertiser does not have a saved report or the report ID does not match the advertiser. Confirm the report exists in Kayzen for that advertiser and resend the correct numeric report ID.
Step 4 — Wait for the first ingestion run
Once the channel is configured, Clarisights schedules the first ingestion. Backfill covers the last 30 days. You will be notified when data is available in your workspace.
Verify the connection
Confirm with Clarisights support that the Kayzen channel has been created and the first run has completed.
Open any report or dashboard, add Kayzen as a data source, and pull Account ID, Campaign, Impressions, Clicks, and Spend for the last 7 days. Non-zero rows confirm the connection is healthy.
First data appears within ~24 hours of credentials being configured (Kayzen ingestion runs daily).
Data available
Hierarchy
How Kayzen's native levels map to the standard Clarisights levels:
Native level (Kayzen) | Clarisights level |
Advertiser | Account |
Campaign | Campaign and Ad Group (Kayzen has no native Ad Group; Ad Group fields alias to Campaign) |
Creative | Ad |
Dimensions
Dimension | Level | Description |
Account ID | Account | Kayzen advertiser ID |
Campaign / Campaign ID | Campaign | Campaign name and ID |
Campaign Type | Campaign | Type of campaign (e.g. user acquisition, retargeting, brand) |
Ad / Ad ID | Ad | Creative name and ID |
Asset Type | Ad | Creative type (image, video, playable, etc.) |
Video Duration | Ad | Length of the video creative in seconds |
Video Resume | Ad | Whether the video creative supports resume playback |
Metrics
Metric | Description |
Impressions | Ad impressions served |
Clicks | Ad clicks |
Spend | Advertiser spend, reported in USD |
Bids | Bid requests submitted by Kayzen |
Wins | Bids that won the auction |
Limitations & known constraints
Admin-managed: there is no self-serve onboarding from the Integrations page. All onboarding and credential changes go through Clarisights support.
No Ad Group level: Kayzen does not expose Ad Groups. Ad Group fields in Clarisights alias to Campaign.
Per-advertiser configuration: each advertiser must be registered individually with its own Kayzen Report ID. Clarisights cannot auto-discover advertisers from the API user alone.
Report-driven schema: data available is bounded by the dimensions and metrics included in the saved Kayzen report. New fields require updating the report in Kayzen and notifying Clarisights.
30-day lookback: backfill and ongoing ingestion are limited to the last 30 days.
USD-only spend:
advertiser_spendis ingested in USD. Conversion to your reporting currency happens inside Clarisights.No segment breakdowns by default: country, OS, and other segment dimensions require an extended Kayzen report and are not enabled for all customers.
Operating notes
Refresh schedule: daily, managed centrally by Clarisights.
Lookback: 30 days.
Multi-account: each Kayzen advertiser is registered separately under the same channel. Multiple advertisers can share one API user (username/password) but each needs its own Report ID.
Currency handling: spend is ingested in USD and converted into your reporting currency by Clarisights' standard FX pipeline.
Credential rotation: when the Kayzen username/password or Report ID changes, send the new values to Clarisights support via the in-app messenger. Self-serve credential edits are not available for this integration.
Token handling: Clarisights mints a fresh OAuth token for every ingestion run; tokens are not stored long-term.
Need help?
When contacting support from the in-app messenger, please include:
That you are asking about Kayzen (admin-managed integration)
The Kayzen advertiser ID(s) involved
Whether the issue is with onboarding, credential rotation, missing data, or unexpected metrics
The exact error message or screenshot, if any
The date range you expected data for, and what you are seeing instead
When the issue started