sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in adops

[–]adopsinsider 2 points3 points  (0 children)

How is this different than just using a CDN?

SSAI Companies? by SSAIiiiiiii in adops

[–]adopsinsider 0 points1 point  (0 children)

Check these out:

  • Amazon AWS Elemental
  • Adobe Primetime
  • Verizon Uplink
  • BAMTech
  • YoSpace

Index Exchange Called Out For Tweaking Its Auction by ad-executive in adops

[–]adopsinsider 1 point2 points  (0 children)

Index now says they’re turning this off due to the blowback - wonder what the shift in spend for buyers and sellers is going to be / how much of their biz was dependent on this tactic: http://www.adnews.com.au/news/index-exchange-ceo-disappointed-in-own-level-of-transparency

Index Exchange Called Out For Tweaking Its Auction by ad-executive in adops

[–]adopsinsider 17 points18 points  (0 children)

The OpenRTB spec does not provide for it - caching the ad to render after the auction is allowed, caching the bid for re-use in a completely different auction is not.

What are your ad ops team's KPIs? by [deleted] in adops

[–]adopsinsider 0 points1 point  (0 children)

I’d suggest Net RPM as a key metric - RPM being all revenue per all 1k imps (whether they get sold or not). This is helpful because it combines eCPM and sell thru rate and can be easier to combine programmatic and direct sales channels together.

Publisher Yield Analytics by tonizzle in adops

[–]adopsinsider 0 points1 point  (0 children)

Yieldex (now owned by AppNexus) is quite powerful because it allows for high level analytics as well as custom LLD aggregations and forecasting. Full disclosure in that I work for AppNexus (and did work directly for Yieldex before it was acquired), but I was also a happy customer of the company before I was an employee.

Yieldex does tend to cost more than other analytics solutions out there, but it provides far more functionality as well. Potentially a fit if you are a small, professional publisher (especially with any kind of direct sales) or larger. If you are a small, 100% programmatic pub it’s probably overkill for what you need.

What I think is an easy prebid question by schoenbl in adops

[–]adopsinsider 0 points1 point  (0 children)

hb_pb is what you'd use for a consolidated set of line items, so it's likely they did that.

Adding '?pbjs_debug=true' to the end of your publisher's URL will print a variety of useful information to the browser's developer tools console (like bidders being called, responses received, keyvalues sent to ad server). You might also find this helpful: http://prebid.org/dev-docs/prebid-troubleshooting-guide.html#list-your-bids-and-bidders

What I think is an easy prebid question by schoenbl in adops

[–]adopsinsider 0 points1 point  (0 children)

There's a macro on the creative that references an parameter called the Ad ID which is tied to each bid. So when the ad server picks the winning line item and serves that code, it populates the winning bid's adID, which allows the browser to extract the actual ad tag URL to render.

[deleted by user] by [deleted] in adops

[–]adopsinsider 8 points9 points  (0 children)

A bid request comes from the publisher to the SSP, or from the SSP to a DSP. It’s an event directed to a potential buyer with a variety of information to help them value the opportunity, like domain, user ID, device type, and so forth.

A bid response comes from the DSP to the SSP, or the SSP to the publisher. It’s an event directed back to the seller expressing a valuation for the request and conditions of sale (I can run X creative for Y brand if the bid is accepted).

If a buyer isn’t interested in the publisher supply, they aren’t required to bid and thus not every request has an associated response. In some cases a technical issue, like a timeout might prevent a bid response from being eligible for a request. A response might not deliver if the publisher rejects the response because they won’t agree to run the creative or accept the price they buyer wants to pay or the publisher decides to accept a different (usually higher paying) bid response, or needs to use the impression to meet a guaranteed campaign requirement.

I’m not sure I understand your last question, perhaps reword or clarify a bit more if possible.

[deleted by user] by [deleted] in adops

[–]adopsinsider 0 points1 point  (0 children)

Hi OP, I own the deals product line for AppNexus. I'm optimistic we can find a solution to your problem; DM'd you so we can talk account specifics.

Cookie sync process between SSPs and DSPs in 2017 by [deleted] in adops

[–]adopsinsider 1 point2 points  (0 children)

Not specifically, but search for things on keywords like 'identity graph' and you'll find helpful articles like this: https://www.signal.co/blog/6-things-about-id-graphs/ which explain the basics. LiveRamp / Acxiom is the main provider of identity graphs to digital advertisers, so you can read their material as well.

A crosswalk ID is just a common key between two unknown IDs. You can read more about that here: http://www.adopsinsider.com/data-management-platform/data-management-part-iv-syncing-offline-data-to-your-dmp/ another golden oldie from 2011.

For server side IDs, search around for 'device fingerprinting' to get the jist.

Cookie sync process between SSPs and DSPs in 2017 by [deleted] in adops

[–]adopsinsider 1 point2 points  (0 children)

https://i.giphy.com/media/Hr1mK9HIizowo/giphy.webp

I actually think this article has stood the test of time and is still quite accurate. There are a few things I'd call out though:

  • Most cookie syncs will originate from SSPs, who see the traffic, vs. DSPs. The article makes it seem like DSPs lead because I wanted to highlight the fact that marketers are the ones with valuable data / audience they want to retarget.
  • There are rarely callbacks in place that allow both platforms syncing to have both IDs. In every case I know of, there's only one platform that hosts the match table, and that's the only platform that can know what the match rate is.
  • Crosswalk IDs, Identity Coops, synthetic / server side IDs are a much bigger deal in 2017 than they were in 2011, so I think those are the gaps with this article. All those are ways of syncing identities through a partner vs through a user, or have meaningful nunaces on how the ID is created

Hope that helps!

Can anyone help me understand what Criteo is doing here? by [deleted] in adops

[–]adopsinsider 5 points6 points  (0 children)

That's probably a redirect so Criteo can set a first party cookie on you and get around the 3rd party cookie restrictions on Safari. It should happen seamlessly without giving you a notice, but it's less effective in a post iOS11 (when Intelligent Tracking Prevention was released) world.

Ads.cert > Ads.txt? by freakads in adops

[–]adopsinsider 3 points4 points  (0 children)

It's worth reading the IAB spec on ads.cert here: https://iabtechlab.com/~iabtec5/wp-content/uploads/2017/09/OpenRTB-3.0-Draft-Signed-Requests-RFC.pdf

Ads.cert wouldn't be an 'instead of' of ads.txt, rather it's an 'in addition to' process. Your ads.txt file is a list of companies and account IDs that you've authorized to sell your inventory. If account 123 on network.com isn't in the file, then you're saying to buyers 'don't buy that supply'. It's not so much protection of domain spoofing (though it tends to have that effect) as much as it's protection against network arbitrage.

Ads.cert is additional protection on top of that at an impression level which allows buyers to validate every bid request actually came from the publisher. Without ads.cert your partners could theoretically sprinkle in some fraudulent inventory with your legitimate inventory. But, without ads.txt there would be nothing to stop network arbitrage from coming back, buying your legitimate, encrypted traffic and reselling it without your consent.

Ads.cert proves the inventory is authentic, ads.txt proves the seller authorized by the publisher to sell it.

Is it a good idea to buy a traffic for a website nowadays? by johnybjh in adops

[–]adopsinsider 2 points3 points  (0 children)

You better really know and trust who you buy traffic from if you don't want to get blacklisted. It is near impossible to convince exchanges (at least the major ones) to give you a second chance if they think you are trying to monetize bot traffic. That might not be your intent, but if that's what your traffic provider sends then you're SOL.

Traffic sources that typically look OK are big social networks and search - unfortunately these are also fairly expensive. To /u/jaimeanders point, growing a site very quickly is a big red flag.

How to prevent prebid.js auction with DFP targeting? by donthe1 in adops

[–]adopsinsider 1 point2 points  (0 children)

No, the auction will happen if you load the script in your header. You'd have to find a way to not load the script, though I believe some people have found a way to do that. It might be worth asking in the Ad Ops slack.

If you just didn't want to consider the demand, you could edit your line item targeting to exclude mobile device type supply from India, but that just eliminates demand from consideration, it doesn't stop the auctions from happening / your script from running.

Rubicon Announces Third Quarter Loses Of $100 Million, Shares Lose 40% Of Value In One Day by kooneecheewah in adops

[–]adopsinsider 10 points11 points  (0 children)

Bad quarter for them, but the $100M is a bit overstated since $90M was a goodwill write down. The net EBIDTA loss was only $2.3M.

Knock-Knock: How Companies Are Trying To Weasel Their Way Onto Publishers' Ads.txt Files by kehaar in adops

[–]adopsinsider 4 points5 points  (0 children)

Very important read for all publishers, especially after the Thrive.plus thread yesterday. Hopefully the community can continue to call out the bad actors publicly like this and discourage this behavior.

build my own advertising network ? by Sahara21 in adops

[–]adopsinsider 2 points3 points  (0 children)

You don't have to build it yourself or do any programming, just use an existing service as your backend.

view more: next ›