Abstract: An ad server logs web traffic regarding web page traffic by users. The web traffic is analyzed to determine web activity indicating that a user is being paid to fake legitimate web traffic. These users are referred to as abusive users. The web traffic is also analyzed to determine web activity indicating that a web page is artificially boosting its own traffic in order to earn undeserved advertising revenue. These web pages are referred to as honeypot web pages. Scores are determined for both users and web pages, where the scores indicate the likelihood that the associated user or web page is an abusive user or a honeypot web page, respectively. The ad server uses these scores to determine an amount to bid on future impressions to those users and web pages.

Abstract: An ad server logs web traffic regarding web page traffic by users. The web traffic is analyzed to determine web activity indicating that a user is being paid to fake legitimate web traffic. These users are referred to as abusive users. The web traffic is also analyzed to determine web activity indicating that a web page is artificially boosting its own traffic in order to earn undeserved advertising revenue. These web pages are referred to as honeypot web pages. Scores are determined for both users and web pages, where the scores indicate the likelihood that the associated user or web page is an abusive user or a honeypot web page, respectively. The ad server uses these scores to determine an amount to bid on future impressions to those users and web pages.

Abstract: The safe pixel is code embedded in a web page that is executed when the web page is accessed by a user agent. When the safe pixel is executed, the safe pixel collects information about the device and invokes the execution of one or more abuse detection functions. Each abuse detection function implements a different technique for estimating the likelihood of abusive behavior being the cause of the safe pixel being executed. The safe pixel transmits in a reporting message the local information and the results of the abuse detection function executions to a traffic server. The traffic server analyzes the reporting message to make a determination of the validity of the action that caused the safe pixel being executed.

Abstract: A third party company (also referred to as an ad server) provides an advertiser with computer code to place on the advertiser's web pages. The web page's code is configured to provide the ad server read and write access to an advertiser's first party cookie on a user's web browser. A user interacts with an ad on a mobile application or third party web page. Based on the user's interaction with the ad a URL containing a web address and ad instance information are sent to the user's web browser. The user's landing page associated with the URL contains code for retrieving the ad instance information and storing it in a first party cookie. When the user navigates to a purchasing page and purchases a product, the code contained in the purchasing page retrieves the ad instance information from the first party cookie and sends it to the ad server.

Abstract: A third party company (also referred to as an ad server) provides an advertiser with computer code to place on the advertiser's web pages. The web page's code is configured to provide the ad server read and write access to an advertiser's first party cookie on a user's web browser. A user interacts with an ad on a mobile application or third party web page. Based on the user's interaction with the ad a URL containing a web address and ad instance information are sent to the user's web browser. The user's landing page associated with the URL contains code for retrieving the ad instance information and storing it in a first party cookie. When the user navigates to a purchasing page and purchases a product, the code contained in the purchasing page retrieves the ad instance information from the first party cookie and sends it to the ad server.

Abstract: An ad server provides an advertiser with computer code to include in advertisement (ad) instances. Upon interaction with one of the ad instances, the computer code determines if a mobile software application associated with an advertiser is installed on a mobile device. The ad server may also provide mobile application developers with a software development kit (SDK) for use in creating mobile applications capable of determining if a mobile software application associated with the advertiser is installed on a mobile device, retrieving usage information associated with the user's use of the mobile device, receiving ad instances for display to a user through the mobile software application, and communicating this information to the ad server. Based on the installation status and the usage information the ad server selects ad instances to serve to the user of the mobile device.

Abstract: A third party company (also referred to as an ad server) provides an advertiser with computer code to place on the advertiser's web pages. The web page's code is configured to provide the ad server read and write access to an advertiser's first party cookie on a user's web browser. A user interacts with an ad on a mobile application or third party web page. Based on the user's interaction with the ad a URL containing a web address and ad instance information are sent to the user's web browser. The user's landing page associated with the URL contains code for retrieving the ad instance information and storing it in a first party cookie. When the user navigates to a purchasing page and purchases a product, the code contained in the purchasing page retrieves the ad instance information from the first party cookie and sends it to the ad server.

Abstract: Third party ad servers log a user's web browsing activities. On web pages where the ad server is a third party, the web page's code is configured to provide the ad server read and write access to an advertiser's first party cookie on a user's web browser. The ad server uses this access to read and write a unique user identification number to the cookie. The ad server also maintains a separate copy of the user identification number on a remote server. Correlating the user identification both within the ad server and within the cookies stored in the user's web browser allows the ad server to identify and log the web traffic associated with particular users. This information is useful in a number of contexts, including determining which ad inventory to purchase for which users, and how to value the corresponding ad inventory.