The brief that defines most SEO engagements is: improve our rankings. The outcome the business actually needs is: grow our revenue. The gap between these two definitions is where most SEO investment is lost.
Rankings are a proxy. They indicate that Google considers your page relevant for a query. They do not indicate that the query produces revenue, that the visitor who finds you through that query is a buyer, or that the page they land on gives them a reason to act. A business that has achieved the brief and improved its rankings can still see zero impact on revenue if the proxy was measuring the wrong thing.
This playbook replaces the rankings brief with a revenue brief. It gives you the specific configuration steps for GA4, the attribution model that connects organic sessions to commercial outcomes, and the reporting format that presents the result in the language of a P&L rather than an analytics dashboard.
Why GA4 alone is not enough
GA4 tracks sessions, events, and conversions. By default, it does not tell you how much revenue each channel produced; it tells you how many sessions each channel produced and, separately, how many conversions occurred across all channels combined. Connecting these two facts requires attribution configuration that most GA4 implementations skip.
The default attribution model in GA4 is data-driven attribution, which uses machine learning to distribute conversion credit across touchpoints in the user journey. This is technically sophisticated but practically opaque – it does not give you a simple, client-explainable answer to "How much revenue did organic search produce last month?"
The fix is not a different GA4 configuration. It is a reporting methodology that takes the data GA4 can produce – organic conversion count, conversion value where available, and source attribution – and translates it into a revenue estimate using agreed business conversion values.
The four-step wiring process
Step 1: Define what conversion means for this business
Before touching GA4, sit with the client or stakeholder and agree on the specific actions that represent genuine commercial value. For a clinic: a booking form submission, a WhatsApp button click, a phone number tap. For an e-commerce store: a completed purchase transaction. For a professional services firm: a qualified lead form submission. For a SaaS product: a trial sign-up or a demo request.
Write these down. Get explicit agreement. A form submission that goes to a general enquiries inbox and converts at 2% is worth a different revenue attribution than a direct booking form that converts at 40%. The definition determines the calculation.
Step 2: Configure GA4 to track those conversions correctly
Each conversion type requires a specific GTM configuration. Form submissions: a GA4 Event tag triggered on form submission events, with an event name of "generate_lead" and parameters including form_id and optionally a value parameter. WhatsApp button clicks: a GA4 Event tag triggered when the click URL contains "wa.me", event name "whatsapp_enquiry". Phone number taps: a GA4 Event tag triggered when click URL begins with "tel:", event name "phone_click".
All configured events should be marked as Conversions in GA4 → Admin → Events. This elevates them from generic event data to conversion data that appears in attribution reports.
Step 3: Build the source attribution report
In GA4 → Reports → Attribution → Model comparison, select the organic search channels and the conversion events defined in Step 1. The report shows, for the selected date range, how many conversions each channel produced under the selected attribution model.
For the monthly Revenue Story, export this report on the first working day of the following month. The organic conversion count becomes the numerator in your revenue calculation.
Step 4: Translate to revenue language
The calculation: organic conversion count × agreed conversion-to-revenue rate × average revenue per conversion = estimated organic-attributed revenue.
Example: 31 form submissions from organic search × 40% enquiry-to-client conversion rate (agreed with client) × SGD 2,500 average project value = SGD 31,000 estimated organic-attributed revenue.
This number belongs in the first paragraph of the monthly client report, not buried in an appendix behind a rankings table. "Organic search contributed an estimated SGD 31,000 of attributable revenue this month" is the opening line of an SEO report that clients read in full and share with their finance director. It is also the opening line of a client relationship that renews.
The objection: "we cannot measure that precisely."
Every client who has not done this before will raise a version of this objection. The conversion rate is an estimate. The average revenue figure is an average. The attribution model distributes credit imperfectly across multi-touch journeys.
All of this is true. The response is the alternative to an imprecise revenue estimate is no revenue estimate. An imprecise figure, agreed between the agency and the client and transparently labelled as an estimate, is more useful than a rankings table that cannot be connected to revenue at all.
The precision improves over time. Once the attribution model is running, patterns emerge. The conversion rate from organic traffic to qualified leads becomes measurable. The difference in value between organic-sourced customers and paid-sourced customers becomes visible. The attribution becomes progressively more accurate without requiring CRM integration or advanced analytics infrastructure.
The SEO team that builds this model in month one of every engagement is building something that compounds. The rankings will fluctuate. The algorithm will update. But an organisation that can see, month on month, that organic search is contributing a quantified fraction of its revenue will invest in it continuously because the investment is visibly working.
