Feature
Revenue correlation
"It slipped a few spots" and "it slipped a few spots and it's costing you" are different conversations. Pecker has the second one, because it's already run the numbers by the time you need them.
Two lines, one chart
Position and a revenue index are plotted against the same timeline, per game, per operator. When the position line drops, watch the revenue line follow — usually within a day or two, not instantly, because players notice a game vanishing from a good spot before they trickle back once it's fixed.
That lag is the part a monthly spreadsheet check always misses. By the time a manual review catches a slip, the revenue has usually already cratered and started drifting back up on its own — which makes it easy to underestimate how much a breach actually cost, because the numbers look "almost normal" again by the time anyone's looking at them side by side.
Why this changes the conversation
A placement clause dispute usually stalls on disagreement about how much a position is actually worth. With position and revenue on the same chart, that stops being a matter of opinion — it's the same evidence an operator can look at and reach the same conclusion from.
Catch the slip while it's small enough that the revenue hit is too.
Read more →Export the chart and the underlying position history together.
Read more →Bring numbers, not adjectives, to a renegotiation.
Read more →