How we created a Publisher Customization Tool that would separate codes in publisher-specific JS files for ad displays

To show an advertisement in a publisher website, they provide a code snippet to the publisher to add to the website. This code snippet calls a JS file, which is responsible for showing the advertisement in the predefined area of the website.

But in various publisher websites, to show the ad properly, there are some small style and JS modifications needed. These modifications would be website specific (not for all the sites), so these CSS and JS were written in the main JS file only.

That was a big issue. The problem is that the main JS file with all the custom rules in it was served to all the publishers. But it included some publisher-specific CSS and JS.

So if there is wrong coding in just one of the script in the main JS file, it caused an error, the entire campaign didn’t run, and everyone would lose money and time.

Our solution was to make a tool called PCT: Publisher Customization Tool. This tool would separate those codes into separate JS files for each publisher. And each newly created file would inject the publisher website with some custom CSS and JS.

Further, this tool is only to be used by the admin. Not by publishers.