Custom Lead Scoring System Development for Your Website

Your sales department spends 70% of its time on leads that never buy. Lead scoring automatically assigns points to each website visitor based on behavior: page views, content downloads, form submissions. Once a lead hits a threshold, it is passed to the CRM as hot. We have implemented this system for a dozen B2B projects — on average, sales conversion increased by 2.5 times. A lead scoring system on your website handles behavioral scoring and automates qualification. Our custom lead scoring system development service focuses on behavioral lead scoring and CRM integration. With 8 years in the lead scoring automation niche and over 10 successful projects, our experienced team guarantees a proven process. We provide a 30-day support period after launch and ensure data privacy. Typical project cost ranges from $3,000 to $6,000, with annual savings of up to $15,000 from reduced manual qualification.

Why standard lead scoring fails without proper configuration?

Simply assigning 5 points for a page view is not enough. You need to consider event repetition — do not count a duplicate demo request, weigh negative signals (unsubscribe, 30 days of inactivity), and dynamically adjust stage thresholds. Without this, the system generates false-positive hot leads that distract managers. Our configuration includes 20+ event types with points from -25 to +50 and four lead levels: cold, warm, hot, mql/sql. Automatic qualification is 4 times faster than manual.

How to set event weights?

Event weight is determined by its proximity to purchase: pricing page view — 15 points, contact form submission — 40, trial start — 50. Negative signals (unsubscribe, more than 30 days inactive) reduce the score by 10–20 points. We recommend reviewing weights quarterly based on lead-to-deal conversion — this improves forecast accuracy. For example, in one project we increased the weight of case study page view from 5 to 10 after noticing a strong correlation with purchase.

MQL and SQL: qualification stages

Marketing Qualified Lead (MQL) — a lead reaching 80 points automatically transfers to the CRM for nurture campaigns. Sales Qualified Lead (SQL) — 100 or more points requires an immediate call from a sales rep. Different thresholds prevent sales from early contact, allowing marketing to nurture warm leads.

System architecture

Data model

// Table schema
Schema::create('lead_scores', function (Blueprint $table) {
    $table->id();
    $table->foreignId('user_id')->nullable()->constrained()->nullOnDelete();
    $table->string('session_id')->index();
    $table->string('email')->nullable()->index();
    $table->integer('score')->default(0);
    $table->json('score_breakdown');
    $table->string('stage')->default('cold');
    $table->timestamp('mql_reached_at')->nullable();
    $table->timestamp('qualified_at')->nullable();
    $table->timestamps();
    $table->index(['score', 'stage']);
});

Schema::create('lead_events', function (Blueprint $table) {
    $table->id();
    $table->foreignId('lead_score_id')->constrained()->cascadeOnDelete();
    $table->string('event');
    $table->integer('points');
    $table->json('metadata')->nullable();
    $table->timestamps();
});

Points configuration

// config/lead_scoring.php
return [
    'events' => [
        'page_view_pricing'          => 15,
        'page_view_case_study'       => 10,
        'page_view_demo'             => 20,
        'demo_requested'             => 50,
        'whitepaper_downloaded'      => 20,
        'webinar_registered'         => 25,
        'free_trial_started'         => 40,
        'pricing_calculator_used'    => 30,
        'comparison_page_viewed'     => 15,
        'contact_form_submitted'     => 40,

        'email_opened'               => 5,
        'email_clicked'              => 10,
        'return_visit'               => 5,
        'visited_3_days_in_row'      => 15,

        'company_size_50_plus'       => 20,
        'role_decision_maker'        => 25,
        'budget_confirmed'           => 30,

        'unsubscribed'               => -20,
        'inactive_30_days'           => -10,
        'student_email_domain'       => -25,
    ],

    'thresholds' => [
        'warm' => 30,
        'hot'  => 60,
        'mql'  => 80,
        'sql'  => 100,
    ],
];

Scoring service

class LeadScoringService
{
    public function track(string $sessionId, string $event, array $metadata = [], ?int $userId = null): LeadScore
    {
        $points = config("lead_scoring.events.{$event}", 0);

        $lead = LeadScore::firstOrCreate(
            ['session_id' => $sessionId],
            ['user_id' => $userId, 'score_breakdown' => []]
        );

        if ($userId && !$lead->user_id) {
            $lead->update(['user_id' => $userId]);
        }

        if (!empty($metadata['email']) && !$lead->email) {
            $lead->update(['email' => $metadata['email']]);
        }

        $onceEvents = ['demo_requested', 'free_trial_started', 'contact_form_submitted'];
        if (in_array($event, $onceEvents)) {
            if (LeadEvent::where('lead_score_id', $lead->id)->where('event', $event)->exists()) {
                return $lead;
            }
        }

        LeadEvent::create([
            'lead_score_id' => $lead->id,
            'event'         => $event,
            'points'        => $points,
            'metadata'      => $metadata,
        ]);

        $breakdown = $lead->score_breakdown ?? [];
        $breakdown[$event] = ($breakdown[$event] ?? 0) + $points;

        $newScore = $lead->score + $points;
        $newStage = $this->calculateStage($newScore);

        $lead->update([
            'score'           => $newScore,
            'score_breakdown' => $breakdown,
            'stage'           => $newStage,
        ]);

        $thresholds = config('lead_scoring.thresholds');
        $prevStage  = $this->calculateStage($lead->score - $points);

        if ($newStage !== $prevStage) {
            $this->onStageChange($lead, $prevStage, $newStage);
        }

        return $lead->fresh();
    }

    private function calculateStage(int $score): string
    {
        $thresholds = config('lead_scoring.thresholds');
        if ($score >= $thresholds['sql'])  return 'sql';
        if ($score >= $thresholds['mql'])  return 'mql';
        if ($score >= $thresholds['hot'])  return 'hot';
        if ($score >= $thresholds['warm']) return 'warm';
        return 'cold';
    }

    private function onStageChange(LeadScore $lead, string $from, string $to): void
    {
        Log::info("Lead stage change: {$from} → {$to}", ['lead_id' => $lead->id, 'score' => $lead->score]);

        if ($to === 'mql') {
            $lead->update(['mql_reached_at' => now()]);
            SyncLeadToCrm::dispatch($lead);
            Notification::route('slack', '#leads-hot')
                ->notify(new MqlReachedNotification($lead));
        }

        if ($to === 'sql') {
            $lead->update(['qualified_at' => now()]);
            $salesManager = User::salesManager()->inRandomOrder()->first();
            $salesManager?->notify(new SqlLeadAssigned($lead));
        }
    }
}

Frontend event tracking

class LeadTracker {
  private sessionId: string;

  constructor() {
    this.sessionId = sessionStorage.getItem('ls_session') || this.generateId();
    sessionStorage.setItem('ls_session', this.sessionId);
  }

  async track(event: string, metadata: Record<string, any> = {}): Promise<void> {
    try {
      await fetch('/api/lead-score/track', {
        method: 'POST',
        headers: { 'Content-Type': 'application/json' },
        body: JSON.stringify({
          session_id: this.sessionId,
          event,
          metadata: { ...metadata, page: window.location.pathname },
        }),
      });
    } catch (e) {
      // Do not block UI on tracking error
    }
  }

  private generateId(): string {
    return Date.now().toString(36) + Math.random().toString(36).substr(2);
  }
}

export const tracker = new LeadTracker();

Manager dashboard

SELECT
  ls.email,
  ls.score,
  ls.stage,
  ls.mql_reached_at,
  COUNT(le.id) AS events_count,
  MAX(le.created_at) AS last_activity
FROM lead_scores ls
JOIN lead_events le ON le.lead_score_id = ls.id
WHERE ls.stage IN ('mql', 'sql', 'hot')
  AND ls.mql_reached_at >= now() - interval '7 days'
GROUP BY ls.id, ls.email, ls.score, ls.stage, ls.mql_reached_at
ORDER BY ls.score DESC;

Deliverables Included in Turnkey Development

• Configurable scoring system with 20+ events (can be changed without a programmer).
• Frontend tracking without performance loss (asynchronous fetch, does not block UI).
• Automatic lead transfer to popular CRMs (AmoCRM, Bitrix24, Salesforce) when MQL is reached.
• Manager dashboard with stage filtering and hot lead highlighting.
• Comprehensive documentation on scoring rules and instructions for marketers.
• 30-day technical support and maintenance after launch.
• Training session for your team (2 hours online).

Implementation process

1. Analytics: collect your current qualification criteria and typical customer journey.
2. Design: set event weights, stage thresholds, integrations.
3. Implementation: build backend and frontend, connect CRM via API.
4. Testing: verify scoring accuracy on historical data.
5. Launch: deploy and train your team.

Timeline and cost

Timeline — from 8 to 14 working days depending on CRM complexity and number of custom events. Implementation cost — from $2,000 to $8,000 depending on integrations and number of events. Average project cost is $3,000–$6,000, with typical annual savings of $15,000 from reduced manual qualification. Contact us — we will find the best solution for your budget.

Typical mistakes in lead scoring implementation

• Counting the same event multiple times (need once-event flag).
• Ignoring negative signals — a lead may be cold even if they click a lot.
• Not updating thresholds over time — audience behavior changes, rules need adaptation.

Our certified CRM integration partners and 8+ years of experience guarantee a smooth implementation. Get a free consultation on lead scoring setup — we will assess your project.

Lead scoring — methodology described on Wikipedia.

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.