What Makes Us Different
The specific things about Hardal that distinguish it from alternatives - as honestly as we can state them.
This page is for internal clarity, not marketing. We should be honest about where we have genuine advantages and where we're still building toward them. The goal is for everyone at Hardal to be able to articulate the real differences.
What Hardal actually does better
Managed infrastructure, not a managed service
The most common alternative to Hardal is doing sGTM hosting yourself on GCP, AWS, or Azure. That works until someone has to maintain it, update the container image, monitor for failures, handle the DNS configuration, and debug why events stopped flowing after a platform API update.
Hardal does all of that. You get a working server-side setup without a DevOps hire. And when something changes (Meta API v18 → v19, iOS permission model updates), we handle the update - you don't.
This is genuinely differentiated. Most competitors offer either managed hosting or managed services. We offer both as part of the same product.
First-party by default
Everything we deploy runs on your domain, under your TLD. Not a subdomain of Hardal. Not a shared container. Yours. This matters for:
- First-party data classification (Google and Meta treat it differently)
- KVKK/GDPR compliance (data collection under your domain vs. a third-party domain)
- Ad blocker bypass (client-side blockers target known third-party domains, not customer-owned subdomains)
We solve your whole measurement stack
sGTM alone fixes one thing: event delivery. You still need analytics, somewhere to store data, and control over where it goes.
Hardal covers all of it in one place: server-side infrastructure, analytics, and destinations (Meta, GA4, TikTok, AppsFlyer, etc.). You're not stitching together three vendors. You set it up once, and you own the whole flow.
Local market depth
We're not a white-labeled SaaS tool sold globally without specific market knowledge. We understand the Turkish digital marketing landscape - the dominant platforms, the regulatory environment, the common setups used by e-commerce companies in this market.
That depth means we can help customers in ways that generic tools can't. We've seen what other Turkish e-commerce companies are doing. We know which setups work and which ones create compliance problems.
Honest sales and onboarding
We tell customers when Hardal isn't the right fit. Our churn rate is evidence that this works; customers who buy Hardal tend to stay, because they understood what they were buying.
We also have a thorough implementation process. We don't hand customers a setup guide and wish them luck. We're there through go-live and the first month of data.
Where we're still building
Being honest:
Mobile is newer. Our web measurement infrastructure is mature. Mobile analytics (server-side for iOS and Android) is newer and still developing. It works, but it has more rough edges than the web product.
Self-service is limited. Right now, getting set up with Hardal requires working with our team. That's fine for the customer segment we're targeting, but it's a ceiling on growth at some point. We're investing in making more of the setup self-service.
European market presence is early. We have customers in Spain, the UK, and broader Europe, but we don't have the same depth of market knowledge there that we have in Turkey. This is improving.
Analytics depth. Our cookieless analytics product is strong on data collection and control, but the analytics interface is not as deep as dedicated analytics tools. We're not trying to replace GA4 or Amplitude. If a customer needs deep analytics UI, they'll still use those tools alongside Hardal.
The honest comparison with competitors
vs. Stape (most common competitor): Stape is a strong product for sGTM hosting. The main differences: Hardal includes destination integrations (Meta CAPI, TikTok eAPI, etc.) and attribution as part of the core product; Stape treats these as separate. Hardal also has stronger support and more direct customer relationships. Stape has more global brand recognition.
vs. in-house setup: Cheaper to build, more expensive to maintain. If you have DevOps resources and a team that will keep the setup current, in-house is a viable option. Most companies that try it end up with a neglected container that's three versions behind and causing data quality issues within a year.
vs. Jentis/other European players: These are enterprise-tier products with enterprise pricing and procurement cycles. We're focused on mid-market and growth-stage companies where that model doesn't fit. Hardal is easier, cheaper and faster to implement.
What we don't do
- We are not a Consent Management Platform (CMP). We work with your CMP; we're not a replacement for it.
- We are not a CDP or data warehouse. We send data to those systems; we're not one.
- We are not an analytics frontend. We collect and route data; the analysis happens in GA4, Mixpanel, your data warehouse, etc.
Understanding the boundaries of what we do helps us avoid selling to customers who need something we're not building.