Skip to main content
Sign in

Search

Flight Control Help Center

Ad Serving Logs

  • Updated

General

Ad serving logs or log files are non-aggregated granular ad engagement events data (such as impressions, clicks, etc.) captured throughout the creative ad-serving process - essentially the raw outputs of serving ad campaigns. Every event is represented as a new row of data attributes.

You can access ad-serving logs in Flight Control within Analytics > Data Outputs.

Clinch offers three types of ad-serving logs:

Type  Details  Use Cases 
Standard Ad Serving Logs  Raw log files that have not been enriched with additional 3rd party identifiers (only Clinch ID is presented). Use creative ad engagement data in your own BI dashboarding or insights tools.
Connected Ad Serving Logs  Log files enriched with third-party identifiers (e.g., LiveRamp, HEMs, MAIDs, etc). 

Onboard ad engagement data to your DMP, CDP, or media partner for improved audience building and/or media optimization.

Create custom attribution data models and offline attributions.
Ad Serving Logs to Media Partner
(DSP / Publisher)  		Log files that include the media partners' impression IDs for data-matching purposes.

Merge ad engagement creative attributes with media partner data attributes (For example: TTD's Creative Variant Reporting) for a more comprehensive analysis.
 

For further information, see Media Performance Data.

You can view the list of all available dimensions for Ad Serving Logs here.

Note: Log-level reporting is a premium service and incurs additional costs.

image.png Prerequisites

  • If requesting Standard Logs for Media Performance data from a media partner, such as the Trade Desk's Creative Variant Reporting (CVR), the following services must be included in your Clinch MSA:
    • Ad Serving Logs to Media Partner
    • Processing of Media Performance Data.
  • Note: Approvals will be needed from both Clinch and the media partner to enable sending log files to the media partner for ingestion.
  • For Connected Logs, cookie syncs need to be enabled with the specific data partner for the account.

Creating Ad Serving Logs

Standard Ad Serving Logs

  1. Create a support ticket (at Help > Open Support Ticket) requesting a log-level impression data output, and provide the following information in the ticket:
    • Clinch Account ID(s) and Account Name(s)
    • Specify where the log-level reports should be sent -
      • your preferred cloud storage for log-level reporting (such as an Amazon S3 bucket or Google Cloud Platform storage). Clinch would need access to the cloud storage. (recommended)
      • or Clinch Temporary Storage
    • Specify how frequently the data would need to be refreshed -
      • Once Per Day, early morning UTC (recommended)
      • Once Per Hour

Once created, the data output will be located in Analytics > Data Outputs.

Note: This process takes an estimated 7 business days.

Ad Serving Logs to Media Partner (for Media Performance Data)

  1. Create a support ticket (at Help > Open Support Ticket) requesting a log-level impression data output, and provide the following information in the ticket:
    • The Media Partner ID (e.g., The Trade Desk Advertiser ID for TTD Creative Variant Reporting)
    • Clinch account ID(s) and name(s)
    • Start date (the date the first log should be dropped)
      • Right now
      • Provide a future date

Once created, the data output will be located in Analytics > Data Outputs, and Clinch will share the new S3 path that has been created for your specified media partner ID.

Note: This process takes an estimated 5 business days for TTD to activate the new path for Creative Variant Report (CVR) and an estimated 7 business days for Clinch to set up a new path for the CVR data.

Note: While Clinch can back-date data, the media partner may not. Therefore, it is recommended to send requests several days before campaign(s) are to start, to avoid receiving partial campaign data, starting the day of the first log file drop. For example, if you are starting a campaign on April 1st, submit the ticket at least a week before April 1st.

Note: If you're receiving log files from media partners while also using a content feed in your account, ensure that the content feed doesn't contain the "|" special character in its naming structure, as this will prevent proper data mapping within The Trade Desk.

Connected Ad Serving Logs

  1. Create a support ticket (at Help > Open Support Ticket) requesting a log-level impression data output, and provide the following information in the ticket:
    • Clinch account ID(s) and name(s)
    • Start date (the date the first log should be dropped)
      • Right now
      • Provide a future date
    • External accounts/identifiers to connect - for example, Merkury, LiveRamp, TTD, etc.

Once created, the data output will be located in Account > Data Outputs, and Clinch will share the specific path name with the specific data team that will be ingesting these log files.

Note: This process takes an estimated 7 business days.