Here user can integrate/add API of a Particular DSP ID which will fetch the data & will show Net Impression and Net Revenue of that particular DSP ID. (“*” are mandatory fields)
DSP Endpoint* – Here user will select DSP ID from the drop-down list for which the user wants to integrate
Login API – Here user needs to enter the Login API provided by the DSP partner.
Reporting API* – Here user needs to enter the Report API provided by DSP
Enter field name of impression* – Here user needs to enter the Impression name of that particular DSP ID. For Example: – If the DSP partner is OwnAdX, then the Impression field is “Audit Impression”
Enter field name of revenue* – Here user needs to enter the revenue name of that particular DSP ID. For Example:– If the DSP partner is OwnAdX, then the Revenue field “Audit Revenue”
Response Type* – Here user needs to select Response type from the drop-down as per DSP requirement. For Example: – if DSP partner is OwnAdX then Response Type is“JSON”.
Partner Template* – Here user needs to select Partner from the drop-down as per DSP requirement. For Example: – If DSP Partner is OwnAdX then, a user needs to select OwnAdX from a drop-down (We have added partner template)
Partner Template:- Select the Partner Template from the dropdown. for example, the Partner name is XYZ & the platform is Ownadx it will appear like XYZ[OwnAdx]. After selecting the partner template, per platform endpoint macros option will appear as shown below...
Cookie Sync It also called cookie matching, is a process that enables the platforms (SSPs, DSPs, DMP's) to synchronize their cookies and share the user’s data from the various Publisher's websites with each other. In this way, Demand partners are able to know about...
Advance Report The Advance report tab is under the Report section here user can download PublisherId or CreativeId or Site/AppId. Date Range - The user can download data for the last 2 days, in order to do so the user has to just select start Date system will set the...