About

Why NullMark exists

We built NullMark because we were losing real money to a problem most people don't even know exists.

The problem we kept running into

We were running our own projects — landing pages, checkout flows, signup funnels — and driving traffic from Instagram, TikTok, and other social media platforms. The numbers looked fine on the surface: clicks were coming in, ads were performing, traffic was flowing.

But conversions were quietly dying.

It took us longer than we'd like to admit to figure out why. The issue wasn't our copy, our pricing, or our offer. It was where the link was opening. Every time someone tapped a link inside Instagram or TikTok, it didn't open in Safari or Chrome. It opened in the platform's built-in mini-browser — a stripped-down, sandboxed environment that silently breaks everything users rely on.

Apple Pay? Gone. Google Pay? Gone. Saved passwords and autofill? Stripped out. Tracking pixels? Unreliable at best, completely broken at worst. Cookie-based sessions? Isolated from the real browser. The user lands on your page with buying intent, and the environment actively fights against them completing the purchase.

The worst part: analytics never flagged it. The session showed up, the click counted, the traffic looked healthy. What we saw was a conversion problem. What actually happened was an infrastructure problem we had no control over.

What we tried first

We went through the usual approaches. JavaScript-based detection scripts on our landing pages, User-Agent string parsing, conditional redirect logic. It worked — sometimes. But User-Agent strings change without warning, each platform's in-app browser behaves differently, and maintaining the detection code across multiple projects became its own headache.

We needed something that sat between the social platform and the landing page. Something that handled the detection once, correctly, and just worked every time someone tapped a link.

So we built it.

What NullMark does

NullMark is a smart link redirect service. You replace your link-in-bio or ad destination with a NullMark link. When someone taps it from inside an in-app browser, NullMark detects the environment and opens the page in the user's real browser — Safari on iOS, Chrome on Android — in under 50 milliseconds.

No code changes to your site. No JavaScript to maintain. No broken User-Agent detection to keep updating. One link, and the problem is solved.

<50ms
Redirect speed
6+
Platforms detected
iOS + Android
Full support

How it works under the hood

NullMark runs on Cloudflare's edge network, which means the redirect happens at the server closest to the user, anywhere in the world. We detect in-app browsers through a combination of User-Agent analysis, JavaScript environment fingerprinting, and platform-specific escape methods.

On iOS, we use Safari URL schemes and native long-press fallbacks. On Android, we use Chrome Intent schemes. Each platform's in-app browser has its own quirks — Meta's browser behaves differently from TikTok's, which behaves differently from Snapchat's — and we handle all of them.

We also support Meta and TikTok Pixel tracking, firing a PageView event on every redirect so your attribution data stays intact. Plus custom branded link slugs and a built-in 18+ age gate for adult content creators.

Who we are

NullMark is built and operated from Austria. What started as an internal tool to fix our own conversion problems became a product when we realized every creator and business running social media traffic faces the exact same issue.

We're a small, focused team that cares about one thing: making sure the clicks you earn actually convert. No bloat, no dashboards full of vanity metrics, no features for the sake of features. Just one thing done right.

Get in touch

Questions, feedback, or just want to say hi? Reach us at hello@nullmark.tech.