FAQ

POAS stands for Profit On Ad Spend. In short, it tells you how much bottom line profit you get from every spent marketing dollar. This way you see the real benefit from your marketing, rather than only revenue that you see when measuring with ROAS.

CLV = Customer Lifetime Value and LTV = Lifetime value. When calculating CLV/LTV, you do not only take into account the profit from one sale but all sales that have preceded and are expected to to follow from the sale.

You can tell Smart bidding strategies, such as Google's Target ROAS to find the customers who turn the highest revenue. It will work the exact same way but now with profit, rather than revenue, as the signal.

You can feed the profit data calculated by Kuvio into any marketing platform, and then you can then either activate smart bidding algorithms with profit instead of revenue, or to simply have profit as a metric when evaluating and adjusting bids manually.

With Kuvio you can essentially export the data generated by Kuvio anywhere. Kuvio offers integrations with Google Data Studio, Google Analytics, Google Sheets, CSV and many other ways to use your data in your favourite platform.

Our recommendation is to focus on sustainable growth. You can still accept lower or negative profit orders if you believe it will have a long term positive impact. Profit will be as a good signal (always better signal) that revenue is.

In case you have negative profits on your orders and there’s a strategy behind it you can adjust the minimum values you send to the advertising platforms. This does not affect the reporting profit, only the values you use for optimization.

You can choose the activation method you prefer, we support them all. Offline import, import from google analytics, normal google conversion tracking setup, conversion adjustments. We recommend using the standard setup for best results.

Kuvio offers native integrations with Google Ads and Facebook Ads, but also dataLayer update so that you can use your profit data on any platform that uses the dataLayer.

Kuvio offers native integrations with Google Analytics and Google Data Studio, but also general csv export so that you can use your profit data in any platform of your choosing.

We support all of Googles marketing tools, facebook and any platform that uses the dataLayer.

Yes, either through historical data upload or through one of our back-end integrations

You can include essentially any data that you can logically link to each SKU and each sale. Most commonly this is COGS, shipping costs, transaction costs, kickbacks, etc.

Using historical sales data, we are able to predict in real-time how much of the order will be returned and can then adjust bids accordingly. Factors such as the product, the product segment, the customer segment, and the market are taken into account.

We would like to invite you to try Kuvio. We have many quite complicated user cases for which we have had no problem successfully implementing Kuvio.

Kuvio calculates order-level profit. This means that if you have certain products that you want to sell at a loss, as you know that more profitable products are often added into the same order, this is not a problem when using profit bidding with Kuvio.

Kuvio is real time, so the possible time lag is in other systems such as Google Ads, Google Analytics, Facebook etc.

Kuvio calculates in real time order-level profit for each sale, which you can feed to marketing- or reporting platforms. Kuvio does not offer any bidding or reporting solutions in itself, it only facilitates profit bidding and measurement.

Yes.

No. The cart-level profit signal can be encrypted by using a multiplier.

No. All data is compartmentalised, so no one else except those explicitly granted access to your Kuvio account will be able to access any of your business information. For extra security, login to the Kuvio interface requires two-factor authentication.

No. We share a signal (total cart profit) which means “total revenue” to the bidding algorithms, not the COGS data.

All data is stored at Amazon RDS instances which are located in Stockholm. For database we use hardened PostgreSQL which is behind a firewall and not accessible outside of the API endpoint.

Yes.

This depends on the complexity of your business model and which of the three packages you choose, but a normal timeframe is around a month from implementation to activation.

No. Kuvio has been developed as a universal solution, meaning that you do not require a developer from your side to set it up.

Yes, this is possible. However, to ensure that everything is up to date, we recommend importing data through a feed.

You can import data either through a manual CSV import, a web hosted CSV data feed, or through one of our back-end integrations.

You can import all relevant cost data for your ecommerce business, such as COGS, costs for different delivery methods, etc. In addition, you can import historical sales data to be able to do historical comparisons

No, there’s an easy implementation through Google Tag Manager. Server side integration is however available.

Yes, that is the preferred way of implementing Kuvio.

Kuvio has fall-backs for all cost metrics, meaning that even if we are missing a certain metric we can continue operating.

All you need to start using Kuvio is a standard Ecom data layer and a web-hosted CSV data feed with SKU and COGS data for your products.