TLJ Tracking
Meta Lead Ads become complete deals inside your CRM
-
Değerlendirme
-
Kurulum sayısı6
-
Geliştirici
Who it is for
For companies that advertise on Facebook and Instagram — with lead forms (Lead Ads) or with campaigns that send people to WhatsApp — and that run their sales pipeline inside Bitrix24.
The problem
The lead arrives, but it arrives with no story. Someone types the contact in by hand, or the details shows up with a name and a phone number and nothing else. When the manager asks which campaign produced this month's sales, the answer is a guess: Ads Manager shows what was spent, the CRM shows what was sold, and nobody can connect the two without a spreadsheet and an entire afternoon.
What TLJ Tracking does
The moment someone submits the form on your ad, the application fetches that submission fr om Meta and creates the record in your CRM with the source already stamped on it: campaign, ad set, ad, form and the network it came from. The form answers land in the fields you choose — you map them once, on the settings screen, matching each question to the matching Bitrix24 field. No typing, no duplicate details: if Meta re-sends the same lead, the application recognises it and ignores it.
With the source written on every deal, the performance screen answers what the spreadsheet used to answer: what each campaign cost, how many leads it brought, how much of that turned into won business, the cost per lead and the return on ad spend. The maths uses the date the lead arrived, not the date the deal closed — today's sale counts in the period the lead came in, which is the only way to compare spend and result over the same window. You drill from campaign to ad set, from ad set to ad, and see each creative's thumbnail next to what it cost and what it produced.
Campaigns that send people to WhatsApp
Ads that open WhatsApp are usually a hole in the measurement: the conversation arrives, the rep answers it, and nobody knows which ad it came from. The application closes that hole with trackable links: you generate a link instead of using the raw number, every click gets a short code, and that code travels inside the first message the customer sends. When the conversation becomes a deal in Bitrix24, the application reads that first message, recognises the code and writes the campaign onto the details — exactly as it does for a form. If the portal uses the official WhatsApp Business connection, the application also uses the referral information Meta attaches to the first message.
Back to Meta
When a deal reaches the stage you marked as won, the application reports that conversion to Meta through the Conversions API, so the algorithm learns which ads produce real sales and not just sign-ups. Name, e-mail and phone never leave in plain text: they are normalised and turned into a SHA-256 hash before leaving the application, exactly as Meta requires.
Reading what the numbers mean
There is also an analysis screen that reads your own data and writes, in plain language, what is going on: which campaign is getting expensive, which creative is worn out, wh ere the funnel is stalling. It is a summary for people who would rather not dig through a table.
How to use it
Install it, connect your Meta ad account, pick the forms that should feed the CRM and map the questions to the fields. From there it runs on its own. The settings screen carries a numbered walkthrough inside the application itself, written for people who have never touched an API.
Ek koşullar
Monthly subscription per Bitrix24 account, billed in US dollars through Stripe. The price covers the whole Bitrix24 account with no per-user charge and can be cancelled at any time — access remains until the end of the period already paid for.
To work, the application needs a Meta ad account with Lead Ads forms and a user with administrator rights on that account. The Meta connection is made through Facebook itself, on the settings screen; TLJ Tracking never asks for or stores a Facebook password.
Technical limitations: form answers pass through the application and are written into your CRM, with no copy kept in our database; spend figures come from Meta's API and are cached for up to three days; campaign, ad set and ad names are cached for up to 24 hours. Meta and Bitrix24 API rate limits apply. Sending conversions through the Conversions API is optional and switched off by default.
