Advertisement placement is a double-edged sword.
You would like to avoid ruining your fancy design, but at the same time, you could leverage advertisement content to foster discovery, and you might find new ways to scale your business.
You have to improve both customers’ and brands’ experience, as all things should be.
There is nothing worse than sharing an intrusive Ad that does not add value to the user.
An example? I am bald, so please don’t waste your money on advertising shampoos to me 🙂
A Brief History of Price Update (Part 2)
Here we go again.
This is the second episode of our docuseries about how we are managing retailers’ data for our beloved customers.
If you did not read our previous post about this topic, you should spend a few minutes catching up on it.
With this part, we would like to introduce the hidden aspect of our product and I promise, it is not a buzzword: Machine Learning.
In the following paragraphs, we are going to show new technical improvements and the analytics aspects under the hood.
A Brief History of Price Update.
Hold onto your seats; I am going to guide you around our brief history of the price updating process.
Prices must be updated every day, following our Retailers procedures to provide the best experience to our customers.
If you think it should be a simple procedure, consisting of just updating the right record and go on with the next one, I totally agree with you!
When we were in the start-up phase back in the days it was that simple, but soon we had to forget about doing it this easily when we had to scale it up from a few thousand updates to millions.
In the next paragraphs, I will show you the evolutions of this process during the years.
How we handled the spike of more than 4k% new users in a week.
Covid-19 changed and is changing everything.
From customer behaviour to customer spend, no one could have expected this.
Our servers neither.
This post would like to be a simple overview of what we did to maintain our website and apps reliable during this time.
And yes, you have read properly, how we kept the infrastructure responsive while serving more than 4000% new users (and of course the previous one) plus a few DoS attacks.