TikTok Pixel Setup: Installation & Server-Side API

Our company is engaged in the development, support and maintenance of sites of any complexity. From simple one-page sites to large-scale cluster systems built on micro services. Experience of developers is confirmed by certificates from vendors.

Development and maintenance of all types of websites:

Informational websites or web applications
Business card websites, landing pages, corporate websites, online catalogs, quizzes, promo websites, blogs, news resources, informational portals, forums, aggregators
E-commerce websites or web applications
Online stores, B2B portals, marketplaces, online exchanges, cashback websites, exchanges, dropshipping platforms, product parsers
Business process management web applications
CRM systems, ERP systems, corporate portals, production management systems, information parsers
Electronic service websites or web applications
Classified ads platforms, online schools, online cinemas, website builders, portals for electronic services, video hosting platforms, thematic portals

These are just some of the technical types of websites we work with, and each of them can have its own specific features and functionality, as well as be customized to meet the specific needs and goals of the client.

Showing 1 of 1All 2062 services
TikTok Pixel Setup: Installation & Server-Side API
Simple
from 4 hours to 2 days
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1358
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1250
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    956
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1188
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    929
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    947

You launch a TikTok ad campaign, but conversion data arrives with a 20-30% error. Budget goes to waste, optimization doesn't work. This is a typical situation when the pixel is set up hastily or server-side transmission is missing. We fix this, ensuring up to 99% accuracy even with ad blockers.

TikTok Pixel is a conversion tracking tool for TikTok advertising. We set it up so that every conversion is counted without duplicates, and ad campaigns are optimized for real purchases, registrations, or subscriptions. Without the pixel, you spend your budget blindly: up to 40% of conversions may go unnoticed due to ad blockers and browser errors. Server-side integration pays off even with a moderate ad budget due to data accuracy.

How to Set Up TikTok Pixel?

Step 1: Install the Base Code

Place the following code in the <head> of all site pages. Replace PIXEL_ID with your pixel ID from the ad account. We recommend using a tag manager (GTM) to simplify updates — this reduces the time for making changes by 2-3 times.

<script>
!function (w, d, t) {
    w.TiktokAnalyticsObject=t;var ttq=w[t]=w[t]||[];ttq.methods=["page","track","identify",
    "instances","debug","on","off","once","ready","alias","group","enableCookie","disableCookie"],
    ttq.setAndDefer=function(t,e){t[e]=function(){t.push([e].concat(Array.prototype.slice.call(arguments,0)))}};
    for(var i=0;i<ttq.methods.length;i++)ttq.setAndDefer(ttq,ttq.methods[i]);
    ttq.instance=function(t){for(var e=ttq._i[t]||[],n=0;n<ttq.methods.length;n++)
    ttq.setAndDefer(e,ttq.methods[n]);return e},ttq.load=function(e,n){
    var i="https://analytics.tiktok.com/i18n/pixel/events.js";
    ttq._i=ttq._i||{},ttq._i[e]=[],ttq._i[e]._u=i,ttq._t=ttq._t||{},ttq._t[e]=+new Date,
    ttq._o=ttq._o||{},ttq._o[e]=n||{};var o=document.createElement("script");
    o.type="text/javascript",o.async=!0,o.src=i+"?sdkid="+e+"&lib="+t;
    var a=document.getElementsByTagName("script")[0];a.parentNode.insertBefore(o,a)};
    ttq.load('PIXEL_ID');ttq.page();
}(window, document, 'ttq');
</script>

Step 2: Configure Standard Events

For an online store, four standard events are sufficient: ViewContent, AddToCart, InitiateCheckout, CompletePayment. Example code:

// View product
ttq.track('ViewContent', {
    contents: [{ content_id: productId, content_name: productName }],
    value: product.price,
    currency: 'RUB'
});

// Purchase
ttq.track('CompletePayment', {
    contents: orderItems.map(i => ({ content_id: i.productId, quantity: i.qty, price: i.price })),
    value:    orderTotal,
    currency: 'RUB',
    order_id: orderId
});

// Registration
ttq.track('CompleteRegistration', { value: 0, currency: 'RUB' });

For more accurate user matching, pass advanced matching via ttq.identify():

ttq.identify({
    sha256_email: sha256(user.email.toLowerCase()),
    sha256_phone_number: sha256(normalizePhone(user.phone))
});

Step 3: Connect the Server-Side Events API

The client-side pixel can lose 15-20% of events due to ad blockers or browser errors. The server-side Events API sends events directly from your backend, increasing reliability to 99%. Example in PHP (Laravel):

Http::withToken(env('TIKTOK_ACCESS_TOKEN'))
    ->post('https://business-api.tiktok.com/open_api/v1.3/event/track/', [
        'pixel_code' => env('TIKTOK_PIXEL_ID'),
        'event'      => 'CompletePayment',
        'timestamp'  => time(),
        'context'    => [
            'user' => [
                'sha256_email' => hash('sha256', strtolower($user->email)),
                'sha256_phone' => hash('sha256', normalizePhone($user->phone))
            ],
            'page' => ['url' => $pageUrl]
        ],
        'properties' => [
            'contents'  => $itemsArray,
            'value'     => $total / 100,
            'currency'  => 'RUB'
        ],
        'event_id' => "purchase_{$orderId}"
    ]);

Important: pass event_id in both channels (client and server) — this allows TikTok to deduplicate events and avoid inflating conversions. In practice, this reduces data discrepancy from 30% to 2-3%. Losing 10% of conversions due to incorrect pixel setup can cost a business significant money.

Why Is the Server-Side Events API Critical for Tracking Accuracy?

The server-side Events API is 2-3 times more reliable than the client-side — it is not affected by ad blockers, JavaScript errors, or browser restrictions. Additionally, the server-side method allows passing extra data, such as exact order ID or internal user ID, which improves audience quality for retargeting. Without server-side transmission, up to 40% of purchases may remain untracked.

How to Avoid Data Discrepancies?

Data discrepancies arise from event duplication, ad blockers, or lack of deduplication. Main solutions:

  • Pass a unique event_id in both client and server pixels.
  • Use ttq.identify() with advanced matching (email and phone in SHA256).
  • Ensure the pixel loads only once.
  • Test with Pixel Helper and TikTok Ads testing mode.

These measures reduce discrepancies to 2-3%.

Typical Integration Errors

Problem Cause Solution
No data in ad account Pixel not installed or blocked Check code via Pixel Helper extension
Conversion discrepancy > 20% No deduplication or duplicate events Pass event_id and ensure pixel loads once
Events not sending Script error or conflict with other trackers Open browser console and check JavaScript errors
Advanced matching not working Incorrect hash (SHA256) or empty data Ensure email/phone are normalized and hashed correctly

What's Included in Turnkey Pixel Setup?

We perform the full cycle: from audit to documentation. Timeline — from 1 day to 1 week depending on complexity.

Stage Result
Audit of current tracking system Identify issues with existing pixels and GTM
Base pixel installation Correct code in <head> on all pages
Event setup (client + server) All key events sent with deduplication
Testing Verification via Pixel Helper and TikTok Ads testing mode
Documentation Maintenance instructions, event list, data format description

Cost is calculated individually. Factors: number of events, need for server-side integration, GTM presence, CMS complexity. Request an audit of your current tracking — we'll provide accurate estimates and timelines. Contact us for a consultation on your project; we'll help set up tracking that pays off from the first campaigns.

Experience: over 30 e-commerce projects, we guarantee correct data transmission and compliance with TikTok requirements.

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 we check after each deploy
  • All recommended events present in DebugView
  • No duplicates (count purchase per 100 sessions)
  • Data layer structure unchanged after frontend update

What the work includes

Component Description
Audit of existing tags Check current GTM tags, data layer, duplicates, and errors
Event schema design Documentation: event list, parameters, triggers
GA4 + GTM setup Create configuration, tags, custom definitions
Yandex.Metrica Install counter, create goals, set up Webvisor
Amplitude (optional) Set up client and server SDK, cohorts
QA and monitoring Testing in Preview Mode, alerting
Training and handover Access, instructions for adding new events, console

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)
Scenario Timeline
Basic GA4 + GTM setup 1 week
Full e-commerce tracking + Metrica 2–3 weeks
Server-side GTM + Amplitude 3–5 weeks

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.