In a time where integrations are key to building efficient Martech stacks, an open API is a necessity. But what is an API and why is it important? We will update you! 

Texts are essential in our everyday lives, professionally and personally. Everyday we write. We write e-mails, blogs, presentations, reports, marketing material, posts for social media, or just simple text messages. All these texts we write – where do we store it? Digital assets, such as images and videos, usually have a special place to be stored in, preferably in a DAM system, but what about your texts?

When images, videos, documents and associated metadata is created in a number of different places, and needs to be directed to multiple channels - having one central hub that can handle both the inflow and outflow of assets (and metadata!) can not only save a lot of time, but also work as a safeguard making sure the right material is made available in the right channels.

To keep up in today's ever evolving communication landscape it is key to work smart. It's easy to say but sometimes harder to put into motion.

Fresh out of school and at around the same time Netscape launched its first browser, I started working in the small multimedia department of an otherwise very traditional advertising agency. There were two different browsers to take into account, the closest you got to multimedia on the internet was animated GIFs, and back-end programming was limited to processing HTML forms. The tools were basic but did the job.

When I first started working in the DAM-business, five months ago, I did not know what Digital Asset Management (DAM) really was. I knew that it was a storage for rich media, but not what kind of features and benefits that came with it. For those of you not yet convinced, bear with me.

Publishing your digtal assets can be a time consuming event with multiple uploadings and exports included. We made it easier for you, with QBank as a central hub.

There was a time when you picked up the phone and called your advertising agency when you needed a certain logotype in a specific file format. If it was urgent, you got it delivered by bike courier, maybe even on a SyQuest disk (look it up). I’m old enough to remember when files weren’t sent by email but by bike. I spent a summer doing just that; riding a bike with that SyQuest as my precious cargo.

A common approach by many organisations to calculating DAM ROI is to use statements like “each of our x employees spend y hours each day, searching for assets”. They then use this statement to count backwards and calculate the ROI; Search time per day (hour) x Employee cost per hour = Cost for Business per day.
This formula however, will only tell what the costs are without using a DAM. But there are more factors to consider when calculating the ROI for a successful DAM implementation.

The annual EPiServer client day took place last week and QBank was of course represented to promote the new version. Along with QBank 3, we're rewriting and rethinking our CMS plugins. Instead of fully custom solutions for each CMS as before, we intend to simplify the process significantly from now on.