Why you need ad injection SDK
Browser companies (Mozilla, Google, Microsoft) limit the usage of Toolbars and browser extension.
Soon users will only be able install extensions approved by Google on Chrome.
This has led to media companies to adapt with an almost certain loss of revenues, at an attempt to comply with new challenging regulations.
Happily Komodia can help with these challenges via the ad injection SDK. Additionally supporting Safari and Opera, two browsers that are not monetize by current plugins solutions.
Komodia’s solution
Komodia’s Redirector SDK, can be used to easily inject javascript into any place in the HTML (HTTP or HTTPS) without relying on browser extensions. Also the code can be used for all five leading browsers which means that you don’t have to write different code per browser.
How does it work
You install Komodia’s SDK on the desktop machine (it’s 3mb compressed, size can be lowered if you don’t need to decrypt SSL pages), by calling the .exe with install flags, and after it’s installed you can choose to intercept any browser on the desktop.
After the traffic is intercepted you can inspect it using the DLL or COM framework and decide per page if you want to inject Javascript or any other HTML component.
SSL
The SSL Digestor component allows you to get/modify/inject all SSL traffic decrypted and without any warning messages to the user.
Latency
There will be added latency but not noticeable for regular users. Also the SSL decryption adds CPU consumption.
Anti viruses
The SDK has anti virus capabilities and each compiled version generates a totally new version.
Global proxy interception
The SDK allows you to intercept all traffic going to a localhost global proxy which means you can:
- Inject your JS even if there’s a solution that uses global proxy.
- Actively remove global proxy injected JS by either removing the JS from HTML or blocking the requests to the ad server.
Ad injection SDK vs global proxy
Some companies use global proxy which is relatively easy to develop (the part of installing a custom root CA can be a challenge). There are number of problems with this approach:
- There can be only one proxy on the machine so you’ll be competing with other players.
- Some of the big players are using this method (and they formed a cartel so they work in collaboration) which means that on any computer that a big player is installed you’ll need to either “fight” them, or your solution would not work at all (unless you can get into this cartel, but it’s only if you’re big enough to let you in the club).
- Since this becomes the “easy” way to avoid Google new policies, we believe that global proxy will be limited/targeted by either Google/Microsoft or the AV companies in the near future.