Bidding on value, not volume
Each stage carries a value, so Google and Meta bid on revenue instead of lead count. Value-based bidding only works when those values arrive reliably.
Growth analytics for banks, fintech and e-commerce. I build the measurement that cuts wasted ad spend and finds the growth last-click reports miss.
Every source resolved to one identity, modelled once, then pushed back to the platforms that spend the money.
Most accounts send a form fill from the browser and nothing after it. The algorithm then finds more people who fill forms, not people who pay.
Qualified leads, approvals and sales go back to Google Ads and Meta from your CRM through the Conversions API and offline conversion imports.
The platform sees 24 identical leads and looks for more people like all of them.
Each stage carries a value, so Google and Meta bid on revenue instead of lead count. Value-based bidding only works when those values arrive reliably.
The interfaces above are mockups with sample numbers.
Four services. Most engagements start with the audit and move up only if it finds something worth building.
Illustrative interface with sample data. No live account is connected.
A short quiz sorts visitors before the form. Only qualifying answers are sent as conversions, so campaigns stop optimising for curiosity clicks.
On submit, the phone and IIN are checked against the mobile citizens database and the business against the tax registry. Only verified leads become conversions.
What the work looks like, by type of client. The numbers for each case are in the portfolio.
An auto-lending MFO
Browser and server sent the same registration twice with no shared ID. GTM now sends one event ID, and lead forms reach the CRM through a signed webhook.
In the portfolioA leasing company in a bank group
Every form submit counted as a lead. The form now checks the tax ID first, and GTM marks a lead qualified only after it passes.
In the portfolioAn insurer inside a super app
Purchase events did not match signed contracts. A shared taxonomy is live on one product; rollout to the rest is in acceptance.
In the portfolioA consumer lender
The client could not change the site, so an interceptor reads the funnel's own API calls and records every step.
In the portfolioAn e-pharmacy marketplace
Moved the storefront to server-side rendering and fixed canonicals and sitemaps, so search engines could index the catalog.
In the portfolioA large Kazakh bank
Found test traffic and phantom users in production analytics, cut the tag manager down and redesigned the app taxonomy.
In the portfolioIllustrative interface with sample data. No live account is connected.
CRM statuses land next to each ad in the account, including lead forms and messenger campaigns that usually stay a black box.
A pLTV model scores each sign-up from early signals, and the predicted value reaches the ad platforms long before the first payment.
The platform gets the whole deal history: application, qualification, payment and rejection. It drops spam sooner and brings leads that pay.
The audit and the retainer have fixed prices. A project is priced once its scope is agreed.
A read-only review of how your funnel is measured, and of the gap between what the platforms report and what your CRM settles.
One build, agreed before it starts: server-side GTM and CAPI, an MMP or S2S pipeline, an event taxonomy, or an offline conversion import.
Standing analytics engineering capacity. I own the measurement layer: new tracking as the product ships, QA when a platform changes the rules, and the reporting on top.
Illustrative interface with sample data. No live account is connected.
Approvals and payments happen in your backend. Measurement Protocol sends them to GA4, so funnel reports reach revenue.
The browser sends one first-party request. Your server-side GTM container decides what each platform receives and strips personal data before it leaves.
Browser and server send the same purchase with one shared ID, so the platform keeps one and drops the copy.
Tools I built for client work and then packaged. Each comes with setup help if you want it.
Claude gets your GA4, Google Ads, Search Console, Tag Manager, BigQuery and Yandex accounts through one login, deployed on your server.
How it worksNine specialist skills plus reviewer and legal agents, and a commit gate that waits for review.
Public release soonOpen-source audits for Google Ads, GA4, Search Console and Meta, plus semantic diffs for Tag Manager.
How it worksA Chrome DevTools recorder for tracking audits: network, dataLayer and consent, exported to Markdown.
How it worksGenerates the event taxonomy from your design files and flags drift when the designs change.
How it worksA free course on digital marketing and analytics on goodlabs.kz.
Open AcademiaIllustrative interface with sample data. No live account is connected.
Product capabilities reviewed on 13 October 2026 against the project README.
Digital marketing leadership, with the technical depth to build what comes next.
Good Labs is my consulting practice for banks, insurers and lenders. Alongside my role at inDrive, I work on attribution, conversion infrastructure, product analytics and acquisition.
I connect business goals to technical requirements, then stay involved through implementation and testing. That perspective comes from leading digital marketing at Halyk Bank and Bereke Bank, as well as working directly on the systems behind acquisition.
Based in Almaty, with consulting experience across Kazakhstan, Russia, the Czech Republic and India.
Technical writeups from client engagements: architecture, event schemas, and the failure modes that cost the most to find.
I start with a two-week audit. Fixed scope, no long-term commitment upfront. If it surfaces value, we continue. If not, you keep the roadmap.
dilshat@goodlabs.kzt.me/arcbaslowAlmaty, UTC+5, remote-first