Troubleshooting for AppNexus
  • 05 Apr 2024
  • 3 阅读时间
  • 贡献者
  • 黑暗

Troubleshooting for AppNexus

  • 黑暗

文章摘要

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 segment to the client?

1. Add Data Providers: Before sharing a private segment with a buyer, verify that they have added zeotap in the Data Marketplace as described in Add Data Provider section. Sharing segments with non-activated buyers can result in un-tracked and un-billed usage.

To access a particular data provider's segment offering, a new Console workflow is available to make that process easier. Link to external video to share with clients: 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 segments are now visible on your account. At this point, you can now run campaigns targeting these 3rd party segments.

PS: Please note that a public segment can not be licensed privately to a client. Appnexus follows ONE SEGMENT ONE PRICE rule. So, you can not license same segment 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 segments created, we will only be able to upload 300 million IDs. All subsequent segment uploads for the day will fail beyond that and they will be carried forward to the next day. On the next day if new segments are created again then the segments from the previous day would get priority for uploads. The priority order is as follows:

  1. Newly created segments from previous days in order of segment creation date
  2. Newly created segments on the same day
  3. Existing segments refresh if triggered

Since 300 million line limit is barely sufficient to support new segments upload, we have paused existing segment refreshes for the time being. So new segments would expire after 30 days. If we want selective segments to be refreshed it needs to be triggered from Unity UI where the segment level trigger control is available. If country level segment 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 segments created during this period and number of segments which have been triggered as part of the refresh.

Reporting

Reporting is automated through API 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 Segments 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 segments with clients

  1. Clients interested in zeotap data to sign Data Usage agreement with zeotap
  2. Client to agree on the segments required and pricing of the segments
  3. Client to provide their AppNexus seat id for segment sharing

Inputs required to push the segments to the client

To push segments to clients, we need the following inputs:

  1. Segment Name(s)/Id(s)
  2. Buyer Member ID - This is the AppNexus seat id of the client

本文对您有帮助吗?

What's Next