Skip to content

[Comment] § 2, § 5.2, § 5.6 — Support coordinated cross-media campaign packages #86

Open

Description

@clerongi

Which section?

1 — Preamble and scope

Field(s) involved

No response

Your comment

OpenProposal should explicitly support commercial offers combining multiple media channels into a coordinated advertising campaign.

For example, an OOH or DOOH campaign in public transport environments may be complemented by social media, mobile or display advertising to extend audience reach and reinforce campaign effectiveness.

Although OpenProposal supports multiple line items, it does not explicitly standardize all the commercial and operational relationships between channels within a coordinated campaign.

We recommend supporting:

Cross-media packages combining OOH, DOOH, social media, mobile and display.

Mandatory versus optional complementary media components.

Shared campaign objectives and coordinated activation periods.

Channel-specific budgets and overall package pricing.

Conditional discounts or pricing linked to combined media purchases.

Cross-media audience measurement and reporting references.

Explicit identification of the parties responsible for delivering each component.

This would allow buying agents to understand and compare integrated advertising offers rather than evaluating each media channel independently.

Concrete scenario

No response

You are commenting as

Publisher / seller

Before you submit

  • I have read CONTRIBUTING.md and agree my contribution may be published under this repository's licence.
  • This comment contains no confidential or commercially sensitive information.

Activity

  1. KonstantinMirin commented on Oct 22, 2026

    @KonstantinMirin

    Postindustria (IAB Tech Lab member) maps #86 to proposals already open:

    We suggest tracking #86 under #23.

    Open questions:

    1. Should this issue be tracked under line-item dependencies and bonus lines (#23), or stay open as the umbrella for cross-media packages, with that issue, cross-publisher composition (#28), and our commitment-set reply on line-item dependencies as its parts?
    2. Should a commitment set also state this issue's shared objective and coordinated activation period, for example by requiring aligned flights across its line items, or is each line item's own flight enough?
    3. Should proposal-level spend tiers (min_proposal_commitment) join the line-item dependencies draft PR (#70), attach to a commitment set as a minimum next to max_total, or stay out of 3.0?
    4. Should this issue's cross-media measurement and reporting references go to open question 3 on comparing guarantees across channels (#4), or to a separate open question on cross-media audience measurement?
    5. Should social and mobile stay display, native, or video line items on an app or site, as our channel definitions change request proposes, or get their own channel values?

    Analyzed and generated with the help of Claude, fully reviewed by me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions