-
Print
-
DarkLight
Error | Stage | Meaning | Resolution |
error":"buyer member …. does not exist" | Licensing | Invalid Seat ID | Ask client to confirm their seat ID |
Other Internal Content on AppNexus
AppNexus Data Marketplace Integration
Zeotap is integrated with the AppNexus Data Marketplace.
Data License Agreement | No additional agreement required, zeotap Terms & Conditions apply |
Data Transfer | The data is transferred directly between zeotap and AppNexus |
Data Usage Reporting | AppNexus reports data usage directly to zeotap |
Billing | AppNexus bills the client on data usage |
How to License Private to the client?
1. Add Data Providers: Before sharing a private with a buyer, verify that they have added zeotap in the Data Marketplace as described in Add Data Provider section. Sharing s with non-activated buyers can result in un-tracked and un-billed usage.
To access a particular data provider's offering, a new Console workflow is available to make that process easier. Link to external video to share with clients: {glossary.API}=v2">Data Management Platform _ Xandr Invest.mp4
After selecting the data providers you want access to, refresh the page and you will see that the data provider's s are now visible on your account. At this point, you can now run campaigns targeting these 3rd party s.

PS: Please note that a public can not be licensed privately to a client. Appnexus follows ONE ONE PRICE rule. So, you can not license same at different prices to different clients.
Data Upload
Appnexus has a daily upload line limit of 300 million IDs. So on a particular day irrespective of the number of s created, we will only be able to upload 300 million IDs. All subsequent uploads for the day will fail beyond that and they will be carried forward to the next day. On the next day if new s are created again then the s from the previous day would get priority for uploads. The priority order is as follows:
- Newly created s from previous days in order of creation date
- Newly created s on the same day
- Existing s refresh if triggered
Since 300 million line limit is barely sufficient to support new s upload, we have paused existing refreshes for the time being. So new s would expire after 30 days. If we want selective s to be refreshed it needs to be triggered from Unity where the level trigger control is available. If country level refresh needs to be triggered, it can be done on an adhoc basis from backend, but it can take anywhere between 1-2 weeks for the refresh to complete depending on the new s created during this period and number of s which have been triggered as part of the refresh.
Reporting
Reporting is automated through and we will get almost real time reporting (delayed by a couple of hours). This can be tracked in Unity UI (real-time) or DOMO (one day delay).
AppNexus DMP Integration
We have currently integrated with AppNexus Direct which means that:
Data License Agreement | We need one agreement per client (publisher/advertiser) we're working with |
Data Transfer | The data is transferred directly between zeotap and AppNexus |
Data Usage Reporting | We have no insights into data usage and have to ask for a manual report |
Billing | We have to bill clients directly based on their self-reported data usage |
Pricing of s and Reporting
Here, the pricing is only contractually agreed between zeotap and the client.
Reporting is also not supported by AppNexus Direct and zeotap needs to contractually bind the client to share regular reports with zeotap so that zeotap can account for revenues and share subsequent revenues with its Data Partners.
Steps required before sharing s with clients
- Clients interested in zeotap data to sign Data Usage agreement with zeotap
- Client to agree on the s required and pricing of the s
- Client to provide their AppNexus seat id for sharing
Inputs required to push the s to the client
To push s to clients, we need the following inputs:
- Name(s)/Id(s)
- Buyer Member ID - This is the AppNexus seat id of the client