Metrics
The counts reported in Fusion, and the rates worked out from them, calculated the same way as in Fusion’s reports| Term | Definition |
|---|---|
| Ad Impressions | The total number of rendered Ad Impressions on-page. Each “Ad Unit Load” can see more than one “Ad Impression” because of Fusions “Ad Refresh” technology |
| Ad Load Rate | The share of the Fusion tag’s ad requests that returned an ad: Ad Loads ÷ (Ad Loads + Ad Misses) |
| Ad Loads and Ad Misses | Ad requests that did and didn’t return an ad, counted by the Fusion tag itself. Shown on the Metrics and Live pages |
| Ad Requests | Each time an ad unit asks the ad server for an ad |
| Ad Responses | Ad requests the ad server answered with an ad, from ad server reporting |
| Ad Server Fill | The share of ad requests the ad server answered with an ad: Ad Responses ÷ Ad Requests. It leaves out what happens after the ad server responds, so it reflects bidding and win rates. A low figure can point to floor prices that are too high |
| Ad Unit Loads | Each time an ad unit’s target is found on the page and the unit is ready to serve. In-view units only request an ad once scrolled into view, so Ad Unit Loads can be higher than Ad Requests. Sometimes called ad opportunities |
| Bid Rate | The share of bid requests that received a bid: Bids ÷ Bid Requests |
| Clicks | The number of times users have clicked on a digital advertisement to reach an online property |
| Cohort | In benchmarking, the other publishers that share at least one IAB category with the publisher. Values are averages per publisher |
| Consent Rate | The share of consent checks where the visitor gave consent: Consent Given ÷ (Consent Given + Consent Denied + No CMP Found) |
| CPM | Cost per mille, revenue per 1,000 ad impressions: Revenue ÷ Ad Impressions × 1,000. Fusion shows it as eCPM (gross) or eRPM (net) |
| CTR | Click-through rate, the share of ad impressions that were clicked: Clicks ÷ Ad Impressions. Usually shown as a percentage |
| eCPM | Gross revenue per 1,000 ad impressions: Gross Revenue ÷ Ad Impressions × 1,000 |
| eRPM | Net revenue per 1,000 ad impressions: Net Revenue ÷ Ad Impressions × 1,000 |
| Fill | The share of ad requests that led to an ad impression: Ad Impressions ÷ Ad Requests. This is the Fill shown on the Revenue Insights, Demand Mix and Benchmarking pages. See also “Ad Server Fill” and “Unit Fill” |
| GIVT Rate | Rate of general invalid traffic over entire traffic |
| Gross eCPM | Gross revenue per 1,000 ad impressions: Gross Revenue ÷ Ad Impressions × 1,000. Shown in Fusion as eCPM |
| Gross Revenue | The gross amount Content Ignite are paid for each Ad Impression |
| Gross RPM | Gross revenue per 1,000 ad unit loads: Gross Revenue ÷ Ad Unit Loads × 1,000 |
| Heavy Ad Intervention Rate | Heavy ad interventions per page: Heavy Ad Interventions ÷ Page Impressions. A heavy ad intervention is when the browser removes an ad for using too much CPU or network |
| IVT Rate | Rate of invalid traffic over entire traffic |
| Mobile Ad Density | The median share of a mobile page taken up by ads, counting every ad on the page |
| Net eCPM | Net revenue per 1,000 ad impressions: Net Revenue ÷ Ad Impressions × 1,000. Shown in Fusion as eRPM |
| Net Revenue | The publisher’s share of Gross Revenue after Content Ignite’s fees. For Plug & Play revenue: Gross Revenue ÷ 100 × Net Revenue Share. For SaaS revenue, the SaaS fee is charged per 1,000 impressions: Gross Revenue − (SaaS eCPM Fee × Ad Impressions ÷ 1,000) |
| Net Revenue Share | The Publisher’s share of the “Gross Revenue”. If the Publisher has a “Customer Revenue Share” of 80% and “Gross Revenue” equals £100, the Publisher will receive 80% of the £100 = £80 |
| Net RPM | Net revenue per 1,000 ad unit loads: Net Revenue ÷ Ad Unit Loads × 1,000 |
| Network | In benchmarking, all other benchmarked publishers on the platform. Values are averages per publisher |
| Page Impressions | Pages the Fusion tag loaded on |
| Page RPM or PageView RPM | Revenue per 1,000 page views: Revenue ÷ Page Views × 1,000 |
| PageViews | Page views from the publisher’s analytics integration, such as Google Analytics. Not the same as Page Impressions |
| RPM | Revenue per mille: revenue per 1,000 of whatever is named, such as Page RPM (per 1,000 page views) or Session RPM (per 1,000 sessions). eRPM on its own is net revenue per 1,000 ad impressions |
| Session RPM | Revenue per 1,000 sessions: Revenue ÷ Sessions × 1,000 |
| SIVT Rate | Rate of sophisticated invalid traffic over entire traffic |
| Tag Error Rate | Tag errors per page: Tag Errors ÷ Page Impressions |
| Throttle Rate | The share of bid opportunities held back by bid throttling: Throttled Bid Requests ÷ (Bid Requests + Throttled Bid Requests) |
| Unfilled Impressions | Unfilled Impressions (only tracked if enabled) |
| Unit Fill | Ad responses per ad unit load, a measure of opportunity: Ad Responses ÷ Ad Unit Loads. It can go over 100% when ad refresh is on |
| Viewability | The share of ad impressions that were viewable: Viewable Impressions ÷ Ad Impressions. Following the MRC standard, an ad is viewable when at least 50% of its pixels are on screen for at least one second |
| Win Rate | The share of bids that won the impression: Won Bids ÷ Bids |
Terms and acronyms
| Term | Definition |
|---|---|
| Ad Products | The ads containers that get inserted onto the page by the “Fusion Tag” such as In-Image or Adhesion that display an “Advert” |
| Ad Refresh | The reload of an advertising unit without reloading the whole page. This lets Publishers gather more impressions when users remain on their pages |
| Ad Usage | For self-serve publishers, they will be billed on either on ‘Ad Unit Load’ (when a target is found and an ad unit is triggered on page) or ‘Ad Requests’ (when an ad is requested from the ad server). The publisher, if a self-serve publisher, will be billed on whichever of ‘Ad Unit Loads’ and ‘Ad Requests’ is higher at month-end, which therefore is defined as ‘Ad Usage’ and this ‘Ad Usage’ figure will be taken from Platform reporting |
| Ads.txt | A text file that lists companies authorised to sell a publisher’s digital ad inventory that sits on the root domain for e.g. example.com/ads.txt |
| Advert | A clickable image or link to content to be displayed on a Website |
| Advertiser | The person or company who is ultimately responsible for placing the advertising content that appears via a Content Ignite solution |
| Browser Cache | Browser cache stores website data like images and scripts to speed up future page loads, reducing load times and bandwidth usage. |
| Consent Management Provider / Platform (CMP) | A tool that helps websites collect and manage user consent that is required for processing their personal data. Personalised ads can not be served without this |
| Content | Editorial content and/or advertising selected by an Advertiser (or prepared by Content Ignite on an Advertiser’s behalf) and which appears on an Advertiser’s website or any third party websites, including any operated by Advertiser |
| Content Ignite’s Fusion platform | https://admin.contentignite.com - where publishers take control of on-page monetisation, ad technology and ad management. |
| Contextual | AI crawls publisher pages, builds entity lists, and integrates them into GAM via the audience builder for targeted advertising, all without cookies or user tracking. |
| Contextual Usage | If the Customer chooses to use Fusions Contextual Targeting technology, the Customer will be charged a crawl-per-page charge each time the Content Ignite technology logs a URL it hasn’t seen before. |
| DSP | Demand Side Platform |
| Floor Price | Floor price is the minimum price set for ad inventory in programmatic advertising, ensuring that ads are not sold below this value to maintain revenue standards. |
| GAM | Google Ad Manager |
| GAM_WR | gam_wr refers to ‘Google Manager with Reporting’ which is the type of integration we have and is set when adding an instance of GAM to Fusion. |
| GTM | Google Tag Manager |
| Managed Ad Operations Monthly Minimum Fee | The fee that the Customer pays to Content Ignite for Ad Operations and Trafficking services if required |
| MCM | Multiple Customer Management |
| MSA | Master Service Agreement |
| Page Cache | Page cache speeds up web response times by storing webpage outputs and serving them from cache, reducing the need for repeated data processing and server requests. |
| Platform | The Content Ignite Fusion platform where a Publisher manages website ad products, reporting and billing |
| Plug & Play | A Publisher that includes the Fusion Publisher Tag and Ad Products onto page and Content Ignite solely monetising all available Publisher Inventory |
| Programmatic Advertising | the automated process of buying and selling digital ad space. |
| Programmatic, Direct and Fallback | The demand types on the Demand Mix page. Programmatic is Ad Exchange, Open Bidding, Header Bidding and AdSense. Direct is ad server line items that aren’t house or fallback. Fallback is house line items and the fallback channel |
| Publisher | The owner of a Website or multiple Websites |
| Publisher Inventory | A space for Adverts on the Websites |
| Publisher Tag | The script tag that is placed onto the Publishers Website which generates an “Advert” via “Ad Products” |
| RFI | Request for Information |
| RFP | Request for Proposal |
| SaaS | A Publisher that includes our Fusion “Publisher Tag” and “Ad Products” onto page and pays a fee rather than getting a Revenue Share |
| SDK | Software Development Kit |
| SLA | Service Level Agreement |
| SSP | Supply Side Platform |
| STUB | A CMP stub is a lightweight piece of code that initiates the Consent Management Platform process, enabling compliance with privacy regulations by managing user consent preferences effectively. |
| Supplier | The company or person that Content Ignite has agreements with to provide advertising via the Content Ignite Products |
| TAM | Amazon’s Transparent Ad Marketplace |
| Video Creation | If the Customer chooses to auto-generate videos in the ‘Video Config’ section of the Platform instead of uploading video, there is an applied charge for each generated video |
| Video Serving | If the Customer chooses to auto-generate or upload videos in the ‘Video Config’ section of the Platform, a Video Serving charge will be applied at a cost per thousand (CPM) rate |
Core Web Vitals
Page speed measures. Fusion’s tag records LCP, INP, CLS and FCP, shown on the Core Web Vitals page| Term | Definition |
|---|---|
| CLS | Cumulative Layout Shift. How much the page layout moves unexpectedly during a visit, such as content jumping when an ad appears. A score with no unit |
| FCP | First Contentful Paint. The time until the first text or image appears on the page |
| FID | First Input Delay. The delay before the page responds to a visitor’s first interaction. Replaced by INP as a Core Web Vital in March 2024 |
| INP | Interaction to Next Paint. How quickly the page responds visibly to clicks, taps and key presses throughout a visit |
| LCP | Largest Contentful Paint. The time until the largest image or block of text in view has loaded, a measure of when the main content appears |
| TTFB | Time to First Byte. The time until the browser receives the first byte of the page from the server |