If the ad industry is serious about transparency, let’s open-source our SDKs

Year after year, a lack of transparency in how ad traffic is sourced, sold and measured is cited by advertisers as a source of frustration and a barrier to entry in working with various providers. But despite progress on the protection and privacy of data through laws like GDPR and COPPA, the overall picture regarding ad-marketing transparency has changed very little.

In part, this is due to the staggering complexity of how programmatic and other advertising technologies work. With automated processes managing billions of impressions every day, there is no universal solution to making things more simple and clear. So the struggle for the industry is not necessarily a lack of intent around transparency, but rather how to deliver it.

Frustratingly, evidence shows that the way data is collected and used by some industry players has played a large part in reducing people’s trust in online advertising. This is not a problem that was created overnight. There is a long history and growing sense of consumer frustration with the way their data is being used, analyzed and monetized and a similar frustration by advertisers with the transparency and legitimacy of ad clicks for which they are asked to pay.

There are continuing efforts by organizations like the IAB and TAG to create policies for better transparency such as ads.txt. But without hard and fast laws, the responsibility lies with individual companies.

One relatively simple yet largely spurned practice that would engender transparency and trust for the benefit of all parties (brands, consumers and ad/marketing providers) would be for the industry to come together and have all parties open their SDKs.

Why open-sourcing benefits advertisers, publishers and the ad industry

Open-source software is code that anyone is free to use, analyze, alter and improve.

Auditing the code and adjusting the SDKs