Fits the stack you already have

The one thing Profitscaler cannot work without. Your server container asks what an order was worth, and gets a number back before the tag fires.

Send profit as the conversion value, so bidding optimises for what you keep instead of what you turn over.

Profit as an event parameter and a custom metric, reported next to the revenue you already have.

A supplementary feed that labels every product with the margin bucket it is projected to earn.

Where many stores already build the feed that carries cost prices and where the margin labels can go back in.

No product feed yet? A published sheet of SKUs and cost prices is enough to get started.

Two scheduled file imports put profit by day and profit by SKU next to the ad spend you already report on.

The same two feeds as plain CSV over HTTPS, for whatever you already use to report.

One of the hosts that can run your server container. Nothing in Profitscaler talks to their API.

Another host for your server container. The product cannot tell the difference, by design.

The profit value is on the event in your server container, so the Conversions API tag can send it as the purchase value.

The Events API tag reads the profit value off the same event, and reports it as the purchase value.