Skip to main content

Fiverr, Pricing and Client Management · Part 1: The client's business, and the numbers they ask about

Chapter 24.2 · 2 of 34 · 2 min

Turning a business goal into a tracking requirement

A client never says "I need a purchase event with dynamic value".

Free to read

A client never says "I need a purchase event with dynamic value". They say "I want to scale my ads but I do not trust the numbers".

The translation between those two sentences is your job. And once you can show that translation in writing, you are no longer a seller who says "I do GTM setup".

The three steps of the translation

One, the goal. What the client wants. "Scale ad spend", "reduce cost per lead", "know which product makes money". This is their language.

Two, the decision. What decision they have to make to reach that goal. To scale, they need to know which campaigns are running at a profit. So the decision is: which campaign do I put more money into.

Three, the number. Which number they need to make that decision: actual revenue by campaign. And which event they need to get that number: a purchase event, with the value, and with the campaign information still intact.

Now your tracking requirement is ready: a purchase event, a dynamic value, the correct currency, and a click ID that does not get lost.

A real example

A client in the UK wrote: "I spend money on Google and Facebook but I cannot tell which one actually works."

Goal: decide which of the two channels gets more money.

Decision: move budget from one channel to the other.

Number: revenue by channel, measured by the same rules. The platforms' own reports cannot do this, because Facebook and Google both claim the same order as their own.

Requirement: a purchase event in GA4, in one place, measured by the same rules for every channel. This was what they really needed, and they could not put it into words themselves.

After I sent that one translation in writing, their reply was a single word: "exactly".

Writing out the requirement raises the price

Because then the client can see you have thought about their problem. And people do not haggle with someone who has thought about their problem.

I put two lines of this translation in every reply to an inquiry: the goal and the requirement. Two lines, no more.

Steps

  1. Pick one of the five sites from the previous chapter.
  2. Put yourself in their place and write three lines: goal, decision, number.
  3. Write down, by name, the event needed to get that number. Name it following GA4's naming rules.
  4. Now write down the parameters that event needs.

What not to do

  • Do not go straight from what the client says to a technical requirement. Do not hear "Pixel is not working" and sit down to repair the pixel. First ask what decision they cannot make. Often the pixel is fine and what is broken is the understanding of the attribution window.
  • Do not put anything in a requirement that you cannot deliver. A written requirement is a promise, and later it is what a dispute is argued over.

Proof

You have four lines written for one site: the goal, the decision, the number needed, and the event needed with its parameters.

Want the full chapter list, or to jump to another chapter?

All chapters in the book