Get your Tilda tracking to 95%+ accuracy guaranteed in writing.
Tilda is the design-first website builder used heavily across CIS, Eastern Europe, and increasingly the EU. The default tracking is Pixel + GA + Yandex.Metrika in a custom code block — all browser-only. iOS users vanish, form submits don't reach Meta CAPI, and ecommerce purchases lose dedup. We rebuild Tilda tracking server-side with full Meta + Google + VK + Yandex coverage.
Free30 minutesNo obligation
Tilda · what breaks
Tilda tracking gaps
- 01
Browser-only tracking = iOS gap
iOS users vanish from Meta + Google.
- 02
Form submissions don't reach CAPI
Lead-gen Tilda sites lose 25%+ of iOS leads.
- 03
Yandex + Meta + Google all fight each other
Multiple analytics tools in code blocks → conflicts and double-fires.
- 04
Tilda CDN cross-domain breaks attribution
Tilda subdomain → custom domain hops drop click_id.
Tilda · the fix
Outcomes — Tilda
Server-side CAPI
Meta + Google + VK + Yandex all clean
Form → CAPI pipeline
100% lead capture
Cross-domain dedup
click_id preserved
iOS recovered
Server-side bypasses ATT
Tilda · architecture
How a Tilda order should reach the ad platforms
Tilda pages are block-built and its forms post to external services, so the conversion you care about is recorded somewhere other than Tilda.
- 1
Click identifiers captured at first touch
Click IDs are captured at landing and written to a first-party cookie, then into hidden fields on Tilda forms so they reach the receiving service.
- 2
The browser sends the fast, fragile copy
Tilda exposes form-submission callbacks and allows custom code in the page settings. The callback is the correct trigger; a redirect is not.
- 3
The order itself is the source of truth
The record in the receiving service — your CRM, email platform or payment processor — is the truth.
- 4
A server container sends the authoritative event
That service's webhook posts to a GTM server container on your own subdomain, keyed on a submission or payment ID.
- 5
Customer identity raises match quality
Submitted email and phone are hashed server-side.
Tilda · events
The event set we build on Tilda, and where each one comes from
Tilda's own form callbacks are reliable; the mistake is usually not using them.
| Event | Fires when, on Tilda | Key parameters | Sent from |
|---|---|---|---|
| view_item | A key page or block set renders | item_id, value, currency, event_id | Browser + server, deduped |
| generate_lead | The Tilda form callback fires on successful submission | hashed email/phone, click IDs, event_id | Server preferred |
| purchase | A payment succeeds in the connected processor | order_id, value, currency, items[], hashed email/phone/name/address, event_id | Server authoritative |
Tilda · normal or broken
Tilda specifics
Block-based pages and external form handling account for most of the confusion.
Normal, not a fault
No page load after a form submit
Tilda forms submit asynchronously. The callback exists precisely for this.
Forms posting to external services
By design, and why the truth lives outside Tilda.
Ad platforms report more conversions than you have orders
Meta credits a 7-day click and 1-day view; Google credits on click date. Two platforms can each claim the same sale. Compare each one to your order records separately and never add them together.
Recent days always look worse than they finish
Conversions are credited back to the date of the click, so yesterday's return on ad spend is understated and will keep improving for several days. This is attribution working, not data arriving late.
Actually broken
A generic submit listener counting failed submissions
Rejected submissions reported as leads.
Conversion counted on a thank-you page that is directly reachable
Any visitor to that URL is a conversion.
Click IDs never reaching the receiving service
Nothing attributable.
Tilda · prove
How we prove the Tilda build is correct
The tag firing proves the tag fires. These prove the numbers are right.
Source of truth
Your form handler's or payment processor's records
- The lead event confirmed firing on Tilda's own success callback.
- Click IDs confirmed present in the receiving service's records.
- Any thank-you page confirmed not independently reachable, or the conversion moved off it.
- Purchase count within a few percent of your form handler's or payment processor's records for a fully closed week, matched on order ID rather than on totals.
- No order ID appearing twice in any platform's event log.
- Deduplication confirmed at every destination that supports it.
- Test and staff orders excluded, with the exclusion confirmed active rather than merely configured.
- The same reconciliation repeated 30 days later, because a setup that works once and then drifts is the harder failure to catch.
Tilda · free audit
What we check in the free audit
- Browser-only tracking = iOS gap
- Form submissions don't reach CAPI
- Yandex + Meta + Google all fight each other
- Tilda CDN cross-domain breaks attribution
Checked against
Your form handler's or payment processor's records
Free30 minutesNo obligation
Tilda · when not to buy
When a Tilda rebuild is not what you need
We would rather say this now than three weeks into an engagement.
- Your Tilda site is informational with no conversion action.
- Low ad spend.
- You have no CRM and your leads close in the same session.
Tilda · what we deliver
Deliverables — Tilda
Tilda code-injection module
Custom HTML block
Server-side gateway
1st-party server-side GTM
Meta CAPI · Google EC · VK + Yandex
All deduped
Notion runbook + 30-day support
Russian + English option
Written guarantee
95%+ tracking accuracy
Measured against Your form handler's or payment processor's records. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Foundation pixel install for your Tilda store. Honest disclosure: this is a starting point only. If you spend $1K+/month on paid media you should be on the 1st-party server-side tier — rather than quote you a recovery percentage, we'll show you how to measure your own gap: compare what the platforms reported against the orders in your backend for the same week. That ratio is the entire argument, and it's yours to check — see trackingconsulting.com/measurement-accuracy-methodology.
- One-time fee · zero monthly · zero SaaS lock-in
- Tilda dataLayer (clean spec)
- GA4 e-commerce events
- Meta Pixel · Google Ads tag
- TikTok Pixel · Microsoft UET
- Consent Mode v2 banner integration
- QA test orders + 7-day support
- No CAPI · no iOS recovery
1st-party server-side
Recommended$800One-time fee · most popular
The done-for-you package every Tilda store running paid ads should start with. We build the entire 1st-party server-side stack on your subdomain — Meta, Google, TikTok, Microsoft, LinkedIn all fed from the server. Recovers the conversions iOS, Safari ITP, ad blockers and cookie deprecation hide today. You don't lift a finger. Built in 2–4 days · accurate data in 7 days.
- One-time fee · save vs SaaS subscriptions over 5 years
- Fully recovered + built in 2–4 days · accurate data in 7 days
- Everything in browser-side starter
- 1st-party server-side GTM (your subdomain)
- Meta CAPI · full advanced matching · 8+ EMQ
- Google Enhanced Conversions (Web + Leads)
- TikTok Events API · Microsoft UET server
- Deterministic browser ↔ server deduplication
- Live EMQ verification + screenshots
- Notion runbook + 30-day support · zero recurring
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid-media channel running 1st-party server-side, end-to-end. For Tilda brands spending $30K+/month who can no longer afford attribution leaks. Pay once. Own everything. Includes Pinterest + Snap + Reddit + LinkedIn CAPI, Klaviyo identity stitching, BigQuery + Looker Studio.
- One-time fee · save 6-figure SaaS subscriptions over 5 years
- Everything in 1st-party server-side tier
- Pinterest · Snapchat · Reddit · LinkedIn · X CAPIs
- Klaviyo identity stitching (if used)
- BigQuery export (server logs + GA4)
- Looker Studio attribution dashboard (branded)
- Multi-region / multi-currency / EU residency
- GDPR-audit-ready Consent Mode v2 wiring
- 60-day support · optional retainer · no lock-in
FAQ
Tilda questions, answered
Yes — Russian + English + multilingual handled.
Custom code requires Personal or Business plan.
More on Tilda
- GuideServer-Side Tracking Explained: What It Is, How It Works, and Who Actually Needs It (2026)
- GuideServer-Side Tracking for Shopify: The 2026 Setup That Actually Works
- Free toolFree Tilda audit
- Enhanced ConversionsEnhanced Conversions enrich the conversions that already fire. First we make sur…
- Meta CAPIA one-click CAPI integration sends thin events. That's why your Event Match Qual…
- Cross-Domain TrackingYour checkout provider is the best performing traffic source in your GA4 account…
