Replace LnkFlow?
KINDA · weekend projectA short link that 302s, logs the click, and injects UTMs is genuinely one sitting on Cloudflare Workers and KV, and the prompt below builds exactly that. What is not one sitting is the loop back out to the ad platforms. Meta and Google bid against the conversion events you send them, and since ATT the browser pixel misses a large share of purchases, which is the entire reason the Conversions API and offline conversion import exist. Closing that loop means persisting fbclid and gclid at redirect time, carrying that identity to a sale that happens days later on another device, posting a Purchase with a stable event_id so it deduplicates against the pixel, rebuilding fbc in Meta's fb.1.{timestamp}.{fbclid} form, importing offline conversions to Google on gclid, gbraid, or wbraid, and reversing all of it on refund. Every one of those fails silently. That is the expensive part: the dashboard still shows clicks while the bidder optimizes against nothing.
Build me a branded link shortener with click tracking to replace LnkFlow. Requirements:
- Cloudflare Workers via wrangler: KV for the slug lookup, D1 for the click
log. Free tier, nothing to babysit.
- A worker on lnk.mydomain.com/{slug} reads KV, writes the click to D1 inside
ctx.waitUntil so the redirect never waits, then 302s with X-Robots-Tag:
noindex and Cache-Control: no-store.
- Inject UTM params at redirect time from the link's KV record, and pass
incoming fbclid, gclid, gbraid, wbraid, and msclkid through to the
destination untouched.
- Log per click: slug, timestamp, country from request.cf, user-agent,
referer, and those ad click ids. Skip bot user-agents from a pattern list
in one file.
- An /admin page behind one password (wrangler secret) to create links and
show clicks per link per day as a plain table.
- Secrets via wrangler secret, never in wrangler.toml. No accounts, no
third-party analytics, no telemetry.
- Out of scope: posting Purchase events back to Meta CAPI or Google offline
conversion import · stable event_id for pixel dedup, fbc as
fb.1.{timestamp_ms}.{fbclid}, and refund reversal. A silently wrong
conversion feed is worse than none.
- Out of scope: TLS for domains I do not own. My own subdomain is one DNS
record · a client's domain means Cloudflare for SaaS and DCV renewals.
- README: wrangler setup, the KV namespace and D1 database, the DNS record,
and adding the first link.$ open in your agent (prompt prefilled, you press enter) or copy it raw
The redirect is commodity and nobody should pay much for it. What is not commodity is staying current with Meta and Google as they change conversion endpoints, identifier formats, and consent requirements, which they do continuously and without waiting for you. Paying outsources that upkeep plus the attribution store that connects a click to a sale days later on a different device. Agencies pay for a second reason: issuing and renewing TLS for a client's branded domain is a genuinely different problem from pointing your own DNS record at a worker.
xPurchase events delivered back to Meta CAPI with stable event_id deduplication against the browser pixel
xGoogle offline conversion import keyed on gclid, gbraid, or wbraid
xclick to lead to sale attribution that survives a multi-day gap, with refund reversal
xTLS on a customer's branded domain (Cloudflare for SaaS and 90-day DCV renewals, not one DNS record)
xper-creator performance and commission reporting
What does the LnkFlow verdict mean?
The core job looks buildable, with meaningful gaps: Purchase events delivered back to Meta CAPI with stable event_id deduplication against the browser pixel, Google offline conversion import keyed on gclid, gbraid, or wbraid. Read the full tradeoff list before committing. This research record is not a hosted IVCIFY tool.
What price does this directory record show for LnkFlow?
The directory records $10/month for Starter, checked 2026-07-30. Verify the source before making a purchase decision. This reference stays outside retail Stack Math unless current matched evidence supports the comparison.
What do I lose by replacing LnkFlow?
Honestly: Purchase events delivered back to Meta CAPI with stable event_id deduplication against the browser pixel; Google offline conversion import keyed on gclid, gbraid, or wbraid; click to lead to sale attribution that survives a multi-day gap, with refund reversal; TLS on a customer's branded domain (Cloudflare for SaaS and 90-day DCV renewals, not one DNS record); per-creator performance and commission reporting. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to LnkFlow?
The listed prior art includes Dub (The most complete open-source link platform · analytics, custom domains, and a conversion API. Self-hostable.), Shlink (Self-hosted URL shortener with a REST API, click stats, and QR codes.), YOURLS (The long-running PHP shortener · drop it on any LAMP host and it works.). Inspect those projects before starting from a blank prompt.