This is not a technical limitation. GA4 has the infrastructure to answer this question precisely. It is a configuration and methodology problem โ most agencies set up GA4 to track page views and generic events, not the specific conversion actions that connect organic traffic to commercial outcomes.
This article documents the four-step model we use at Copyleft to build revenue attribution for every SEO client. It requires approximately four hours to set up once per client and produces a monthly revenue attribution figure that can be stated in the language of a P&L, not an analytics dashboard.
Step 1: Define what conversion means for this specific business
The first and most important step is one that most agencies skip: sitting with the client to define exactly what actions, on the website, represent a genuine commercial conversion. This definition varies significantly by business type and cannot be defaulted to "form submission" without losing accuracy.
For a clinic or healthcare provider: the conversion is a new patient enquiry. This might be a form submission, a WhatsApp button click, a phone number click on mobile, or a direct phone call tracked via a call tracking number on the site. Depending on the client, all four may be relevant.
For an e-commerce store: the conversion is a completed purchase transaction. GA4's e-commerce event schema tracks this natively if properly implemented. The revenue value is available directly โ no estimation required.
For a professional services firm (law, accounting, consulting): the conversion is a qualified lead โ typically a form submission or a scheduled consultation booking. The revenue attribution requires multiplying the number of qualified leads by an estimated close rate and average client lifetime value, both of which the client should be able to provide.
For a B2B SaaS product: the conversion may be a free trial sign-up, a demo request, or a pricing page visit combined with a form submission. In complex B2B sales, the conversion event is often several steps removed from revenue, requiring a CRM integration to complete the attribution path.
The output of Step 1 is a written definition, agreed with the client, of exactly what GA4 events will be used as the conversion signal for revenue attribution reporting.
Step 2: Configure GA4 to track those conversions correctly
Most GA4 implementations track page views, scroll depth, and outbound link clicks out of the box from Google Tag Manager. The specific conversion events defined in Step 1 typically require custom configuration.
Form submission tracking: in GTM, create a trigger on form submission events. Use a GA4 Event tag with an event name of "generate_lead" (the recommended GA4 event name for lead generation) and include parameters: form_id, form_destination, and optionally a value parameter if the lead has an estimated value.
WhatsApp button click tracking: a WhatsApp Business link (wa.me/...) is an outbound link. GTM captures outbound link clicks automatically via the Click - All Elements trigger. Create a specific GA4 Event tag for WhatsApp clicks by adding a condition to the trigger that fires only when the click URL contains "wa.me". Event name: "whatsapp_enquiry".
Phone number click tracking: use a GTM trigger on click events where the click URL begins with "tel:". Event name: "phone_click". This captures mobile users who tap to call directly from the site.
All three events should then be marked as Conversions in GA4 โ Admin โ Events โ Mark as conversion. This tells GA4 to give these events first-class treatment in attribution reports.
Step 3: Build the source attribution report
Once conversions are tracking correctly, the attribution report is built in GA4 โ Reports โ Attribution โ Model comparison. This report shows, for each channel, the number of conversions and the conversion value attributed to that channel under different attribution models.
For SEO revenue attribution, the relevant channels are: Organic Search (Google organic), Organic Search (other engines), and Direct (which in practice often contains significant organic-originated traffic where the attribution has been lost).
The recommended attribution model for SEO is data-driven attribution, which uses machine learning to distribute conversion credit across the touchpoints in the user journey. If data-driven is not available (it requires a minimum conversion volume to activate), the position-based model (40% credit to first touch, 40% to last touch, and 20% distributed across middle touches) is a reasonable approximation for multi-channel journeys.
The output of Step 3 is a monthly organic conversion count and, for e-commerce clients, an organic revenue figure. For non-e-commerce clients, the conversion count must be multiplied by an estimated value to produce a revenue attribution figure.
Step 4: Translate conversions into revenue language
The final step is the translation layer โ converting raw GA4 conversion data into a revenue attribution statement that makes sense to a business owner rather than an analyst.
The template calculation is: Organic conversion count ร conversion-to-revenue rate ร average revenue per conversion = estimated organic-attributed revenue.
For the TCM hair clinic case study in Day 7: 31 organic enquiries ร 40% consultation-to-treatment conversion rate ร SGD 1,500 average treatment value = SGD 18,600 estimated organic-attributed revenue. This is the number that appears in the Revenue Story.
The important qualifier is "estimated". This is not a guarantee or an audited figure โ it is a revenue attribution estimate based on agreed conversion values. The agreement on those values โ the conversion rate and average revenue per conversion โ should be made with the client once and documented. If the client subsequently reports that the actual close rate for organic leads is different from the estimate, the model should be updated.
For clients who can provide CRM data, the estimation layer can be replaced with actuals โ matching organic-originated leads in GA4 against closed deals in the CRM. This produces a true revenue attribution figure rather than an estimate. HubSpot, Salesforce, and most major CRMs can be connected to GA4 through native integrations or GTM.
The monthly reporting cadence
Once the four-step model is set up, the monthly reporting task reduces to exporting the GA4 attribution report, calculating the revenue estimate, and drafting the Beat 3 section of the Revenue Story (what it produced).
After Chaos-X integration, the n8n pipeline will pull this data automatically โ GSC for ranking and traffic data, GA4 for conversion data, Claude for the calculation, and Beat 1โ4 drafts. The four-step model does not change. The delivery mechanism becomes automated.
The difference this model makes to client retention is not subtle. An agency that can show a client, in a monthly report, that the organic channel contributed SGD 18,600 of estimated revenue last month is operating in a completely different client relationship than an agency showing a rankings table. The former has created an outcome. The latter has documented activity.
Build the attribution model in the first month of every engagement. It is four hours of setup that changes the entire character of the client relationship for the duration.
Senior Editor ยท Revenue desk
