The User Matching for sellers allows the advertisers who would like to you to buy impressions via RTB to submit its user data to you (AdSpirit). Thereby AdSpirit is to give back this user data in a position at a bid request to the advertisers so that the advertiser can deliver based on this data more accurate bids.
procedure
The sequence corresponds to the user matching for bidders: First, a URL will be sent to you by advertisers. In this URL data is inserted through corresponding placeholders. Hits a new user on AdSpirit a 1x1 pixel AdSpirit this user show where the URL of the Werbekudnen is included. So the request is sent to the user to identify the latter. The advertiser in turn responds by that it sends the data in the form of HTTP redirects to AdSpirit back.
Request expiry
- The first thing needed by advertisers a user matching URL, this Leave RTB advertising.
- You also have the advertisement a user matching database (see below)
- Within the User matching URL, you can use the following placeholders to the respective data to the advertisers to send:
| %dataid% | (Required), the user ID matching database |
| %redirect% | (Required) callback URL to the advertising customer send the data |
| %userid% | (Required) ID of the user at AdSpirit |
| %calltype% | (optional) tpye as the advertising client to send the data (js, iframe, redirect) |
- all unreconciled user is now AdSpirit send to these users matching URL and ask for data synchronization.
response expiry
the ad server of the advertising Customer receives the request for data matching this responds by appending the following parameters to redirect as%% passed callback URL:
| dataid= | (Required), the user ID matching database (%dataiD%) |
| user_id= | (Required) ID of the user at AdSpirit (%userid%) |
| external_user_id= | (Required) ID of the user when advertisers |
| custom_*= | (optional) additional user information. The user data is AdSpirit send them along with every bid request as HTTP cookies. Teh name of teh cookie ist then written without "custom_" (d.h. aus Parameter "&custom_abc=123" wird Cookie "abc=123"). |
The AdServer of advertisers will spend this callback URL, depending on the value of the parameter %calltype% as follows:
| js | document.write('<div style="position:absolute; left:0px; top:0px;"><img border="0" width="1" height="1" alt="" src="[CALLBACK-URL]" /></div>'); |
| iframe | <html><body><div style="position:absolute; left:0px; top:0px;"><img border="0" width="1" height="1" alt="" src="[CALLBACK-URL]" /></div></body></html> |
| redirect | PHP-Code: header('Location: [CALLBACK-URL]'); |
What is a user matching database?
Users matching database stores all information received via user matching the advertisers on the individual user. Depending on the application, it is important to use the same or different users matching databases:
| same databases | Because we will send all the information of the selected database on the user at each bid request to the advertisers, it makes sense then to use the same databases when it comes to the same advertisers. As you use the same database for multiple advertising media within the same campaign or advertising campaigns different but belong to the same customers. |
| different databases | To the user information of an advertiser not to mix with the user information of other advertisers using always different databases when it comes to different advertisers to which the bid requests are sent. |
Request types
AdSpirit can also accept the formats of other providers requests or answer next to the AdSpirit's own format. See "Other supported API's."