Will using SFP's mediation feature cause additional latency?
Latency is a valid concern, as with all ad serving solutions. That said, we do not expect SFP's mediation feature to cause any additional latency on top of what you might otherwise expect from a standard ad serving waterfall setup. We are in the process of collecting data points to cite specific numbers, but we have yet to see any latency concerns from any of our other publishers.
Does Sharethrough have existing partnerships with any third-party networks?
We do not have existing partnerships with any third-party ad networks. We are in the process of expanding our partnerships with DSP's and other alternative demand sources, but we encourage publishers to run additional native networks inside of SFP to ultimately simplify your operations and maximize your native yield. That said, you will need to establish independent business terms with each of these networks. You will also need to manage blocklist and pricing settings, as we do not have any control over third-party network technology.
What happens if there are two networks at the same price? How does SFP allocate the impression?
This entirely depends on where the publisher has chosen to prioritize each tag. Publishers do not have the ability to set networks at the same priority, so the impression will go to whichever network is set at a higher priority.
How will SFP handle blacklisting or whitelisting?
SFP is not responsible for enforcing blacklists or whitelists across third-party networks. The publisher is ultimately responsible for ensuring that all demand sources, besides those sourced via STX, comply with the publisher's provided blacklist or whitelist.
What if the third-party network doesn't support responsive design?
While we generally do not recommend running static creatives inside of SFP as that conflicts with the concept of native advertising, we do support any and all tags from the provided list of networks should you want to run them inside of SFP.
Does Sharethrough provide viewability data for third-party networks?
Sharethrough does not extend its viewability beacon to third-party networks. Once the impression has been allocated to a specific network, that network is ultimately responsible for both filling and reporting on that impression.
I have trafficked and prioritized my third-party networks. Why is the impression and revenue data in SFP different from what I'm seeing in the third-party network's UI?
While discrepancy can be an annoyance, it is a fairly common element of ad serving. We will do our best to investigate discrepancy issues, although we cannot guarantee that a third-party network's technology will always function properly.
For content recommendation widgets, does Sharethrough pull in multiple pieces of content or just one?
It all depends on the integration. For a standard, in-feed integration, we recommend trafficking a network tag that only pulls one piece of content so that it matches the format of other demand.
Can third-party networks collect user data? What data is being collected, if any?
SFP has no control over whether third-party networks collect user data, nor do we know what data they can and will collect. It varies on a network by network basis. With that said, we encourage all publishers to conduct due diligence before deciding to work with additional native networks.
Why do my network earnings not match my actual earnings for that network?
For more accurate information please refer to your third-party network’s revenue reporting. To track your network’s revenue in SFP, please enter the CPMs on your placement's Network screen.
Can I mediate third-party networks if SFP's tags are hardcoded on my page?
Yes! SFP is ad server agnostic, so a publisher can traffic our tags either in their ad server or directly on the page. As long as SFP.js is on the site, mediation will be fully supported.*
How can I prioritize networks ahead of STX?
The goal of SFP is to provide publishers with the most yield optimal solution for managing native ads. While the current iteration of mediation does not support prioritizing third-party demand ahead of STX, we are in the process of building a solution that will enable publishers to prioritize both STX and third-party networks however they please -- this includes both prioritization ahead of STX, as well as ultimately a unified auction.
*Keep in mind that the current version of our SDK does NOT support mediation.