About US
At Leadtech, we’ve been redefining digital businesses since 2009, creating innovative online solutions that reach millions of users every month. With a diverse team of over 700 members from 23+ nationalities, we’re united by a passion for creativity and collaboration.
We specialize in delivering user-centric experiences across web and mobile platforms, where people can connect with our products like never before.
We’re proud of our global reach and committed to fostering an inclusive workplace where every individual contributes to our shared vision of bringing cutting-edge projects to life. Learn more about our journey and mission on our page!
About the Role
We are looking for a MarTech Specialist with strong expertise in web tracking projects, ideally with experience in companies with subscriptions models.
This is not a “ticket executor” role. We want someone who owns the tech side of web tracking, challenges assumptions, and builds scalable, future-proof solutions.
And one more thing: we don’t care what you studied 🎓. Master’s in Advanced Translation? Great. Law & Politics double degree? Fantastic. Finance vocational training? Perfect. Degrees are nice, but here we care about your skills, curiosity, and hands-on experience.
Why Join Us
- Real ownership of projects. Not buzzwords, not empty promises — you’ll actually own things end to end.
- Room to grow. This department is relatively new, which means there’s a lot of space to expand your scope and responsibilities as we scale.
- Future opportunities. Our web projects will very likely grow both in number and in scope. This is an Individual Contributor role (IC), not a management position — but the right person will naturally find opportunities to take on more responsibility and influence as things expand.
- We’re a team of nerds. We get excited about browser updates or privacy changes, and yes — sometimes we cry together when new rules make our lives harder. But we love the challenge.
A company where your voice matters. A lot. If you don’t enjoy having responsibility, explaining your decisions, and defending your work, we might not be the right match.
Must-have
- Core requirement: Deep experience working on web products in production. Real web — not just diagrams, not just tools, not just theory. The kind where browsers disagree, cookies disappear, and tracking still needs to work.
- Deep understanding of attribution across modern tracking environments (browser restrictions, signal loss, privacy frameworks, and server-side recovery strategies — yes, the real-world kind, not the slide-deck version). You understand how tracking infrastructure decisions directly impact attribution accuracy and campaign optimization.
- Solid understanding of how Ad Networks work — e.g., the difference between Campaign / Ad Group / Ad, how CAPI or parameter-based tracking works, and how UA teams rely on these setups. You don’t need to run campaigns, but you need to speak their language (and understand why they panic when conversions drop 12%).
- Fluent English (written & spoken). Don’t worry — you don’t need to be Shakespeare. And if you don’t even know who Shakespeare is… you don’t need to be Harry Styles either. What matters is that we can communicate clearly, understand each other, and even have some fun while doing it.
- Experience working with architectures where tools like Google Tag Gateway (GTG) or equivalent network-side signal routing solutions play a key role in maintaining conversion visibility — particularly in environments with high non-Chrome traffic share (because, unfortunately, not everyone lives inside Chrome).
- Strong experience designing, implementing, and optimizing server-to-server (S2S) conversion and event tracking setups across Ad Networks — regardless of the tool used (e.g., server-side GTM, AddingWell, Staple, direct API integrations, or custom pipelines). You understand how S2S tracking impacts campaign optimization, signal quality, and attribution (and why “browser-only will be fine” is usually famous last words).
- You understand how hashing, normalization, and formatting of user identifiers directly impact match rates and downstream optimization. You don’t just know what hashing is — you’ve implemented it multiple times, debugged it, validated payloads, and you know exactly which documentation to open when something breaks (because something always breaks eventually). Metrics like Event Match Quality (EMQ) or equivalent signal quality indicators across networks are part of your daily toolkit, and you know how to improve them through tracking architecture, data quality, and consent-aware implementations.
- Hands-on experience with online payments (Stripe, card gateways) and the ability to capture and process payment data for analytics and attribution (including when payment flows and tracking don’t fully agree with each other).
- Experience with GA4 and Amplitude. Knowledge of Adobe Analytics (or similar enterprise platforms) is a plus — but GTM expertise is mandatory (yes, still).
- Experience with CMPs / consent management tools (e.g., Didomi, OneTrust, Usercentrics, or similar). Not just basic setup — you’ve worked hands-on with Legal teams, verified implementations in DevTools, and ensured that signals are firing correctly. Concepts like GDPR, DMA, Consent Mode V2, Purposes, Vendors, Notice and so on are not foreign to you — you’ve danced with them more than a few times (and you know they always lead).
- Practical experience with cloud systems (ideally GCP: BigQuery, Cloud Functions, Pub/Sub, APIs). SQL proficiency to query and consume data in a Data Warehouse (e.g., BigQuery, Databricks) — including knowing when the problem is actually upstream tracking and not the query
Big plus
- Python (or other scripting languages) for automation. We’re not looking for a Data Engineer, but you should feel comfortable writing small scripts when needed — for example, to pull data from an API, send events into GCP, clean or transform datasets before pushing them into a warehouse, spin up a quick Cloud Function to avoid manual work, or even make life easier for the SEO team by processing Google Search Console data.
- Data Engineering / Analytics Engineering exposure (e.g., Airbyte, dbt, Dataform). You won’t be replacing our Data team — they’re the experts — but having this background makes collaboration smoother and helps reduce small bottlenecks.
- Experience with Affiliation platforms (e.g., Impact, Rakuten, Awin, or similar). We don’t run affiliation today, but we’d love to launch it, and your experience can help us design the right tracking and attribution setup from day one.
- Solid understanding of Technical SEO fundamentals (indexation, sitemaps, canonicals, hreflangs, Core Web Vitals). Many tracking challenges start with landing pages, organic funnels, or GSC, so speaking the SEO language helps.
Nice-to-have
- Experience with other TMS systems (Tealium, Adobe Launch, etc.). GTM is mandatory, but knowing others is a plus.
- Experience with Customer Data Platforms (CDPs) such as Segment, mParticle, Rudderstack or Composable CDPs like Census, Hightouch.
- Experience with dashboards and BI tools — e.g., Looker Studio, Tableau, Power BI — to help Paid UA teams analyze test results, especially in attribution-sensitive cases.
- Experience with CRMs and marketing automation platforms, especially the technical side (Braze, Iterable, OneSignal, Hubspot, Brevo, ActiveCampaign, etc.).
- Awareness of AEO (Answer Engine Optimization) — understanding how search and discovery through LLMs (ChatGPT, Perplexity, etc.) works, so you can help evaluate how much value we’re getting from these appearances and how we attribute them.
How we think & work
We’d love you to see yourself in these principles, because they’re not just words — they show up in our daily work:
- Level up. We grow, and we make our teammates grow. That means if you find a smarter SQL trick, you share it in Slack. If Paid UA asks for a new event, you don’t just copy-paste — you ask “why?” and propose a smarter way to track it.
- See it, fix it. We don’t let problems rot. If a conversion event breaks on Friday, we fix it before Monday. If GA4 and Amplitude don’t match, you don’t wait for someone to complain — you investigate and solve it.
- Always ahead. New SDK drops? We’ve already tested it on staging before anyone asks. Same with Safari updates or cookie deprecations — you’re the one reading the changelog and warning the team before it hits production.
- Now means now. If it can be done today, it doesn’t wait until sprint planning. If a tag breaks in GTM, you don’t just open a Jira ticket — you fix it or bring a concrete proposal.
- Team spirit. We’re collaborative and keep it fun. You help Paid UA debug a Meta Ads issue on Friday afternoon, and you also drop a meme about how Google loves making our lives harder
- Hands-on. When you need test data, you don’t wait for someone else — you spin up your own test purchase flow and validate the tracking yourself.
- Translator mindset. You can explain GTM S2S to a marketer and LeadGen campaigns to an engineer, and both walk away nodding.
Posted about 13 hours ago