# Content Ignite

- [Welcome to Content Ignite](https://docs.contentignite.com/index.md): Documentation for Fusion, Content Ignite's ad management platform for publishers: setup guides, integrations, reporting and the API
- [1. Signing Up](https://docs.contentignite.com/getting-started/signing-up.md): Let's get you into the Fusion platform in just a few minutes!
- [2. Creating your first publisher](https://docs.contentignite.com/getting-started/first-publisher.md): Set up your first publisher in just a few clicks
- [3. Creating your first ad unit](https://docs.contentignite.com/getting-started/first-tag-config.md): A few simple settings to get you a fully functioning ad unit
- [4. Going Live](https://docs.contentignite.com/getting-started/going-live.md): Your list of pre-flight checks
- [SaaS vs P&P vs Fully Managed](https://docs.contentignite.com/getting-started/saas-vs-pap.md): To bring your own relationships, or to use ours?
- [Fusion Pro vs Mapped](https://docs.contentignite.com/getting-started/pro-vs-mapped.md): The same platform, different approaches to Ad Server mapping
- [Ad Units](https://docs.contentignite.com/getting-started/ad-units.md): Get to know our core ad unit types
- [Ad Stack Examples](https://docs.contentignite.com/getting-started/ad-stack-examples.md): Your demand sources, ad servers and tech; grouped
- [Integrations](https://docs.contentignite.com/integrations/index.md): Integrations unlock various features and monetisation options throughout the Fusion platform.
- [Policy Centre](https://docs.contentignite.com/integrations/policy-centre.md): Control and transparency where it matters most
- [Integrating Ad Servers](https://docs.contentignite.com/integrations/ad-servers.md): The all important ad server, the minimum needed for a complete ad stack
- [Ad Demand Integrations](https://docs.contentignite.com/integrations/ad-demand.md): Plug in demand beyond your ad server
- [Ad Tech Integrations](https://docs.contentignite.com/integrations/ad-tech.md): Beyond demand; think IDs, think ad block recovery
- [Fallback Creatives](https://docs.contentignite.com/integrations/fallbacks.md): When all demand sources have been exhausted, choose how you want to handle blanks
- [Analytics Integrations](https://docs.contentignite.com/integrations/analytics.md): Empower Fusion with data from your analytics platform
- [Communication Integrations](https://docs.contentignite.com/integrations/comms.md): Stay informed via the communication platforms you already use
- [Integrations Settings](https://docs.contentignite.com/integrations/settings.md): Dive into an integration and set your preferences
- [Publisher Management](https://docs.contentignite.com/publishers/index.md): Each publisher dashboard is your window into a world of insights and control
- [Publisher Settings](https://docs.contentignite.com/publishers/settings.md): Powerful high-level settings for your publisher, enable contextual, integration and so much more
- [Publisher Tag](https://docs.contentignite.com/publishers/tag.md): Our single Publisher Tag is at the core of everything we do
- [Publisher Tag Deployment](https://docs.contentignite.com/publishers/tag-deployment.md): Get your Publisher Tag to page once, and manage the rest inside Fusion
- [Publisher Tag Configs](https://docs.contentignite.com/publishers/tag-configs.md): These configs wrap up unit types, behaviours, targeting and more
- [Ad Stacks](https://docs.contentignite.com/publishers/tag-ad-stacks.md): Group ad servers, demand and more into reusable ad stacks
- [Publisher Tag Targeting](https://docs.contentignite.com/publishers/tag-targeting.md): On web we target units with CSS selectors and use filters to refine it
- [Unit Dependencies](https://docs.contentignite.com/publishers/unit-dependencies.md): Delay selected ad units until another unit or page-level process has resolved
- [Experiments](https://docs.contentignite.com/publishers/experiments.md): Test two or more tag configs head-to-head to find out which performs best on your site
- [JS API](https://docs.contentignite.com/publishers/js-api.md): Our tag has a number of public methods for setting data and triggering actions
- [Publisher Tag - Video Unit](https://docs.contentignite.com/publishers/tag-video.md): A video unit designed to serve your supplementary content
- [Video Config](https://docs.contentignite.com/publishers/video-config.md): Describe the content and content behaviour of your video unit
- [Audiences & Segments](https://docs.contentignite.com/audiences/index.md): Build audiences right from within Fusion
- [Contextual](https://docs.contentignite.com/audiences/contextual.md): Allow our tech to categorise your pages ready for building audiences
- [Organisation Management](https://docs.contentignite.com/organisations/index.md): Control various aspects of your organisation and its children
- [Organisation Tag](https://docs.contentignite.com/organisations/tag.md): For large networks, an org tag can streamline rollout
- [Organisation Branding](https://docs.contentignite.com/organisations/branding.md): Control unit branding to match your identity
- [User Management](https://docs.contentignite.com/users/index.md): Manage users and their roles
- [Dashboard](https://docs.contentignite.com/reporting/dashboard.md): Your landing page in Fusion, for quick network insights
- [Notifications & Alerts](https://docs.contentignite.com/reporting/alerts.md): Fusion can keep you in the loop at all times, via your preferred comms method
- [Revenue Report](https://docs.contentignite.com/reporting/revenue.md): Build completely custom reports, and even visualise the data in chart form!
- [Campaign Reporting](https://docs.contentignite.com/reporting/campaigns.md): Fusion conveniently surfaces your campaign reports
- [Experiment Reporting](https://docs.contentignite.com/reporting/experiments.md): What insight will you gain from Fusion's powerful experiments?
- [Billing](https://docs.contentignite.com/reporting/billing.md): Simple auto-generated invoices and billing processes
- [API Reporting](https://docs.contentignite.com/reporting/api.md): Use your own BI systems? Pull in your Fusion data easily with our API
- [Insights Hub](https://docs.contentignite.com/reporting/insights/index.md): Welcome to a world of publisher insights like you've never seen before
- [Ads.txt Insights](https://docs.contentignite.com/reporting/insights/ads-txt.md): Refine your Ads.txt file for optimal performance
- [Benchmarking](https://docs.contentignite.com/reporting/insights/benchmarking.md): See how you compare with your cohort and the wider network
- [Core Web Vitals Insights](https://docs.contentignite.com/reporting/insights/cwv.md): How do your CWVs stack up?
- [Demand Mix](https://docs.contentignite.com/reporting/insights/demand-mix.md): Analyse your mix of programmatic and direct demand
- [Diagnostics](https://docs.contentignite.com/reporting/insights/diagnostics.md): A central place to identify common pitfalls in your setup
- [Health Check Report & Score](https://docs.contentignite.com/reporting/insights/health-score.md): See how the industry sees you!
- [Live](https://docs.contentignite.com/reporting/insights/live.md): Minute by minute data for the time critical transient moments
- [Metrics](https://docs.contentignite.com/reporting/insights/metrics.md): Dive into the industry standard metrics and even live revenue
- [Revenue Analytics](https://docs.contentignite.com/reporting/insights/revenue-analytics.md): Spot trends easily by plotting your analytical data against revenue
- [Revenue Insights](https://docs.contentignite.com/reporting/insights/revenue.md): Learn where revenue is flowing in from and how it is performing
- [SSP Insights](https://docs.contentignite.com/reporting/insights/ssp.md): How hard are your SSP demand connections working for you?
- [Spark](https://docs.contentignite.com/ai/spark.md): Meet Spark, your AI assistant in Fusion. Just ask!
- [AI summaries](https://docs.contentignite.com/ai/summaries.md): Your daily AI written catch-up, so you know where to focus
- [AI and your data](https://docs.contentignite.com/ai/ai-and-your-data.md): How Spark and AI summaries keep your data private and secure
- [MCP Server (Beta)](https://docs.contentignite.com/guide/mcp.md): Connect Claude and other AI assistants to your Content Ignite account
- [CMP Guide](https://docs.contentignite.com/getting-started/cmp-guide.md): Your guide to Consent Management Platforms
- [Core Web Vitals & Advertising](https://docs.contentignite.com/publishers/tag-core-web-vitals.md): How advertising affects Core Web Vitals, and how Content Ignite keeps the impact on your site to a minimum
- [General FAQs](https://docs.contentignite.com/getting-started/faqs.md): Let's cover off some common FAQs for publishers working with Content Ignite for the first time.
- [Google FAQs](https://docs.contentignite.com/guide/google-faqs.md): Frequently asked questions on Google Ad Manager
- [Operational FAQs](https://docs.contentignite.com/guide/ops-faqs.md): Frequently asked questions on ad operations
- [Ad Debugging](https://docs.contentignite.com/guide/ad-debugging.md): URL parameters for isolating ad issues, from debug logs and demo ads to switching off parts of the ad stack
- [Glossary](https://docs.contentignite.com/guide/glossary.md): Definitions of the metrics, terms and acronyms used in Fusion
- [Fusion Pro Tips](https://docs.contentignite.com/getting-started/top-tips.md): Now you are familiar with Fusion, how can you become a pro user?
- [/report](https://docs.contentignite.com/api-reference/reportingrevenue-reports/report.md): Lists the custom revenue reports saved in your organisation. Run one with `/v1/report/{id}/data`
- [/report](https://docs.contentignite.com/api-reference/reportingrevenue-reports/report-1.md): Creates a user defined report with the given fields and filters. Call /report/filters for possible filter values
- [/report/:id](https://docs.contentignite.com/api-reference/reportingrevenue-reports/report:id.md): The saved set-up of one custom revenue report (fields, filters and date range), not its results
- [/report/:id](https://docs.contentignite.com/api-reference/reportingrevenue-reports/report:id-1.md): Update a reports config
- [/report/:id](https://docs.contentignite.com/api-reference/reportingrevenue-reports/report:id-2.md): Delete a report
- [/report/filters](https://docs.contentignite.com/api-reference/reportingrevenue-reports/reportfilters.md): Lists the values available as filters in custom revenue reports, such as publishers, partners, countries and devices
- [/report/:id/data](https://docs.contentignite.com/api-reference/reportingrevenue-reports/report:iddata.md): Runs a saved custom revenue report and returns its rows. The columns depend on the report.
- [/report/experiment](https://docs.contentignite.com/api-reference/reportingexperiment-reporting/reportexperiment.md): Lists experiments, which split a site's traffic between ad unit configs to see which earns more, with their status. Experiments that ended over two weeks ago are left out
- [/report/experiment/:id](https://docs.contentignite.com/api-reference/reportingexperiment-reporting/reportexperiment:id.md): Results of one experiment: each config's daily performance, traffic share and RPM, and which config is winning
- [/report/campaign](https://docs.contentignite.com/api-reference/reportingcampaign-reports/reportcampaign.md): Lists ad server campaigns that have delivered in the last week, with their dates, publishers and status
- [/report/campaign/:id](https://docs.contentignite.com/api-reference/reportingcampaign-reports/reportcampaign:id.md): Delivery for one ad server campaign: impressions, clicks, CTR, spend and viewability, as totals, a daily trend and breakdowns by publisher, ad unit, creative size and device
- [/report/health-check](https://docs.contentignite.com/api-reference/reportinghealth-check/reporthealth-check.md): Lists health checks from the last 30 days. A health check is a dated review of a site with an overall score and recommendations
- [/v2/report/health-check/:uid/:id](https://docs.contentignite.com/api-reference/reportinghealth-check/v2reporthealth-check:uid:id.md): The full report for one health check: score, commentary on each area reviewed, comparison with similar sites and an action plan
- [/report/adstxt](https://docs.contentignite.com/api-reference/reportingadstxt/reportadstxt.md): The ads.txt status of every website publisher: whether the file was found, includes the platform's lines and is up to date
- [/report/adstxt/:uid](https://docs.contentignite.com/api-reference/reportingadstxt/reportadstxt:uid.md): The lines a publisher's ads.txt file must contain, and which are missing from its live file
- [/report/app-adstxt/:uid](https://docs.contentignite.com/api-reference/reportingadstxt/reportapp-adstxt:uid.md): The lines a publisher's app-ads.txt file must contain, and which are missing from its live file
- [/report/date-range](https://docs.contentignite.com/api-reference/reportingutility/reportdate-range.md): Converts a date range preset into the dates it covers today, with the previous period used for comparisons
- [/report/insight/ssp](https://docs.contentignite.com/api-reference/reportinginsights-hubssp-insights/reportinsightssp.md): Header bidding activity and bid revenue by SSP, or by ad unit, config, country or device, with the previous period for comparison
- [/report/insight/ssp/ssp-filter](https://docs.contentignite.com/api-reference/reportinginsights-hubssp-insights/reportinsightsspssp-filter.md): Lists the SSPs with bid activity in the period, for filtering `/v1/report/insight/ssp`
- [/report/insight/cwv](https://docs.contentignite.com/api-reference/reportinginsights-hubcore-web-vitals/reportinsightcwv.md): Daily Core Web Vitals (LCP, INP, CLS and FCP), with baselines that show how much advertising affects page speed. To compare with similar publishers, use `/v1/report/insight/benchmarking/cwv`
- [/report/insight/ads-txt](https://docs.contentignite.com/api-reference/reportinginsights-hubadstxt-insights/reportinsightads-txt.md): An audit of one publisher's current ads.txt or app-ads.txt file: errors, missing lines, direct and reseller lines by exchange, and whether it is up to date
- [/report/insight/live](https://docs.contentignite.com/api-reference/reportinginsights-hublive-insights/reportinsightlive.md): Near real-time activity for one publisher over the last 1 to 48 hours: ad loads, bids, tag errors and latency. For daily history, use `/v1/report/insight/metrics`
- [/report/insight/metrics](https://docs.contentignite.com/api-reference/reportinginsights-hubmetrics/reportinsightmetrics.md): Daily page impressions, ad unit loads, ad loads and misses, and ad impressions. Month and quarter grouping return daily averages, not totals
- [/report/insight/metrics/revenue](https://docs.contentignite.com/api-reference/reportinginsights-hubmetrics/reportinsightmetricsrevenue.md): Revenue and impressions over time, lined up against the previous period (and the same days a week earlier, for shorter ranges) to show whether performance is up or down
- [/report/insight/metrics/live-revenue](https://docs.contentignite.com/api-reference/reportinginsights-hubmetrics/reportinsightmetricslive-revenue.md): Hourly revenue for today so far, compared with yesterday and the same day last week, with a forecast for the rest of the day. Runs a few hours behind and leaves out some revenue sources
- [/report/insight/metrics/latency](https://docs.contentignite.com/api-reference/reportinginsights-hubmetrics/reportinsightmetricslatency.md): Daily page, tag, ad unit and ad latency at the 50th, 95th and 99th percentiles, weighted by traffic
- [/report/insight/diagnostics](https://docs.contentignite.com/api-reference/reportinginsights-hubdiagnostics/reportinsightdiagnostics.md): Daily consent outcomes (consent given, consent denied and no CMP found) alongside page impressions
- [/report/insight/diagnostics/:uid](https://docs.contentignite.com/api-reference/reportinginsights-hubdiagnostics/reportinsightdiagnostics:uid.md): A health check of one publisher covering consent, ad experience, tag errors and latency, viewability, ads.txt and integrations. Most figures are for yesterday
- [/report/insight/diagnostics/traffic/:uid](https://docs.contentignite.com/api-reference/reportinginsights-hubdiagnostics/reportinsightdiagnosticstraffic:uid.md): Daily page impressions from the ad tag next to page views from the publisher's analytics, with revenue, to check tag coverage against site traffic
- [/report/insight/revenue](https://docs.contentignite.com/api-reference/reportinginsights-hubrevenue-insights/reportinsightrevenue.md): Revenue and ad delivery over time, as totals and a date series.
- [/report/insight/revenue/dimension](https://docs.contentignite.com/api-reference/reportinginsights-hubrevenue-insights/reportinsightrevenuedimension.md): Revenue and ad delivery broken down by one dimension, such as publisher, ad unit type, country, device or partner.
- [/report/insight/revenue/totals](https://docs.contentignite.com/api-reference/reportinginsights-hubrevenue-insights/reportinsightrevenuetotals.md): Revenue totals for fixed periods (yesterday, this week, this month and the last 30 days), each with its previous period for comparison.
- [/report/insight/revenue-analytics](https://docs.contentignite.com/api-reference/reportinginsights-hubrevenue-analytics/reportinsightrevenue-analytics.md): Checks whether a publisher has an analytics integration connected. The other revenue analytics endpoints only return traffic figures when it is
- [/report/insight/revenue-analytics/overview](https://docs.contentignite.com/api-reference/reportinginsights-hubrevenue-analytics/reportinsightrevenue-analyticsoverview.md): Daily revenue alongside site traffic (page views, users and sessions) for one publisher, for revenue per page view, session or user. Needs a connected analytics integration
- [/report/insight/revenue-analytics/totals](https://docs.contentignite.com/api-reference/reportinginsights-hubrevenue-analytics/reportinsightrevenue-analyticstotals.md): Revenue and site traffic totals for one publisher over the date range, with fixed lookback periods. Send `isConnected` only when `/v1/report/insight/revenue-analytics` shows analytics is connected
- [/report/insight/demand-mix](https://docs.contentignite.com/api-reference/reportinginsights-hubdemand-mix/reportinsightdemand-mix.md): Revenue and impressions split by demand type (direct, programmatic, fallback) and by Plug&Play or SaaS demand. For a breakdown by partner, channel, advertiser or platform, use `/v1/report/insight/demand-mix/dimension`
- [/report/insight/demand-mix/dimension](https://docs.contentignite.com/api-reference/reportinginsights-hubdemand-mix/reportinsightdemand-mixdimension.md): Demand Mix figures broken down by partner, channel, advertiser or platform. Filter to specific values from `/v1/report/insight/demand-mix/dimension-filter` to get a date series for them
- [/report/insight/demand-mix/campaign](https://docs.contentignite.com/api-reference/reportinginsights-hubdemand-mix/reportinsightdemand-mixcampaign.md): Revenue and impressions per campaign over time, with where each campaign ran, its delivery dates, its demand source and whether it is live or complete
- [/report/insight/demand-mix/dimension-filter](https://docs.contentignite.com/api-reference/reportinginsights-hubdemand-mix/reportinsightdemand-mixdimension-filter.md): Lists the values of one Demand Mix dimension that can be used as filters on `/v1/report/insight/demand-mix/dimension`
- [/report/insight/benchmarking/ad-delivery](https://docs.contentignite.com/api-reference/reportinginsights-hubbenchmarking/reportinsightbenchmarkingad-delivery.md): Ad loads, fill, CTR and viewability for one publisher, compared with similar publishers (its cohort) and the network. For figures without a comparison, use `/v1/report/insight/revenue`
- [/report/insight/benchmarking/ad-density](https://docs.contentignite.com/api-reference/reportinginsights-hubbenchmarking/reportinsightbenchmarkingad-density.md): Mobile ad density and heavy ad interventions for one publisher, compared with similar publishers (its cohort) and the network
- [/report/insight/benchmarking/ads-txt](https://docs.contentignite.com/api-reference/reportinginsights-hubbenchmarking/reportinsightbenchmarkingads-txt.md): Ads.txt health for one publisher, such as direct and reseller lines, compared with similar publishers (its cohort) and the network. Based on the latest crawl, not a date range
- [/report/insight/benchmarking/cmp](https://docs.contentignite.com/api-reference/reportinginsights-hubbenchmarking/reportinsightbenchmarkingcmp.md): Consent outcomes for one publisher, compared with similar publishers (its cohort) and the network
- [/report/insight/benchmarking/cwv](https://docs.contentignite.com/api-reference/reportinginsights-hubbenchmarking/reportinsightbenchmarkingcwv.md): Core Web Vitals for one publisher, compared with similar publishers (its cohort) and the network. For CWV without a comparison, use `/v1/report/insight/cwv`
- [/report/insight/benchmarking/latency](https://docs.contentignite.com/api-reference/reportinginsights-hubbenchmarking/reportinsightbenchmarkinglatency.md): Page, tag, ad unit and ad latency for one publisher, compared with similar publishers (its cohort) and the network. For latency over time, use `/v1/report/insight/metrics/latency`
- [/report/insight/benchmarking/revenue](https://docs.contentignite.com/api-reference/reportinginsights-hubbenchmarking/reportinsightbenchmarkingrevenue.md): Programmatic revenue, impressions and eCPM for one publisher, compared with similar publishers (its cohort) and the network. Counts programmatic channels only, so totals differ from `/v1/report/insight/revenue`
- [/report/insight/benchmarking/revenue-dimension](https://docs.contentignite.com/api-reference/reportinginsights-hubbenchmarking/reportinsightbenchmarkingrevenue-dimension.md): Programmatic revenue benchmarks for one publisher, broken down by one dimension such as country, device or partner
- [/report/insight/benchmarking/ssps](https://docs.contentignite.com/api-reference/reportinginsights-hubbenchmarking/reportinsightbenchmarkingssps.md): Header bidding results per SSP for one publisher (bid rate, win rate and bid value), compared with similar publishers (its cohort) and the network
- [/report/insight/benchmarking/ssp-overview](https://docs.contentignite.com/api-reference/reportinginsights-hubbenchmarking/reportinsightbenchmarkingssp-overview.md): Header bidding results across all SSPs for one publisher, compared with similar publishers (its cohort) and the network. For each SSP separately, use `/v1/report/insight/benchmarking/ssps`
- [/report/insight/benchmarking/publisher-info](https://docs.contentignite.com/api-reference/reportinginsights-hubbenchmarking/reportinsightbenchmarkingpublisher-info.md): The IAB categories a publisher has been assigned. Publishers sharing a category form its cohort in the benchmarking endpoints
- [/report/dash/stats](https://docs.contentignite.com/api-reference/reporting/reportdashstats.md): Dashboard summary for fixed periods: headline revenue, 30-day CTR and viewability, a 30-day trend, and top, rising and falling publishers. For other periods, use `/v1/report/insight/revenue`
- [/organisation/:id/mapping](https://docs.contentignite.com/api-reference/organisationorganisation-meta/organisation:idmapping.md): Fetches all integrations that suport organisation mapping, the schemas and the data for each
- [/organisation/:id/roles](https://docs.contentignite.com/api-reference/organisationorganisation-meta/organisation:idroles.md): Returns a list of users that have access to the given organisation
- [/organisation/:id/pricing](https://docs.contentignite.com/api-reference/organisationpricing/organisation:idpricing.md): Returns a list of pricing rules; data based periods of pricing settings made up of tech/saas fees, demand revenue shares and fixed fees
- [/organisation/:id/pricing](https://docs.contentignite.com/api-reference/organisationpricing/organisation:idpricing-1.md): Create a new pricing period. New period must be in the future to be valid
- [/organisation/:id/pricing/:pid](https://docs.contentignite.com/api-reference/organisationpricing/organisation:idpricing:pid.md): Updates a pricing period. Period must be in the future as historic or active periods can not be modified (create a new period if needed)
- [/organisation/:id/pricing/:pid](https://docs.contentignite.com/api-reference/organisationpricing/organisation:idpricing:pid-1.md): Deletes a pricing period, Period must be in the future as historic or active periods can not be modified
- [/organisation](https://docs.contentignite.com/api-reference/organisation/organisation.md): Returns a list containing the active organisation, and any child organisations
- [/organisation](https://docs.contentignite.com/api-reference/organisation/organisation-1.md): Creates a new child organisation under the currently logged in organisation
- [/organisation/:id](https://docs.contentignite.com/api-reference/organisation/organisation:id.md): Fetches a single organisation
- [/organisation/:id](https://docs.contentignite.com/api-reference/organisation/organisation:id-1.md): Updates an existing organisation
- [/organisation/:id](https://docs.contentignite.com/api-reference/organisation/organisation:id-2.md): Deletes a child organisation
- [/ad-stack/integration](https://docs.contentignite.com/api-reference/ad-stackintegration/ad-stackintegration.md): Fetches a list of integrations that could be used to build an ad stack under the given publisher
- [/ad-stack/integration/:type/:id](https://docs.contentignite.com/api-reference/ad-stackintegration/ad-stackintegration:type:id.md): Fetches an individual integration, The response includes everything needed to configure that integration within an ad stack, such as the schema for any config fields
- [/ad-stack/integration/:type/:id](https://docs.contentignite.com/api-reference/ad-stackintegration/ad-stackintegration:type:id-1.md): Validate the configuration of a given integration. Each integrations requirements vary, so use this endpoint to check all requirements have been met
- [/ad-stack](https://docs.contentignite.com/api-reference/ad-stack/ad-stack.md): Fetches a list of ad stacks in use by the provided publisher
- [/ad-stack](https://docs.contentignite.com/api-reference/ad-stack/ad-stack-1.md): Creates a new ad stack. Call the `/v1/integration?target=ad_stack` endpoint to find available integrations, and call the `/v1/integration/{id}/stack-schema` endpoint to find the field requirements for each integration.
- [/ad-stack/:id](https://docs.contentignite.com/api-reference/ad-stack/ad-stack:id.md): Gets an individual ad stack and all the integrations connected to it
- [/ad-stack/:id](https://docs.contentignite.com/api-reference/ad-stack/ad-stack:id-1.md): Updates an existing ad stack. Call the `/v1/integration?target=ad_stack` endpoint to find available integrations, and call the `/v1/integration/{id}/stack-schema` endpoint to find the field requirements for each integration.
- [/ad-stack/:id](https://docs.contentignite.com/api-reference/ad-stack/ad-stack:id-2.md): Deletes the given ad stack
- [/pub-stack/:uid/integration](https://docs.contentignite.com/api-reference/publisherpublisher-stack/pub-stack:uidintegration.md): Fetches a list of publisher level integrations that could be connected to the given publisher
- [/pub-stack/:uid/integration](https://docs.contentignite.com/api-reference/publisherpublisher-stack/pub-stack:uidintegration-1.md): Creates an association between a publisher and a publisher level integration (adding it to the "Pub stack")
- [/pub-stack/:uid/integration/:id](https://docs.contentignite.com/api-reference/publisherpublisher-stack/pub-stack:uidintegration:id.md): Fetches the field schema and data for a single connected integration
- [/pub-stack/:uid/integration/:id](https://docs.contentignite.com/api-reference/publisherpublisher-stack/pub-stack:uidintegration:id-1.md): Updates an existing integration association
- [/pub-stack/:uid/integration/:id](https://docs.contentignite.com/api-reference/publisherpublisher-stack/pub-stack:uidintegration:id-2.md): Deletes the assosication between the publisher and an integration
- [/tag/:uid/email/preview](https://docs.contentignite.com/api-reference/publisherpublisher-tag/tag:uidemailpreview.md): Provides an email template for onboarding a publisher. It contains the tag that needs to be deployed and the ads.txt requirents
- [/tag/:uid/status](https://docs.contentignite.com/api-reference/publisherpublisher-tag/tag:uidstatus.md): Fetches the status of the publisher tag and the app sdk for the given publisher
- [/publisher/:uid/stats](https://docs.contentignite.com/api-reference/publisherpublisher-meta/publisher:uidstats.md): Daily tag activity for one publisher over the last 30 days, including today: ad loads and misses, page impressions, tag errors, consent outcomes and latency
- [/publisher/:uid/status](https://docs.contentignite.com/api-reference/publisherpublisher-meta/publisher:uidstatus.md): Provides the onboarding tasks for the given publisher, and their status
- [/publisher/:uid/owners](https://docs.contentignite.com/api-reference/publisherpublisher-meta/publisher:uidowners.md): Fetch a list of organisations that are in the owner hierachy of the given publisher, useful for populating the O&O (Owned & Operated) field on the publisher
- [/publisher/:uid/overview](https://docs.contentignite.com/api-reference/publisherpublisher-meta/publisher:uidoverview.md): Returns the top level configuration for the given publisher
- [/publisher/:uid/mapping](https://docs.contentignite.com/api-reference/publisherpublisher-meta/publisher:uidmapping.md): Returns the top level configuration for the given publisher
- [/publisher/:uid/completeness](https://docs.contentignite.com/api-reference/publisherpublisher-meta/publisher:uidcompleteness.md): Returns the top level configuration for the given publisher
- [/tag/:uid/experiment](https://docs.contentignite.com/api-reference/publisherexperiment/tag:uidexperiment.md): Returns a list of experiments for a given publisher
- [/tag/:uid/experiment](https://docs.contentignite.com/api-reference/publisherexperiment/tag:uidexperiment-1.md): Creates an experiment, where 2 or more configs are run against one another
- [/tag/:uid/experiment/:id](https://docs.contentignite.com/api-reference/publisherexperiment/tag:uidexperiment:id.md): Get the configuration for a given experiment
- [/tag/:uid/experiment/:id](https://docs.contentignite.com/api-reference/publisherexperiment/tag:uidexperiment:id-1.md): Updates an existing config. Actions are restricted for live experiments, to just modifying dates and the title & description
- [/tag/:uid/experiment/:id](https://docs.contentignite.com/api-reference/publisherexperiment/tag:uidexperiment:id-2.md): Terminates an experiment immediately
- [/tag/:uid/experiment/compare](https://docs.contentignite.com/api-reference/publisherexperiment/tag:uidexperimentcompare.md): Takes a list of configs, and returns the differences between them. Used before creating an experiment to confirm the bahavioural subject(s) that the experiment will be testing
- [/tag/:uid/experiment/:id/activate-winner](https://docs.contentignite.com/api-reference/publisherexperiment/tag:uidexperiment:idactivate-winner.md): Activates the winnning config of an experiment. This can be run upon completion, or during an experiment, where the experiment will be immmediately terminated
- [/tag/:uid/config](https://docs.contentignite.com/api-reference/publisherconfig-ad-unit/tag:uidconfig.md): Fetches the list of configs under the given publisher
- [/tag/:uid/config](https://docs.contentignite.com/api-reference/publisherconfig-ad-unit/tag:uidconfig-1.md): Creates a new config under the given publisher
- [/tag/:uid/config/:id](https://docs.contentignite.com/api-reference/publisherconfig-ad-unit/tag:uidconfig:id.md): Fetches a single publisher config (ad unit)
- [/tag/:uid/config/:id](https://docs.contentignite.com/api-reference/publisherconfig-ad-unit/tag:uidconfig:id-1.md): Updates and existing config
- [/tag/:uid/config/:id](https://docs.contentignite.com/api-reference/publisherconfig-ad-unit/tag:uidconfig:id-2.md): Deletes a config
- [/tag/:uid/config/:id/mapping](https://docs.contentignite.com/api-reference/publisherconfig-ad-unit/tag:uidconfig:idmapping.md): Fetches a single publisher config (ad unit)
- [/tag/:uid/placement](https://docs.contentignite.com/api-reference/publisherapp-placement/tag:uidplacement.md): Fetch a list of all app placements under the given publisher
- [/tag/:uid/placement](https://docs.contentignite.com/api-reference/publisherapp-placement/tag:uidplacement-1.md): Creates a new app placement
- [/tag/:uid/placement/:id](https://docs.contentignite.com/api-reference/publisherapp-placement/tag:uidplacement:id.md): Fetch the app placement from the given placement ID
- [/tag/:uid/placement/:id](https://docs.contentignite.com/api-reference/publisherapp-placement/tag:uidplacement:id-1.md): Updates an existing app placement
- [/tag/:uid/placement/:id](https://docs.contentignite.com/api-reference/publisherapp-placement/tag:uidplacement:id-2.md): Deletes the given app placement.
- [/publisher/:uid](https://docs.contentignite.com/api-reference/publisher/publisher:uid.md): Fetches all the publisher level settings for the given publisher
- [/publisher/:uid](https://docs.contentignite.com/api-reference/publisher/publisher:uid-1.md): Sets the publisher level configuration for the given publisher
- [/publisher/:uid](https://docs.contentignite.com/api-reference/publisher/publisher:uid-2.md): Permenantly archives the given publisher, this will stop the tag from serving ads
- [/publisher](https://docs.contentignite.com/api-reference/publisher/publisher.md): List all publishers under the loggedin organisation, and some top level configuration
- [/publisher](https://docs.contentignite.com/api-reference/publisher/publisher-1.md): Creates a new publisher from the given domain
- [/publisher/taxonomy](https://docs.contentignite.com/api-reference/publisher/publishertaxonomy.md): Lists the tags used to group publishers, from your organisation and the organisations in your account structure below it, with how many publishers carry each
- [/ai/activity/overview](https://docs.contentignite.com/api-reference/aiactivity/aiactivityoverview.md): Headline usage, cost and failure figures for Spark chat and AI summaries in the period, with a daily series, failure reasons, the pages questions come from, and the top organisations and users. Only available to admins. Results cover the organisations your account can access.
- [/ai/activity/trends](https://docs.contentignite.com/api-reference/aiactivity/aiactivitytrends.md): Cost, usage and adoption for fixed lookbacks (last 7 and 14 days, last week, month and quarter), each against the period before it, with this month's projected cost and a 14-day daily series. Every filter applies except the date range. Only available to admins. Results cover the organisations your a…
- [/ai/activity/conversations](https://docs.contentignite.com/api-reference/aiactivity/aiactivityconversations.md): Spark chats with activity in the period, with their questions, failures, tokens and cost. Only available to admins. Results cover the organisations your account can access.
- [/ai/activity/conversations/:id](https://docs.contentignite.com/api-reference/aiactivity/aiactivityconversations:id.md): Per-turn usage for one Spark chat. The chat's messages are not included. Only available to admins. Results cover the organisations your account can access.
- [/ai/activity/log](https://docs.contentignite.com/api-reference/aiactivity/aiactivitylog.md): The most recent Spark questions and AI summary generations, with their outcome, tokens and cost. Only available to admins. Results cover the organisations your account can access.
- [/ai/activity/users](https://docs.contentignite.com/api-reference/aiactivity/aiactivityusers.md): Users with AI activity in the period. Only available to admins. Results cover the organisations your account can access.
- [/ai/summaries](https://docs.contentignite.com/api-reference/ai/aisummaries.md): AI summaries for the period with their status, tokens, cost and every generation attempt. Only available to admins. Results cover the organisations your account can access.
- [/billing/invoice](https://docs.contentignite.com/api-reference/billinginvoice/billinginvoice.md): Fetches a list of invoices for the logged in organisation
- [/billing/invoice/:id](https://docs.contentignite.com/api-reference/billinginvoice/billinginvoice:id.md): Fetches a specific invoice
- [/audit-log](https://docs.contentignite.com/api-reference/audit-log/audit-log.md): Lists changes to the organisation’s setup, newest first: what changed, who changed it, when, and whether it was made directly or by an AI client. Only available to users with audit log access. Use `next_cursor` to load the next page.
- [/integration/:id/mapping](https://docs.contentignite.com/api-reference/[in-progress]-integrationmapping/integration:idmapping.md): Fetches general itengration info and the ad stack field schema for the given integration, schema is in JSON-schema format
- [/integration/:id/mapping](https://docs.contentignite.com/api-reference/[in-progress]-integrationmapping/integration:idmapping-1.md): Fetches general itengration info and the ad stack field schema for the given integration, schema is in JSON-schema format
- [/integration](https://docs.contentignite.com/api-reference/[in-progress]-integration/integration.md): Fetches a list of integrations that are connected into the logged in organisation
- [/integration/completeness](https://docs.contentignite.com/api-reference/[in-progress]-integration/integrationcompleteness.md): Fetches general itengration info and the ad stack field schema for the given integration, schema is in JSON-schema format
- [/integration/:id/validate](https://docs.contentignite.com/api-reference/[in-progress]-integration/integration:idvalidate.md): Fetches general itengration info and the ad stack field schema for the given integration, schema is in JSON-schema format
- [/integration/:id/fields](https://docs.contentignite.com/api-reference/[in-progress]-integration/integration:idfields.md): Fetches general itengration info and the ad stack field schema for the given integration, schema is in JSON-schema format
- [/integration/:id/stack-schema](https://docs.contentignite.com/api-reference/[in-progress]-integration/integration:idstack-schema.md): Fetches general itengration info and the ad stack field schema for the given integration, schema is in JSON-schema format
- [/integration/:id/preview](https://docs.contentignite.com/api-reference/[in-progress]-integration/integration:idpreview.md): Preview how unsaved settings would change an integration’s figures for one mapped platform ID. Returns before/after totals; nothing is saved. Only works for modules that support previews (currently Google Analytics).
- [/account/branding](https://docs.contentignite.com/api-reference/[in-progress]-useraccount/accountbranding.md): Fetches branding for the refering domain
- [Changelog](https://docs.contentignite.com/change-log.md): Product updates and announcements
- [Releases](https://docs.contentignite.com/releases.md): Platform release notes
- [Mobile SDK Introduction](https://docs.contentignite.com/app/index.md): Monetise your Android, iOS and React Native apps with the Content Ignite Mobile SDK, powered by Fusion
- [Agent Skills](https://docs.contentignite.com/app/agent-skills.md): Let an AI coding agent integrate the Content Ignite Mobile SDK for you
- [Privacy & Consent (CMPs)](https://docs.contentignite.com/app/privacy.md): Why a TCF-certified Consent Management Platform is required for your mobile app integration
- [app-ads.txt](https://docs.contentignite.com/app/app-ads-txt.md): Authorising sellers of your app's ad inventory with app-ads.txt
- [Introduction (Android)](https://docs.contentignite.com/app/android/android_intro.md): Get started with your Android integration
- [Banner Ads (Android Compose)](https://docs.contentignite.com/app/android/android_banner_compose.md): Set up banner ads in an Android app built with Jetpack Compose
- [Banner Ads (Android View-Based)](https://docs.contentignite.com/app/android/android_banner_view_based.md): Set up banner ads in a view-based Android app
- [Interstitial Ads (Android)](https://docs.contentignite.com/app/android/android_interstitial.md): Set up interstitial ads in your Android app
- [App Open Ads (Android Compose)](https://docs.contentignite.com/app/android/android_app_open_compose.md): Set up app open ads in an Android app built with Jetpack Compose
- [App Open Ads (Android View-Based)](https://docs.contentignite.com/app/android/android_app_open_view_based.md): Set up app open ads in a view-based Android app
- [Migrate v1 to v2 (Android)](https://docs.contentignite.com/app/android/android_migrate_v1_to_v2.md): Upgrade the Content Ignite Android SDK from v1 to v2
- [Debug Features (Android)](https://docs.contentignite.com/app/android/debugging.md): Use the debug gesture and test ads to troubleshoot ads in your Android app
- [Introduction (iOS SwiftUI)](https://docs.contentignite.com/app/ios_swiftui/ios_swiftui_intro.md): Get started with your iOS (SwiftUI) integration
- [Banner Ads (iOS SwiftUI)](https://docs.contentignite.com/app/ios_swiftui/ios_swiftui_banner.md): Set up banner ads in an iOS app built with SwiftUI
- [Interstitial Ads (iOS SwiftUI)](https://docs.contentignite.com/app/ios_swiftui/ios_swiftui_interstitial.md): Set up interstitial ads in an iOS app built with SwiftUI
- [App Open Ads (iOS SwiftUI)](https://docs.contentignite.com/app/ios_swiftui/ios_swiftui_app_open.md): Set up app open ads in an iOS app built with SwiftUI
- [Debug Features (iOS SwiftUI)](https://docs.contentignite.com/app/ios_swiftui/debugging.md): Use the debug gesture and test ads to troubleshoot ads in your SwiftUI app
- [Introduction (iOS UIKit)](https://docs.contentignite.com/app/ios_uikit/ios_uikit_intro.md): Get started with your iOS (UIKit) integration
- [Banner Ads (iOS UIKit)](https://docs.contentignite.com/app/ios_uikit/ios_uikit_banner.md): Set up banner ads in an iOS app built with UIKit
- [Interstitial Ads (iOS UIKit)](https://docs.contentignite.com/app/ios_uikit/ios_uikit_interstitial.md): Set up interstitial ads in an iOS app built with UIKit
- [App Open Ads (iOS UIKit)](https://docs.contentignite.com/app/ios_uikit/ios_uikit_app_open.md): Set up app open ads in an iOS app built with UIKit
- [Debug Features (iOS UIKit)](https://docs.contentignite.com/app/ios_uikit/debugging.md): Use the debug gesture and test ads to troubleshoot ads in your UIKit app
- [Introduction (React Native)](https://docs.contentignite.com/app/react_native/react_native_intro.md): Get started with your React Native integration
- [Banner Ads (React Native)](https://docs.contentignite.com/app/react_native/banner.md): Set up banner ads in your React Native app
- [Interstitial Ads (React Native)](https://docs.contentignite.com/app/react_native/interstitial.md): Set up interstitial ads in your React Native app
- [App Open Ads (React Native)](https://docs.contentignite.com/app/react_native/app-open.md): Set up app open ads in your React Native app
- [Debug Features (React Native)](https://docs.contentignite.com/app/react_native/debugging.md): Use the debug gesture and test ads to troubleshoot ads in your React Native app
- [CMP Guide](https://docs.contentignite.com/getting-started/cmp-guide.md): Your guide to Consent Management Platforms
- [Glossary](https://docs.contentignite.com/guide/glossary.md): Definitions of the metrics, terms and acronyms used in Fusion
- [Fusion Pro Tips](https://docs.contentignite.com/getting-started/top-tips.md): Now you are familiar with Fusion, how can you become a pro user?
- [/report](https://docs.contentignite.com/api-reference/reportingrevenue-reports/report.md): Lists the custom revenue reports saved in your organisation. Run one with `/v1/report/{id}/data`
- [/report](https://docs.contentignite.com/api-reference/reportingrevenue-reports/report-1.md): Creates a user defined report with the given fields and filters. Call /report/filters for possible filter values
- [/report/:id](https://docs.contentignite.com/api-reference/reportingrevenue-reports/report:id.md): The saved set-up of one custom revenue report (fields, filters and date range), not its results
- [/report/:id](https://docs.contentignite.com/api-reference/reportingrevenue-reports/report:id-1.md): Update a reports config
- [/report/:id](https://docs.contentignite.com/api-reference/reportingrevenue-reports/report:id-2.md): Delete a report
- [/report/filters](https://docs.contentignite.com/api-reference/reportingrevenue-reports/reportfilters.md): Lists the values available as filters in custom revenue reports, such as publishers, partners, countries and devices
- [/report/:id/data](https://docs.contentignite.com/api-reference/reportingrevenue-reports/report:iddata.md): Runs a saved custom revenue report and returns its rows. The columns depend on the report.
- [/report/experiment](https://docs.contentignite.com/api-reference/reportingexperiment-reporting/reportexperiment.md): Lists experiments, which split a site's traffic between ad unit configs to see which earns more, with their status. Experiments that ended over two weeks ago are left out
- [/report/experiment/:id](https://docs.contentignite.com/api-reference/reportingexperiment-reporting/reportexperiment:id.md): Results of one experiment: each config's daily performance, traffic share and RPM, and which config is winning
- [/report/campaign](https://docs.contentignite.com/api-reference/reportingcampaign-reports/reportcampaign.md): Lists ad server campaigns that have delivered in the last week, with their dates, publishers and status
- [/report/campaign/:id](https://docs.contentignite.com/api-reference/reportingcampaign-reports/reportcampaign:id.md): Delivery for one ad server campaign: impressions, clicks, CTR, spend and viewability, as totals, a daily trend and breakdowns by publisher, ad unit, creative size and device
- [/report/health-check](https://docs.contentignite.com/api-reference/reportinghealth-check/reporthealth-check.md): Lists health checks from the last 30 days. A health check is a dated review of a site with an overall score and recommendations
- [/v2/report/health-check/:uid/:id](https://docs.contentignite.com/api-reference/reportinghealth-check/v2reporthealth-check:uid:id.md): The full report for one health check: score, commentary on each area reviewed, comparison with similar sites and an action plan
- [/report/adstxt](https://docs.contentignite.com/api-reference/reportingadstxt/reportadstxt.md): The ads.txt status of every website publisher: whether the file was found, includes the platform's lines and is up to date
- [/report/adstxt/:uid](https://docs.contentignite.com/api-reference/reportingadstxt/reportadstxt:uid.md): The lines a publisher's ads.txt file must contain, and which are missing from its live file
- [/report/app-adstxt/:uid](https://docs.contentignite.com/api-reference/reportingadstxt/reportapp-adstxt:uid.md): The lines a publisher's app-ads.txt file must contain, and which are missing from its live file
- [/report/date-range](https://docs.contentignite.com/api-reference/reportingutility/reportdate-range.md): Converts a date range preset into the dates it covers today, with the previous period used for comparisons
- [/report/insight/ssp](https://docs.contentignite.com/api-reference/reportinginsights-hubssp-insights/reportinsightssp.md): Header bidding activity and bid revenue by SSP, or by ad unit, config, country or device, with the previous period for comparison
- [/report/insight/ssp/ssp-filter](https://docs.contentignite.com/api-reference/reportinginsights-hubssp-insights/reportinsightsspssp-filter.md): Lists the SSPs with bid activity in the period, for filtering `/v1/report/insight/ssp`
- [/report/insight/cwv](https://docs.contentignite.com/api-reference/reportinginsights-hubcore-web-vitals/reportinsightcwv.md): Daily Core Web Vitals (LCP, INP, CLS and FCP), with baselines that show how much advertising affects page speed. To compare with similar publishers, use `/v1/report/insight/benchmarking/cwv`
- [/report/insight/ads-txt](https://docs.contentignite.com/api-reference/reportinginsights-hubadstxt-insights/reportinsightads-txt.md): An audit of one publisher's current ads.txt or app-ads.txt file: errors, missing lines, direct and reseller lines by exchange, and whether it is up to date
- [/report/insight/live](https://docs.contentignite.com/api-reference/reportinginsights-hublive-insights/reportinsightlive.md): Near real-time activity for one publisher over the last 1 to 48 hours: ad loads, bids, tag errors and latency. For daily history, use `/v1/report/insight/metrics`
- [/report/insight/metrics](https://docs.contentignite.com/api-reference/reportinginsights-hubmetrics/reportinsightmetrics.md): Daily page impressions, ad unit loads, ad loads and misses, and ad impressions. Month and quarter grouping return daily averages, not totals
- [/report/insight/metrics/revenue](https://docs.contentignite.com/api-reference/reportinginsights-hubmetrics/reportinsightmetricsrevenue.md): Revenue and impressions over time, lined up against the previous period (and the same days a week earlier, for shorter ranges) to show whether performance is up or down
- [/report/insight/metrics/live-revenue](https://docs.contentignite.com/api-reference/reportinginsights-hubmetrics/reportinsightmetricslive-revenue.md): Hourly revenue for today so far, compared with yesterday and the same day last week, with a forecast for the rest of the day. Runs a few hours behind and leaves out some revenue sources
- [/report/insight/metrics/latency](https://docs.contentignite.com/api-reference/reportinginsights-hubmetrics/reportinsightmetricslatency.md): Daily page, tag, ad unit and ad latency at the 50th, 95th and 99th percentiles, weighted by traffic
- [/report/insight/diagnostics](https://docs.contentignite.com/api-reference/reportinginsights-hubdiagnostics/reportinsightdiagnostics.md): Daily consent outcomes (consent given, consent denied and no CMP found) alongside page impressions
- [/report/insight/diagnostics/:uid](https://docs.contentignite.com/api-reference/reportinginsights-hubdiagnostics/reportinsightdiagnostics:uid.md): A health check of one publisher covering consent, ad experience, tag errors and latency, viewability, ads.txt and integrations. Most figures are for yesterday
- [/report/insight/diagnostics/traffic/:uid](https://docs.contentignite.com/api-reference/reportinginsights-hubdiagnostics/reportinsightdiagnosticstraffic:uid.md): Daily page impressions from the ad tag next to page views from the publisher's analytics, with revenue, to check tag coverage against site traffic
- [/report/insight/revenue](https://docs.contentignite.com/api-reference/reportinginsights-hubrevenue-insights/reportinsightrevenue.md): Revenue and ad delivery over time, as totals and a date series.
- [/report/insight/revenue/dimension](https://docs.contentignite.com/api-reference/reportinginsights-hubrevenue-insights/reportinsightrevenuedimension.md): Revenue and ad delivery broken down by one dimension, such as publisher, ad unit type, country, device or partner.
- [/report/insight/revenue/totals](https://docs.contentignite.com/api-reference/reportinginsights-hubrevenue-insights/reportinsightrevenuetotals.md): Revenue totals for fixed periods (yesterday, this week, this month and the last 30 days), each with its previous period for comparison.
- [/report/insight/revenue-analytics](https://docs.contentignite.com/api-reference/reportinginsights-hubrevenue-analytics/reportinsightrevenue-analytics.md): Checks whether a publisher has an analytics integration connected. The other revenue analytics endpoints only return traffic figures when it is
- [/report/insight/revenue-analytics/overview](https://docs.contentignite.com/api-reference/reportinginsights-hubrevenue-analytics/reportinsightrevenue-analyticsoverview.md): Daily revenue alongside site traffic (page views, users and sessions) for one publisher, for revenue per page view, session or user. Needs a connected analytics integration
- [/report/insight/revenue-analytics/totals](https://docs.contentignite.com/api-reference/reportinginsights-hubrevenue-analytics/reportinsightrevenue-analyticstotals.md): Revenue and site traffic totals for one publisher over the date range, with fixed lookback periods. Send `isConnected` only when `/v1/report/insight/revenue-analytics` shows analytics is connected
- [/report/insight/demand-mix](https://docs.contentignite.com/api-reference/reportinginsights-hubdemand-mix/reportinsightdemand-mix.md): Revenue and impressions split by demand type (direct, programmatic, fallback) and by Plug&Play or SaaS demand. For a breakdown by partner, channel, advertiser or platform, use `/v1/report/insight/demand-mix/dimension`
- [/report/insight/demand-mix/dimension](https://docs.contentignite.com/api-reference/reportinginsights-hubdemand-mix/reportinsightdemand-mixdimension.md): Demand Mix figures broken down by partner, channel, advertiser or platform. Filter to specific values from `/v1/report/insight/demand-mix/dimension-filter` to get a date series for them
- [/report/insight/demand-mix/campaign](https://docs.contentignite.com/api-reference/reportinginsights-hubdemand-mix/reportinsightdemand-mixcampaign.md): Revenue and impressions per campaign over time, with where each campaign ran, its delivery dates, its demand source and whether it is live or complete
- [/report/insight/demand-mix/dimension-filter](https://docs.contentignite.com/api-reference/reportinginsights-hubdemand-mix/reportinsightdemand-mixdimension-filter.md): Lists the values of one Demand Mix dimension that can be used as filters on `/v1/report/insight/demand-mix/dimension`
- [/report/insight/benchmarking/ad-delivery](https://docs.contentignite.com/api-reference/reportinginsights-hubbenchmarking/reportinsightbenchmarkingad-delivery.md): Ad loads, fill, CTR and viewability for one publisher, compared with similar publishers (its cohort) and the network. For figures without a comparison, use `/v1/report/insight/revenue`
- [/report/insight/benchmarking/ad-density](https://docs.contentignite.com/api-reference/reportinginsights-hubbenchmarking/reportinsightbenchmarkingad-density.md): Mobile ad density and heavy ad interventions for one publisher, compared with similar publishers (its cohort) and the network
- [/report/insight/benchmarking/ads-txt](https://docs.contentignite.com/api-reference/reportinginsights-hubbenchmarking/reportinsightbenchmarkingads-txt.md): Ads.txt health for one publisher, such as direct and reseller lines, compared with similar publishers (its cohort) and the network. Based on the latest crawl, not a date range
- [/report/insight/benchmarking/cmp](https://docs.contentignite.com/api-reference/reportinginsights-hubbenchmarking/reportinsightbenchmarkingcmp.md): Consent outcomes for one publisher, compared with similar publishers (its cohort) and the network
- [/report/insight/benchmarking/cwv](https://docs.contentignite.com/api-reference/reportinginsights-hubbenchmarking/reportinsightbenchmarkingcwv.md): Core Web Vitals for one publisher, compared with similar publishers (its cohort) and the network. For CWV without a comparison, use `/v1/report/insight/cwv`
- [/report/insight/benchmarking/latency](https://docs.contentignite.com/api-reference/reportinginsights-hubbenchmarking/reportinsightbenchmarkinglatency.md): Page, tag, ad unit and ad latency for one publisher, compared with similar publishers (its cohort) and the network. For latency over time, use `/v1/report/insight/metrics/latency`
- [/report/insight/benchmarking/revenue](https://docs.contentignite.com/api-reference/reportinginsights-hubbenchmarking/reportinsightbenchmarkingrevenue.md): Programmatic revenue, impressions and eCPM for one publisher, compared with similar publishers (its cohort) and the network. Counts programmatic channels only, so totals differ from `/v1/report/insight/revenue`
- [/report/insight/benchmarking/revenue-dimension](https://docs.contentignite.com/api-reference/reportinginsights-hubbenchmarking/reportinsightbenchmarkingrevenue-dimension.md): Programmatic revenue benchmarks for one publisher, broken down by one dimension such as country, device or partner
- [/report/insight/benchmarking/ssps](https://docs.contentignite.com/api-reference/reportinginsights-hubbenchmarking/reportinsightbenchmarkingssps.md): Header bidding results per SSP for one publisher (bid rate, win rate and bid value), compared with similar publishers (its cohort) and the network
- [/report/insight/benchmarking/ssp-overview](https://docs.contentignite.com/api-reference/reportinginsights-hubbenchmarking/reportinsightbenchmarkingssp-overview.md): Header bidding results across all SSPs for one publisher, compared with similar publishers (its cohort) and the network. For each SSP separately, use `/v1/report/insight/benchmarking/ssps`
- [/report/insight/benchmarking/publisher-info](https://docs.contentignite.com/api-reference/reportinginsights-hubbenchmarking/reportinsightbenchmarkingpublisher-info.md): The IAB categories a publisher has been assigned. Publishers sharing a category form its cohort in the benchmarking endpoints
- [/report/dash/stats](https://docs.contentignite.com/api-reference/reporting/reportdashstats.md): Dashboard summary for fixed periods: headline revenue, 30-day CTR and viewability, a 30-day trend, and top, rising and falling publishers. For other periods, use `/v1/report/insight/revenue`
- [/organisation/:id/mapping](https://docs.contentignite.com/api-reference/organisationorganisation-meta/organisation:idmapping.md): Fetches all integrations that suport organisation mapping, the schemas and the data for each
- [/organisation/:id/roles](https://docs.contentignite.com/api-reference/organisationorganisation-meta/organisation:idroles.md): Returns a list of users that have access to the given organisation
- [/organisation/:id/pricing](https://docs.contentignite.com/api-reference/organisationpricing/organisation:idpricing.md): Returns a list of pricing rules; data based periods of pricing settings made up of tech/saas fees, demand revenue shares and fixed fees
- [/organisation/:id/pricing](https://docs.contentignite.com/api-reference/organisationpricing/organisation:idpricing-1.md): Create a new pricing period. New period must be in the future to be valid
- [/organisation/:id/pricing/:pid](https://docs.contentignite.com/api-reference/organisationpricing/organisation:idpricing:pid.md): Updates a pricing period. Period must be in the future as historic or active periods can not be modified (create a new period if needed)
- [/organisation/:id/pricing/:pid](https://docs.contentignite.com/api-reference/organisationpricing/organisation:idpricing:pid-1.md): Deletes a pricing period, Period must be in the future as historic or active periods can not be modified
- [/organisation](https://docs.contentignite.com/api-reference/organisation/organisation.md): Returns a list containing the active organisation, and any child organisations
- [/organisation](https://docs.contentignite.com/api-reference/organisation/organisation-1.md): Creates a new child organisation under the currently logged in organisation
- [/organisation/:id](https://docs.contentignite.com/api-reference/organisation/organisation:id.md): Fetches a single organisation
- [/organisation/:id](https://docs.contentignite.com/api-reference/organisation/organisation:id-1.md): Updates an existing organisation
- [/organisation/:id](https://docs.contentignite.com/api-reference/organisation/organisation:id-2.md): Deletes a child organisation
- [/ad-stack/integration](https://docs.contentignite.com/api-reference/ad-stackintegration/ad-stackintegration.md): Fetches a list of integrations that could be used to build an ad stack under the given publisher
- [/ad-stack/integration/:type/:id](https://docs.contentignite.com/api-reference/ad-stackintegration/ad-stackintegration:type:id.md): Fetches an individual integration, The response includes everything needed to configure that integration within an ad stack, such as the schema for any config fields
- [/ad-stack/integration/:type/:id](https://docs.contentignite.com/api-reference/ad-stackintegration/ad-stackintegration:type:id-1.md): Validate the configuration of a given integration. Each integrations requirements vary, so use this endpoint to check all requirements have been met
- [/ad-stack](https://docs.contentignite.com/api-reference/ad-stack/ad-stack.md): Fetches a list of ad stacks in use by the provided publisher
- [/ad-stack](https://docs.contentignite.com/api-reference/ad-stack/ad-stack-1.md): Creates a new ad stack. Call the `/v1/integration?target=ad_stack` endpoint to find available integrations, and call the `/v1/integration/{id}/stack-schema` endpoint to find the field requirements for each integration.
- [/ad-stack/:id](https://docs.contentignite.com/api-reference/ad-stack/ad-stack:id.md): Gets an individual ad stack and all the integrations connected to it
- [/ad-stack/:id](https://docs.contentignite.com/api-reference/ad-stack/ad-stack:id-1.md): Updates an existing ad stack. Call the `/v1/integration?target=ad_stack` endpoint to find available integrations, and call the `/v1/integration/{id}/stack-schema` endpoint to find the field requirements for each integration.
- [/ad-stack/:id](https://docs.contentignite.com/api-reference/ad-stack/ad-stack:id-2.md): Deletes the given ad stack
- [/pub-stack/:uid/integration](https://docs.contentignite.com/api-reference/publisherpublisher-stack/pub-stack:uidintegration.md): Fetches a list of publisher level integrations that could be connected to the given publisher
- [/pub-stack/:uid/integration](https://docs.contentignite.com/api-reference/publisherpublisher-stack/pub-stack:uidintegration-1.md): Creates an association between a publisher and a publisher level integration (adding it to the "Pub stack")
- [/pub-stack/:uid/integration/:id](https://docs.contentignite.com/api-reference/publisherpublisher-stack/pub-stack:uidintegration:id.md): Fetches the field schema and data for a single connected integration
- [/pub-stack/:uid/integration/:id](https://docs.contentignite.com/api-reference/publisherpublisher-stack/pub-stack:uidintegration:id-1.md): Updates an existing integration association
- [/pub-stack/:uid/integration/:id](https://docs.contentignite.com/api-reference/publisherpublisher-stack/pub-stack:uidintegration:id-2.md): Deletes the assosication between the publisher and an integration
- [/tag/:uid/email/preview](https://docs.contentignite.com/api-reference/publisherpublisher-tag/tag:uidemailpreview.md): Provides an email template for onboarding a publisher. It contains the tag that needs to be deployed and the ads.txt requirents
- [/tag/:uid/status](https://docs.contentignite.com/api-reference/publisherpublisher-tag/tag:uidstatus.md): Fetches the status of the publisher tag and the app sdk for the given publisher
- [/publisher/:uid/stats](https://docs.contentignite.com/api-reference/publisherpublisher-meta/publisher:uidstats.md): Daily tag activity for one publisher over the last 30 days, including today: ad loads and misses, page impressions, tag errors, consent outcomes and latency
- [/publisher/:uid/status](https://docs.contentignite.com/api-reference/publisherpublisher-meta/publisher:uidstatus.md): Provides the onboarding tasks for the given publisher, and their status
- [/publisher/:uid/owners](https://docs.contentignite.com/api-reference/publisherpublisher-meta/publisher:uidowners.md): Fetch a list of organisations that are in the owner hierachy of the given publisher, useful for populating the O&O (Owned & Operated) field on the publisher
- [/publisher/:uid/overview](https://docs.contentignite.com/api-reference/publisherpublisher-meta/publisher:uidoverview.md): Returns the top level configuration for the given publisher
- [/publisher/:uid/mapping](https://docs.contentignite.com/api-reference/publisherpublisher-meta/publisher:uidmapping.md): Returns the top level configuration for the given publisher
- [/publisher/:uid/completeness](https://docs.contentignite.com/api-reference/publisherpublisher-meta/publisher:uidcompleteness.md): Returns the top level configuration for the given publisher
- [/tag/:uid/experiment](https://docs.contentignite.com/api-reference/publisherexperiment/tag:uidexperiment.md): Returns a list of experiments for a given publisher
- [/tag/:uid/experiment](https://docs.contentignite.com/api-reference/publisherexperiment/tag:uidexperiment-1.md): Creates an experiment, where 2 or more configs are run against one another
- [/tag/:uid/experiment/:id](https://docs.contentignite.com/api-reference/publisherexperiment/tag:uidexperiment:id.md): Get the configuration for a given experiment
- [/tag/:uid/experiment/:id](https://docs.contentignite.com/api-reference/publisherexperiment/tag:uidexperiment:id-1.md): Updates an existing config. Actions are restricted for live experiments, to just modifying dates and the title & description
- [/tag/:uid/experiment/:id](https://docs.contentignite.com/api-reference/publisherexperiment/tag:uidexperiment:id-2.md): Terminates an experiment immediately
- [/tag/:uid/experiment/compare](https://docs.contentignite.com/api-reference/publisherexperiment/tag:uidexperimentcompare.md): Takes a list of configs, and returns the differences between them. Used before creating an experiment to confirm the bahavioural subject(s) that the experiment will be testing
- [/tag/:uid/experiment/:id/activate-winner](https://docs.contentignite.com/api-reference/publisherexperiment/tag:uidexperiment:idactivate-winner.md): Activates the winnning config of an experiment. This can be run upon completion, or during an experiment, where the experiment will be immmediately terminated
- [/tag/:uid/config](https://docs.contentignite.com/api-reference/publisherconfig-ad-unit/tag:uidconfig.md): Fetches the list of configs under the given publisher
- [/tag/:uid/config](https://docs.contentignite.com/api-reference/publisherconfig-ad-unit/tag:uidconfig-1.md): Creates a new config under the given publisher
- [/tag/:uid/config/:id](https://docs.contentignite.com/api-reference/publisherconfig-ad-unit/tag:uidconfig:id.md): Fetches a single publisher config (ad unit)
- [/tag/:uid/config/:id](https://docs.contentignite.com/api-reference/publisherconfig-ad-unit/tag:uidconfig:id-1.md): Updates and existing config
- [/tag/:uid/config/:id](https://docs.contentignite.com/api-reference/publisherconfig-ad-unit/tag:uidconfig:id-2.md): Deletes a config
- [/tag/:uid/config/:id/mapping](https://docs.contentignite.com/api-reference/publisherconfig-ad-unit/tag:uidconfig:idmapping.md): Fetches a single publisher config (ad unit)
- [/tag/:uid/placement](https://docs.contentignite.com/api-reference/publisherapp-placement/tag:uidplacement.md): Fetch a list of all app placements under the given publisher
- [/tag/:uid/placement](https://docs.contentignite.com/api-reference/publisherapp-placement/tag:uidplacement-1.md): Creates a new app placement
- [/tag/:uid/placement/:id](https://docs.contentignite.com/api-reference/publisherapp-placement/tag:uidplacement:id.md): Fetch the app placement from the given placement ID
- [/tag/:uid/placement/:id](https://docs.contentignite.com/api-reference/publisherapp-placement/tag:uidplacement:id-1.md): Updates an existing app placement
- [/tag/:uid/placement/:id](https://docs.contentignite.com/api-reference/publisherapp-placement/tag:uidplacement:id-2.md): Deletes the given app placement.
- [/publisher/:uid](https://docs.contentignite.com/api-reference/publisher/publisher:uid.md): Fetches all the publisher level settings for the given publisher
- [/publisher/:uid](https://docs.contentignite.com/api-reference/publisher/publisher:uid-1.md): Sets the publisher level configuration for the given publisher
- [/publisher/:uid](https://docs.contentignite.com/api-reference/publisher/publisher:uid-2.md): Permenantly archives the given publisher, this will stop the tag from serving ads
- [/publisher](https://docs.contentignite.com/api-reference/publisher/publisher.md): List all publishers under the loggedin organisation, and some top level configuration
- [/publisher](https://docs.contentignite.com/api-reference/publisher/publisher-1.md): Creates a new publisher from the given domain
- [/publisher/taxonomy](https://docs.contentignite.com/api-reference/publisher/publishertaxonomy.md): Lists the tags used to group publishers, from your organisation and the organisations in your account structure below it, with how many publishers carry each
- [/ai/activity/overview](https://docs.contentignite.com/api-reference/aiactivity/aiactivityoverview.md): Headline usage, cost and failure figures for Spark chat and AI summaries in the period, with a daily series, failure reasons, the pages questions come from, and the top organisations and users. Only available to admins. Results cover the organisations your account can access.
- [/ai/activity/trends](https://docs.contentignite.com/api-reference/aiactivity/aiactivitytrends.md): Cost, usage and adoption for fixed lookbacks (last 7 and 14 days, last week, month and quarter), each against the period before it, with this month's projected cost and a 14-day daily series. Every filter applies except the date range. Only available to admins. Results cover the organisations your a…
- [/ai/activity/conversations](https://docs.contentignite.com/api-reference/aiactivity/aiactivityconversations.md): Spark chats with activity in the period, with their questions, failures, tokens and cost. Only available to admins. Results cover the organisations your account can access.
- [/ai/activity/conversations/:id](https://docs.contentignite.com/api-reference/aiactivity/aiactivityconversations:id.md): Per-turn usage for one Spark chat. The chat's messages are not included. Only available to admins. Results cover the organisations your account can access.
- [/ai/activity/log](https://docs.contentignite.com/api-reference/aiactivity/aiactivitylog.md): The most recent Spark questions and AI summary generations, with their outcome, tokens and cost. Only available to admins. Results cover the organisations your account can access.
- [/ai/activity/users](https://docs.contentignite.com/api-reference/aiactivity/aiactivityusers.md): Users with AI activity in the period. Only available to admins. Results cover the organisations your account can access.
- [/ai/summaries](https://docs.contentignite.com/api-reference/ai/aisummaries.md): AI summaries for the period with their status, tokens, cost and every generation attempt. Only available to admins. Results cover the organisations your account can access.
- [/billing/invoice](https://docs.contentignite.com/api-reference/billinginvoice/billinginvoice.md): Fetches a list of invoices for the logged in organisation
- [/billing/invoice/:id](https://docs.contentignite.com/api-reference/billinginvoice/billinginvoice:id.md): Fetches a specific invoice
- [/audit-log](https://docs.contentignite.com/api-reference/audit-log/audit-log.md): Lists changes to the organisation’s setup, newest first: what changed, who changed it, when, and whether it was made directly or by an AI client. Only available to users with audit log access. Use `next_cursor` to load the next page.
- [/integration/:id/mapping](https://docs.contentignite.com/api-reference/[in-progress]-integrationmapping/integration:idmapping.md): Fetches general itengration info and the ad stack field schema for the given integration, schema is in JSON-schema format
- [/integration/:id/mapping](https://docs.contentignite.com/api-reference/[in-progress]-integrationmapping/integration:idmapping-1.md): Fetches general itengration info and the ad stack field schema for the given integration, schema is in JSON-schema format
- [/integration](https://docs.contentignite.com/api-reference/[in-progress]-integration/integration.md): Fetches a list of integrations that are connected into the logged in organisation
- [/integration/completeness](https://docs.contentignite.com/api-reference/[in-progress]-integration/integrationcompleteness.md): Fetches general itengration info and the ad stack field schema for the given integration, schema is in JSON-schema format
- [/integration/:id/validate](https://docs.contentignite.com/api-reference/[in-progress]-integration/integration:idvalidate.md): Fetches general itengration info and the ad stack field schema for the given integration, schema is in JSON-schema format
- [/integration/:id/fields](https://docs.contentignite.com/api-reference/[in-progress]-integration/integration:idfields.md): Fetches general itengration info and the ad stack field schema for the given integration, schema is in JSON-schema format
- [/integration/:id/stack-schema](https://docs.contentignite.com/api-reference/[in-progress]-integration/integration:idstack-schema.md): Fetches general itengration info and the ad stack field schema for the given integration, schema is in JSON-schema format
- [/integration/:id/preview](https://docs.contentignite.com/api-reference/[in-progress]-integration/integration:idpreview.md): Preview how unsaved settings would change an integration’s figures for one mapped platform ID. Returns before/after totals; nothing is saved. Only works for modules that support previews (currently Google Analytics).
- [/account/branding](https://docs.contentignite.com/api-reference/[in-progress]-useraccount/accountbranding.md): Fetches branding for the refering domain
- [Changelog](https://docs.contentignite.com/change-log.md): Product updates and announcements
- [Releases](https://docs.contentignite.com/releases.md): Platform release notes

## OpenAPI Specs

- [openapi](/openapi.json)

## Optional

- [Website](https://www.contentignite.com/)
- [Blog](https://www.contentignite.com/blog)
- [Website](https://www.contentignite.com/)
- [Blog](https://www.contentignite.com/blog)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.