Build a Chrome Browser Extension -- 2
Budget: $10 – $20 USD
We are testing the capabilities of a browser extension to capture data from users’ devices. Users will opt-in and provide explicit permission to access their data, and then collect it as they browse the web.
The focus of the extension is to monitor ads delivered to the user and their website visitation behavior.
Ads delivered may be delivered programmatically (through ad exchanges and bid requests) or by the site the user is visiting. In both scenarios, various datapoints about the ad impression will be sent with the ad as it renders on screen; those data points need to be captured with the extension. See the resources section for an example of bidstream data.
Minimum Functionality
User permission to track all browsing and ad request data across domains
Monitor and pass all ad delivery data to Mint’s servers
Bid stream data (details on the ads being served on page)
Site data (URLs visited, tracking parameters after “?”, etc.)
Timestamps - pages viewed, clicks activity, etc.
Function on mobile and desktop devices
Always on/recording data
Success criteria
Extension is successfully installed on desktop and mobile devices
Web browsing activity is monitored and sent to Mint servers
Ad tracking/bidstream data is found and passed to Mint servers
Questions
What is the approval process for chrome extensions? Do all need to be approved?
What maintenance, if any, is required for a chrome extension?
How do we add a user interface? We’ll have a UI eventually, but will need some way for users to engage within the chrome window
Resources
Similar extension - https://chrome.google.com/webstore/detail/reklaim-for-chrome/iokjgeodkfgdpgnfdccfeboekahebihk
Sample bid request data format - https://protocol.bidswitch.com/rtb-ssp/bid-request.html
Standard framework for ad requests - https://iabtechlab.com/wp-content/uploads/2017/09/OpenRTB-3.0-Draft-Framework-for-Public-Comment.pdf
https://kb.indexexchange.com/dsps/open-rtb/examples_of_openrtb_requests_and_responses.htm
The focus of the extension is to monitor ads delivered to the user and their website visitation behavior.
Ads delivered may be delivered programmatically (through ad exchanges and bid requests) or by the site the user is visiting. In both scenarios, various datapoints about the ad impression will be sent with the ad as it renders on screen; those data points need to be captured with the extension. See the resources section for an example of bidstream data.
Minimum Functionality
User permission to track all browsing and ad request data across domains
Monitor and pass all ad delivery data to Mint’s servers
Bid stream data (details on the ads being served on page)
Site data (URLs visited, tracking parameters after “?”, etc.)
Timestamps - pages viewed, clicks activity, etc.
Function on mobile and desktop devices
Always on/recording data
Success criteria
Extension is successfully installed on desktop and mobile devices
Web browsing activity is monitored and sent to Mint servers
Ad tracking/bidstream data is found and passed to Mint servers
Questions
What is the approval process for chrome extensions? Do all need to be approved?
What maintenance, if any, is required for a chrome extension?
How do we add a user interface? We’ll have a UI eventually, but will need some way for users to engage within the chrome window
Resources
Similar extension - https://chrome.google.com/webstore/detail/reklaim-for-chrome/iokjgeodkfgdpgnfdccfeboekahebihk
Sample bid request data format - https://protocol.bidswitch.com/rtb-ssp/bid-request.html
Standard framework for ad requests - https://iabtechlab.com/wp-content/uploads/2017/09/OpenRTB-3.0-Draft-Framework-for-Public-Comment.pdf
https://kb.indexexchange.com/dsps/open-rtb/examples_of_openrtb_requests_and_responses.htm