Tilda CRM Integration via Webhook, GTM & UTM Setup

Lost leads due to manual export of Tilda forms to CRM is a frequent problem we solve in one day. Built-in integrations often cover non-standard logic: you need a custom webhook handler, UTM tag passing, and fine analytics tuning. Our team with 10+ years of experience has delivered over 150 projects, deploying handlers on Laravel and configuring GTM. We offer turnkey integration with protection and guarantee. Cost is calculated individually—contact us for a project assessment.

How We Integrate Tilda with CRM

We use three approaches: built-in integrations, a custom webhook handler, or JS integration via the T123 block. The choice depends on logic complexity and required flexibility.

Comparison of Approaches

Why Webhook Is Better Than Built-in Integrations

Built-in integrations are convenient for simple scenarios but do not allow adding conditions or enriching leads with data from external APIs. A webhook gives full control: you can validate fields, send data to multiple CRMs, trigger actions. Development time is only 3–5 hours—that saves budget compared to building a custom solution from scratch. We can assess your project for free.

Built-in Integrations

In the 'Integrations' section of the Tilda site settings, ready connectors are available for AmoCRM, Bitrix24, GetResponse, Mailchimp, SendPulse. Setup takes 15–30 minutes: enter the API key, map form fields to CRM fields—done. Limitation: field mapping is limited, no conditions, no additional logic.

Webhook to Custom Handler

For non-standard CRMs or complex logic—a webhook. In Tilda form settings: 'After submission' → 'Webhook' → enter URL. Tilda sends a POST with form data in application/x-www-form-urlencoded format:

Name=John+Doe&Phone=%2B1234567890&Email=john%40example.com&formid=form123456789&tranid=1234567890

Handler in Laravel:

public function handleTildaWebhook(Request $request): Response
{
    $data = $request->all();

    // Basic validation — Tilda does not sign requests cryptographically,
    // so protect via IP filter or secret parameter in URL
    $expectedToken = config('services.tilda.webhook_token');
    if ($request->query('token') !== $expectedToken) {
        abort(403);
    }

    $lead = [
        'name'   => $data['Name'] ?? $data['name'] ?? '',
        'phone'  => $data['Phone'] ?? $data['phone'] ?? '',
        'email'  => $data['Email'] ?? $data['email'] ?? '',
        'source' => 'tilda',
        'form'   => $data['formid'] ?? '',
    ];

    // Create lead in CRM
    dispatch(new CreateCRMLead($lead));

    return response('OK', 200);
}

Important nuance: Tilda does not sign webhook requests cryptographically. Protection: either a secret token in the URL (?token=xxx) or an IP filter (Tilda server IPs are published in Tilda documentation).

How to Configure Event Transmission to Analytics via GTM

For tracking form events in Google Analytics 4 or Yandex Metrica, the standard approach is Google Tag Manager. Tilda supports inserting a GTM code: 'Site Settings' → 'Analytics' → 'Google Tag Manager' → enter the container ID (GTM-XXXXXXX). Then in GTM set up a trigger on Tilda form submission. Tilda emits a custom event:

// Event that Tilda sends to the dataLayer after successful form submission
window.addEventListener('message', function(event) {
    if (event.data && event.data.indexOf('tildaCallback') >= 0) {
        const data = JSON.parse(event.data);
        if (data.event === 'tf-success') {
            dataLayer.push({
                event: 'tilda_form_submit',
                formId: data.formId,
                pageName: document.title,
            });
        }
    }
});

In GTM: trigger → 'Custom Event' → tilda_form_submit. Attach a GA4 tag with event generate_lead to it.

How to Pass UTM Tags to CRM

UTM tags from the URL must be saved and sent with the lead. Tilda supports this via hidden form fields:

1. Add hidden fields to the form with names utm_source, utm_medium, utm_campaign.
2. In form settings, enable 'Automatically insert UTM tags into hidden fields'.

After that, the webhook will receive filled UTM fields, which can be transmitted to CRM as deal attributes. This improves lead quality and allows assessing advertising channel effectiveness, reducing lead generation costs.

Typical Errors and Their Solutions

• 404 error on webhook — check the route and HTTP method (must be POST).
• Empty leads in CRM — check field mapping: field names from Tilda (Name, Phone) must match what the handler expects.
• No UTM in webhook — ensure automatic UTM substitution is enabled in form settings.

What Is Included in the Integration Work

• Development of a webhook handler (Laravel, Node.js, or Django) with field mapping, validation, and security.
• Configuration of GTM, GA4, and Yandex Metrica with triggers on form submission.
• Implementation of UTM tag transmission to CRM.
• Operation documentation and support contacts.
• Training for your team: up to 1 hour online.

Timeline and Guarantee

Built-in Tilda → CRM integration via standard connector: 30–60 minutes. Custom webhook handler with field mapping and UTM tracking: 3–5 hours. Full analytics setup with GTM, GA4, Metrica, and UTM transmission to CRM: 1 business day. Our guarantee: the integration works without failures, data is not lost. Contact us for a project assessment—get a free consultation.

Website CRM Integration: Bitrix24, amoCRM, Salesforce, HubSpot

A sales manager manually copies leads from email into the CRM. Half of them never make it. Follow‑up calls are missed. This isn’t a people problem — it’s an architectural gap between the website and the company’s core system. We close that gap with a direct site‑to‑CRM connection: leads land in the pipeline within 30 seconds after form submission, duplication is blocked, and status changes flow both ways automatically. Request a free integration audit to identify the bottlenecks in your current flow.

Integration isn’t just a POST to an API endpoint. It’s a battle against timeouts, duplicate records, data loss, and desynchronised states. We handle three core problems at once: asynchronous delivery (so the user never waits for the CRM), deduplication by email (one address – one lead), and two‑way feedback (a status change in the CRM instantly appears on the site). Below is how we tackle each.

Bitrix24: REST API and Event Handlers

Bitrix24 dominates the Russian B2B space. Its REST API works via OAuth 2.0 or an incoming webhook (webhook is simpler but less secure for production). Main entities are lead, deal, contact, and company.

Creating a lead requires POST /rest/crm.lead.add with the correct field set. Attaching it to a funnel means passing SOURCE_ID. Adding a timeline comment uses crm.timeline.comment.add. Real‑time tracking is done through Event Handlers: register a hook with event.bind; Bitrix24 pushes a POST to your endpoint when any deal status changes.

The real complexity lies in custom fields. Every Bitrix24 installation has its own set, and their IDs must be fetched via crm.lead.fields. Mapping those fields between the site and the CRM can be done manually or automatically — we use an automatic detection mechanism that works even in non‑standard configurations (proven on 20+ projects). We guarantee correct matching, so no lead arrives without the right pipeline stage or source tag.

amoCRM: Clean REST with Predictable Endpoints

amoCRM (now Kommo for international markets) offers a cleaner API. OAuth 2.0 with refresh token, JSON API, and well‑structured endpoints. Pipelines are pipelines, deals are leads, contacts are contacts.

A common mistake: when creating a deal you must supply pipeline_id and status_id explicitly. Without them the deal lands in the default pipeline – often the wrong one. Tags for source classification go into _embedded.tags. Incoming webhooks are configured in the admin panel; they support add, update, delete, status, and note events. We always verify the webhook signature using the API key and make sure the endpoint responds with 200 OK in under 5 seconds – otherwise the CRM marks delivery as failed.

Salesforce and HubSpot: Enterprise‑Grade Integration

Salesforce is the enterprise standard. It offers REST API, SOQL for complex queries, and Apex for server‑side logic. Integration can be direct via Salesforce REST API or through middleware like Zapier or MuleSoft. For PHP projects we use phpforce/soap-client or the Force.com‑Toolkit. The main challenge is mapping hundreds of custom objects and fields; we solve it with Describe Global to collect metadata automatically – cutting setup time by three‑quarters compared to reading documentation manually (Salesforce Developer Guide).

HubSpot is popular among SaaS companies and international B2B. Its API v3 provides a REST interface with solid SDKs for PHP and Node.js (@hubspot/api-client). Contacts, Companies, Deals are standard objects. The Forms API lets you send data from any custom form directly to HubSpot without using the native widget. One pitfall: the access_token must include the right scopes; a misconfigured token returns 403 Forbidden with a vague message. We include error_logging that captures the error code – debugging takes minutes instead of hours.

Which CRM fits your business: Bitrix24, amoCRM, or HubSpot?

Why is asynchronous sending important?

Calling a CRM API synchronously from the form handler is a mistake. The API may respond in 2 seconds – or time out. The user sits waiting. The correct pattern: form submission → save to database → queue a job → return 200 to the user immediately. A background worker then pushes the lead to the CRM. If the CRM is down, the worker retries with exponential backoff. We use Redis + Bull on Node.js or Laravel Queue on PHP – this guarantees delivery even during temporary outages.

Deduplication – how we stop duplicate leads

The same contact may fill the form twice. Without deduplication the CRM ends up with two identical leads. Before creating a new lead we search by email: for Bitrix24 we call crm.duplicate.findByComm, for HubSpot we use contacts/search. If a match is found we attach a task or comment to the existing lead instead of creating a new one. In our projects this cuts duplicate entries by 95%.

Two‑way synchronization – what happens when a manager changes a deal status

If a manager updates a deal status in the CRM, the website needs to reflect that change – especially if the client has a personal account. We configure webhooks from the CRM to an endpoint on the site, then update the local database and notify the client. Critical details: verify the webhook signature and respond with 200 OK within 5 seconds, otherwise the CRM assumes delivery failed. We guarantee that the delay between a status change in the CRM and its appearance on the site never exceeds 3 seconds.

How do we conduct integration in 5 steps?

1. Audit of data flows – analyse current lead transfer, CRM field structure, and performance bottlenecks. Deliverable: “as‑is” and “to‑be” data flow diagrams.
2. Architecture design – choose the queue mechanism (Redis Bull or Laravel Queue), define the deduplication method, and prepare a field mapping specification.
3. Implementation on staging – write code on Laravel or Node.js, configure webhooks, and test with real data: lead creation, status updates, and error handling.
4. Load testing – simulate peak traffic (e.g. 500 requests per minute) and adjust retry policies and timeout settings.
5. Deployment and documentation – push to production, train the team on monitoring and retry cleanup, and deliver full endpoint documentation.

What is included in the work

• Audit report with current data flow diagrams and typical error patterns.
• Architecture design document specifying queue, deduplication, and mapping.
• Production‑ready integration code on Laravel or Node.js.
• Webhook configuration and signature verification.
• Team training on support tasks and retry cleanup.
• 30‑day warranty support for bug fixes and mapping adjustments.

Real‑world case: real‑estate agency with 400 leads per month

Timelines

The exact cost is calculated after an audit of your current processes and CRM data structure. Contact us for a project estimate – we will send a commercial proposal within one business day. With 5+ years of experience and more than 20 completed integrations, you get a solution that works from day one. Get an engineer consultation to see how your sales funnel can run without manual lead transfer.

Additional sources: Customer relationship management (Wikipedia) · REST API (Wikipedia)