Last month I switched from Google Analytics to Yandex.Metrika as my analytics suite. In this blog post, I explain why I chose Yandex.Metrika and why I believe it is a great and powerful tool.
On this page you can find all my blog posts across all topics.
When I finished preparing the code for another blog post, I had to add a LICENSE and a README file to the Git repository of my code. Adding those files to the very first commit and adding a copyright notice to all C# source files, required rewriting of Git history. In this blog post, I share the scripts I used myself.
I created an open sourced inbound connector to demonstrate how to make a simple, yet powerful, integration for loading large XML documents with product data into iPMC. After doing thorough profiling of the code, I also incorporated several performance optimizations.
What if product managers wants to have all images tagged in InRiver, but does not really like to do it manually? How can that be automated using artificial intelligence in the cloud? In this blog post I create a new InRiver iPMC extension that integrates to Azure's Computer Vision API.
In InRiver some fields have raw values that need to be transformed because of a target system. It could be that all color codes should be consolidated to just 20 color groups. But how to do that? And where to store all the transformation combinations? In this blog post, I demonstrate how to implement an InRiver iPMC extension that transforms field values using a custom table in Azure Table Storage.
From working on InRiver PIM projects, I have implemented a few custom outbound connectors. They would export catalogs to EPiServer Commerce, Demandware (now Salesforce Commerce Cloud) as well as Azure Blob Storage. In this post I give away six tips on implementing a good outbound connector for InRiver Product Marketing Cloud (iPMC).
Digital marketers of today might want to work with dynamic product ads on platforms like Google and Facebook. This requires a machine readable product catalog file. To showcase how to make that data available, I created a tool for EPiServer Commerce, which generates and provides such a file.
When EPiServer runs in a load-balanced environment, the servers rely on exchanging messages about system events with each other. At the moment, EPiServer supplies four event providers. This post is about implementing a new event provider, using Redis as a broker for these event messages.
I have heard a lot about Bitcoins and other cryptocurrencies. About what they are, what they can do and how much they will revolutionize payments and money transfers. So, as an experiment I decided to create an EPiServer Commerce plugin to accept payments in cryptocurrencies.
How can an AJAX service serve texts (error messages, label texts, product descriptions) or images from a multilingual EPiServer site? How to make sure that the server returns content in the correct language?