Computer implemented method for partner pixelling for user identification

Abstract

The embodiments herein provide a computer implemented method for partner pixelling for user identification. The method includes sending a unique identifier request message to an identity broker when a user is on an advertiser webpage. The method includes receiving a unique identifier of the user from the identifier entity broker; and sending a rule file to a publisher server, wherein the rule file comprises the unique identifier of the user for which at least one DSP is interested in displaying an advertisement. Further, when the user visits the publisher website, the publisher server uses the unique identifier, revived from the identity broker, to identify the user and the list of DSPs that are interested in displaying advisement to the user.

I claim: 
     
         1 . A computer implemented method for partner pixelling for user identification, the method comprising:
 sending, by a Demand Side Platform (DSP) server, a unique identifier request message to an identity broker when a user is on an advertiser webpage;   receiving, by said DSP server, a unique identifier of said user from said identity broker; and   sending, by said DSP server, a rule file to a publisher server, wherein said rule file comprises said unique identifier of said user for which at least one DSP is interested in displaying an advertisement.   
     
     
         2 . The computer implemented method of  claim 1 , wherein said DSP server calls an identifier entity broker service to send said unique identifier request message to said identity broker. 
     
     
         3 . The computer implemented method of  claim 1 , wherein said rule file defines a plurality of conditions based on which a DSP buys an advertising inventory to display said advertisement to said user. 
     
     
         4 . The computer implemented method of  claim 1 , wherein said plurality of conditions are defined based on at least one of a DSP bid value, number of impressions, publisher website information, time of the day, a day of a year, type of inventory, a variable defined by an exchange, a variable defined by said at least one DSP, and a user behaviors on said advertiser webpage. 
     
     
         5 . The computer implemented method of  claim 1 , wherein said unique identifier is a random value generated by said identity broker, a fingerprint of a browser, a fingerprint of a user electronic device, and a cross identifier. 
     
     
         6 . A computer implemented method for partner pixelling for user identification, the method comprising:
 sending, by a publisher server, a unique identifier request message to an identity broker when a user is on a publisher webpage;   receiving, by said publisher server, a unique identifier of said user from said identity broker; and   identifying, by said publisher server, at least one Demand Side Platform (DSP) interested to display an advertisement to said user based on said unique identifier.   
     
     
         7 . The computer implemented method of  claim 6 , wherein identifying said at least one DSP interested to display said advertisement to said user based on said unique identifier comprises:
 receiving, by said publisher server, a rule file from a DSP server, wherein said rule file comprises unique identifier of a user for which at least one DSP is interested in displaying said advertisement;   determining, by said publisher server, a match between said unique identifier received from said identity broker; and said unique identifier in said rule file; and   identifying, by said publisher server, said at least one DSP interested to display said advertisement to said user in response to determining said match.   
     
     
         8 . The computer implemented method of  claim 6 , wherein said rule file defines a plurality of conditions based on which a DSP buys an advertising inventory to display said advertisement to said user. 
     
     
         9 . The computer implemented method of  claim 8 , wherein said plurality of conditions are defined based on at least one of a DSP bid value, number of impressions, publisher website information, time of the day, a day of a year, type of inventory, a variable defined by an exchange, a variable defined by said at least one DSP, and a user behaviors on said advertiser webpage. 
     
     
         10 . The computer implemented method of  claim 6 , wherein said unique identifier is a random value generated by said identity broker, a fingerprint of a browser, a fingerprint of a user electronic device, and a cross identifier. 
     
     
         11 . A computer implemented method for partner pixelling for user identification, the method comprising:
 receiving, by an identity broker, a unique identifier request message for a user from one of a Demand Side Platform (DSP) server and a publisher server; and   sending, by said identity broker, said unique identifier for said user to one of said DSP server and said publisher server, wherein said unique identifier for said user is generated based on at least one parameter.   
     
     
         12 . The computer implemented method of  claim 11 , wherein sending said unique identifier for said user to one of said DSP server and said publisher server comprises:
 determining whether said unique identifier is available in a database based on at least one parameter;   generating said unique identifier for said user based on at least one said parameter when said unique identifier is unavailable in said database; and   sending said unique identifier for said user to one of said DSP server and said publisher server.   
     
     
         13 . The computer implemented method of  claim 11 , wherein sending said unique identifier for said user to one of said DSP server and said publisher server comprises:
 determining whether said unique identifier is available in said database based on at least one parameter; and   sending said unique identifier for said user to one of said DSP server and said publisher server when said unique identifier is unavailable in said database.   
     
     
         14 . The computer implemented method of  claim 11 , wherein said unique identifier is a random value generated by said identity broker, a fingerprint of a browser, a fingerprint of a user electronic device, and a cross identifier. 
     
     
         15 . A Demand Side Platform (DSP) server for partner pixelling for user identification, the DSP configured to:
 send a unique identifier request message to an identity broker when a user is on an advertiser webpage;   receive a unique identifier of said user from said identifier entity broker; and   send a rule file to a publisher server, wherein said rule file comprises said unique identifier of said user for which at least one DSP is interested in displaying an advertisement.   
     
     
         16 . The DSP of  claim 15 , wherein said DSP server calls an identifier entity broker service to send said unique identifier request message to said identity broker. 
     
     
         17 . The DSP of  claim 15 , wherein said rule file defines a plurality of conditions based on which a DSP buys an advertising inventory to display said advertisement to said user. 
     
     
         18 . The DSP of  claim 15 , wherein said plurality of conditions are defined based on at least one of a DSP bid value, number of impressions, publisher website information, time of the day, a day of a year, type of inventory, a variable defined by an exchange, a variable defined by said at least one DSP, and a user behaviors on said advertiser webpage. 
     
     
         19 . The DSP of  claim 15 , wherein said unique identifier is a random value generated by said identity broker, a fingerprint of a browser, a fingerprint of a user electronic device, and a cross identifier. 
     
     
         20 . A publisher server for partner pixelling for user identification, the publisher server configured to:
 send a unique identifier request message to an identity broker when a user is on a publisher webpage;   receive a unique identifier of said user from said identity broker; and   identify at least one Demand Side Platform (DSP) interested to display an advertisement to said user based on said unique identifier.   
     
     
         21 . The publisher server of  claim 20 , wherein said publisher server configured to identify at least one Demand Side Platform (DSP) interested to display an advertisement to said user based on said unique identifier by:
 receiving a rule file from a DSP server, wherein said rule file comprises unique identifier of a user for which at least one DSP is interested in displaying said advertisement;   determining a match between said unique identifier received from said identity broker; and said unique identifier in said rule file; and   identifying said at least one DSP interested to display said advertisement to said user in response to determining said match.   
     
     
         22 . The publisher server of  claim 20 , wherein said rule file defines a plurality of conditions based on which a DSP buys an advertising inventory to display said advertisement to said user. 
     
     
         23 . The publisher server of  claim 22 , wherein said plurality of conditions are defined based on at least one of a DSP bid value, number of impressions, publisher website information, time of the day, a day of a year, type of inventory, a variable defined by an exchange, a variable defined by said at least one DSP, and a user behaviors on said advertiser webpage. 
     
     
         24 . The publisher server of  claim 20 , wherein said unique identifier is a random value generated by said identity broker, a fingerprint of a browser, a fingerprint of a user electronic device, and a cross identifier. 
     
     
         25 . An identity broker for partner pixelling for user identification, the identity broker configured to:
 receive a unique identifier request message for a user from one of a Demand Side Platform (DSP) server and a publisher server; and   send said unique identifier for said user to one of said DSP server and said publisher server, wherein said unique identifier for said user is generated based on at least one parameter.   
     
     
         26 . The identity broker of  claim 25 , wherein said identity broker configured to send said unique identifier for said user to one of said DSP server and said publisher server by:
 determining whether said unique identifier is available in a database based on at least one parameter;   generating said unique identifier for said user based on at least one said parameter when said unique identifier is unavailable in said database; and   sending said unique identifier for said user to one of said DSP server and said publisher server.   
     
     
         27 . The identity broker of  claim 25 , wherein said identity broker configured to send said unique identifier for said user to one of said DSP server and said publisher server by:
 determining whether said unique identifier is available in said database based on at least one parameter; and   sending said unique identifier for said user to one of said DSP server and said publisher server when said unique identifier is unavailable in said database.   
     
     
         28 . The identity broker of  claim 25 , wherein said unique identifier is a random value generated by said identity broker, a fingerprint of a browser, a fingerprint of a user electronic device, and a cross identifier.