Conversion Attribution Setup: Guide & Implementation

Conversion Attribution Setup for Your Website

A client arrives via organic search, then three days later returns through an email campaign and makes a purchase. Which channel gets the credit? If you attribute the conversion to the last touch (email), your SEO budget appears ineffective. If you give it to the first touch (search), email marketing is devalued. This dilemma is resolved by choosing an adequate attribution model. As web integrators, we encounter distorted data from improper attribution daily and help businesses avoid wasting budget on underperforming channels. Setting up attribution isn't just picking a model in GA4—it's a systematic effort: from auditing current settings to integrating with CRM and your own UTM tag storage.

Attribution Models

How to Choose an Attribution Model for Your Business?

Choosing a model depends on your sales cycle length, number of touches, and goals. If you sell low-cost items with a short cycle, Last Click is adequate. For complex B2B products, we recommend Time Decay or Position-based. Data-driven attribution is the most accurate option but requires at least 1000 conversions per month. Our experience shows Data-driven allows 1.5–2× more precise budget allocation compared to Last Click. We guarantee transparent setup for any model.

What Does Custom Attribution Provide?

Standard GA4 models don't always account for offline conversions or CRM data. Custom attribution gives you full control: you can define your own attribution window, combine data from different sources, and build reports tailored to your KPIs. Moreover, it's the only way to correctly distribute credit among channels in a long sales cycle. We have experience setting up such systems for 50+ projects.

Setting Up in GA4

GA4 uses Data-Driven Attribution by default. To switch:

GA4 → Admin → Attribution Settings → Reporting Attribution Model

To compare models:

Reports → Advertising → Attribution → Model Comparison

Select two channels (e.g., Paid Search and Email) and compare their contribution under different models. Our GA4 certified specialists help you interpret the results.

Storing UTM Parameters in the Database

For your own attribution, store UTM parameters on each visit:

// On page load
const utmParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_content', 'utm_term'];
const currentUtm = {};
const urlParams = new URLSearchParams(window.location.search);
utmParams.forEach(param => {
    if (urlParams.has(param)) {
        currentUtm[param] = urlParams.get(param);
        sessionStorage.setItem(param, urlParams.get(param));
    }
});
// Save to localStorage for last-touch
if (Object.keys(currentUtm).length > 0) {
    localStorage.setItem('last_utm', JSON.stringify({ ...currentUtm, timestamp: Date.now() }));
}

// On order completion — pass UTM parameters
$order->update([
    'utm_source'   => session('utm_source'),
    'utm_medium'   => session('utm_medium'),
    'utm_campaign' => session('utm_campaign')
]);

Multi-Channel Attribution on the Server

-- Analyze conversions by first-touch attribution
SELECT
    first_visit.utm_source,
    COUNT(DISTINCT o.id) as orders,
    SUM(o.total) / 100.0 as revenue
FROM orders o
JOIN sessions first_visit ON first_visit.user_id = o.user_id
    AND first_visit.id = (
        SELECT id FROM sessions
        WHERE user_id = o.user_id
        ORDER BY created_at ASC
        LIMIT 1
    )
WHERE o.created_at >= NOW() - INTERVAL '30 days'
GROUP BY first_visit.utm_source
ORDER BY revenue DESC;

Attribution Window

The window defines how many days back a touch should be counted. GA4 defaults: 30 days for conversions, 90 days for purchases. For B2B with a long cycle, increase to 90–180 days.

Implementation Stages

Why Data-Driven Attribution Is More Accurate

Data-driven attribution uses machine learning to analyze real user paths. It doesn't rely on simplified assumptions like Last Click or First Click, but calculates each touch's contribution based on statistics. With sufficient data (from 1000 conversions per month), this model gives the most objective picture. Important: data quality directly affects accuracy—you need correct UTM tags and no duplicate conversions.

What's Included in Conversion Attribution Setup

• Audit of current analytics and ad channel settings
• Selection of the optimal attribution model for your business
• GA4 configuration (conversions, models, attribution window)
• Implementation of UTM parameter storage in the database (frontend + backend)
• Creation of multi-channel attribution reports (SQL queries, visualization)
• Setup documentation and interpretation recommendations
• Consultation and post-implementation support

Case study: a client — an electronics e‑commerce store with a 5‑day decision cycle. After the audit, we discovered 70% of conversions came through search, but Last Touch attribution showed only 40% for search. We implemented Time Decay and increased the search budget by 30%. Within a month, ROI grew by 18%.

Why Work with Us

We have over 5 years in web development and have completed 80+ analytics setup projects. Our team includes GA4 certified specialists with experience integrating with any CRM. We guarantee transparent attribution and data confidentiality.

Setup time: 2–4 days depending on complexity. Pricing is determined after analysis.

Order conversion attribution setup and get a consultation on choosing the right model for your business. Contact us to discuss details and get a budget estimate.

Setup Web Analytics: GA4, GTM, Yandex.Metrica, and Amplitude

We often see: conversion rate 1.2%, traffic grows, but conversion stays flat. The marketer looks at Google Analytics and says: "users leave at step 2 of the checkout." The developer opens the same step — no errors, Sentry is silent. So it's not a JS bug, but a UX issue or skewed data from analytics. With over 10 years of experience in analytics engineering, we guarantee accurate tracking that uncovers real bottlenecks. Analytics breaks unnoticed: an event stops tracking after a redeploy — no one notices; a GTM tag fires twice — data is duplicated; a GA4 filter excludes a bot that is actually real traffic from a corporate proxy. An audit of your current tags will find the cause within a week.

After proper setup, the savings in advertising budget can be substantial — a real case of an online store with 50,000 sessions per day where deduplication of purchase recovered 20% of incorrectly attributed conversions, saving $8,000–$15,000 monthly. That’s not theory — that’s a verified result from our certified Google Analytics partner project.

Why do GA4 events duplicate and how to fix it?

Universal Analytics is gone, replaced by GA4's event-based model. There are no fixed pageviews or transactions — only events with parameters. This is more flexible but requires proper event design. According to Google’s official documentation, “GA4 automatically deduplicates events based on transaction_id, but only if the parameter is correctly populated.” Many implementations miss this.

Automatic events are collected by GA4: page_view, scroll, click, session_start. Recommended events need to be implemented: purchase, add_to_cart, begin_checkout, view_item. Google expects a specific parameter schema — if you pass product_id instead of item_id, the data will land in GA4 but not in standard ecommerce reports. Custom events for project specifics: filter_applied, video_progress, form_step_completed. Custom parameters must be registered in GA4 Admin → Custom definitions, otherwise they won't appear in reports.

A common mistake is the purchase event being duplicated. Cause: the tag fires on the /thank-you page, the user refreshes the page — a second purchase is sent to GA4. Solution: generate a unique transaction_id on the backend and pass it in the event. In our experience, 80% of e-commerce stores have this issue. GA4 deduplicates based on it (in theory — verify with DebugView). Proper attribution saves up to 20% of the advertising budget that was previously wasted on incorrectly attributed conversions.

How to set up the data layer to avoid data loss?

GTM is a tool for managing tags without code deployment. But "no code" doesn't mean "no architecture." The data layer is the foundation. We pass data from the application to GTM via dataLayer.push(). Structure: event + contextual data. For e-commerce: before opening a product page — push with product data. GTM tag reads from the data layer, not from the DOM.

window.dataLayer = window.dataLayer || [];
dataLayer.push({
  event: 'view_item',
  ecommerce: {
    items: [{
      item_id: 'SKU-12345',
      item_name: 'Product name',
      price: 1990.00,
      currency: 'USD'
    }]
  }
});

Bad practice: GTM tag parses the DOM — looks for the price in span.price, the name in h1. This breaks with any layout change. Good practice: always use the data layer. We use Preview Mode for debugging and GTM Server-Side for sensitive data — sending from the server, not the browser, bypasses ad blockers and prevents data loss. A properly implemented data layer reduces tracking errors by 95%.

How does Yandex.Metrica complement web analytics?

For a Russian audience, Metrica is a must — especially Webvisor. Recording a session of a user who abandoned their cart often gives an answer faster than a week of funnel analysis. Goals in Metrica: event-based (via ym(COUNTER_ID, 'reachGoal', 'GOAL_NAME')) or automatic (button click, page visit). Integration with CRM via Metrica Plus — passing offline conversions. Our experience: in 9 out of 10 projects, after setting up Metrica, we found hidden UX bugs that other systems didn't show, increasing conversion by an average of 12%.

What does product analytics give in Amplitude?

Amplitude is a product tool, unlike marketing-oriented GA4 and Metrica. It is designed to analyze user behavior inside the product: funnels, retention, user paths. Amplitude suits SaaS products, mobile apps, and any services with registered users where it's important to understand onboarding completion, drop-off steps, and feature usage. Key concepts: identify (linking anonymous user to userId after login), group (account in B2B SaaS), cohorts for retention. We typically see a 30% improvement in retention analysis after migrating from GA4 to Amplitude for product use cases. Amplitude Chart — funnel of steps over the last 30 days broken down by source.

Monitoring Data Quality

Analytics without monitoring is a black box. We set up:

• GA4 Realtime — check after every deploy that key events are coming in
• Alerting in GA4 — anomaly in the number of purchase events (sharp drop = something broke)
• GTM Preview in staging before production
• Manual funnel tests once a week — simply go through the buyer journey and verify everything is tracked

What the work includes

Process and timeline

1. Audit of existing tags and data (2 days)
2. Event schema design (2 days)
3. Data layer development and tag setup (3–5 days)
4. QA in Preview Mode and staging (2 days)
5. Deploy and dashboard setup (1 day)

Cost is calculated individually. Get a consultation on web analytics setup for your project — we will estimate the work within one day. Contact us to get started with a free audit of your current tracking.