Daily Report
This report is sent out daily, applicable for the previous day’s performance for that partner’s inventory on Skyscanner. A day is measured in GMT, starting at 0:00 and ending at 24:00. CPC ingestion and bounce times (when new CPCs are live) are independent of this reporting cycle. The report is delivered daily to partners via SFTP.
Information on Every Impression
We aim to provide partners with performance feedback based on every relevant impression of their inventory on Skyscanner. Data is made available for partners who have successfully submitted a dynamic CPC into our system (markets where legacy business models of CPA/flat CPC are still in effect do not receive this data), and when an impression is generated by a customer search on Skyscanner. The report reflects all movement of partner offers due to auction promotion logic, rotation logic, and other levers to increase or decrease prominence.
Report Contents
- Search Date
a. Descriptor variable
b. Column heading: search_date
c. In brief: when a customer conducts a car hire search, that generates impressions on partner-supplied inventory. The search date that the customer made this search on is recorded as ‘search_date’ and aggregated along with other customers who made a search with that same grouping reported. Data is only aggregated and sent once per day; thus, only 24 hours of activity would be sent in this report.
d. Time zone for calculation is Greenwich Mean Time (GMT)
e. Value is in YYYY-MM-DD format (for example, 2026-04-22)
2. Partner Name
a. Descriptor variable
b. Column heading: partner_name
c. In brief: partners will only receive data on their own groupings. Thus, the only name they’ll see here is the name they registered with Skyscanner
d. Values is a string (for example: ‘Partner 1’).
3. Grouping
a. c. Descriptor variable (used only for easy partner reference)
b. Column heading: grouping
c. In brief: In order for partners to see clearly their data in the report, any grouping variables that have been both released to and utilised by the partner will be reported. In V01 of this report, we have market + platform, which constitute the only grouping variables available to partners in terms of setting CPCs dynamically. Over time this list of grouping variables may increase, but for this version we report only on market + platform.
d. Value is a string encompassing two grouping variables. For example: ‘uk_mobile’
4. Market
a. Grouping variable
b. Column heading: market
c. The market the customer searched from (customer configured or default).
d. Value is a two-letter market code, for example: ‘UK’
5. Platform
a. Grouping variable
b. Column heading: platform
c. The platform the customer was searching on. If the customer was using a desktop computer, we will label this ‘desktop’, and if the customer was using a mobile device, we will label this ‘mobile’
d. Value is a string, either ‘desktop’ or ‘mobile’
6. Average Rank
a. Performance metric
b. Column heading: avg_rank
c. Within the inventory card (a concept described in more detail in the Dynamic CPC Operations Guide’), partners are ranked therein according to certain factors. All inventory cards that had rendered impressions with the partner’s quotes are then averaged according to their rank. For example, if that grouping had two rendered impressions featuring the partner’s quotes, one with a rank of 1, and one with a rank of 3, the average rank value for that grouping would be 2.00
d. Value is a float, with two decimal places (rounded). For example, 1.53
7. Clicks
a. Performance metric
b. Column heading: clicks
c. The number of clicks received for that aggregation on that single-day reporting period
d. Value is a positive integer greater than or equal to zero.
8. Cost Per Click
a. Performance metric
b. Column heading: CPC
c. For this grouping, which the partner will have specified (described in more detail in the Dynamic CPC Operations Guide’), the CPC is then displayed for the partner in this column.
d. Value is a float greater than zero, with two decimal places. For example, 2.05
9. Currency
a. Performance metric
b. Column heading: currency
c. Partners can submit dynamic CPCs in the (supported and approved) currency of their choice. This currency value specified is populated in this report for each grouping.
d. Value refers to the 3-digit currency code (ISO 4217), for example, ‘usd’ for United States Dollar.
10. Group Total Clicks
a. Performance metric
b. Column heading: grouping_total_clicks
c. The number of clicks recorded during the reporting period for that grouping which was received by all partners.
d. Value is a positive integer greater than or equal to zero.
11. Cost
a. Performance variable
b. Column heading: cost
c. The sum of all costs from that grouping, in the currency submitted (and approved by Skyscanner) by that partner. The cost equals the total number of clicks for that aggregation times the number of clicks times the cost per click (CPC) for that reporting period. For example, if the grouping was in USD, and the CPC designated was $1.50, and the partner received two clicks, the total cost for that grouping would equal $3.00.
d. Value is a float with two decimal places (for example, 3.00)
12. Impression Rendered
a. Performance variable
b. Column heading: impressions_rendered
c. This defines how many car hire ‘cards’ were rendered using a customer-triggered search. We aggregate the total number of times that cards for that grouping were shown. If one customer in one market were to search one time on desktop, that would trigger 15 cards rendered. If they were to click to the next page or filter, another 15 cards would render (equalling now 30 ‘impressions rendered’). On mobile web and app, that value is 25 per unique search result page, up from 15.
d. Value is an integer, greater than or equal to zero.
13. Impressions Missed Due to Availability
a. Performance variable
b. Column heading: avail_impressions_missed
c. Every time the partner has not supplied a quote for that grouping, and a customer has searched for that grouping where that partner’s quote then was not included (a concept described in more detail in the ‘Dynamic CPC Operations Guide’), we will record and then aggregate the number of times this happened in this column. For example, if one customer searched for a grouping (for simplicity, uk_mobile), and the partner had quotes that were rendered for 10 of 25 total car results on that page, the value displayed in this column would be 15.
d. Value is an integer, greater than or equal to zero.
14. Average Price Difference (Percent)
a. Performance variable
b. Column heading: avg_price_difference_pct
c. Every time a partner’s quote is rendered for that grouping, we will record the displayed price. We will also record the lowest price for that grouping and calculate the average of price differences within that grouping and display it in the report accordingly. Negative values indicate that the partner was cheaper (on average for that grouping). For example, if the partner has one grouping where they were 90 GBP, where the next lowest partner had a price of 100 GBP . In the same grouping, a partner had a price of 100 USD, and it matched another partner’s price of 100 USD as the lowest; the value for this dimension in the report would equal -5.00.
d. Value is a float with two decimal places and can be positive or negative, indicating percentage. For example, ‘-15.55’ would correspond to a price advantage of 15.55%.
15. Beat Price Impressions
a. Performance variable
b. Column heading: beat_price_impressions
c. When a partner has a price in a grouping that is cheaper than its competitors in that grouping, we will consider this a ‘beat’ impression and record it here. Only ‘rendered’ impressions would count towards this value. For example, if the partner had 100 rendered impressions for that grouping, 10 of which were the cheapest price and 90 of which were not, we would show a value of 10 here.
d. Value is an integer, greater than or equal to zero.
16. Meet Price Impressions
a. Performance variable
b. Column heading: meet_price_impressions
c. When a partner has a price in a grouping that is tied for the lowest alongside competitors in that grouping, we will consider this a ‘meet’ impression and record it here. Only ‘rendered’ impressions would count towards this value. For example, if the partner had 100 rendered impressions for that grouping, 40 of which were tied for the cheapest price and 60 of which were not, we would show a value of 40 here.
d. Value is an integer, greater than or equal to zero.