@adcp/sdk API Reference - v14.3.0
    Preparing search index...

    Type Alias DAASTTrackerAsset

    DAASTTrackerAsset: {} & {
        asset_type: "daast_tracker";
        daast_event: DAASTTrackingEvent & {};
        url: MacroBearingURL8;
        macro_declarations?: [
            MacroDeclaration & { location?: { field?: "url" } },
            ...(MacroDeclaration & { location?: { field?: "url" } })[],
        ];
        offset?: string;
        target?: "linear" | "companion";
        provenance?: Provenance;
    }

    A single tracker URL bound to a DAAST TrackingEvents event. Audio-side analogue of vast-tracker-asset. The Impression URL MUST be modeled as a url asset with url_type: "tracker_pixel", not as a daast_tracker with daast_event: "impression".

    Type Declaration

      • asset_type: "daast_tracker"

        Discriminator identifying this as a DAAST tracker asset. See /schemas/creative/asset-types for the registry.

      • daast_event: DAASTTrackingEvent & {}

        The DAAST tracking event this URL fires on. MUST NOT be impression (model as url asset with url_type: "tracker_pixel"), clickTracking / customClick (click-tracking trackers go on their own URL asset), error, or any of the ViewableImpression-element children (viewable, notViewable, viewUndetermined, measurableImpression, viewableImpression).

      • url: MacroBearingURL8
      • Optionalmacro_declarations?: [
            MacroDeclaration & { location?: { field?: "url" } },
            ...(MacroDeclaration & { location?: { field?: "url" } })[],
        ]

        Exact tokens in url and their resolver/encoding contracts.

        1

      • Optionaloffset?: string

        DAAST offset attribute. Required when daast_event is progress (DAAST 1.1 §3.2.4.3); ignored otherwise for compatibility with existing 3.x manifests. Same format as VAST 4.2 Tracking@offset: HH:MM:SS or HH:MM:SS.mmm for absolute time (two-digit hours, minutes 00–59, seconds 00–59), or an integer percentage 0–100 suffixed with %. Negative offsets are NOT permitted.

      • Optionaltarget?: "linear" | "companion"

        Which DAAST creative element this tracker scopes to — linear for <Linear>/<TrackingEvents> (DAAST 1.1 §3.2.1.7), companion for <CompanionAds>/<Companion>/<TrackingEvents> (DAAST 1.1 §3.2.2.7). DAAST has no <NonLinearAds> element. Defaults to linear. Existing 3.x assets remain structurally permissive; a tracker execution contract applies the standards-valid event/target matrix when matching a creative to a product.

      • Optionalprovenance?: Provenance

      Settings
      Member Visibility