Forum Moderators: martinibuster
Why do they do that? Why can't they just store these thing into their database? Like the google_ad_client, why can't they just use the website url to find out which client they are? It's not like google can save time from database retrieval just because of these few data, they have to do at least some server retrieval to get those ads and tracking.
There should be a reason, I know that google engineers are not stupid.
Many thanks.
Why do they do that? Obviously only Google engineers would have the answer, but I can think of a few reasons:
I'm sure there are other reasons as well, those are just a few that I can come up with quickly.
Chad
Yes, a Google database could do the same thing, but not as flexible. And from an ITIL point of view, change management is fully in their own hands, without requiring any changes on websites (usually). Impact analysis is more simple. Change impact plans are smaller. Incidents and problems are easier to manage and determine and even more important, problem ownership is simple and clear. Most of the time without requiring any [discussion / communication / questioning / labour / cost] with the 'external' website owners and/or the (javascript) endusers.
Then again, a serverside driven database feed would make it possible to make ads more accessible, technically (W3C-wise), for text-browsers, non-javascript browsers, screenreaders, (adblockers), etc.
Hey... I want both! ;)
The parameters that I am aware of are:
All of the google_color variables can also be arrays of color codes to be chosen at random.
Chad