Visuals are all the rage today: it is immediate, direct, and convenient for the one viewing it. Today’s easily accessible way to consume digitally is something that advertisers need to consider. This is due to the high likelihood of online users staying onto the campaign once hooked with an appealing setup. Today, we will talk about the importance of video ad formats and how to better optimize your video ad campaigns.
Today we want to give you an insight on how to get connected to plista by using the plista APIs. In the following we wrote a short and easy setup guide.
In order to connect your system to plista, feel free to use our public APIs.
For these REST based APIs, you need to have an user account set up. No SDK are needed, just create simple calls with e.g. cURL.
2018 is the year that calls for advertisers to consider revamping their ad formats. Nowadays, innovative and creative outlets go a long way in targeting markets. With more visual and optimized formats, advertisers are sure to reach their targets and offer a better, user experience. We recently discussed that advertisers have a need for innovation: creative optimization. Our expert, Stefan Klimek, Global Vice President of Finance, HR, and Commercial at plista describes that advertising formats are “becoming more dynamic, animated, and fundamentally more creative.” Today, we would like to share with you a case study of a plista e-commerce client who had a great campaign experience using our DCO technology.
2017 has been an incredibly transformative year for the digital advertising industry. Global advertisers and publishers had the opportunity of experiencing shifts impacting the industry, such as increased ad spending budgets to the rise of mobile users. Groundbreaking trends and topics that stuck around soon became household names such as going programmatic and transparency .
This past year has also been full of change for us at plista. We launched our new SSP integration as well as announced our new global managing director, Michel Gagnon.
Let’s have a look at an overview of 2017 and reflect on the memorable moments that have occurred this last year.
Every team managing more than a few Debian packages at some point faces issues with serving, or, if not that, how effective it’s being served. In our case, we used to use a different tool, Reprepro, which does a pretty good job on the package management, however it does not support having more than one version per package. This kind of constraint directly affects when we need to meet dependencies or even rollback to previous versions and was always problematic in achieving the required results when facing this kind of scenario.
In the past years, we have seen budgets for online marketing activities rise. News sites and social media channels such as Facebook are competing to grab the biggest slice of the budgets. Advertisers are seeking innovative and effective ways to reach their target groups across different channels.
This article quickly describes how we handled the transit of external-generated customers events toward our internal Kafka cluster and how we built a reliable failover system using Flume-NG.
We started to work with Apache Flume on its 0.9 version since the beginning, because it was fitting well our need to make internet events landing into a first dumb backet, before being processed.
There are many different ad formats for your advertising message. Each has its own advantages and meets a certain need. Today we want to talk about a format that is sometimes underestimated but is actually very effective: the In-Feed Ad.
This series of articles is an experimental attempt to explain problems of unit tests in PHP applications, turning the theory upside down. From my practice I know it well that even skilled developers often have difficulties with rearranging their OOP knowledge onto new test driven approach. I will try to share my experience with the subject in form of original questions and answers, that elucidate very important and not always obvious aspects of unit testing and clean code practices.
In the first part we’ll consider the common misunderstandings of the OOP and unit testing principles, that may lead to wrong perception of test driven design practices.
At the beginning, we used to cluster our Spark applications using Apache Yarn as our main Resource Manager. At that time we considered an RM that was more like a “Spark extension,” which was basically used to optimize Spark processes and nothing more. Our usage of Yarn then never went beyond deploying those applications, such as monitoring them via web browser by typing something like http://yarn.url:4040/<spark_app>.
Problems in Yarn came with the need to deploy applications using different Spark versions, which were thus submitted to the cluster as Docker containers. This requirement with the relatively first deploy attempt raised a set of structural issues and unplanned limitations using Yarn. One example: deployed containers used a private ipv4 IP (eg: 10.0.0.20) in the slave, which of course was preventing us from connecting to the Spark-monitoring interface from outside.
After some brainstorming, we worked around this situation by setting up an IPv6 stack for each Yarn slave, thus assigning an IPv6 address to each container and finally reaching the exposed Spark web interface. It was surely working, but then we moved to Mesos.