715 karma · joined December 11, 2009
As the article mentions Trade Desk ad delivery is currently blocked because they use the same apex domain for delivery and ID matching.
- api.id5-sync.com
- api.rlcdn.com
- b1-nydc1.zemanta.com
- check.analytics.rlcdn.com
- di.rlcdn.com
- direct.adsrvr.org
- htlb.casalemedia.com
- ib.3lift.com
- id.hadron.ad.gt - id.rlcdn.com
- id5-sync.com
- idsync.reson8.com
- idsync.rlcdn.com
- img.3lift.com
- lb.eu-1-id5-sync.com
- match.adsrvr.org
- pippio.com
- pix.cdnwidget.com
- pixel.tapad.com
- ups.analytics.yahoo.com
- v2.pixel.newscgp.com
“When we refer to postponed work as technical debt this automatically biases us to assume that both ongoing and future costs are more certain than they really are. This, in turn, causes us to overestimate these costs, leading us to be overly cautious about deferring work. If it is your intention to bias the decision against postponement, this is clearly the best term to use. However, if you are trying to carefully weigh of pros and cons of postponing work, I’d recommend using a more neutral term like deferred work.”
http://reinertsenassociates.com/technical-debt-adding-math-m...
https://github.com/openai/openai-cookbook/tree/main/apps/fil...
There's a useful framework called RICE where you evaluate/score ideas by Reach, Impact, Confidence, and Effort. Sometimes assigning numeric values feels forced so I often use it as "dimensions to be thinking about" rather than a literal scoring system. [1]
There's some great stuff in Reinertsen's Flow book about different sequencing strategies and when to use each. Eg, When delay costs are homogeneous, do the shortest task first. When task durations are homogeneous, do the highest cost-of-delay task first.
[1] https://www.intercom.com/blog/rice-simple-prioritization-for...
Too many metrics can be a problem but it's not the real problem. The real problem is choosing metrics without any regard for the decisions they're supposed to inform.
When you understand that the purpose of all measurement in business is to reduce uncertainty for a decision to be made, everything comes into focus, and you'll have a natural constraint on your scope of measurement.
The quote you keep referencing is false. The ePD says nothing about this.
That was the moment Zoom received your consent to store data transmitted by cookies. Adding a few more cookies to the pile, regardless of expiration date, doesn’t change the agreement.
Rummaging round the cookie bin on uninstall is a nice find and deserves a raised eyebrow but this doesn’t really have anything to do with GDPR.
The point of tag managers is to let non-developers update production without going through a code deployment so the usual code review and oversight doesn't apply.
Also worth keeping in mind that this is the bank's marketing site. It's almost surely managed by a different team than the actual online banking site and probably has looser restrictions.
Btw, tracking scroll points for specific DOM elements is one of the plugin options, so for instance you could track the end of the .comments div as you mentioned.
Just wrote you back! You know, I actually don't see major publishers embracing responsive design, at least in the short term. I think mobile-specific sites and dedicated apps are much more inline with how they see the world. It's also a business opportunity for them to sell separate experiences as separate products, right? Merging everything into one isn't necessarily a win.
The goal with responsive design is to serve the same site—the same mark-up, the same assets—to all devices. Which means that any conditional serving of ads has to happen client-side.