openapi: 3.2.0 info: title: Skai Asynchronous Reports API description: "# Overview\nSkai APIs provide programmatic access to advertising data and campaign management across Search, Social, and Retail Media publishers.\n\n## Choosing the Right API\n\n| What you want to do | API to use | Scale | Notes |\n|---|---|---|---|\n| Pull performance data, metrics, or any reportable field | [Reporting](#tag/Synchronous-Reports) or [Async Reporting](#tag/Asynchronous-Reports) | Unlimited | Primary data access API — the main Skai value-prop |\n| Discover what columns and metrics are available | [Available Columns](#operation/getAvailableColumns) | — | Full list of reportable fields per entity type |\n| Create or update campaigns, keywords, bids, budgets, targeting, and more — at scale | [Bulk Update (One File)](#tag/Bulk-Update) | Millions of rows | Supports Skai's main entity types and hundreds of attributes; all publishers except Meta |\n| Create/update a small number of campaigns or ad groups (common attributes only) | [Campaigns](#tag/Campaigns) / [Ad Groups](#tag/Ad-Groups) / [Ads](#tag/Ads) | Thousands | Limited attribute set — use Bulk Update for full control |\n| Manage Meta (Facebook/Instagram) entities | [Meta Campaigns](#tag/Meta-Campaigns) / [Meta Ad Groups](#tag/Meta-Ad-Groups) / [Meta Ads](#tag/Meta-Ads) | Thousands | Meta-specific tag and attribution management |\n| Use Skai from an AI coding assistant (Claude, Cursor, ChatGPT, Windsurf) | [MCP Integration](#tag/MCP) | — | Full reporting access via natural language |\n\nSkai APIs are RESTful and language agnostic. Authentication uses Bearer tokens over HTTPS.\n\n## What Data Can I Access?\n\nSkai aggregates advertising data across three publisher categories:\n\n| Publisher category | Examples |\n|---|---|\n| **Search** | Google Ads, Microsoft Ads, Yahoo Japan, Baidu, and others |\n| **Social (excl. Meta)** | Pinterest, Snapchat, TikTok, LinkedIn, Reddit, and others |\n| **Social (Meta)** | Facebook, Instagram |\n| **Retail Media** | Amazon Ads, Walmart, Instacart, Kroger, Target, and 100+ others |\n\n**Reportable entity types:**\n\n| Entity | Description | Publishers |\n|---|---|---|\n| `CAMPAIGN` | Campaign-level data | All |\n| `ADGROUP` | Ad group / ad set level | All |\n| `KEYWORD` | Keyword-level performance and settings | Search, Retail Media |\n| `AD` | Individual ad creatives | All |\n| `PRODUCT_ASSET` | Product-level data for shopping and retail media (called \"Products\" in the Skai UI) | Retail Media, Search Shopping |\n| `PRODUCT_TARGETING` | Product targeting entities — ASINs, categories, and product attributes | Retail Media |\n| `PORTFOLIO` | Portfolio-level budget aggregations and pacing | All |\n\n**Available metric categories per entity:**\n\n- **Performance** — Impressions, Clicks, Cost, Conversions, Revenue, ROAS, CTR, CPC, and more\n- **Attributes** — Names, statuses, budgets, bids, targeting settings, and publisher-specific fields\n- **Account-configured** — Dimensions (custom tagging labels), Conversion events (publisher, pixel, and 3rd-party), Custom Metrics (formula-based calculations your team defines)\n\nUse [Available Columns](#operation/getAvailableColumns) to see the complete column list for any entity — including full descriptions and types. A static reference is embedded in that endpoint's documentation.\n\n\n## Authentication\nThe Skai API uses the Bearer authentication scheme.\nThe first step is to generate a *refresh token* (once), which you can then exchange for a temporary *access token*, programmatically, before making an API call.\n\n> Note: The user you use to generate your *refresh token* will determine the token's permissions. API access is allowed for users with Standard role or higher.\nIt is recommended that you create and use a specialized user for your API requests.\n\n\n#### Step 1: Get a Refresh Token\nYou only need to do this once, for each API user you plan to use. \n\nLog into [this page](https://login.kenshoo.com/api/dev/refresh-token) in order to get your *refresh token* and *client ID*. The user you log in with will be the user accessing the API. \nPlease store your refresh token in a secure place. While it is not possible to recover a refresh token, you can generate a new one. The refresh token does not expire.\n\n\n#### Step 2: Generating an Access Token\nBefore making API calls, your code uses the permanent *refresh token* to generate a temporary *access token*.\n\nMake a call to /api/v1/token (as shown below) with your *refresh token* and *client ID* to generate an *access token*:\n\n curl -X POST -d \"refresh_token=&client_id=\" \\\n https://services.kenshoo.com/api/v1/token\n\nNote: the client_id and refresh token should be sent in the POST request body, as the refresh token is confidential and should not be sent as url param.\nthe API will reject refresh tokens sent in url params.\n\nGet token for specific agency context:\nIn case your API user is assigned to multi accounts (agencies), you should explicitly specify in the get access-token request which agency context you would like to receive the token for.\nJust add to the request mentioned above another form param called *agency_id*, and pass the relevant agency ID like this:\n \n curl -X POST -d \"refresh_token=&client_id=&agency_id=\" \\\n https://services.kenshoo.com/api/v1/token\n\nToken expiration:\nPlease check for token expiration before sending another API request , you have 2 options:\n\n1. Call the API and get 401 status code indicating authentication failed.\n2. Consider the *expires_in* field of the token to issue a new access token.\n\nThe response will return a JSON containing the token and time for expiration in seconds.\nIt is recommended to use the token expiration time and reuse tokens while they are still valid, to prevent rate limit issues with generating new tokens too often.\n\n {\"email\":\"my.user@skai.io\",\"expires_in\":21600,\"access_token\":\"eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJzaGxvbWkuY29oZW5Ac2thaS5pbyIsImV4cCI6MTcxNDU2NjgxMSwiaXNzIjoiaHR0cDovL2tlbnNob28uY29tL2xvZ2luLXNlcnZlciIsInVzZXJpZCI6MzU5NDMsImFnZW5jeUlkIjoxNSwibmFtZSI6IlNobG9taSBDb2hlbiIsInJvbGVzIjpbIktlbnNob28gQWRtaW4iLCJTa2FpIERldmVsb3BlciJdLCJhZ2VuY3lfcm9sZXMiOlt7ImFnZW5jeUlkIjoxNSwicm9sZSI6IktlbnNob28gQWRtaW4ifV0sImJpbGxpbmdJZCI6OTIwMzEsImFwaWMiOiI5MjAzMSIsIm9yaSI6ImFwaSIsImFsbG93ZWRfYXBwcyI6W119.R3tHoaecUrMGzijnF5suo9SVsffXWbWxdMv5fdB3Jx8\"}\n\n\n\n\n\n#### Step 3: Making an API call\nWith any API call to all Skai APIs, you must send a valid *access token* in the Authorization header when making requests. For example:\n\n curl -H \"Authorization: Bearer \" -X POST \\\n https://services.kenshoo.com/api/v1/campaigns\n\n\n## Rate Limits\nAPI calls are limited per user, to the following:\n - 60 requests per minute\n - 2,000 requests per hour\n\nWhen you meet the limit, you receive the following 429 HTTP error: “API rate limit exceeded”.\nWhen calling any API endpoint the response headers will show the limits relevant to this user, and the number of remaining calls you can make within the current minute/hour.\n\n\n## Reporting Best Practices\n\n- **Filter for non-zero data:** For performance reports, filter to rows where a key metric (e.g., impressions > 0) to reduce report size and speed up generation.\n- **Scope structure reports:** Apply a filter like \"Last updated > X days ago\" to retrieve only recently changed entities.\n- **Use Async for large datasets:** If your report may return more than a few thousand rows, use [Async Analysis Reports](#tag/Asynchronous-Reports) and poll for results rather than the synchronous endpoint.\n\n\n## Group by and Segmentation\n### Understanding Group by and Segmentation\nWhen querying the /api/v1/reports/async/analysis and /reports endpoints, the breakdown_type parameter\ndetermines how data is structured.\n- FLAT: Returns unsegmented data without any grouping.\n- GROUP: Allows data segmentation based on specified columns (e.g., by date).\n- SEGMENT: Enables segmentation by date and an additional column, such as CampaignId.\n\n### How Group by works\nWhen using \"breakdown_type\": \"GROUP\", the group_bys parameter defines how the data is grouped. For instance:\n\"group_bys\": [ { \"name\": \"Day\", \"group\": \"TimeSegment\" } ]\n This groups data only by date, meaning campaign details won’t be included, similar to what is displayed in the grid export.\n\n| Conv. | Cost | Day |\n|-------|------|------------|\n| 2 | 100 | 09/29/2024 |\n| 3 | 200 | 09/28/2024 |\n\n### Using SEGMENT for Additional Grouping\nTo segment data by both date and another column (e.g., CampaignId), use \"breakdown_type\": \"SEGMENT\", specifying only the date column under group_bys while including the additional column in fields. Example:\n\"breakdown_type\": \"SEGMENT\",\n\"group_bys\": [ { \"name\": \"Day\", \"group\": \"TimeSegment\" } ],\n\"fields\": [ { \"name\": \"CampaignId\", \"group\": \"ATTRIBUTES\" } ]\n\nThis ensures data is segmented by day while preserving campaign details.\n\n| Campaign ID | Conv. | Cost | Day |\n|-------------|-------|------|------------|\n| 25000 | 1 | 50 | 09/29/2024 |\n| 25001 | 1 | 50 | 09/29/2024 |\n| 25000 | 2 | 150 | 09/28/2024 |\n| 25001 | 1 | 50 | 09/28/2024 |\n" version: 1.0.0 x-logo: url: https://grid.kenshoo.com/resources-frontend/latest/kenshoo_logo/skai-logo-devportal.svg backgroundColor: '#FFFFFF' altText: Skai servers: - url: https://services.kenshoo.com security: - BearerAuth: [] tags: - name: Asynchronous Reports paths: /api/v1/reports/async/existing_report/{report_id}: post: tags: - Asynchronous Reports summary: Configure and run any existing report by ID description: Trigger a run of an existing report, previously created in the Skai interface, by report ID. This is available for all report types in Skai operationId: runAsyncReportById parameters: - $ref: '#/components/parameters/ks' - $ref: '#/components/parameters/useOriginalDeliveryMethod' requestBody: $ref: '#/components/requestBodies/asyncReportByIdRequest' responses: 201: description: Report execution triggered successfully headers: Location: description: 'The `execution_id` of the report will show in this header. Use this ID to poll for the report status or to download the report. The value will be in this format: `https://api.kenshoo.com/v2/reports/runs/rpx-fec94574-152c-4e47-ba57-e5a4029d652e?ks=1234`. In this example, `rpx-fec94574-152c-4e47-ba57-e5a4029d652e` is the `execution_id`.' style: simple explode: false schema: type: string content: application/json: schema: type: string example: The response body will be empty. See the Location header to get the Execution ID 400: description: Invalid report request content: application/json: schema: type: object properties: errorMessage: type: string description: Reason for failure 500: description: Server error content: application/json: schema: type: object properties: errorMessage: type: string /api/v1/reports/async/{execution_id}/status: get: tags: - Asynchronous Reports summary: Poll report execution status description: 'After calling the API to trigger a report, the Skai query will begin processing. The runtime may vary between a few seconds and an hour, depending on the scope of the report and the amount of data returned. This API call is designed to be run at recurring polling intervals so that you can inquire from the Skai API when the report is ready. A best practice would be to run the report manually a few times to figure out the average run time before deciding on the polling interval you will use. For reports that take an average of a few seconds, we recommend using a series of intervals such as 10s, 30s, or 60s. For reports that take an average of a number of minutes or more, we recommend using a series of intervals such as 10m, 20m, or 30m.' operationId: getAsyncReportStatus parameters: - $ref: '#/components/parameters/ks' - name: execution_id in: path description: The execution id received in response to the 'Run a Report' API call. required: true style: simple explode: false schema: type: string responses: 200: description: Report execution triggered successfully content: application/json: schema: type: object properties: status: type: string description: "Status description:\n * `COMPLETED` - Your report is ready to download.\n * `COMPLETED_WITH_ERRORS` - The report run was completed but there were some errors during report generation. If this issue persists, please contact Skai support.\n * `PARTIALLY_COMPLETED` - Some data may be missing from the report. If this issue persists, please contact Skai support.\n * `FAILED` - Skai could not run this report. If this issue persists, please contact Skai support.\n * `ABORTED` - Skai had to abort this report run. If this issue persists, please contact Skai support.\n * `FAILED_DATA_NOT_READY` - The data for the requested dates is not yet ready in Skai (this data is pulled into Skai from the publishers and from external vendors). Abort the flow and try again in an hour.\n" enum: - COMPLETED - COMPLETED_WITH_ERRORS - PARTIALLY_COMPLETED - FAILED - ABORTED - FAILED_DATA_NOT_READY example: status: COMPLETED 400: description: Invalid request content: application/json: schema: type: object properties: errorMessage: type: string errorCode: type: string example: errorCode: SCHREP-04 errorMessage: No execution found with execution id rxp-12345 500: description: Server error content: application/json: schema: type: object properties: errorMessage: type: string /api/v1/reports/async: post: tags: - Asynchronous Reports summary: Configure and run a Fusion/Structure report (deprecated) description: 'Trigger a Fusion/Structure/Tracking template report run asynchronously. **For new integrations, use [POST /api/v1/reports/async/analysis](#operation/asyncAnalysisReport) instead.** This endpoint runs legacy template-based reports, which expose a fixed subset of columns and entity types. It remains fully supported for existing clients — but if you start here, you may find that columns you need later are not available through these templates. The analysis endpoint gives access to the full column set available in the Skai platform.' operationId: runAsyncReport parameters: - $ref: '#/components/parameters/ks' requestBody: $ref: '#/components/requestBodies/asyncReportRequest' responses: 200: description: Report execution triggered successfully content: application/json: schema: type: object properties: run_id: type: string description: Triggered report execution ID 400: description: Invalid report request content: application/json: schema: type: object properties: errorMessage: type: string description: Reason for failure 500: description: Server error content: application/json: schema: type: object properties: errorMessage: type: string /api/v1/reports/async/analysis: post: tags: - Asynchronous Reports summary: Configure and run an analysis grid report (recommended) description: "Run a report asynchronously and download the results as a file. Use this instead of [Synchronous Reports](#operation/fetchReport) when your dataset exceeds 1,000 rows, or when you want to avoid blocking on a long-running query.\n\nThe request body uses the same `entity`, `fields`, `date_range`, `filters`, and `sort` structure as the synchronous report endpoint — refer to [Available Columns](#operation/getAvailableColumns) for field names and groups.\n\n#### Workflow\n\n**1. Submit** — this endpoint returns immediately. The `execution_id` is in the `Location` response header:\n```\nLocation: https://api.kenshoo.com/v2/reports/runs/rpx-fec94574-152c-4e47-ba57-e5a4029d652e?ks=1234\n```\nExtract the path segment after `/runs/` — that is your `execution_id`.\n\n**2. Poll for completion** — [GET /api/v1/reports/async/{execution_id}/status](#operation/getAsyncReportStatus)\nPoll until status is `COMPLETED`. Runtime varies from a few seconds to an hour depending on data volume.\n\n**3. Download** — [GET /api/v1/reports/async/{execution_id}](#operation/downloadAsyncReport)\nReturns a compressed file (ZIP or GZIP, set via `compress_method`) containing a CSV with all result rows — no row limit.\n\n#### Key parameters\n\n| Parameter | Required | Description |\n|---|---|---|\n| `entity` | Yes | Entity type to report on (e.g. `CAMPAIGN`, `KEYWORD`) |\n| `fields` | Yes | Columns to include — use names from [Available Columns](#operation/getAvailableColumns) |\n| `date_range` | Yes | `start_date` and `end_date` in `YYYY-MM-DD` format |\n| `profile_id` | Conditional | Required for single-profile columns; use `0` for cross-profile columns only |\n| `info_level` | No | `SUMMARY`, `BREAKDOWN`, or `BOTH` (default: `BOTH`) |\n| `breakdown_type` | No | `FLAT` (default), `GROUP` (segment by date), or `SEGMENT` (date + another column) |\n| `skip_zero_performance_rows` | No | Exclude rows with no performance data (default: `false`) |\n\n#### cURL example\n\n```bash\n# Step 1 — submit the report\ncurl -i -X POST \\\n 'https://services.kenshoo.com/api/v1/reports/async/analysis?ks=' \\\n -H 'Authorization: Bearer ' \\\n -H 'Content-Type: application/json' \\\n -d '{\n \"entity\": \"CAMPAIGN\",\n \"profile_id\": 118,\n \"date_range\": {\"start_date\": \"2026-01-01\", \"end_date\": \"2026-01-14\"},\n \"fields\": [\n {\"name\": \"CampaignName\", \"group\": \"ATTRIBUTES\"},\n {\"name\": \"Clicks\", \"group\": \"PERFORMANCE\"},\n {\"name\": \"Day\", \"group\": \"TimeSegment\"}\n ]\n }'\n# Check the Location response header for your execution_id\n\n# Step 2 — poll until COMPLETED\ncurl 'https://services.kenshoo.com/api/v1/reports/async//status?ks=' \\\n -H 'Authorization: Bearer '\n# {\"status\": \"COMPLETED\"}\n\n# Step 3 — download the file\ncurl -o report.zip \\\n 'https://services.kenshoo.com/api/v1/reports/async/?ks=' \\\n -H 'Authorization: Bearer '\n```" operationId: asyncAnalysisReport parameters: - $ref: '#/components/parameters/ks' requestBody: $ref: '#/components/requestBodies/AsyncAnalysis' responses: 200: description: Report execution triggered successfully headers: Location: description: 'The `run_id` of the report will show in this header. Use this ID to poll for the report status or to download the report. The value will be in this format: `https://api.kenshoo.com/v2/reports/runs/rpx-fec94574-152c-4e47-ba57-e5a4029d652e?ks=1234`. In this example, `rpx-fec94574-152c-4e47-ba57-e5a4029d652e` is the `execution_id`.' style: simple explode: false schema: type: string content: application/json: schema: type: string example: The response body will be empty. See the Location header to get the Run ID 400: description: Invalid report request content: application/json: schema: type: object properties: errorMessage: type: string description: Reason for failure 500: description: Server error content: application/json: schema: type: object properties: errorMessage: type: string /api/v1/reports/async/{execution_id}: get: tags: - Asynchronous Reports summary: Download completed report file description: Once the report status polling produces a COMPLETED status, use this API to download the compressed report file. operationId: downloadAsyncReport parameters: - $ref: '#/components/parameters/ks' - name: execution_id in: path description: The execution id received in response to the 'Run a Report' API call. required: true style: simple explode: false schema: type: string responses: 200: description: OK content: application/x-zip-compressed: schema: type: string description: The compressed report file. format: binary 404: description: Report not found content: application/json: schema: type: object properties: errorMessage: type: string example: errorMessage: 'Couldn''t find report by execution token: rpx-8fcf61ce-d3a5-4858-9609-d2e7f1f6110e' 500: description: Server error content: application/json: schema: type: object properties: errorMessage: type: string components: requestBodies: asyncReportByIdRequest: description: Configuration for the existing report run content: application/json: schema: $ref: '#/components/schemas/asyncReportByIdRequest' required: true AsyncAnalysis: description: Create async analysis report content: application/json: schema: $ref: '#/components/schemas/AsyncAnalysis' required: true asyncReportRequest: description: The report request to create content: application/json: schema: $ref: '#/components/schemas/asyncReportRequest' required: true parameters: useOriginalDeliveryMethod: name: useOriginalDeliveryMethod in: query description: Set this parameter to true for the report to be delivered to its original destination (the one that is set in the report configuration in Skai, e.g. an email address or an FTP location) required: false style: form explode: true schema: type: boolean example: 'true' ks: name: ks in: query description: The KS to refer the request to. You can find this ID in the Skai platform under _Administration_ -> _About Skai_ -> _Server ID_ required: true style: form explode: true schema: type: string example: '1234' schemas: FusionReportTemplateName: type: string description: One of the available Fusion Reports. enum: - 'Fusion: Profiles' - 'Fusion: Channels' - 'Fusion: Campaigns' - 'Fusion: Campaigns by Device' - 'Fusion: Adgroups' - 'Fusion: Ads' - 'Fusion: Keywords' - 'Fusion: Keywords by Device' - 'Fusion: Keywords with Content and PLA' - 'Fusion: Dynamic Ad Targets' - 'Fusion: Product Groups' - 'Fusion: Sitelinks' - 'Fusion: Audiences' - 'Fusion: Audiences by Device' ReportEntity: type: string description: The base entity for the report, indicated in the analysis grid name. Important - When using the API for product grids, refer to the entity as "PRODUCT_ASSET". enum: - CAMPAIGN - ADGROUP - KEYWORD - AD - PORTFOLIO - PRODUCT_ASSET - LOCATIONS - NEGATIVE_KEYWORDS - SITELINK - CREATIVE_ASSET - PRODUCT_TARGETING - ASSET_GROUP asyncReportTrackingField: type: string description: "\n\n\n| Field name | Reports the field is available in | Data type | Description |\n|-------------------------|---------------------------------------------------------------------------------------------------------------------------|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `Event_Time` | Tracking Raw Data - Click Tracking Data
Tracking Raw Data - Flat P2C | DATETIME | Time of the tracked event, in the time zone of the profile
Format: `yyyy-MM-dd HH:mm:ss`
Example: `2026-01-01 00:00:00` |\n| `Date` | Tracking Raw Data - Keywords Daily Performance | DATE | Date of the event that created performance data
Format: `yyyy-MM-dd`
Example: `2026-01-01` |\n| `User_ID` | Tracking Raw Data - Click Tracking Data
Tracking Raw Data - Flat P2C | TEXT(100) | A unique ID given to the user who clicked the ad
Example: `47e36981-ec4f-44c7-9304-4ed30dbedbd7` |\n| `Profile` | Tracking Raw Data - Click Tracking Data
Tracking Raw Data - Keywords Daily Performance
Tracking Raw Data - Flat P2C | TEXT(50) | Profile name in Skai
Example: `ACME Brand` |\n| `Profile_ID` | Tracking Raw Data - Click Tracking Data
Tracking Raw Data - Keywords Daily Performance
Tracking Raw Data - Flat P2C | INT | Profile ID in Skai
Example: `102` |\n| `Channel` | Tracking Raw Data - Click Tracking Data
Tracking Raw Data - Keywords Daily Performance
Tracking Raw Data - Flat P2C | TEXT(50) | Name of the publisher
Example: `Google` |\n| `Campaign` | Tracking Raw Data - Click Tracking Data
Tracking Raw Data - Keywords Daily Performance
Tracking Raw Data - Flat P2C | TEXT(255) | Campaign name in Skai
Example: `ACME Brand Clothing` |\n| `Campaign_ID` | Tracking Raw Data - Click Tracking Data
Tracking Raw Data - Keywords Daily Performance | BIGINT | Campaign ID in Skai
Example: `1123` |\n| `Campaign ID KS Unique` | Tracking Raw Data - Flat P2C | BIGINT | Campaign ID in Skai
Example: `1123` |\n| `Campaign_ID_In_Target` | Tracking Raw Data - Flat P2C | BIGINT | Campaign ID in the publisher
Example: `121270991` |\n| `Ad_Group` | Tracking Raw Data - Click Tracking Data
Tracking Raw Data - Keywords Daily Performance
Tracking Raw Data - Flat P2C | TEXT(256) | Name of the ad group
Example: `Northwest Region Trucks` |\n| `Adgroup_ID` | Tracking Raw Data - Click Tracking Data
Tracking Raw Data - Keywords Daily Performance | BIGINT | Ad group ID in Skai
Example: `2124` |\n| `Ad Group ID KS Unique` | Tracking Raw Data - Flat P2C | BIGINT | Ad group ID in Skai
Example: `2124` |\n| `Ad_Group_ID_In_Target` | Tracking Raw Data - Flat P2C | BIGINT | Ad group ID in the publisher
Example: `15782818485` |\n| `Keyword` | Tracking Raw Data - Click Tracking Data
Tracking Raw Data - Keywords Daily Performance
Tracking Raw Data - Flat P2C | TEXT(4096) | Keyword text
Example: `Small Hybrid Cars` |\n| `Keyword_ID` | Tracking Raw Data - Click Tracking Data
Tracking Raw Data - Keywords Daily Performance | BIGINT | Tracking ID of the keyword in Skai
Example: `1123` |\n| `Keyword ID KS Unique` | Tracking Raw Data - Flat P2C | BIGINT | Keyword ID in Skai
Example: `1234` |\n| `KW_Tracking_ID` | Tracking Raw Data - Flat P2C | BIGINT | Tracking ID of the keyword in Skai
Example: `1123` |\n| `Match_Type` | Tracking Raw Data - Click Tracking Data
Tracking Raw Data - Keywords Daily Performance
Tracking Raw Data - Flat P2C | TEXT(50) | Match type of the keyword
Valid values: `Exact`, `Phrase`, `Broad` |\n| `Bid` | Tracking Raw Data - Keywords Daily Performance | FLOAT(20,8) | Bid of the tracked entity, in the currency of the profile
Example: `1.50` |\n| `Ad_ID` | Tracking Raw Data - Click Tracking Data | BIGINT | Tracking ID of the ad in Skai
Example: `1123` |\n| `Ad ID KS Unique` | Tracking Raw Data - Flat P2C | BIGINT | Ad ID in Skai
Example: `2124` |\n| `Ad_ID_In_Target` | Tracking Raw Data - Flat P2C | BIGINT | Ad ID in the publisher
Example: `121270991` |\n| `Ad_Tracking_ID` | Tracking Raw Data - Flat P2C | BIGINT | Tracking ID of the ad in Skai
Example: `1123` |\n| `Ad_Headline` | Tracking Raw Data - Click Tracking Data
Tracking Raw Data - Flat P2C | TEXT(255) | Headline of the ad
Example: `Chicago Cars 2016` |\n| `Product Group ID` | Tracking Raw Data - Flat P2C | BIGINT | ID of the product group
Example: `1234` |\n| `Conv_ID` | Tracking Raw Data - Flat P2C | BIGINT | Unique identifier for a conversion. Can be used to connect clicks and other conversions from a single path, to the conversion at the end of the path.
Example: `12345` |\n| `Event_Type` | Tracking Raw Data - Flat P2C | TEXT(100) | Type of tracking event
Example: `Click` |\n| `Order_ID` | Tracking Raw Data - Flat P2C | TEXT(3000) | Order ID of the conversoin, if sent
Example: `2384hr83y487ty354` |\n| `Promo_Code` | Tracking Raw Data - Flat P2C | TEXT(3000) | Promo code sent with the conversion. Used as a free text field.
Example: `fff--0212-shopping-cart` |\n| `Assigned_Weight` | Tracking Raw Data - Flat P2C | FLOAT(20,8) | The relative weight (out of 1) given to a click in a path leading to a conversion
Example: `0.5` |\n| `Path_Duration` | Tracking Raw Data - Flat P2C | Duration | Total time from the first click in the path to the conversion
Example: `04:23:11` |\n| `Number_of_Clicks` | Tracking Raw Data - Flat P2C | INT | Total number of clicks in the path leading to a conversion
Example: `4` |\n| `Number_of_Channels` | Tracking Raw Data - Flat P2C | INT | Number of different publishers with clicks participating in the path to a conversion
Example: `2` |\n| `Country` | Tracking Raw Data - Click Tracking Data
Tracking Raw Data - Flat P2C | TEXT(100) | Country (by IP) of the tracking event
Example: `US` |\n| `City` | Tracking Raw Data - Click Tracking Data
Tracking Raw Data - Flat P2C | TEXT(100) | City (by IP) of the tracking event
Example: `New York` |\n| `State` | Tracking Raw Data - Click Tracking Data
Tracking Raw Data - Flat P2C | TEXT(100) | State (by IP) of the tracking event
Example: `NY` |\n| `IP` | Tracking Raw Data - Click Tracking Data
Tracking Raw Data - Flat P2C | TEXT(100) | IP address of the user who clicked the ad, with the last octet redacted to 00
Example: `207.242.48.00 ` |\n| `Browser` | Tracking Raw Data - Click Tracking Data
Tracking Raw Data - Flat P2C | TEXT(100) | Browser used by the user who clicked the ad
Example: `Chrome 11` |\n| `Language` | Tracking Raw Data - Click Tracking Data
Tracking Raw Data - Flat P2C | TEXT(100) | Browser language used by the user who clicked the ad
Example: `Spanish ` |\n| `Revenue` | Tracking Raw Data - Keywords Daily Performance
Tracking Raw Data - Flat P2C | FLOAT(40,20) | Total revenue, in the currency of the profile. Contains revenue from all “aggregated to conv total” conversion columns.
Example: `23.34` |\n| `Cost` | Tracking Raw Data - Keywords Daily Performance
Tracking Raw Data - Flat P2C | FLOAT(40,20) | Publisher cost, in the currency of the profile
Example: `13.12` |\n| `Device` | Tracking Raw Data - Click Tracking Data | TEXT(100) | Device used by the user who clicked the ad
Example: `iPhone 11` |\n| `Status` | Tracking Raw Data - Keywords Daily Performance | TEXT(50) | Status of the keyword
Valid values: `Active`, `Paused`, `Deleted`, `Pending`, `Inactive`, `Disapproved`, `Approved`, `Failed`, `To Pause`, `To Delete`, `Failed to Pause`, `Failed to Delete` |\n| `Quality_Score` | Tracking Raw Data - Keywords Daily Performance | INT | Quality score of the keyword
Example: `3` |\n| `Impressions` | Tracking Raw Data - Keywords Daily Performance | FLOAT(20,8) | Impressions reported by the publisher
Example: `14,519` |\n| `Clicks` | Tracking Raw Data - Keywords Daily Performance | FLOAT(20,8) | Clicks reported by the publisher
Example: `14` |\n| `Avg_Position` | Tracking Raw Data - Keywords Daily Performance | FLOAT(40,20) | Average position of the impression
Example: `2.1` |\n| `Avg_CPC` | Tracking Raw Data - Keywords Daily Performance | FLOAT(40,20) | Average cost per click
Example: `0.64227` |\n| `Conversions` | Tracking Raw Data - Keywords Daily Performance | FLOAT(40,20) | Conversion total. Contains all “aggregated to conv total” conversion columns.
Example: `1200` |\n| `CTR` | Tracking Raw Data - Keywords Daily Performance | FLOAT(40,20) | Click-through rate
Example: `0.125` |\n| `Conv_Rate` | Tracking Raw Data - Keywords Daily Performance | FLOAT(40,20) | Average number of conversions per click
Example: `0.4` |\n| `Cost_per_Conv` | Tracking Raw Data - Keywords Daily Performance | FLOAT(40,20) | Cost per conversion
Example: `1.54` |\n| `Rev_per_Conv` | Tracking Raw Data - Keywords Daily Performance | FLOAT(40,20) | Revenue per conversion
Example: `52.51` |\n| `ROI` | Tracking Raw Data - Keywords Daily Performance | FLOAT(40,20) | Return on investment
Example: `11.25` |\n| `Profit` | Tracking Raw Data - Keywords Daily Performance | FLOAT(40,20) | Revenue minus cost
Example: `27511` |\n" asyncReportChannel: type: string description: To view all available channels, including any Universal Channel instances, go to Administration > Channel Management enum: - All Elements - Google - MSN - YahooGemini - Pinterest - FB - Yandex - Baidu - YahooJapan - Snapchat - Amazon DateRange: required: - end_date - start_date type: object properties: start_date: type: string description: Start date in YYYY-MM-dd format end_date: type: string description: End date in YYYY-MM-dd format exclude_dates: type: array items: type: string description: Dates to exclude in YYYY-MM-dd format readOnly: true description: The properties of the date range. example: - start_date: '2026-01-01' end_date: '2026-01-14' exclude_dates: - '2026-01-07' asyncReportFusionField: type: string description: "\n\n\n| Field name | Reports the field is available in | Data type | Description |\n|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `Profile ID` | Fusion: Profiles
Fusion: Campaigns
Fusion: Channels
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Product Groups
Fusion: Sitelinks
Fusion: Audiences
Fusion: Audiences by Device | INT | Profile ID in Skai
Example: `102` |\n| `Profile Name` | Fusion: Profiles
Fusion: Campaigns
Fusion: Channels
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Product Groups
Fusion: Sitelinks
Fusion: Audiences
Fusion: Audiences by Device | TEXT(50) | Profile name in Skai
Example: `ACME Brand` |\n| `Profile Currency` | Fusion: Profiles
Fusion: Campaigns
Fusion: Channels
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Product Groups
Fusion: Sitelinks
Fusion: Audiences
Fusion: Audiences by Device | TEXT(10) | Currency in which all monetary values under this profile will be stored in Skai. Any other currencies will be converted upon processing.
Format: 3-character ISO 4217 currency code
Example: `USD` |\n| `Time Zone` | Fusion: Profile | TEXT(50) | Time zone for the profile.
All data reported for the profile will be displayed in this time zone.
Example: `US/Eastern` |\n| `Create Date` | Fusion: Profile | DATETIME | Date and time the profile was created
Format: `yyyy-MM-dd HH:mm:ss`
Example: `2026-01-01 00:00:00` |\n| `Creation Date` | Fusion: Dynamic Ad Targets
Fusion: Product Groups
Fusion: Sitelinks
Fusion: Audiences
Fusion: Audiences by Device | DATETIME | Date the element was created
Format: `yyyy-MM-dd HH:mm:ss`
Example: `2026-01-01 00:00:00.0` |\n| `Last Modified` | Fusion: Profiles
Fusion: Campaigns
Fusion: Channels
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Product Groups
Fusion: Audiences
Fusion: Audiences by Device | DATETIME | Date and time the entity was last modified
Format: `yyyy-MM-dd HH:mm:ss`
Example: `2026-01-01 00:00:00` |\n| `Profile Token` | Fusion: Profile | TEXT(50) | Unique value assigned to all Skai profiles. Used in configuration of event tracking like the Skai infinity tag.
Example: `1acbf593-7551-4aea-83d0-711f4446320e` |\n| `Status` | Fusion: Campaigns
Fusion: Channels
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Product Groups | TEXT(50) | Status of the reported entity
Valid values: `Active`, `Paused`, `Deleted`, `Pending`, `Inactive`, `Disapproved`, `Approved`, `Failed`, `To Pause`, `To Delete`, `Failed to Pause`, `Failed to Delete` |\n| `Bid` | Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Product Groups | FLOAT(20,8) | Bid of the reported element, in the currency of the profile
Example: `1.50` |\n| `Search Bid` | Fusion: Campaigns
Fusion: Campaigns by Device
Fusion: Adgroups | FLOAT(20,8) | Default bid for Search, in the currency of the profile
Example: `1` |\n| `Content Bid` | Fusion: Campaigns
Fusion: Campaigns by Device
Fusion: Adgroups | FLOAT(20,8) | Default bid for Content, in the currency of the profile
Example: `1` |\n| `Mobile Bid Adjustment` | Fusion: Campaigns
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA | INT | Mobile bid adjustment, in the currency of the profile
Example: `-50` |\n| `Tablet Bid Adjustment` | Fusion: Campaigns
Fusion: Campaigns by Device
Fusion: Adgroups | INT | Tablet bid adjustment, in the currency of the profile
Example: `-50` |\n| `Desktop Bid Adjustment` | Fusion: Campaigns
Fusion: Campaigns by Device
Fusion: Adgroups | INT | Desktop bid adjustment. in the currency of the profile
Example: `-50` |\n| `Network` | Fusion: Campaigns
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device | TEXT(128) | List of networks used in this campaign, comma delimited
Example: `Content Network, Search Network` |\n| `Channel` | Fusion: Campaigns
Fusion: Channels
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Product Groups
Fusion: Sitelinks
Fusion: Audiences
Fusion: Audiences by Device | TEXT(50) | Name of the publisher
Example: `Google` |\n| `Account Name` | Fusion: Campaigns
Fusion: Channels
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets | TEXT(255) | Name of the account, if available, or the username configured in Skai to access the account
Example: `Northwest_Google` |\n| `Channel Type ID` | Fusion: Channels | INT | Skai numeric identifier for the name of the publisher:
1 - Google
2 - Bing (MSN)
3 - Yahoo
4 - Yandex
5 - Baidu
Example: `1` |\n| `Channel Account ID` | Fusion: Campaigns
Fusion: Channels
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Sitelinks
Fusion: Audiences
Fusion: Audiences by Device | INT | ID of this publisher account, in Skai
Example: `408` |\n| `Unique Channel Account ID` | Fusion: Campaigns
Fusion: Adgroups
Fusion: Sitelinks | BIGINT | Unique ID of this publisher account, in Skai. Will be identical for several instances of the same account, across multiple profiles.
Example: `102` |\n| `Channel Account Publisher ID` | Fusion: Campaigns
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Ads
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Sitelinks | TEXT(255) | ID of this publisher account, in the publisher
Example: `123456789` |\n| `Channel Currency` | Fusion: Channels | TEXT(10) | Reported currency from the publisher
Example: `USD` |\n| `Campaign Name` | Fusion: Campaigns
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Product Groups
Fusion: Sitelinks
Fusion: Audiences
Fusion: Audiences by Device | TEXT(255) | Campaign name in Skai
Example: `ACME Brand Clothing` |\n| `Campaign ID` | Fusion: Campaigns
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Product Groups
Fusion: Sitelinks
Fusion: Audiences
Fusion: Audiences by Device | BIGINT | Campaign ID in Skai
Example: `1123` |\n| `Channel Campaign ID` | Fusion: Campaigns
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Product Groups
Fusion: Sitelinks
Fusion: Audiences
Fusion: Audiences by Device | BIGINT | Campaign ID in the publisher
Example: `121270991` |\n| `Campaign Status` | Fusion: Adgroups
Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Product Groups
Fusion: Sitelinks
Fusion: Audiences
Fusion: Audiences by Device | TEXT(50) | Status of the campaign
Valid values: `Active`, `Paused`, `Deleted`, `Pending`, `Inactive`, `Disapproved`, `Approved`, `Failed`, `To Pause`, `To Delete`, `Failed to Pause`, `Failed to Delete` |\n| `Campaign Start Date` | Fusion: Campaigns | DATETIME | Date and time the campaign starts
Format: `yyyy-MM-dd HH:mm:ss`
Example: `2026-01-01 00:00:00` |\n| `Campaign End Date` | Fusion: Campaigns | DATETIME | Date and time the campaign ends
Format: `yyyy-MM-dd HH:mm:ss`
Example: `2026-01-01 00:00:00` |\n| `Campaign Creation Date` | Fusion: Campaigns
Fusion: Campaigns by Device | DATETIME | Date and time the campaign was created
Format: `yyyy-MM-dd HH:mm:ss`
Example: `2026-01-01 00:00:00` |\n| `Daily Budget` | Fusion: Campaigns
Fusion: Campaigns by Device | FLOAT(20,8) | Daily budget of the campaign, in the currency of the profile
Example: `100` |\n| `Default Landing Page` | Fusion: Campaigns
Fusion: Campaigns by Device | TEXT(255) | Default landing page of the campaign
Example: `http://www.url.com` |\n| `Geo Targeting countries` | Fusion: Campaigns
Fusion: Campaigns by Device | TEXT(3000) | List of countries targeted by this campaign, comma delimited
Example: `Andorra,Afghanistan,Albania,Bangladesh` |\n| `Geo Targeting territories` | Fusion: Campaigns
Fusion: Campaigns by Device | TEXT(3000) | List of territories targeted by this campaign, comma delimited
Example: `Saint Petersburg,Russia,Tambov Oblast,Russia,Republic of Tatarstan,Russia` |\n| `Device targeting` | Fusion: Campaigns
Fusion: Campaigns by Device | TEXT(100) | Device targeting enabled for this campaign, comma delimited if several devices
Valid values: `desktop`, `high_end_mobile`, `wap_mobile`, `tablet` |\n| `Mirroring Status` | Fusion: Campaigns
Fusion: Campaigns by Device | TEXT(30) | Mirroring status of this campaign, if mirrored
Valid values: `Source`, `Destination`, `Errors on Destination` |\n| `Tracking Level` | Fusion: Campaigns
Fusion: Campaigns by Device | TEXT(20) | Tracking level of the campaign
Valid values: `Keywords`, `Ads`, `Ads + Keywords`, `Profile Default`, `None` |\n| `Portfolio ID` | Fusion: Campaigns
Fusion: Campaigns by Device | INT | ID of the portfolio in Skai
Example: `1234` |\n| `Portfolio Name` | Fusion: Campaigns
Fusion: Campaigns by Device | TEXT(200) | Name of the portfolio in Skai
Example: `Non-Brand` |\n| `Ad Group Name` | Fusion: Adgroups
Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Product Groups
Fusion: Audiences
Fusion: Audiences by Device | TEXT(256) | Name of the ad group
Example: `Northwest Region Trucks` |\n| `Ad Group ID` | Fusion: Adgroups
Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Product Groups | BIGINT | Ad group ID in Skai
Example: `2124` |\n| `Ad Group ID in Skai` | Fusion: Audiences
Fusion: Audiences by Device | BIGINT | Ad group ID in Skai
Example: `2124` |\n| `Channel Ad Group ID` | Fusion: Adgroups
Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Product Groups
Fusion: Audiences
Fusion: Audiences by Device | BIGINT | Ad group ID in the publisher
Example: `15782818485` |\n| `AdGroup Status` | Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Product Groups | TEXT(50) | Status of the ad group
Valid values: `Active`, `Paused`, `Deleted`, `Pending`, `Inactive`, `Disapproved`, `Approved`, `Failed`, `To Pause`, `To Delete`, `Failed to Pause`, `Failed to Delete` |\n| `Ad Group Status` | Fusion: Audiences
Fusion: Audiences by Device | TEXT(50) | Status of the ad group
Valid values: `Active`, `Paused`, `Deleted`, `Pending`, `Inactive`, `Disapproved`, `Approved`, `Failed`, `To Pause`, `To Delete`, `Failed to Pause`, `Failed to Delete` |\n| `AdGroup Creation Date` | Fusion: Adgroups | DATETIME | Date and time the ad group was created
Format: `yyyy-MM-dd HH:mm:ss`
Example: `2026-01-01 00:00:00` |\n| `Tracking ID` | Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Product Groups | BIGINT | ID used for tracking in Skai
Example: `1123` |\n| `Upgr. URL Ind.` | Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Sitelinks | TEXT(10) | Upgraded URL indicator, TRUE if the URL is upgraded
Valid values: `TRUE`, `FALSE` |\n| `Tracking Template` | Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Sitelinks | TEXT(3000) | Tracking template of the entity, applicable for upgraded URLs
Example: `http://www.track.com?url={lpurl}` |\n| `Land URL` | Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA | TEXT(2100) | Destination URL (for non-upgraded ads) or Final URL (for upgraded ads)
Example: `http://www.url.com` |\n| `Mobile URL` | Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Sitelinks | TEXT(3000) | URL for mobile-optimized destination
Example: `http://m.url.com` |\n| `Custom Parameter 1` | Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Sitelinks | TEXT(500) | First custom parameter name and value for upgraded URLs
Example: `{_paramname1} paramvalue1` |\n| `Custom Parameter 2` | Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Sitelinks | TEXT(500) | Second custom parameter name and value for upgraded URLs
Example: `{_paramname2} paramvalue2` |\n| `Custom Parameter 3` | Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Sitelinks | TEXT(500) | Third custom parameter name and value for upgraded URLs
Example: `{_paramname3} paramvalue3` |\n| `Quality Score` | Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Sitelinks | INT | Quality score of the reported entity
Example: `3` |\n| `Keyword` | Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA | TEXT(4096) | Keyword text
Example: `Small Hybrid Cars` |\n| `Keyword ID` | Fusion: Keywords
Fusion: Keywords by Device | BIGINT | Keyword ID in Skai
Example: `1234` |\n| `Channel Keyword ID` | Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA | BIGINT | Keyword ID in the publisher
Example: `1145221822` |\n| `Match Type` | Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA | TEXT(50) | Match type of the keyword
Valid values: `Exact`, `Phrase`, `Broad` |\n| `Min. Bid` | Fusion: Keywords | FLOAT(20,8) | Minimum allowed bid, in the currency of the profile
Example: `1.50` |\n| `Keyword Creation Date` | Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA | DATETIME | Date and time the keyword was created
Format: `yyyy-MM-dd HH:mm:ss`
Example: `2026-01-01 00:00:00` |\n| `Ad Type` | Fusion: Ads
Fusion: Ads by Device | TEXT(50) | Ad type
Valid values: `Text`, `Image`, `Mobile Text`, `Product`, `Dynamic Search`, `App Install`, `Image App Install`, `Call Only`, `Facebook`*
Note: All Facebook ad types display as “Facebook” in this report. |\n| `Ad Name` | Fusion: Ads
Fusion: Ads by Device | TEXT(128) | Name of the ad, for supported ad types
Example: `my_ad` |\n| `Ad ID` | Fusion: Ads
Fusion: Ads by Device | BIGINT | Ad ID in Skai
Example: `2124` |\n| `Channel Ad ID` | Fusion: Ads
Fusion: Ads by Device | BIGINT | Ad ID in the publisher
Example: `121270991` |\n| `Headline` | Fusion: Ads
Fusion: Ads by Device | TEXT(255) | Headline of the ad
Example: `Chicago Cars 2016` |\n| `Headline 2` | Fusion: Ads
Fusion: Ads by Device | TEXT(255) | Headline 2 of the ad
Example: `Chicago Cars 2016` |\n| `Line 1` | Fusion: Ads
Fusion: Ads by Device | TEXT(255) | Line 1 of the ad
Example: `Visit url.com today` |\n| `Line 2` | Fusion: Ads
Fusion: Ads by Device | TEXT(255) | Line 2 of the ad
Example: `for massive discounts` |\n| `Display URL` | Fusion: Ads
Fusion: Ads by Device | TEXT(255) | Display URL of the ad
Example: `url.com` |\n| `Path 1` | Fusion: Ads
Fusion: Ads by Device | TEXT(15) | Part 1 of the path added to the display URL after your website’s domain
Example: `products` |\n| `Path 2` | Fusion: Ads
Fusion: Ads by Device | TEXT(15) | Part 2 of the path added to the display URL after your website’s domain
Example: `shoes` |\n| `Image Name` | Fusion: Ads
Fusion: Ads by Device | TEXT(256) | Name of the image used in the ad
Example: `sunset_120*120.png` |\n| `Image Url` | Fusion: Ads
Fusion: Ads by Device | TEXT(1024) | URL of the image used in the ad
Example: `https://www.acme.com/images/1234` |\n| `Device Preference` | Fusion: Ads
Fusion: Ads by Device | TEXT(50) | Preferred device
Valid values: `All`, `Mobile` |\n| `Last Updated` | Fusion: Ads
Fusion: Ads by Device | DATETIME | Date and time the entity was last modified
Format: `yyyy-MM-dd HH:mm:ss`
Example: `2026-01-01 00:00:00` |\n| `Promotion` | Fusion: Ads
Fusion: Ads by Device | TEXT(255) | Promotion line of product listing ads, blank for other ad types
Example: `Free Shipping & Free Returns` |\n| `ASIN` | Fusion: Ads | TEXT(50) | ASIN of the product that was promoted in each ad, for ecommerce publishers
Example: `B07FSYQT23` |\n| `Serving Error` | Fusion: Ads | TEXT(100) | Serving errors of the product that was promoted in each ad, for ecommerce publishers
Example: `Ad missing decoration.` |\n| `Dynamic Ad Target` | Fusion: Dynamic Ad Targets | TEXT(3000) | Condition defining the dynamic ad target
Example: `PAGE_CONTENT contains Accessories` |\n| `Dynamic Ad Target ID in Skai` | Fusion: Dynamic Ad Targets | BIGINT | Dynamic ad target ID in Skai
Example: `2397842893` |\n| `Dynamic Ad Target ID in Channel` | Fusion: Dynamic Ad Targets | BIGINT | Dynamic ad target ID in the publisher
Example: `2397842893` |\n| `Gender` | Fusion: Adgroups | TEXT(32) | Gender this ad targets, for Pinterest ads
Valid values: `Female`, `Male`, `Unspecified` |\n| `Country` | Fusion: Adgroups | TEXT(128) | List of countries this ad group targets, for Pinterest ads, comma delimited
Example: `US` |\n| `Audience Include` | Fusion: Adgroups | TEXT(2048) | List of audiences this ad group targets, for Pinterest ads, comma delimited
Example: `123123412,4534645645` |\n| `Audience Exclude` | Fusion: Adgroups | TEXT(2048) | List of audiences this ad group excludes, for Pinterest ads, comma delimited
Example: `123123412,4534645645` |\n| `Interests` | Fusion: Adgroups | TEXT(2048) | List of interests this ad group targets, for Pinterest ads, comma delimited
Example: `Cherry Pie, Baking` |\n| `Ad Group Budget Type` | Fusion: Adgroups | TEXT(30) | For publishers with ad group level budget
Valid values: `DAILY`, `LIFETIME` |\n| `Campaign Order Line` | Fusion: Campaigns | TEXT(150) | ID of the order line used in this campaign, for Pinterest campaigns
Example: `1234` |\n| `One Tap` | Fusion: Campaigns | TEXT(10) | Indicates if this campaign is enabled for One Tap, for Pinterest campaigns
Valid values: `No`, `Yes` |\n| `Campaign Bid Strategy` | Fusion: Campaigns | TEXT(30) | Bid strategy of the campaign
Example: `enhanced_cpc` |\n| `Lifetime Spend Cap` | Fusion: Campaigns | TEXT(50) | Lifetime spend cap of the campaign. `Unlimited` if no cap.
Example: `100000` |\n| `Daily Spend Cap` | Fusion: Campaigns | TEXT(50) | Daily spend cap of the campaign. `Unlimited` if no cap.
Example: `100000` |\n| `Placements` | Fusion: Campaigns | TEXT(30) | Placement enabled for this campaign, for Pinterest campaigns
Valid values: `ALL`, `BROWSE`, `SEARCH` |\n| `Product Group` | Fusion: Product Groups | TEXT(4000) | Name of the product group
Example: `ALL/Domestic/Tools` |\n| `Channel Product Group ID` | Fusion: Product Groups | BIGINT | Product group ID in the publisher
Example: `65244597854` |\n| `Biddable` | Fusion: Product Groups | TEXT(10) | Indicates if the product group is biddable. Non-biddable product groups are higher in the hierarchy and cannot have a bid of their own.
Valid values: `Yes`, `No` |\n| `Product Group Level 0` | Fusion: Product Groups | TEXT(500) | Level 0 of the product group definition
Example: `ALL` |\n| `Product Group Level 1` | Fusion: Product Groups | TEXT(500) | Level 1 of the product group definition
Example: `Domestic` |\n| `Product Group Level 2` | Fusion: Product Groups | TEXT(500) | Level 2 of the product group definition
Example: `Tools` |\n| `Product Group Level 3` | Fusion: Product Groups | TEXT(500) | Level 3 of the product group definition
Example: `Tools` |\n| `Product Group Level 4` | Fusion: Product Groups | TEXT(500) | Level 4 of the product group definition
Example: `Tools` |\n| `Product Group Level 5` | Fusion: Product Groups | TEXT(500) | Level 5 of the product group definition
Example: `Tools` |\n| `Product Group Level 6` | Fusion: Product Groups | TEXT(500) | Level 6 of the product group definition
Example: `Tools` |\n| `Product Group Level 7` | Fusion: Product Groups | TEXT(500) | Level 7 of the product group definition
Example: `Tools` |\n| `Destination URL` | Fusion: Product Groups | TEXT(2100) | Destination URL of the product group. Used for tracking, commonly empty.
Example: `http://www.track.com?url={escapedlpurl}` |\n| `Benchmark Max. CPC` | Fusion: Product Groups | FLOAT(40,20) | Benchmarks set for Max. CPC
Example: `0` |\n| `Search Impr. Share` | Fusion: Product Groups | FLOAT(20,8) | Impression share of the product group
Example: `0.75` |\n| `Benchmark CTR` | Fusion: Product Groups | FLOAT(40,20) | Benchmarks set for CTR
Example: `0` |\n| `Sitelink ID` | Fusion: Sitelinks | BIGINT | Sitelink ID in Skai
Example: `1123` |\n| `Channel Sitelink ID` | Fusion: Sitelinks | BIGINT | Sitelink ID in the publisher
Example: `1123` |\n| `Sitelink Text` | Fusion: Sitelinks | TEXT(35) | Text of the sitelink
Example: `Accessories` |\n| `Sitelink Status` | Fusion: Sitelinks | TEXT(50) | Status of the sitelink
Valid values: `Active`, `Paused`, `Deleted`, `Pending`, `Inactive`, `Disapproved`, `Approved`, `Failed`, `To Pause`, `To Delete`, `Failed to Pause`, `Failed to Delete` |\n| `Sitelink Description1` | Fusion: Sitelinks | TEXT(255) | Description 1 of the sitelink
Example: `This is a sitelink` |\n| `Sitelink Description2` | Fusion: Sitelinks | TEXT(255) | Description 2 of the sitelink
Example: `This is a sitelink` |\n| `Shared with Campaign` | Fusion: Sitelinks | TEXT(10) | Indicates if the sitelink was assigned to a campaign
Valid values: `Yes`, `No` |\n| `Account SiteLink` | Fusion: Sitelinks | TEXT(10) | Indicates if the sitelink was assigned to an account
Valid values: `Yes`, `No` |\n| `Sitelink Feed ID` | Fusion: Sitelinks | BIGINT | Feed ID of the sitelink
Example: `1234` |\n| `Account ID` | Fusion: Sitelinks | INT | ID of this publisher account, in Skai
Example: `1349798214` |\n| `Sitelink URL` | Fusion: Sitelinks | TEXT(3000) | URL of the sitelink
Example: `http://www.url.com` |\n| `Sitelinks Schedule Start Date` | Fusion: Sitelinks | DATETIME | Date the sitelink schedule starts
Format: `yyyy-MM-dd HH:mm:ss`
Example: `2026-01-01 00:00:00` |\n| `Sitelinks Schedule End Date` | Fusion: Sitelinks | DATETIME | Date the sitelink schedule ends
Format: `yyyy-MM-dd HH:mm:ss`
Example: `2026-01-01 00:00:00` |\n| `Device Target` | Fusion: Sitelinks | TEXT(100) | Device targeting enabled for this sitelink, comma delimited if several devices
Valid values: `desktop`, `high_end_mobile`, `wap_mobile`, `tablet` |\n| `Audience` | Fusion: Audiences
Fusion: Audiences by Device | TEXT(300) | Audience Name
Example: `addToCart` |\n| `Audience ID in Skai` | Fusion: Audiences
Fusion: Audiences by Device | BIGINT | Audience ID in Skai
Example: `1123` |\n| `Audience ID in Channel` | Fusion: Audiences
Fusion: Audiences by Device | BIGINT | Audience ID in the publisher
Example: `1349798214` |\n| `Audience Type` | Fusion: Audiences
Fusion: Audiences by Device | TEXT(100) | Type of this audience
Valid values: `Website`, `Similar`, `InMarket`, `List`, `Combination`, `Affinity`, `Unknown` |\n| `Description` | Fusion: Audiences
Fusion: Audiences by Device | TEXT(1024) | Description of this audience
Example: `People who converted on your site.` |\n| `Assignment ID` | Fusion: Audiences
Fusion: Audiences by Device | BIGINT | Assignment ID in Skai
Example: `1123` |\n| `Assignment Level` | Fusion: Audiences
Fusion: Audiences by Device | TEXT(100) | Assignment level
Valid values: `Campaign`, `Ad Group` |\n| `Assignment Status` | Fusion: Audiences
Fusion: Audiences by Device | TEXT(100) | Status of this assigment
Valid values: `Active`, `Paused`, `Deleted`, `Pending`, `Inactive`, `Disapproved`, `Approved`, `Failed`, `To Pause`, `To Delete`, `Failed to Pause`, `Failed to Delete` |\n| `Membership Status` | Fusion: Audiences
Fusion: Audiences by Device | TEXT(100) | Is audience collecting new memberships
Valid values: `Open`, `Closed` |\n| `Membership Duration` | Fusion: Audiences
Fusion: Audiences by Device | INT | Duration of membership, in days
Example: `180` |\n| `Membership Size` | Fusion: Audiences
Fusion: Audiences by Device | INT | Number of users in this audience.
Example: `2900` |\n| `Membership Size Range` | Fusion: Audiences
Fusion: Audiences by Device | TEXT(100) | Bracket of the number of uses in this audience
Example: `From 1,001 to 10,000` |\n| `Targeting Settings` | Fusion: Audiences
Fusion: Audiences by Device | TEXT(100) | Type of targeting used
Valid values: `Bid only`, `Target and Bid` |\n| `Targeting Status` | Fusion: Audiences
Fusion: Audiences by Device | TEXT(100) | Status of targeting
Valid values: `Managed`, `Excluded` |\n| `Bid Adjustment` | Fusion: Audiences
Fusion: Audiences by Device | INT | Bid adjustment of the audience
Example value: `-20` |\n| `Bid Strategy` | Fusion: Audiences
Fusion: Audiences by Device | TEXT(100) | Bid startegy for this campaign
Valid values: `CPC`, `Target CPA`, `Unknown` |\n| `Date` | Fusion: Profiles
Fusion: Campaigns
Fusion: Channels
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Product Groups
Fusion: Sitelinks
Fusion: Audiences
Fusion: Audiences by Device | DATE | Date of the event that created performance data
Format: `yyyy-MM-dd`
Example: `2026-01-01` |\n| `Device` | Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Keywords by Device
Fusion: Ads by Device
Fusion: Audiences by Device | TEXT(20) | Device used in ad-click
Valid values: `Computer`, `Mobile`, `Tablets`, `Unknown` |\n| `Impressions` | Fusion: Profiles
Fusion: Campaigns
Fusion: Channels
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Product Groups
Fusion: Sitelinks
Fusion: Audiences
Fusion: Audiences by Device | FLOAT(20,8) | Impressions reported by the publisher
Example: `14,519` |\n| `Clicks` | Fusion: Profiles
Fusion: Campaigns
Fusion: Channels
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Product Groups
Fusion: Sitelinks
Fusion: Audiences
Fusion: Audiences by Device | FLOAT(20,8) | Clicks reported by the publisher
Example: `14` |\n| `Click Others` | Fusion: Sitelinks | FLOAT(20,8) | When sitelinks are shared with multiple campaigns, displays the clicks reported by the publisher for all other campaigns
Example: `23` |\n| `CTR` | Fusion: Profiles
Fusion: Campaigns
Fusion: Channels
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Ads
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Product Groups
Fusion: Sitelinks
Fusion: Audiences
Fusion: Audiences by Device | FLOAT(40,20) | Click-through rate
Example: `0.125` |\n| `CTR Others` | Fusion: Sitelinks | FLOAT(40,20) | When sitelinks are shared with multiple campaigns, displays the click-through rate reported by the publisher for all other campaigns
Example: `23` |\n| `Conversions` | Fusion: Profiles
Fusion: Campaigns
Fusion: Channels
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Ads
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Product Groups
Fusion: Sitelinks
Fusion: Audiences
Fusion: Audiences by Device | FLOAT(40,20) | Conversion total, cntains all “aggregated to conv total” conversion columns
Example: `1200` |\n| `Cost` | Fusion: Profiles
Fusion: Campaigns
Fusion: Channels
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Product Groups
Fusion: Sitelinks
Fusion: Audiences
Fusion: Audiences by Device | FLOAT(40,20) | Publisher cost, in the currency of the profile
Example: `13.12` |\n| `Avg CPC` | Fusion: Profiles
Fusion: Campaigns
Fusion: Channels
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Product Groups
Fusion: Sitelinks
Fusion: Audiences
Fusion: Audiences by Device | FLOAT(40,20) | Average cost per click
Example: `0.64227` |\n| `Cost/Conv.` | Fusion: Profiles
Fusion: Campaigns
Fusion: Channels
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Product Groups
Fusion: Sitelinks
Fusion: Audiences
Fusion: Audiences by Device | FLOAT(40,20) | Cost per conversion
Example: `1.54` |\n| `Conv. Rate` | Fusion: Profiles
Fusion: Campaigns
Fusion: Channels
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Product Groups
Fusion: Sitelinks
Fusion: Audiences
Fusion: Audiences by Device | FLOAT(40,20) | Average number of conversions per click
Example: `0.4` |\n| `Avg Pos` | Fusion: Profiles
Fusion: Campaigns
Fusion: Channels
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Product Groups
Fusion: Sitelinks
Fusion: Audiences
Fusion: Audiences by Device | FLOAT(40,20) | Average position of the impression
Example: `2.1` |\n| `Rev.` | Fusion: Profiles
Fusion: Campaigns
Fusion: Channels
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Product Groups
Fusion: Sitelinks
Fusion: Audiences
Fusion: Audiences by Device | FLOAT(40,20) | Total revenue, in the currency of the profile, contains revenue from all “aggregated to conv total” conversion columns
Example: `23.34` |\n| `ROI` | Fusion: Profiles
Fusion:\ \ Campaigns
Fusion: Channels
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Product Groups
Fusion: Sitelinks
Fusion: Audiences
Fusion: Audiences by Device | FLOAT(40,20) | Return on investment
Example: `11.25` |\n| `Rev./Conv.` | Fusion: Profiles
Fusion: Campaigns
Fusion: Channels
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Product Groups
Fusion: Sitelinks
Fusion: Audiences
Fusion: Audiences by Device | FLOAT(40,20) | Revenue per conversion
Example: `52.51` |\n| `Profit` | Fusion: Profiles
Fusion: Campaigns
Fusion: Channels
Fusion: Campaigns by Device
Fusion: Adgroups
Fusion: Ads
Fusion: Ads by Device
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA
Fusion: Dynamic Ad Targets
Fusion: Product Groups
Fusion: Sitelinks
Fusion: Audiences
Fusion: Audiences by Device | FLOAT(40,20) | Revenue minus cost
Example: `27511` |\n| `Imp. Share` | Fusion: Campaigns
Fusion: Adgroups
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA | FLOAT(20,8) | Impression share of the reported entity
Example: `0.75` |\n| `Lost IS-rank` | Fusion: Campaigns
Fusion: Adgroups
Fusion: Keywords
Fusion: Keywords by Device
Fusion: Keywords with Content and PLA | FLOAT(20,8) | Lost impressoin share due to rank
Example: `34.5` |\n| `Lost-IS budget` | Fusion: Campaigns
Fusion: Adgroups | FLOAT(20,8) | Lost impression share due to budget
Example: `34.5` |\n| `Potential Impressions` | Fusion: Adgroups
Fusion: Keywords
Fusion: Keywords by Device | INT | Calculated potential impressions given 100% impresions share
Example: `100000` |\n" asyncReportField: required: - name type: object properties: display_name: type: string description: Can be provided to rename the field in the report group: type: string description: Can be provided to display the field group in case any field names exist under multiple groups enum: - Attributes - Performance - Dimensions - Conversion Types - Conversions name: description: Field name to include in the report oneOf: - $ref: '#/components/schemas/asyncReportFusionField' - $ref: '#/components/schemas/asyncReportStructureField' - $ref: '#/components/schemas/asyncReportTrackingField' description: Field properties example: - name: Profile ID - name: Ad Group Name display_name: AdGroup - name: leads group: Conversions ReportFilter: required: - field - operator - values type: object properties: field: type: string description: Field name to be fetched operator: type: string enum: - EQUALS - NOT_EQUALS - IN - NOT_IN - GREATER_THAN - GREATER_THAN_EQUALS - LESS_THAN - LESS_THAN_EQUALS - STARTS_WITH - CONTAINS - DOES_NOT_CONTAIN - CONTAINS_ANY - CONTAINS_NONE - ENDS_WITH - IS_EMPTY - IS_NOT_EMPTY - BETWEEN values: type: array items: type: string group: type: string description: Each column belongs to a group. This list is partial - your account may have additional column groups. Group names are available in the getAvailableColumns endpoint enum: - ATTRIBUTES - PERFORMANCE - DIMENSIONS - CUSTOM_METRICS - CUSTOM_METRICS_PLUS - CONVERSION_TYPES - CHANNEL_CUSTOMER_CONVERSION_TYPES - PROXY_CUSTOMER_CONVERSION_TYPES - EXTERNAL_CUSTOMER_CONVERSION_TYPES description: Name of the field to which the condition will apply with certain values. example: - field: StatusToDisplay group: ATTRIBUTES operator: In values: - Approved - Active - field: CampaignName group: ATTRIBUTES operator: CONTAINS values: - New - field: Impressions group: PERFORMANCE operator: GREATER_THAN values: - '0' asyncReportByIdRequest: required: - dateRange type: object properties: dateRange: required: - end_date - start_date type: object properties: start_date: type: string description: Start date in YYYY-MM-dd format end_date: type: string description: End date in YYYY-MM-dd format description: The date range for this report run (overrides the existing report settings for this run only). _NOTE:_ Analysis grid reports must be created with 'Custom' date range (vs. a preset range like 'Last 7 Days') for the API date override to work. example: from: '2026-01-01' to: '2026-01-14' description: The run properties for the requested report example: dateRange: from: '2026-01-01' to: '2026-01-14' asyncReportTemplateName: description: The name of the report oneOf: - $ref: '#/components/schemas/StructureReportTemplateName' - $ref: '#/components/schemas/TrackingReportTemplateName' - $ref: '#/components/schemas/FusionReportTemplateName' asyncReportRequest: required: - fields - require_yesterday_performance - template_name type: object properties: template_name: $ref: '#/components/schemas/asyncReportTemplateName' start_date: type: string description: The start date for your report data. format: yyyy-MM-dd end_date: type: string description: The end date for your report data. format: yyyy-MM-dd currency: type: string description: The currency for all monetary values in the report. In cross-profile reports, use Profile Currency to get all monetary values in each row presented in the currency of this row’s profile. Use any other currency to get all data in the report in the same currency. example: USD default: Profile Currency channels: type: array description: The channels to include data from in the report. example: - Google - MSN items: $ref: '#/components/schemas/asyncReportChannel' default: - All Elements custom_file_name: type: string description: Enter any text and attribute (parameters) to include in the filename of the generated reports. compress_method: type: string description: How you want the file to be compressed. enum: - ZIP - GZIP default: GZIP delimiter: type: string description: The character used to separate the values in the report. enum: - ',' - / - Tab - '|' default: Tab require_yesterday_performance: type: boolean description: Whether the report should only be sent once performance data from the previous day is ready. include_revenue_columns: type: boolean description: Whether the report includes a revenue column for each selected conversion or conversion type column. default: false selected_profile_ids: type: array description: The IDs of Skai profiles to include in the report. When this parameter is not used, all profile IDs to which the user has access are included in the report. entity_level: type: string description: 'The entity level of the report. Relevant for Structure Data: Dimensions report only.' enum: - Ad - Keyword - Ad Group - Campaign - Profile dimensions: type: string description: 'The dimensions to include in the report. Relevant for Structure Data: Dimensions report only.' default: All Elements fields: type: array description: The fields to include in the report. items: $ref: '#/components/schemas/asyncReportField' description: The properties for the report request example: template_name: 'Fusion: Ads' start_date: '2026-01-01' end_date: '2026-01-14' currency: USD channels: - Google fields: - name: Clicks custom_file_name: Name test compress_method: ZIP delimiter: Tab require_yesterday_performance: 'true' include_revenue_columns: 'false' selected_profile_ids: - 401 - 402 TrackingReportTemplateName: type: string description: One of the available Tracking Reports. enum: - Tracking Raw Data - Click Tracking Data - Tracking Raw Data - Keywords Daily Performance - Tracking Raw Data - Flat P2C AsyncAnalysis: required: - date_range - entity - fields type: object properties: entity: $ref: '#/components/schemas/ReportEntity' date_range: $ref: '#/components/schemas/DateRange' fields: uniqueItems: true type: array description: 'The columns to be fetched. See [here](#operation/getAvailableColumns) for available columns. To get data segmented by date, add a date column, like so: `{"name": "Day", "group": "TimeSegment"}`' items: $ref: '#/components/schemas/Column' filters: uniqueItems: true type: array items: $ref: '#/components/schemas/ReportFilter' sort: $ref: '#/components/schemas/ReportSort' info_level: type: string description: Show summary records only, breakdown records only, or both. enum: - SUMMARY - BREAKDOWN - BOTH default: BOTH breakdown_type: type: string description: To get data segmented only by date, use `GROUP`. To segment by both date and another column, use `SEGMENT` with only the date column in group_bys and include the other column in `fields` (these columns will be fetched). Otherwise, use `FLAT` enum: - FLAT - GROUP - SEGMENT default: FLAT group_bys: type: Array description: When the breakdown type is "GROUP", select columns by which to group the data. Often, this would be the date column (see example) and the ID of the entity you are pulling. profile_token: type: string description: Profile token. Either profile token or profile ID is needed to access [Single-Profile columns](#operation/getAvailableColumns) (alternative to profile_id). profile_id: type: number description: Profile ID. Either profile token or profile ID is needed to access [Single-Profile columns](#operation/getAvailableColumns) (alternative to profile_token). custom_file_name: type: string description: Enter any text and attribute (parameters) to include in the filename of the generated reports. compress_method: type: string description: How you want the file to be compressed. enum: - ZIP - GZIP default: GZIP skip_zero_performance_rows: type: boolean description: When set to true, the report includes only rows with performance data greater than 0. When set to false, all rows will be returned, even if there is no performance data. Relevant grids - `CAMPAIGN`, `ADGROUP`, `AD`, `KEYWORD`. This parameter has no effect on other grids. default: false description: The properties for the async analysis request example: entity: CAMPAIGN profile_id: 118 date_range: start_date: '2026-01-01' end_date: '2026-01-14' info_level: BREAKDOWN fields: - name: CampaignName group: ATTRIBUTES - name: Clicks group: PERFORMANCE - name: Day group: TimeSegment filters: - field: StatusToDisplay group: ATTRIBUTES operator: In values: - Approved - Active - field: CampaignName group: ATTRIBUTES operator: CONTAINS values: - My - field: Impressions group: PERFORMANCE operator: GREATER_THAN values: - '0' sort: field: CampaignName group: ATTRIBUTES order: DESCENDING breakdown_type: GROUP group_bys: - name: Day group: TimeSegment customFileName: my_report compressMethod: ZIP skip_zero_performance_rows: true StructureReportTemplateName: type: string description: One of the available Structure Reports. enum: - 'Structure Data: Ads' - 'Structure Data: Keywords' - 'Structure Data: Ad Groups' - 'Structure Data: Product Groups' - 'Structure Data: Campaigns' - 'Structure Data: Channels' - 'Structure Data: Dimensions' - 'Structure Data: Profiles' - 'Structure Data: Sitelinks' Column: required: - group - name type: object properties: name: type: string description: Field name to be fetched group: type: string description: Each column belongs to a group. This list is partial - your account may have additional column groups. Group names are available in the getAvailableColumns endpoint enum: - Attributes - Performance - Dimensions - CustomMetrics - CustomMetricsPlus - ConversionTypes - ChannelCustomerConversionTypes - ProxyCustomerConversionTypes - ExternalCustomerConversionTypes id: type: string readOnly: true display_name: type: string readOnly: true value_type: type: string readOnly: true enum: - STRING - INTEGER - FLOAT - BOOLEAN - DATE description: The properties of a field example: - name: Clicks group: Performance asyncReportStructureField: type: string description: "\n\n\n| Field name | Reports the field is available in | Data type | Description |\n|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `Profile Name` | Structure Data: Profiles
Structure Data: Campaigns
Structure Data: Channels
Structure Data: Ad Groups
Structure Data: Keywords
Structure Data: Ads
Structure Data: Product Groups
Structure Data: Sitelinks | TEXT(50) | Profile name in Skai
Example: `ACME Brand` |\n| `Profile ID` | Structure Data: Profiles
Structure Data: Campaigns
Structure Data: Channels
Structure Data: Ad Groups
Structure Data: Keywords
Structure Data: Ads
Structure Data: Product Groups
Structure Data: Sitelinks
Structure Data: Dimensions | INT | Profile ID in Skai
Example: `102` |\n| `Profile Currency` | Structure Data: Profiles
Structure Data: Campaigns
Structure Data: Channels
Structure Data: Ad Groups
Structure Data: Keywords
Structure Data: Ads
Structure Data: Product Groups | TEXT(10) | Currency in which all monetary values under this profile will be stored in Skai. Any other currencies will be converted upon processing.
Format: 3-character ISO 4217 currency code
Example: `USD` |\n| `Time Zone` | Structure Data: Profiles | TEXT(50) | Time zone for the profile
All data reported for the profile will be displayed in this time zone.
Example: `US/Eastern` |\n| `Profile Token` | Structure Data: Profiles | TEXT(50) | Unique value assigned to all Skai profiles. Used in configuration of event tracking such as the Skai infinity tag.
Example: `1acbf593-7551-4aea-83d0-711f4446320e` |\n| `Create Date` | Structure Data: Profiles | DATETIME | Date and time the profile was created
Format: `yyyy-MM-dd HH:mm:ss`
Example: `2026-01-01 00:00:00` |\n| `Last Modified` | Structure Data: Profiles
Structure Data: Campaigns
Structure Data: Channels
Structure Data: Ad Groups
Structure Data: Keywords
Structure Data: Product Groups
Structure Data: Dimensions | DATETIME | Date and time the profile was last modified
Format: `yyyy-MM-dd HH:mm:ss`
Example: `2026-01-01 00:00:00` |\n| `Status` | Structure Data: Campaigns
Structure Data: Channels
Structure Data: Ad Groups
Structure Data: Keywords
Structure Data: Ads
Structure Data: Product Groups | TEXT(50) | Status of the reported entity
Valid values: `Active`, `Paused`, `Deleted`, `Pending`, `Inactive`, `Disapproved`, `Approved`, `Failed`, `To Pause`, `To Delete`, `Failed to Pause`, `Failed to Delete` |\n| `Channel` | Structure Data: Campaigns
Structure Data: Channels
Structure Data: Ad Groups
Structure Data: Keywords
Structure Data: Ads
Structure Data: Product Groups
Structure Data: Sitelinks
Structure Data: Dimensions | TEXT(50) | Name of the publisher
Example: `Google` |\n| `Channel Account ID` | Structure Data: Campaigns
Structure Data: Channels
Structure Data: Ad Groups
Structure Data: Keywords
Structure Data: Ads
Structure Data: Sitelinks | INT | ID of this publisher account, in Skai
Example: `408` |\n| `Unique Channel Account ID` | Structure Data: Campaigns
Structure Data: Ad Groups
Structure Data: Sitelinks | BIGINT | Unique ID of this publisher account, in Skai. Will be identical for several instances of the same account, across multiple profiles.
Example: `102` |\n| `Channel Account Publisher ID` | Structure Data: Campaigns
Structure Data: Channels
Structure Data: Ad Groups
Structure Data: Keywords
Structure Data: Ads
Structure Data: Product Groups
Structure Data: Sitelinks
Structure Data: Dimensions | INT | ID of this publisher account, in the publisher
Example: `123456789` |\n| `Channel Type ID` | Structure Data: Channels | INT | Skai numeric identifier for the name of the publisher:
1 - Google
2 - Bing (MSN)
3 - Yahoo
4 - Yandex
5 - Baidu
Example: `1` |\n| `Channel Currency` | Structure Data: Channels | TEXT(10) | Reported currency from the publisher
Example: `USD` |\n| `Account Name` | Structure Data: Campaigns
Structure Data: Channels
Structure Data: Ad Groups
Structure Data: Keywords
Structure Data: Ads | TEXT(255) | Name of the account, if available, or the username configured in Skai to access the account
Example: `Northwest_Google` |\n| `Account Status` | Structure Data: Campaigns
Structure Data: Ad Groups
Structure Data: Keywords
Structure Data: Ads
Structure Data: Product Groups
Structure Data: Dimensions | TEXT(50) | Status of the publisher in Skai
Valid values: `Active`, `Paused` |\n| `Campaign Name` | Structure Data: Campaigns
Structure Data: Ad Groups
Structure Data: Keywords
Structure Data: Ads
Structure Data: Product Groups
Structure Data: Sitelinks | TEXT(255) | Campaign name in Skai
Example: `ACME Brand Clothing` |\n| `Campaign ID` | Structure Data: Campaigns
Structure Data: Ad Groups
Structure Data: Keywords
Structure Data: Ads
Structure Data: Product Groups
Structure Data: Sitelinks | BIGINT | Campaign ID in Skai
Example: `1123` |\n| `Channel Campaign ID` | Structure Data: Campaigns
Structure Data: Ad Groups
Structure Data: Keywords
Structure Data: Ads
Structure Data: Product Groups
Structure Data: Sitelinks | BIGINT | Campaign ID in the publisher
Example: `121270991` |\n| `Campaign Status` | Structure Data: Ad Groups
Structure Data: Keywords
Structure Data: Ads
Structure Data: Product Groups
Structure Data: Sitelinks | TEXT(50) | Status of the campaign
Valid values: `Active`, `Paused`, `Deleted`, `Pending`, `Inactive`, `Disapproved`, `Approved`, `Failed`, `To Pause`, `To Delete`, `Failed to Pause`, `Failed to Delete` |\n| `Campaign Start Date` | Structure Data: Campaigns | DATETIME | Date and time the campaign starts
Format: `yyyy-MM-dd HH:mm:ss`
Example: `2026-01-01 00:00:00` |\n| `Campaign End Date` | Structure Data: Campaigns | DATETIME | Date and time the campaign ends
Format: `yyyy-MM-dd HH:mm:ss`
Example: `2026-01-01 00:00:00` |\n| `Campaign Creation Date` | Structure Data: Campaigns | DATETIME | Date and time the campaign was created
Format: `yyyy-MM-dd HH:mm:ss`
Example: `2026-01-01 00:00:00` |\n| `Daily Budget` | Structure Data: Campaigns | FLOAT(20,8) | Daily budget of the campaign, in the currency of the profile
Example: `100` |\n| `Geo Targeting countries` | Structure Data: Campaigns | TEXT(3000) | List of countries targeted by this campaign, comma delimited
Example: `Andorra,Afghanistan,Albania,Bangladesh` |\n| `Geo Targeting territories` | Structure Data: Campaigns | TEXT(3000) | List of territories targeted by this campaign, comma delimited
Example: `Saint Petersburg,Russia,Tambov Oblast,Russia,Republic of Tatarstan,Russia` |\n| `Tracking Level` | Structure Data: Campaigns | TEXT(20) | Tracking level of the campaign
Valid values: `Keywords`, `Ads`, `Ads + Keywords`, `Profile Default`, `None` |\n| `Mirroring Status` | Structure Data: Campaigns | TEXT(30) | Mirroring status of this campaig, if mirrored
Valid values: `Source`, `Destination`, `Errors on Destination` |\n| `Default Landing Page` | Structure Data: Campaigns | TEXT(255) | Name of the entity
Example: `Google North America` |\n| `Device targeting` | Structure Data: Campaigns | TEXT(100) | Device targeting enabled for this campaign, comma delimited if several devices
Valid values: `desktop`, `high_end_mobile`, `wap_mobile`, `tablet` |\n| `Network` | Structure Data: Campaigns | TEXT(128) | Comma delimited list of networks used in this campaign
Example: `Content Network, Search Network` |\n| `Failure Reason` | Structure Data: Campaigns | TEXT(250) | Latest error recorded upon failed attempt to sync this campaign to the publisher
Example: `Trying to create a duplicate campaign` |\n| `Portfolio ID` | Structure Data: Campaigns | INT | ID of the portfolio in Skai
Example: `1234` |\n| `Portfolio Name` | Structure Data: Campaigns | TEXT(200) | Name of the portfolio in Skai
Example: `Non-Brand` |\n| `Search Bid` | Structure Data: Campaigns
Structure Data: Ad Groups | FLOAT(20,8) | Default bid for Search, in the currency of the profile
Example: `1` |\n| `Content Bid` | Structure Data: Campaigns
Structure Data: Ad Groups | FLOAT(20,8) | Default bid for Content, in the currency of the profile
Example: `1` |\n| `Mobile Bid Adjustment` | Structure Data: Campaigns
Structure Data: Ad Groups
Structure Data: Keywords | INT | Mobile bid adjustment, in the currency of the profile
Example: `-50` |\n| `Tablet Bid Adjustment` | Structure Data: Campaigns
Structure Data: Ad Groups | INT | Tablet bid adjustment, in the currency of the profile
Example: `-50` |\n| `Desktop Bid Adjustment` | Structure Data: Campaigns
Structure Data: Ad Groups | INT | Desktop bid adjustment, in the currency of the profile
Example: `-50` |\n| `Ad Group Name` | Structure Data: Ad Groups
Structure Data: Keywords
Structure Data: Ads
Structure Data: Product Groups | TEXT(256) | Name of the ad group
Example: `Northwest Region Trucks` |\n| `Ad Group ID` | Structure Data: Ad Groups
Structure Data: Keywords
Structure Data: Ads
Structure Data: Product Groups | BIGINT | Ad group ID in Skai
Example: `2124` |\n| `AdGroup Status` | Structure Data: Keywords
Structure Data: Ads
Structure Data: Product Groups
Structure Data: Sitelinks | TEXT(50) | Status of the ad group
Valid values: `Active`, `Paused`, `Deleted`, `Pending`, `Inactive`, `Disapproved`, `Approved`, `Failed`, `To Pause`, `To Delete`, `Failed to Pause`, `Failed to Delete` |\n| `Channel Ad Group ID` | Structure Data: Ad Groups
Structure Data: Keywords
Structure Data: Ads
Structure Data: Product Groups | BIGINT | Ad group ID in the publisher
Example: `15782818485` |\n| `AdGroup Creation Date` | Structure Data: Ad Groups | DATETIME | Date and time the ad group was created
Format: `yyyy-MM-dd HH:mm:ss`
Example: `2026-01-01 00:00:00` |\n| `Number of Expanded Text Ads` | Structure Data: Ad Groups | INT | Number of expanded text ads in this ad group
Example: `4` |\n| `Quality Score` | Structure Data: Keywords
Structure Data: Ads | INT | Quality score of the reported entity
Example: `3` |\n| `Tracking ID` | Structure Data: Keywords
Structure Data: Ads
Structure Data: Product Groups | BIGINT | ID used for tracking in Skai
Example: `1123` |\n| `Land URL` | Structure Data: Keywords
Structure Data: Ads | TEXT(2100) | Destination URL (for non-upgraded ads) or Final URL (for upgraded ads)
Example: `http://www.url.com` |\n| `Mobile URL` | Structure Data: Keywords
Structure Data: Ads
Structure Data: Sitelinks | TEXT(3000) | URL for mobile-optimized destination
Example: `http://m.url.com` |\n| `Upgr. URL Ind.` | Structure Data: Keywords
Structure Data: Ads
Structure Data: Sitelinks | TEXT(10) | Upgraded URL indicator, TRUE if the URL is upgraded
Valid values: `TRUE`, `FALSE` |\n| `Tracking Template` | Structure Data: Keywords
Structure Data: Ads
Structure Data: Sitelinks | TEXT(3000) | Tracking template of the entity (applicable for upgraded URLs)
Example: `http://www.track.com?url={lpurl}` |\n| `Custom Parameter 1` | Structure Data: Keywords
Structure Data: Ads
Structure Data: Sitelinks | TEXT(500) | First custom parameter name and value for upgraded URLs
Example: `{_paramname1} paramvalue1` |\n| `Custom Parameter 2` | Structure Data: Keywords
Structure Data: Ads
Structure Data: Sitelinks | TEXT(500) | Second custom parameter name and value for upgraded URLs
Example: `{_paramname2} paramvalue2` |\n| `Custom Parameter 3` | Structure Data: Keywords
Structure Data: Ads
Structure Data: Sitelinks | TEXT(500) | Third custom parameter name and value for upgraded URLs
Example: `{_paramname3} paramvalue3` |\n| `Disapproval Reason` | Structure Data: Keywords
Structure Data: Ads | TEXT(250) | Latest publisher disapproval reason
Example: `Phone numbers are not allowed in ad text` |\n| `Bid` | Structure Data: Keywords
Structure Data: Product Groups | FLOAT(20,8) | Bid of the reported element, in the currency of the profile
Example: `1.50` |\n| `Keyword` | Structure Data: Keywords | TEXT(4096) | Keyword text
Example: `Small Hybrid Cars` |\n| `Keyword ID` | Structure Data: Keywords | BIGINT | Keyword ID in Skai
Example: `1234` |\n| `Channel Keyword ID` | Structure Data: Keywords | BIGINT | Keyword ID in the publisher
Example: `1145221822` |\n| `Match Type` | Structure Data: Keywords | TEXT(50) | Match type of the keyword
Valid values: `Exact`, `Phrase`, `Broad` |\n| `Mobile effective bid` | Structure Data: Keywords | FLOAT(20,8) | Mobile effective bid, in the currency of the profile
Example: `5` |\n| `Min. Bid` | Structure Data: Keywords | FLOAT(20,8) | Minimum allowed bid, in the currency of the profile
Example: `1.50` |\n| `Keyword Creation Date` | Structure Data: Keywords | DATETIME | Date and time the keyword was created
Format: `yyyy-MM-dd HH:mm:ss`
Example: `2026-01-01 00:00:00` |\n| `Ad ID` | Structure Data: Ads | BIGINT | Ad ID in Skai
Example: `2124` |\n| `Channel Ad ID` | Structure Data: Ads | BIGINT | Ad ID in the publisher
Example: `121270991` |\n| `Ad Type` | Structure Data: Ads | TEXT(50) | Ad type
Valid values: `Text`, `Image`, `Mobile Text`, `Product`, `Dynamic Search`, `App Install`, `Image App Install`, `Call Only`, `Facebook`*
Note: All Facebook ad types display as “Facebook” in this report. |\n| `Headline` | Structure Data: Ads | TEXT(255) | Headline of the ad
Example: `Chicago Cars 2016` |\n| `Headline 2` | Structure Data: Ads | TEXT(255) | Headline 2 of the ad
Example: `Chicago Cars 2016` |\n| `Line 1` | Structure Data: Ads | TEXT(255) | Line 1 of the ad
Example: `Visit url.com today` |\n| `Display URL` | Structure Data: Ads | TEXT(255) | Display URL of the ad
Example: `url.com` |\n| `Line 2` | Structure Data: Ads | TEXT(255) | Line 2 of the ad
Example: `for massive discounts` |\n| `Path 1` | Structure Data: Ads | TEXT(15) | Part 1 of the path added to the display URL after your website’s domain
Example: `products` |\n| `Path 2` | Structure Data: Ads | TEXT(15) | Part 2 of the path added to the display URL after your website’s domain
Example: `shoes` |\n| `Image Name` | Structure Data: Ads | TEXT(256) | Name of the image used in the ad
Example: `sunset_120*120.png` |\n| `ASIN` | Structure Data: Ads | TEXT(50) | ASIN of the product that was promoted in each ad, for ecommerce publishers
Example: `B07FSYQT23` |\n| `Promotion` | Structure Data: Ads | TEXT(255) | Promotion line of product listing ads, blank for other ad types
Example: `Free Shipping & Free Returns` |\n| `Last Updated` | Structure Data: Ads | DATETIME | Date and time the element was last modified
Format: `yyyy-MM-dd HH:mm:ss`
Example: `2026-01-01 00:00:00` |\n| `Device Preference` | Structure Data: Ads
Structure Data: Sitelinks | TEXT(50) | Preferred device
Valid values: `All`, `Mobile` |\n| `Sitelink Text` | Structure Data: Sitelinks | TEXT(35) | Text of the sitelink
Example: `Accessories` |\n| `Sitelink ID` | Structure Data: Sitelinks | BIGINT | Sitelink ID in Skai
Example: `1123` |\n| `Channel Sitelink ID` | Structure Data: Sitelinks | TEXT(100) | Sitelink ID in the publisher
Example: `1123` |\n| `Sitelink Description1` | Structure Data: Sitelinks | TEXT(255) | Description 1 of the sitelink
Example: `This is a sitelink` |\n| `Sitelink Description2` | Structure Data: Sitelinks | TEXT(255) | Description 2 of the sitelink
Example: `This is a sitelink` |\n| `Sitelink URL` | Structure Data: Sitelinks | TEXT(3000) | URL of the sitelink
Example: `http://www.url.com` |\n| `Sitelink Status` | Structure Data: Sitelinks | TEXT(50) | Status of the sitelink
Valid values: `Active`, `Paused`, `Deleted`, `Pending`, `Inactive`, `Disapproved`, `Approved`, `Failed`, `To Pause`, `To Delete`, `Failed to Pause`, `Failed to Delete` |\n| `Adgroup ID` | Structure Data: Sitelinks | BIGINT | Ad group ID in Skai
Example: `2124` |\n| `Channel Adgroup ID` | Structure Data: Sitelinks | BIGINT | Ad group ID in the publisher
Example: `15782818485` |\n| `adGroup Name` | Structure Data: Sitelinks | TEXT(256) | Name of the ad group
Example: `Northwest Region Trucks` |\n| `Account SiteLink` | Structure Data: Sitelinks | TEXT(10) | Indicates if the sitelink was assigned to an account
Valid values: `Yes`, `No` |\n| `Device Target` | Structure Data: Sitelinks | TEXT(100) | Device targeting enabled for this sitelink, comma delimited if several devices
Valid values: `desktop`, `high_end_mobile`, `wap_mobile`, `tablet` |\n| `Sitelink Feed ID` | Structure Data: Sitelinks | TEXT(100) | Feed ID of the sitelink
Example: `1234` |\n| `Sitelinks Schedule Start Date` | Structure Data: Sitelinks | DATETIME | Date the sitelink schedule starts
Format: `yyyy-MM-dd HH:mm:ss`
Example: `2026-01-01 00:00:00` |\n| `Sitelinks Schedule End Date` | Structure Data: Sitelinks | DATETIME | Date the sitelink schedule ends
Format: `yyyy-MM-dd HH:mm:ss`
Example: `2026-01-01 00:00:00` |\n| `Product Group` | Structure Data: Product Groups | TEXT(4000) | Name of the product group
Example: `ALL/Domestic/Tools` |\n| `Channel Product Group ID` | Structure Data: Product Groups | BIGINT | Product group ID in the publisher
Example: `65244597854` |\n| `Product Group Level 0` | Structure Data: Product Groups | TEXT(500) | Level 0 of the product group definition
Example: `ALL` |\n| `Product Group Level 1` | Structure Data: Product Groups | TEXT(500) | Level 1 of the product group definition
Example: `Domestic` |\n| `Product Group Level 2` | Structure Data: Product Groups | TEXT(500) | Level 2 of the product group definition
Example: `Tools` |\n| `Product Group Level 3` | Structure Data: Product Groups | TEXT(500) | Level 3 of the product group definition
Example: `Tools` |\n| `Product Group Level 4` | Structure Data: Product Groups | TEXT(500) | Level 4 of the product group definition
Example: `Tools` |\n| `Product Group Level 5` | Structure Data: Product Groups | TEXT(500) | Level 5 of the product group definition
Example: `Tools` |\n| `Product Group Level 6` | Structure Data: Product Groups | TEXT(500) | Level 6 of the product group definition
Example: `Tools` |\n| `Product Group Level 7` | Structure Data: Product Groups | TEXT(500) | Level 7 of the product group definition
Example: `Tools` |\n| `Biddable` | Structure Data: Product Groups | TEXT(10) | Indicates if the product group is biddable. Non-biddable product groups are higher in the hierarchy and cannot have a bid of their own.
Valid values: `Yes`, `No` |\n| `Destination URL` | Structure Data: Product Groups | TEXT(2100) | Destination URL of the product group. Used for tracking, commonly empty.
Example: `http://www.track.com?url={escapedlpurl}` |\n| `Dimension Name` | Structure Data: Dimensions | TEXT(100) | Name of the dimension
Example: `Brand` |\n| `Dimension ID` | Structure Data: Dimensions | INT | Dimension ID in Skai
Example: `123` |\n| `Category Name` | Structure Data: Dimensions | TEXT(100) | Name of the category
Example: `NonBrand` |\n| `Category ID` | Structure Data: Dimensions | INT | Category ID in Skai
Example: `12` |\n| `Entity Level` | Structure Data: Dimensions | TEXT(50) | Entity level for this report
Valid values: `Profile`, `Campaign`, `Ad Group`, `Ad`, `Keyword` |\n| `Entity Name` | Structure Data: Dimensions | TEXT(4096) | Name of the entity
Example: `Google North America` |\n| `Entity ID` | Structure Data: Dimensions | BIGINT | Entity ID in Skai
Example Campaign ID Value: `1123` |\n| `Entity ID in Channel` | Structure Data: Dimensions | BIGINT | Entity ID in the publisher
Example Campaign ID Value: `1123` |\n" ReportSort: required: - field - group type: object properties: field: type: string description: The field to be sorted order: type: string enum: - ASCENDING - DESCENDING default: ASCENDING group: type: string description: Each column belongs to a group. This list is partial - your account may have additional column groups. Group names are available in the getAvailableColumns endpoint enum: - ATTRIBUTES - PERFORMANCE - DIMENSIONS - CUSTOM_METRICS - CUSTOM_METRICS_PLUS - CONVERSION_TYPES - CHANNEL_CUSTOMER_CONVERSION_TYPES - PROXY_CUSTOMER_CONVERSION_TYPES - EXTERNAL_CUSTOMER_CONVERSION_TYPES description: The properties of the sort example: field: CampaignId group: ATTRIBUTES order: DESCENDING x-tagGroups: - name: Reporting tags: - Available Columns - Synchronous Reports - Asynchronous Reports - name: Bulk Operations tags: - Jobs - Bulk Update - name: AI & MCP tags: - MCP - name: Objects tags: - Profile - Campaigns - Ad Groups - Ads - Product Groups - Portfolios - Meta Campaigns - Meta Ad Groups - Meta Ads - Columns