GITHUB . COM {}

Detected CMS Systems:

Wordpress (8 occurrences)

Analyzed Page
Matching Content Categories
CMS
Monthly Traffic Estimate
How Does Github.com Make Money
How Much Does Github.com Make
Wordpress Themes And Plugins
Keywords
Topics
Payment Methods
Questions
Schema
External Links
Analytics And Tracking
Libraries
Hosting Providers

We are analyzing https://github.com/wicg/turtledove/issues/1220.

Title:
Third Party reporting · Issue #1220 · WICG/turtledove
Description:
The original description is outdated, the actual proposal can be found here:#1220 (comment) Problem Statement: The current PA API logic doesn't support the middle layer between Sellers and Buye...
Website Age:
17 years and 9 months (reg. 2007-10-09).

Matching Content Categories {📚}

Social Networks
Non-Profit & Charity
Events

Content Management System {📝}

What CMS is github.com built with?

Github.com operates using WORDPRESS.

Traffic Estimate {📈}

What is the average monthly size of github.com audience?

🚀🌠 Tremendous Traffic: 10M - 20M visitors per month

Based on our best estimate, this website will receive around 10,000,019 visitors per month in the current month.
However, some sources were not loaded, we suggest to reload the page to get complete results.

check SE Ranking
check Ahrefs
check Similarweb
check Ubersuggest
check Semrush

How Does Github.com Make Money? {💸}

Subscription Packages {💳}

We've located a dedicated page on github.com that might include details about subscription plans or recurring payments. We identified it based on the word pricing in one of its internal links. Below, you'll find additional estimates for its monthly recurring revenues.

How Much Does Github.com Make? {💰}

Subscription Packages {💳}

Prices on github.com are in US Dollars ($). They range from $4.00/month to $21.00/month.
We estimate that the site has approximately 5,013,426 paying customers.
The estimated monthly recurring revenue (MRR) is $21,056,387.
The estimated annual recurring revenues (ARR) are $252,676,649.

Wordpress Themes and Plugins {🎨}

What WordPress theme does this site use?

It is strange but we were not able to detect any theme on the page.

What WordPress plugins does this website use?

It is strange but we were not able to detect any plugins on the page.

Keywords {🔍}

event, reporting, commented, thirdparties, mdaviesbidswitch, sendreportto, seller, dsp, ssp, events, shivanigithub, buyers, impression, data, add, request, fhoering, contributor, multiple, registeradbeacon, reservedimpression, beacon, party, issue, default, httpswwwthirdpartycom, buyer, time, case, wicg, proposal, auction, config, perbuyerthirdpartysignals, function, ajvelasquezprivacysandbox, react, call, triggered, billing, sign, comment, api, logic, support, extpigsignals, section, based, called, similar,

Topics {✒️}

ajvelasquez-privacy-sandbox edits collaborator /wicg/turtledove/blob/main/fenced_frames_ads_reporting mdavies-bidswitch edits author report result/reportwin pings ad iframe/fenced frames middle-layer technical providers fenced-frame-automatic-beacons receive impression notifications ff report events navigation start default click events problems brought forward iframe/fenced frame multiple default events iframe completed loading impression notifications impression_commit events signify 3rd party reporting manage budgets type projects projects milestone generic beacon api valuable billable event send reporting data issues comment metadata assignees wicg call wicg discussion multiple ssp reporting default display event section contextual signals interestgroupowner}&signals=${thirdpartysignals declare 3p destinations reserved event reserved registered multiple times custom event data original description middle layer technical providers auction config simplified solution declare thirdparties based ad/auction bid}&dsp=${browsersignals bidswitch custom events browser sends buyers' specific data ad frame auction results

Payment Methods {📊}

Braintree

Questions {❓}

Already have an account?
Also above is a more simplified solution, does this work better?
Any news on #1220 (comment) ?
Do you confirm ?
Do you think anything could be blocking on you side ?
Perhaps another way to scope this request could be to express what are the gaps between that and the problems brought forward here?
Com/reporting?
Example/imp?

Schema {🗺️}

DiscussionForumPosting:
      context:https://schema.org
      headline:Third Party reporting
      articleBody:**The original description is outdated, the actual proposal can be found here:https://github.com/WICG/turtledove/issues/1220#issuecomment-2536569406** ### Problem Statement: The current PA API logic doesn't support the middle layer between Sellers and Buyers. So while DSPs and SSPs do receive impression notifications from Chrome, middle-layer technical providers (e.g. BidSwitch) by default don't. It is essential for technical providers to get impression notifications in real-time or close to that to manage budgets and shape traffic. ### Proposal - Provide a new mechanism for ThirdParties enrollment. - The ThirdParties (or Buyers on behalf of ThirdParties) provide their signals in the ext.3p_ig_signals section of an OpenRTB response as follows: ``` 'ext': { '3p_ig_signals': { 'https://www.third-party-1.com/': { 'url': 'https://www.third-party-1.com/thirdPartyReport.js', 'data': { 'https://www.example-dsp.com/': 'someDataOfThirdParty1', 'https://www.another-buyer.com/': 'someOtherDataOfThirdParty2', ... } } } } ``` It is supposed that ThirdParties put in this section **contextual signals, seller origins, and buyers' specific data**. - Support the new key in auction config, e.g. - thirdParties, where Seller could declare ThirdParties based on the ext.3p_ig_signals in OpenRTB response. - Support the new key in auction config e.g. - perBuyerThirdPartySignals, where Seller could declare what ThirdParties are eligible to get reporting data for a given Buyer and signals for them. This key is based on the ext.3p_ig_signals in the OpenRTB response. - The seller has to take into account all the ThirdParties data from ext.3p_ig_signals and form the sections thirdParties and perBuyerThirdPartySignals in the auction config as follows: ``` const AuctionConfig = { 'seller': 'https://www.example-ssp.com/', 'interestGroupBuyers': [ 'https://www.example-dsp.com/', 'https://www.another-buyer.com/', ], 'thirdParties': 'https://www.third-party-1.com/': https://www.third-party-1.com/thirdPartyReport.js, 'https://www.third-party-2.com/': 'https://www.third-party-2.com/thirdPartyReport.js', ... }, 'perBuyerThirdPartySignals': { 'https://www.example-dsp.com/': { 'https://www.third-party-1.com/': someDataOfThirdParty1, 'https://www.third-party-2.com/': someDataOfThirdParty2 }, 'https://www.another-buyer.com/': { 'https://www.third-party-1.com/': someOtherDataOfThirdParty2 }, ... }, ... }; ``` - Add the logic to execute reportResultsToThirdParty() function from the specific ThirdParty's worklet (thirdPartyReport.js). The function is called at the same time as won Buyer's reportWin. It is called only for those ThirdParties that are defined in perBuyerThirdPartySignals section for this Buyer. The arguments to the function are auctionConfig, browserSignals, and a section of perBuyerThirdPartySignals that is specific for these Buyers and ThirdParties. The purpose of the function is to send reporting data to a ThirdParty. Example of a reportResultsToThirdParty() function: ``` reportResultsToThirdParty(auctionConfig, browserSignals, ThirdPartySignals) { sendReportTo('https://www.third-party-1.com/reporting?bid=${browserSignals.bid}&dsp=${browserSignals.interestGroupOwner}&signals=${thirdPartySignals.signals}'); } ``` ### similar request / issue A similar request for aggregated reporting - https://github.com/WICG/turtledove/issues/1115 ### Privacy concerns Potential issue - auction config could be modified by any script on the publisher's page, which could provide access to auction results for non-trusted third parties.
      author:
         url:https://github.com/mdavies-bidswitch
         type:Person
         name:mdavies-bidswitch
      datePublished:2024-07-09T13:10:04.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:19
      url:https://github.com/1220/turtledove/issues/1220
      context:https://schema.org
      headline:Third Party reporting
      articleBody:**The original description is outdated, the actual proposal can be found here:https://github.com/WICG/turtledove/issues/1220#issuecomment-2536569406** ### Problem Statement: The current PA API logic doesn't support the middle layer between Sellers and Buyers. So while DSPs and SSPs do receive impression notifications from Chrome, middle-layer technical providers (e.g. BidSwitch) by default don't. It is essential for technical providers to get impression notifications in real-time or close to that to manage budgets and shape traffic. ### Proposal - Provide a new mechanism for ThirdParties enrollment. - The ThirdParties (or Buyers on behalf of ThirdParties) provide their signals in the ext.3p_ig_signals section of an OpenRTB response as follows: ``` 'ext': { '3p_ig_signals': { 'https://www.third-party-1.com/': { 'url': 'https://www.third-party-1.com/thirdPartyReport.js', 'data': { 'https://www.example-dsp.com/': 'someDataOfThirdParty1', 'https://www.another-buyer.com/': 'someOtherDataOfThirdParty2', ... } } } } ``` It is supposed that ThirdParties put in this section **contextual signals, seller origins, and buyers' specific data**. - Support the new key in auction config, e.g. - thirdParties, where Seller could declare ThirdParties based on the ext.3p_ig_signals in OpenRTB response. - Support the new key in auction config e.g. - perBuyerThirdPartySignals, where Seller could declare what ThirdParties are eligible to get reporting data for a given Buyer and signals for them. This key is based on the ext.3p_ig_signals in the OpenRTB response. - The seller has to take into account all the ThirdParties data from ext.3p_ig_signals and form the sections thirdParties and perBuyerThirdPartySignals in the auction config as follows: ``` const AuctionConfig = { 'seller': 'https://www.example-ssp.com/', 'interestGroupBuyers': [ 'https://www.example-dsp.com/', 'https://www.another-buyer.com/', ], 'thirdParties': 'https://www.third-party-1.com/': https://www.third-party-1.com/thirdPartyReport.js, 'https://www.third-party-2.com/': 'https://www.third-party-2.com/thirdPartyReport.js', ... }, 'perBuyerThirdPartySignals': { 'https://www.example-dsp.com/': { 'https://www.third-party-1.com/': someDataOfThirdParty1, 'https://www.third-party-2.com/': someDataOfThirdParty2 }, 'https://www.another-buyer.com/': { 'https://www.third-party-1.com/': someOtherDataOfThirdParty2 }, ... }, ... }; ``` - Add the logic to execute reportResultsToThirdParty() function from the specific ThirdParty's worklet (thirdPartyReport.js). The function is called at the same time as won Buyer's reportWin. It is called only for those ThirdParties that are defined in perBuyerThirdPartySignals section for this Buyer. The arguments to the function are auctionConfig, browserSignals, and a section of perBuyerThirdPartySignals that is specific for these Buyers and ThirdParties. The purpose of the function is to send reporting data to a ThirdParty. Example of a reportResultsToThirdParty() function: ``` reportResultsToThirdParty(auctionConfig, browserSignals, ThirdPartySignals) { sendReportTo('https://www.third-party-1.com/reporting?bid=${browserSignals.bid}&dsp=${browserSignals.interestGroupOwner}&signals=${thirdPartySignals.signals}'); } ``` ### similar request / issue A similar request for aggregated reporting - https://github.com/WICG/turtledove/issues/1115 ### Privacy concerns Potential issue - auction config could be modified by any script on the publisher's page, which could provide access to auction results for non-trusted third parties.
      author:
         url:https://github.com/mdavies-bidswitch
         type:Person
         name:mdavies-bidswitch
      datePublished:2024-07-09T13:10:04.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:19
      url:https://github.com/1220/turtledove/issues/1220
Person:
      url:https://github.com/mdavies-bidswitch
      name:mdavies-bidswitch
      url:https://github.com/mdavies-bidswitch
      name:mdavies-bidswitch
InteractionCounter:
      interactionType:https://schema.org/CommentAction
      userInteractionCount:19
      interactionType:https://schema.org/CommentAction
      userInteractionCount:19

External Links {🔗}(5)

Analytics and Tracking {📊}

Site Verification - Google

Libraries {📚}

Clipboard.js
D3.js
GSAP
Lodash

Emails and Hosting {✉️}

Mail Servers:

aspmx.l.google.com
alt1.aspmx.l.google.com
alt2.aspmx.l.google.com
alt3.aspmx.l.google.com
alt4.aspmx.l.google.com

Name Servers:

dns1.p08.nsone.net
dns2.p08.nsone.net
dns3.p08.nsone.net
dns4.p08.nsone.net
ns-1283.awsdns-32.org
ns-1707.awsdns-21.co.uk
ns-421.awsdns-52.com
ns-520.awsdns-01.net

9.75s.