Required Agreements

• TAG TrustNet Membership Agreement (signed with TAG)
• TAG TrustNet Licensing and Service Level Agreement (signed with Fiducia)

General Requirements

• SSPs are required to receive Verified by TAG status before applying for TAG TrustNet Membership.
• SSPs are required to support a log level data product available to its clients compliant with specifications set out below, specifically the ‘required’ fields.

Log Level Data Accessibility Requirements

• Log level data access should be provided to clients promptly upon request by the DSP seat owner.

• SSPs shall not prevent or delay its clients from accessing log level data, and support the goal of its ingestion into TAG TrustNet for analysis and/or sharing with third parties.

• Log level data files should be provided with comprehensive documentation with detailed descriptions of all data fields provided, required data dictionaries.

• Impression events should be reported in compliance industry guidelines, e.g. IAB begin to render:

  • Desktop Display Impression Measurement Guidelines-US

  • Digital Video Impression Measurement Guidelines 1.1

  • Mobile In-App Measurement Guidelines (MMTF Final v1.1)

Log Level Data Ingestion Automation (Optional)

• To simplify the activation of a SSPs log level data in TAG TrustNet for SSP clients, the SSP may support the following mechanism:

  • Upon a client’s request for a log level data feed enablement for an owned seat ID:

    • Start continuous upload of seat ID log files into TAG TrustNet Node Amazon S3 storage bucket provided by Fiducia, or
    • Enable seat ID log data in the data view shared with Fiducia Snowflake account using Snowflake Data Exchange;

  • Fiducia will configure a dedicated instance of TAG TrustNet Node for each SSP, which will automatically share provided SSP seat log level data with TAG TrustNet Nodes of DSP seat owners;

  • Data will be protected from unauthorised access end-to-end using encryption in transit and at rest.

Compliance with Data Protection Laws

• Log level data provided for ingestion into TAG TrustNet shall not include any Personal Data (as defined below) and, as such, should fall outside of the scope of any data protection laws, including, without limitation, the GDPR and the CCPA. All Personal Data, and any data fields which represent pseudonymous data, shall be removed from the data before it is ingested into TAG TrustNet. “Personal Data” means any information defined as “personal data,” “personal information,” “personally identifiable information,” “nonpublic personal information,” or other similar term under any applicable data protection laws.

Log Level Data Technical Requirements

The tables below list the type of data files required, the frequency, and format.

Technical Requirements

• SSP should not change data record contents in internal systems in a way that they will become out of sync with log level data provided to a client. If data restatement is required, then the seat owners and TAG TrustNet should be informed in a timely fashion so impression events can be reprocessed.

• Impression log file records and database records provided to a client are deemed immutable in TAG TrustNet for the purpose of ad delivery audit.

• Impression log file records should be included in the log files no later than 48 hours after the impression event. Any impression log file record delivered beyond this time limit will be ignored for the purpose of ad delivery audit in TAG TrustNet.

• Timestamps for impression events should be determined server-side using an authoritative time source.

• Timestamps should always be reported in UTC time zone.

• If impression records are reported via database (e.g. Snowflake), they should contain both the impression timestamp and timestamp of data record insertion into the log database.

• As part of SSP log file delivery, data dictionaries allowing the mapping of impression record data fields to their meaning should be provided at least every 24 hours.

• Reported seller IDs and buyer IDs should match respective records in sellers.json and buyers.json files.

• SSP should ensure that no impression records are filtered in log files due to technical or legal constraints and every delivered impression is reported. SSP should ensure that seller agreements allow this.

Required and Recommended Data Fields

The following table details the ‘required’ and ‘recommended’ fields for impression events, with references to the OpenRTB specs where appropriate.

Download Requirements

Download a copy of the requirements here: TAG TrustNet - Supply Side Platform Requirements v1.2.