Bitnami MediaWiki - User contributions [en]

FLoC

2021-01-25T14:46:41Z

99.45.169.158:

The goal of Google's Federated Learning of Cohorts (FLoC) is to reduce organizations' ability to access [[Audience|audience]] membership across different publishers.<ref>https://https://github.com/WICG/floc</ref>

Google's FloC proposal collects and processes web client behavior across various web sites to assign each web client to a [[cohort]] cluster. A cohort identifier, which Google calls “flock,” is short enough string (e.g., “43A7”) such that it cannot – even with other data – be used to uniquely identify a particular device. On each request the web client will send the cohort ID Google has assigned to this web client using the "Sec-CH-Flock" header.

The minimum number of people in a cohort is likely in the thousands.<ref>https://iabtechlab.com/blog/explaining-the-privacy-sandbox-explainers</ref> To ensure that a minimum number of web clients is in each cohort, the web client identifier is sent to a Google controlled server to enable distinct counting.

Marketers could measure which cohorts interact with their content, but would not know distinct reach or frequency. Marketers would also presumably be prohibited from associating particular outcomes on their web property with the cohort associated with the user's web client.

Google published a research paper that compared the accuracy of assigning browser identifiers to cohorts.<ref>https://github.com/google/ads-privacy/blob/master/proposals/FLoC/FLOC-Whitepaper-Google.pdf</ref> Google's findings were that it was able to achieve 70% accuracy in building cohort clusters relative to random assignment, which is still well below the segmentation accuracy of the current industry standard of using cookies for audience creation.

== Impact ==
By removing audience segmentation, marketers would be unable to perform retargeting and frequency capping.

Another potential impact of removing this information is a degraded end user experience.

Another impact of cohorts is that they do not support smaller organizations (advertisers or publishers) as their audiences may be too small to meet the minimum threshold set by the cohort.

== Open Questions ==
* How frequently does a user's cohort membership change?
* What is the value impairment associated with shifting from marketer-defined audiences to Google-defined cohorts?

== References ==

<references />

[[Category:Glossary|FLoC]]
[[Category:Privacy Sandbox|FLoC]]

Category:Privacy Sandbox

2021-01-21T21:39:01Z

99.45.169.158: /* Experience Mangagement Projects */

Privacy Sandbox is a set of proprietary Chrome browser APIs that provide information to buyers and sellers of digital media.<ref>https://iabtechlab.com/blog/explaining-the-privacy-sandbox-explainers</ref> Many of these APIs rely on server-side components.

This page lists Google Privacy Sandbox projects as well as proposed modifications to these projects to better meet the needs of publishers and marketers. When an organization other than Google is proposing a project in the list below there name appears in parentheses.

== Media Planning Projects ==
Given a goal of the Privacy Sandbox is to prevent marketers from understanding which audiences are interacting across different publishers, this will not be directly addressed by this project.

== Experience Mangagement Projects ==
Marketers engagement requirements are to show their content to their desired audience in the right context, while limiting the frequency capping across these different publishers. The "right" context is determined by the relative cost for a subsequent value generated from the exposure, such as brand awareness, click or conversion. Part of determining a desired audience is also filtering [[Non-human_Traffic|Non-human traffic]].

Publisher engagement requirements are to show their content to their desired audience, while controlling for publisher business rules, such as controlling which types of advertising content can appear or appear together on the same page to a particular audience. Privacy Sandbox's time-delayed feedback may not meet publisher requirements for A/B testing nor quality assurance of their advertising.

A goal of the Privacy Sandbox is to limit the precision of audience segments in context, as well as to limit the real-time feedback marketers receive to update their measurement and budget allocations. Thus the Privacy Sandbox engagement proposals either force marketers to choose to control audience OR context, but not combine the two, or alternately force marketers to engage imprecise cohorts defined by Google.

* '''Audience Creation'''
** [[FLoC]]
** [[Turtledove]]
** [[Scaup]]
** [[Trust Tokens]]
** [[Privacy Budget]]
** [[Client Hints]]
** [[First Party Sets]]

* '''Auction Management'''
** [[Turtledove]]
** [[Augury]]
** [[Dovekey]]
** [[Sparrow]] (Criteo)
** [[Parrrot]] (Magnite)
** [[Fenced Frames]]
** [[Tern]] (Adroll)

== Reporting Projects ==
Marketers reporting requirements are to understand which content generating relatively better outcomes when shown to particular audiences in particular contexts. The attribution of outcomes, which often occur on marketer properties, is part of the process that enables marketers to value the publisher inventory they buy.

A goal of Privacy Sandbox is to prevent the link of positive outcomes on marketer properties back to particular publisher contexts.

* '''Auction Management'''
** [[Aggregate Reporting API]]
** [[Conversion Measurement API]]
** [[Privacy Click Attribution]] (Apple)
** [[Pelican]] (Neustar)

== References ==
<references />

[[Category:Glossary|Privacy Sandbox]]

Category:Privacy Sandbox

2021-01-21T21:38:33Z

99.45.169.158: /* Experience Mangagement Projects */

Privacy Sandbox is a set of proprietary Chrome browser APIs that provide information to buyers and sellers of digital media.<ref>https://iabtechlab.com/blog/explaining-the-privacy-sandbox-explainers</ref> Many of these APIs rely on server-side components.

This page lists Google Privacy Sandbox projects as well as proposed modifications to these projects to better meet the needs of publishers and marketers. When an organization other than Google is proposing a project in the list below there name appears in parentheses.

== Media Planning Projects ==
Given a goal of the Privacy Sandbox is to prevent marketers from understanding which audiences are interacting across different publishers, this will not be directly addressed by this project.

== Experience Mangagement Projects ==
Marketers engagement requirements are to show their content to their desired audience in the right context, while limiting the frequency capping across these different publishers. The "right" context is determined by the relative cost for a subsequent value generated from the exposure, such as brand awareness, click or conversion. Part of determining a desired audience is also filtering [[Non-Human_Traffic|Non-human traffic]].

Publisher engagement requirements are to show their content to their desired audience, while controlling for publisher business rules, such as controlling which types of advertising content can appear or appear together on the same page to a particular audience. Privacy Sandbox's time-delayed feedback may not meet publisher requirements for A/B testing nor quality assurance of their advertising.

A goal of the Privacy Sandbox is to limit the precision of audience segments in context, as well as to limit the real-time feedback marketers receive to update their measurement and budget allocations. Thus the Privacy Sandbox engagement proposals either force marketers to choose to control audience OR context, but not combine the two, or alternately force marketers to engage imprecise cohorts defined by Google.

* '''Audience Creation'''
** [[FLoC]]
** [[Turtledove]]
** [[Scaup]]
** [[Trust Tokens]]
** [[Privacy Budget]]
** [[Client Hints]]
** [[First Party Sets]]

* '''Auction Management'''
** [[Turtledove]]
** [[Augury]]
** [[Dovekey]]
** [[Sparrow]] (Criteo)
** [[Parrrot]] (Magnite)
** [[Fenced Frames]]
** [[Tern]] (Adroll)

== Reporting Projects ==
Marketers reporting requirements are to understand which content generating relatively better outcomes when shown to particular audiences in particular contexts. The attribution of outcomes, which often occur on marketer properties, is part of the process that enables marketers to value the publisher inventory they buy.

A goal of Privacy Sandbox is to prevent the link of positive outcomes on marketer properties back to particular publisher contexts.

* '''Auction Management'''
** [[Aggregate Reporting API]]
** [[Conversion Measurement API]]
** [[Privacy Click Attribution]] (Apple)
** [[Pelican]] (Neustar)

== References ==
<references />

[[Category:Glossary|Privacy Sandbox]]

Category:Privacy Sandbox

2021-01-21T21:38:07Z

99.45.169.158: /* Experience Mangagement Projects */

Privacy Sandbox is a set of proprietary Chrome browser APIs that provide information to buyers and sellers of digital media.<ref>https://iabtechlab.com/blog/explaining-the-privacy-sandbox-explainers</ref> Many of these APIs rely on server-side components.

This page lists Google Privacy Sandbox projects as well as proposed modifications to these projects to better meet the needs of publishers and marketers. When an organization other than Google is proposing a project in the list below there name appears in parentheses.

== Media Planning Projects ==
Given a goal of the Privacy Sandbox is to prevent marketers from understanding which audiences are interacting across different publishers, this will not be directly addressed by this project.

== Experience Mangagement Projects ==
Marketers engagement requirements are to show their content to their desired audience in the right context, while limiting the frequency capping across these different publishers. The "right" context is determined by the relative cost for a subsequent value generated from the exposure, such as brand awareness, click or conversion. Part of determining a desired audience is also filtering [[Non-Human Traffic|Non-human traffic]].

Publisher engagement requirements are to show their content to their desired audience, while controlling for publisher business rules, such as controlling which types of advertising content can appear or appear together on the same page to a particular audience. Privacy Sandbox's time-delayed feedback may not meet publisher requirements for A/B testing nor quality assurance of their advertising.

A goal of the Privacy Sandbox is to limit the precision of audience segments in context, as well as to limit the real-time feedback marketers receive to update their measurement and budget allocations. Thus the Privacy Sandbox engagement proposals either force marketers to choose to control audience OR context, but not combine the two, or alternately force marketers to engage imprecise cohorts defined by Google.

* '''Audience Creation'''
** [[FLoC]]
** [[Turtledove]]
** [[Scaup]]
** [[Trust Tokens]]
** [[Privacy Budget]]
** [[Client Hints]]
** [[First Party Sets]]

* '''Auction Management'''
** [[Turtledove]]
** [[Augury]]
** [[Dovekey]]
** [[Sparrow]] (Criteo)
** [[Parrrot]] (Magnite)
** [[Fenced Frames]]
** [[Tern]] (Adroll)

== Reporting Projects ==
Marketers reporting requirements are to understand which content generating relatively better outcomes when shown to particular audiences in particular contexts. The attribution of outcomes, which often occur on marketer properties, is part of the process that enables marketers to value the publisher inventory they buy.

A goal of Privacy Sandbox is to prevent the link of positive outcomes on marketer properties back to particular publisher contexts.

* '''Auction Management'''
** [[Aggregate Reporting API]]
** [[Conversion Measurement API]]
** [[Privacy Click Attribution]] (Apple)
** [[Pelican]] (Neustar)

== References ==
<references />

[[Category:Glossary|Privacy Sandbox]]

Category:Privacy Sandbox

2021-01-11T18:32:48Z

99.45.169.158: Created page with "Privacy Sandbox is a set of proprietary Chrome browser APIs that provide information to buyers and sellers of digital media.<ref>https://iabtechlab.com/blog/explaining-the-pri..."

Privacy Sandbox is a set of proprietary Chrome browser APIs that provide information to buyers and sellers of digital media.<ref>https://iabtechlab.com/blog/explaining-the-privacy-sandbox-explainers</ref> Many of these APIs rely on server-side components.

This page lists Google Privacy Sandbox projects as well as proposed modifications to these projects to better meet the needs of publishers and marketers. When an organization other than Google is proposing a project in the list below there name appears in parentheses.

== Media Planning Projects ==
Given a goal of the Privacy Sandbox is to prevent marketers from understanding which audiences are interacting across different publishers, this will not be directly addressed by this project.

== Engagement Projects ==
Marketers engagement requirements are to show their content to their desired audience in the right context, while limiting the frequency capping across these different publishers. The "right" context is determined by the relative cost for a subsequent value generated from the exposure, such as brand awareness, click or conversion. Part of determining a desired audience is also filtering [[Non-Human Traffic|non-human traffic]].

Publisher engagement requirements are to show their content to their desired audience, while controlling for publisher business rules, such as controlling which types of advertising content can appear or appear together on the same page to a particular audience. Privacy Sandbox's time-delayed feedback may not meet publisher requirements for A/B testing nor quality assurance of their advertising.

A goal of the Privacy Sandbox is to limit the precision of audience segments in context, as well as to limit the real-time feedback marketers receive to update their measurement and budget allocations. Thus the Privacy Sandbox engagement proposals either force marketers to choose to control audience OR context, but not combine the two, or alternately force marketers to engage imprecise cohorts defined by Google.

* '''Audience Creation'''
** [[FLoC]]
** [[Turtledove]]
** [[Privacy Budget]]

* '''Auction Management'''
** [Turtledove]]
** [[Augury]]
** [[Dovekey]]
** [[Sparrow]] (Criteo)
** [[Parrrot]] (Magnite)
** [[Fenced Frames]]
** [[Tern]] (Nextroll)

== Reporting Projects ==
Marketers reporting requirements are to understand which content generating relatively better outcomes when shown to particular audiences in particular contexts. The attribution of outcomes, which often occur on marketer properties, is part of the process that enables marketers to value the publisher inventory they buy.

A goal of Privacy Sandbox is to prevent the link of positive outcomes on marketer properties back to particular publisher contexts.

* '''Auction Management'''
** [[Aggregate Reporting API]]
** [[Privacy Click Attribution]] (Apple)
** [[Pelican]] (Neustar)

== References ==
<references />

[[Category:Glossary|Privacy Sandbox]]

Privacy Budget

2021-01-11T18:32:08Z

99.45.169.158:

The goal of Google's “privacy budget” is to reduce organizations' ability to create a statistical identifier from web client technographics.
Privacy budget suggests that a limit on this information will be provided to an organization for each user session.

Particular technographics Google wants to prevent other organizations from accessing include:
* Detailed user agent strings including operating system and browser minor version;
* Screen resolution, installed system fonts, and similar data;
* Easily available client IP address information.

The exact information that will be accounting of this budget remains unknown.<ref>https://iabtechlab.com/blog/explaining-the-privacy-sandbox-explainers</ref>

== Impact ==
By removing this ability, this has the risk of preventing organizations from detecting [[Non-human Traffic|non-human traffic]]. Another potential impact of removing this information is a degraded end user experience.

== References ==

<references />

[[Category:Glossary|Privacy Budget]]
[[Category:Privacy Sandbox|Privacy Budget]]

Privacy Budget

2021-01-11T18:30:56Z

99.45.169.158: Created page with "The goal of Google's “privacy budget” is to reduce organizations' ability to create a statistical identifier from web client technographics. Privacy budget suggests that..."

Addressability

2021-01-11T14:24:23Z

99.45.169.158:

Media can either be “addressable” (has an [[identifier]]) or “non-addressable” (no identifier present).

Programmatic display, video, mobile, native are examples of addressable media.

Static billboards are an example of non-addressable media.

[[Category:Personal Data|Addressability]]

[[Category:Glossary|Deterministic]]

Main Page

2021-01-11T14:23:42Z

99.45.169.158:

MediaWiki has been installed.

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.

== Prebid Wikipedia ==

[[Prebid: About]]

[[Prebid Members]]

[[Prebid GitHub]]

[[Prebid Membership]]

[[Prebid Blog]]

[[Prebid Products]]

[[:Category:Prebid_Project_Management_Committeess|Prebid Project Management Committees]]

[[:Category:Glossary|Glossary]]

== Getting started ==
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

[[File:File.jpg]]$wgLogo = "{$wgUploadPath}/6/62/mylogo.png";

Main Page

2021-01-11T14:23:19Z

99.45.169.158:

MediaWiki has been installed.

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.

== Prebid Wikipedia ==

[[Prebid: About]]

[[Prebid Members]]

[[Prebid GitHub]]

[[Prebid Membership]]

[[Prebid Blog]]

[[Prebid Products]]

[[:Category:Prebid_Project_Management_Committeess|Prebid Project Management Committees]]

[[Category:Glossary|Glossary]]

== Getting started ==
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

[[File:File.jpg]]$wgLogo = "{$wgUploadPath}/6/62/mylogo.png";

Main Page

2021-01-11T14:23:01Z

99.45.169.158:

MediaWiki has been installed.

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.

== Prebid Wikipedia ==

[[Prebid: About]]

[[Prebid Members]]

[[Prebid GitHub]]

[[Prebid Membership]]

[[Prebid Blog]]

[[Prebid Products]]

[[:Category:Prebid_Project_Management_Committeess|Prebid Project Management Committees]]

[[Category:Glossary]]

== Getting started ==
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

[[File:File.jpg]]$wgLogo = "{$wgUploadPath}/6/62/mylogo.png";

Main Page

2021-01-11T14:19:38Z

99.45.169.158:

MediaWiki has been installed.

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.

== Prebid Wikipedia ==

[[Prebid: About]]

[[Prebid Members]]

[[Prebid GitHub]]

[[Prebid Membership]]

[[Prebid Blog]]

[[Prebid Products]]

[[:Category:Prebid_Project_Management_Committeess|Prebid Project Management Committees]]

[[Glossary]]

== Getting started ==
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

[[File:File.jpg]]$wgLogo = "{$wgUploadPath}/6/62/mylogo.png";

Prebid: About

2021-01-11T14:18:45Z

99.45.169.158:

==A Brief Prehistory==

Header bidding is a response to the “waterfall” method, a fragmented and highly inefficient process for implementing programmatic advertising. Instead of offering impressions to one partner at a time, header bidding lets all partners bid simultaneously. With header bidding, publishers can also receive bids that may be unavailable through their primary ad server.

'''Prebid is born:'''

Prebid.js launched in 2015 to make header bidding easy for publishers by bringing conformity and simplicity to the header bidding process. By creating a simple, open tech layer upon which companies could add their code to a standard but optimized foundation, Prebid.js made it easier to implement header bidding, and offered the largest repository of working adapters.

Today, Prebid.js is the most widely used header bidding “container” or “wrapper” on the web.

Privacy and Identity

2021-01-11T14:17:12Z

99.45.169.158:

Privacy and Identity

'''Scope''': User Identification and Identifiers

'''Description''': Chart Prebid’s role in the future of identity and identifiers on the web and coordinate any implementation efforts

'''Chair''': Stephanie Layser (NewsCorp)

'''Audience''': Product, Business, and Engineers

== GitHub Repositories ==
https://github.com/prebid/shared-id

[[Category:Prebid Project Management Committeess|Privacy and Identity]]

Prebid.js

2021-01-11T14:16:42Z

99.45.169.158:

Prebid.js

'''Scope''': Prebid.js and related repositories

'''Description''': Browser-based header bidding

'''Chair''': Gareth Glaser (Magnite)

'''Audience''': Product and Engineers

== GitHub Repositories ==
https://github.com/prebid/prebid.js

https://github.com/prebid/Prebid.js-packager

https://github.com/prebid/prebid-universal-creative

https://github.com/prebid/currency-file-generator

https://github.com/prebid/prebid-js-build-generator

[[Category:Prebid Project Management Committeess|Prebid.js]]

Prebid Video Taskforce

2021-01-11T14:16:16Z

99.45.169.158:

Prebid Video Taskforce

'''Scope''': Video

'''Description''': Define the needs for video header bidding

'''Chair''': Mike Chowla (Pubmatic)

'''Format Lead''': Joel Korpi (Xandr)

'''Audience''': Product, Business, and Engineers

[[Category:Prebid Project Management Committeess|Prebid Video Taskforce]]

Prebid Taxonomy taskforce

2021-01-11T14:15:48Z

99.45.169.158:

Prebid Taxonomy Taskforce

'''Scope''': Standardized signaling and naming conventions

'''Description''': Implementing standardized signaling and naming conventions for things such as log files, transparency audits,
content categories, and audience segments

'''Chair''': Steve Francolla (Permutive)

'''Audience''': Product, Business, Engineers

[[Category:Prebid Project Management Committeess|Prebid Taxonomy Taskforcee]]

Prebid Publisher Taskforce

2021-01-11T14:15:18Z

99.45.169.158:

Prebid Publisher Taskforce

'''Scope''': Publisher-related topics

'''Description''': Header bidding issues, optimization, strategy, best practices

'''Chair''': Stephanie Layser (NewsCorp)

'''Audience''': Business

[[Category:Prebid Project Management Committeess|Prebid Publisher Taskforcee]]

Prebid mobile

2021-01-11T14:14:50Z

99.45.169.158:

Prebid Mobile

'''Scope''': Prebid Mobile SDK

'''Description''': Mobile-app based header bidding

'''Chair''': Bryan Szekely (Magnite)

'''Audience''': Product and Engineers

== GitHub Repositories ==
https://github.com/prebid/prebid-mobile-ios

https://github.com/prebid/prebid-mobile-android

[[Category:Prebid Project Management Committeess|Prebid Mobile ]]

Prebid Marketing Taskforce

2021-01-11T14:14:05Z

99.45.169.158:

Prebid Marketing Taskforce

'''Scope''': Prebid.org events and marketing

'''Description''': Coordinates Prebid events and press releases

'''Chair''': Joel Fisher (Magnite)

'''Audience''': Marketing, Business

[[Category:Prebid Project Management Committeess|Prebid Marketing Taskforcee]]

Prebid server

2021-01-11T14:13:31Z

99.45.169.158:

Prebid Server

'''Scope''': Prebid Server and Prebid Cache

'''Description''': Server-side header bidding

'''Chair''': Bret Gorsline (Magnite)

'''Vice Chair''': Scott Kay (Xandr)

'''Audience''': Product and Engineers

== GitHub Repositories ==
https://github.com/prebid/prebid-server

https://github.com/prebid/prebid-cache

https://github.com/rubicon-project/prebid-server-java

https://github.com/rubicon-project/prebid-cache-java

[[Category:Prebid Project Management Committeess|Prebid Server]]

Prebid.js

2021-01-07T23:40:52Z

99.45.169.158:

Prebid.js

Scope: Prebid.js and related repositories

Description: Browser-based header bidding

Chair: Gareth Glaser (Magnite)

Audience: Product and Engineers

== GitHub Repositories ==
https://github.com/prebid/prebid.js

https://github.com/prebid/Prebid.js-packager

https://github.com/prebid/prebid-universal-creative

https://github.com/prebid/currency-file-generator

https://github.com/prebid/prebid-js-build-generator

[[Category:Prebid Project Management Committeess|Prebid.js]]

Prebid.js

2021-01-07T23:40:41Z

99.45.169.158: Created page with "Prebid.js Scope: Prebid.js and related repositories Description: Browser-based header bidding Chair: Gareth Glaser (Magnite) Audience: Product and Engineers == GitHub Rep..."

Prebid.js

Scope: Prebid.js and related repositories

Description: Browser-based header bidding

Chair: Gareth Glaser (Magnite)

Audience: Product and Engineers

== GitHub Repositories ==
https://github.com/prebid/prebid.js
https://github.com/prebid/Prebid.js-packager
https://github.com/prebid/prebid-universal-creative
https://github.com/prebid/currency-file-generator
https://github.com/prebid/prebid-js-build-generator

[[Category:Prebid Project Management Committeess|Prebid.js]]

Privacy and Identity

2021-01-07T23:37:49Z

99.45.169.158:

Privacy and Identity

Scope: User Identification and Identifiers

Description: Chart Prebid’s role in the future of identity and identifiers on the web and coordinate any implementation efforts

Chair: Stephanie Layser (NewsCorp)

Audience: Product, Business, and Engineers

== GitHub Repositories ==
https://github.com/prebid/shared-id

[[Category:Prebid Project Management Committeess|Privacy and Identity]]

Privacy and Identity

2021-01-07T23:36:41Z

99.45.169.158: Created page with "Privacy and Identity Scope: User Identification and Identifiers Description: Chart Prebid’s role in the future of identity and identifiers on the web and coordinate any impl..."

Privacy and Identity
Scope: User Identification and Identifiers
Description: Chart Prebid’s role in the future of identity and identifiers on the web and coordinate any implementation efforts
Chair: Stephanie Layser (NewsCorp)
Audience: Product, Business, and Engineers

== GitHub Repositories ==
https://github.com/prebid/shared-id

[[Category:Prebid Project Management Committeess|Privacy and Identity]]

Main Page

2021-01-07T23:28:47Z

99.45.169.158: /* Prebid Wikipedia */

MediaWiki has been installed.

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.

== Prebid Wikipedia ==

[[Personal Data]]

[[Prebid GitHub]]

[[Prebid Membership]]

[[Prebid Blog]]

[[Prebid Products]]

[[Prebid Project Management Committees]]

== Getting started ==
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

Talk:Personal Data

2021-01-07T23:27:08Z

99.45.169.158:

Question: Is personal data the same as personal information?
Answer: Yes. Different privacy regulations use "personal data" and "personal information" to mean the same thing.