Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Proposal for Consent and Measurement #17

Open
nickvenezia opened this issue Nov 16, 2023 · 4 comments · May be fixed by #73
Open

New Proposal for Consent and Measurement #17

nickvenezia opened this issue Nov 16, 2023 · 4 comments · May be fixed by #73
Assignees

Comments

@nickvenezia
Copy link

nickvenezia commented Nov 16, 2023

Field Description
API family name "Consent & Measurement"
API family owner Centillion
API summary The “Consent & Measurement” API suite is designed to provide the inputs necessary to power the world's digital ecosystem. From fueling insights for audience planning, measuring ad exposure, along post campaign validation and audience contextual and behavioral lift measurement, Auditing of AI and LLM usage. The Measurement APIs are designed to integrate with leading enterprises needing consent for AI, ad tech companies both on the Sell Side (SSPs, DOOH, CTV, Publishers etc.) and the Buy Side (DSPs, Agency Trading Desks) and use the Mobile Network Operators (MNOs) as the digital backbone of the ad-tech and AI in the 'measurement' space. Leveraging the geospatial capabilities of the "CAMARA device location", natively integrated with a specific advertiser focused privacy/consent by design and ad-fraud free approach, this new technologythese innovative inputs will streamline the $674B industry. The CAMARA capabilities are a natural enhancement to provide measurement lift in physical retail and along with digital out of home device exposure (Rideshares, billboards, Points of interest). Leveraging conversion signals from "CarrierBillingCheckOut" (Purchase/digital transaction/click to call) enables both physical and digital transaction impact measurement, tying mobile device to ad exposure to audience behavior to business objectives. CAMARA's commitment to interoperability and compliance with industry standards is a testament to its dedication to providing a transparent ad-tech measurement and advertiser consent verification framework.
Technical viability The "Consent & Measurement" API family provides validated technical integrations with next generation ad tech and AI infrastructure, mass adoption potential with emerging industry standards, such as the Interactive Advertising Bureau (IAB) Tech Lab's. For MNOs and developers, this offers a path to long term viability, new revenue, and compliance across jurisdictions. By leveraging the scale of a standardized federated deployment, MNOs can reclaim revenue back from the tech industry that has created immense value on the back of the telecom infrastructure. By leveraging the structural advantages of the mobile network operators and provide a viable (if not superior alternative) to walled gardens (META / Google) "self-measurement" approach. CAMARA will uplift brands with greater transparency on ad measurement, the Consent and Measurement API will incentivize the adoption of the developer ecosystem with more ad revenue and innovation.
Commercial viability The "Consent & Measurement" API has been proposed to leading conglomerate consumer brands, tech platforms, sell side publishers, buy side ad exchanges, and advertising trade organizations to gauge viability and industry adoption. When considering the commercial viability of the "Consent & Measurement" API, interested industry leaders gave it a unanimous “Yes.” The interested parties include LinkedIn, Univision, Proctor and Gamble, and TradeDesk.
YAML code available? NO
Validated in lab/productive environments? YES, this API has been validated in lab setting
Validated with real customers? YES, the features of CAMARA API can replace existing third-party tools useds by brands which have been proven to be inaccurate.
Validated with operators? NO.
Supporters in API Backlog Working Group NO.
@jordonezlucena
Copy link

I suggest having this discussion in the ICM Sub-Project. I include @jpengar (ICM chair) for further guidance.

@nickvenezia
Copy link
Author

@jpengar How can we best coordinate a time to talk with you?

@jpengar
Copy link

jpengar commented Nov 20, 2023

As recommended in the last Identity & Consent Management WG call (meeting minutes are here: camaraproject/IdentityAndConsentManagement#83) and also mentioned in the comments of the pull request itself (camaraproject/IdentityAndConsentManagement#83 (comment)), if you have any suggestions or proposals, please submit them by creating a new issue in the WG github subproject (https://github.com/camaraproject/IdentityAndConsentManagement/issues) so that all WG participants can review it and provide feedback if necessary.
(CC @jordonezlucena)

@jpengar How can we best coordinate a time to talk with you?

I'm chairing the WG and also representing Telefónica, but any new proposal should be discussed with the rest of the WG, not just with me.

@nickvenezia nickvenezia changed the title New Proposal for Consent and Measurement New Proposal for ADTECH Consent and Measurement Nov 20, 2023
@nickvenezia nickvenezia changed the title New Proposal for ADTECH Consent and Measurement New Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement Nov 22, 2023
@nickvenezia nickvenezia changed the title New Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement New Proposal for Authorization for Consent and Measurement Jan 11, 2024
@nickvenezia
Copy link
Author

@jpengar Would the proposal be better titled if it was only "Measurement" or "adtech". The presentation given in WG was different.

@nickvenezia nickvenezia changed the title New Proposal for Authorization for Consent and Measurement New Proposal for Consent and Measurement Jan 29, 2024
nickvenezia referenced this issue in camaraproject/WorkingGroups Feb 11, 2024
@TEF-RicardoSerr TEF-RicardoSerr transferred this issue from camaraproject/WorkingGroups Apr 26, 2024
@TEF-RicardoSerr TEF-RicardoSerr linked a pull request Aug 13, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants