When users matching bidder for all users information is the AdSpirit about the user has to the partner transmitted. Once this partner the partner is then demands a bid of AdSpirit forward with the bid request, the user data, so AdSpirit yet has all the information, even without direct contact with the user.
How does the user matching for bidders?
For all inquiries, the publisher of AdSpirit sends should be created before the publisher a user profile. Users over nor the publisher with AdSpirit should have no user profile request to a user profile. For this, the user matching is used to the user data of AdSpirit to hand over to the publisher. The publisher binds to an all new users a pixel code with a AdSpirit URL. By means of the pixel codes is to get at AdSpirit the request sent user data. As a result to this request AdSpirit will send to the publisher, the user data to that user.
Request expiry
- Generate the menu item "RTB users matching" a user matching code. This consists of the following parameters:
| UMID = | ID of the user matching codes |
| DataID = | ID has the AdSpirit the Publisher |
| userid = | ID of the user with the publisher |
| RedirectURL = | Callback URL |
| call_type = | Callback type |
- Generate this URL and send it where you buy the publisher traffic.
- The publisher binds this URL into a 1x1 pixel and shows him every new user.
- At each display the URL / pixel of Publisher replaces the placeholders with the relevant information
response
If the request is sent by the user to the AdSpirit AdServer it responds with a redirect to the passed as the callback URL landing page. Here AdSpirit following URL parameter to the callback URL depends on:
| DataID = | ID has the AdSpirit the Publisher |
| user_id = | ID of the user with the publisher |
| external_user_id = | ID of the user at AdSpirit |
Moreover AdSpirit transmits a series of user-relevant data. These are passed with other parameters, and each begin with "custom_".
The data sent the AdSpirit to the publisher (external_user_id and custom _ * - parameters), the publisher should now at each bid request to AdSpirit with information such as: external_user_id as HTTP parameters X-RTB user ID and custom _ * - parameters as HTTP cookies. The names of the cookies are in this case designed without "custom_" (ie of parameters "custom_abc = 123" is cookie "abc = 123").
Request types
AdSpirit can also accept the formats of other providers requests or answer next to the AdSpirit's own format. See "Other supported APIs."