Conversion tracking
First-party conversion tracking, without third-party cookies
First-party conversion tracking means directinapp sets its own visitor id (dia_vid) on the domain the shopper is already on, so there are no third-party ad trackers loading on your customers. You still get the sale matched back to the click, but honestly: a first-party cookie is scoped to one browser, so it won't recognise the same person across devices.
What is first-party conversion tracking?
First-party conversion tracking ties a click to a sale using an id your own site sets (dia_vid, a first-party cookie) plus a server-side postback, not a third-party ad-network pixel. It keeps working when browsers block third-party cookies, but it is cookie-scoped to one browser, so it won't follow the same buyer across devices.
Why it matters
It keeps counting when third-party pixels get blocked
Safari ITP, Brave, and ad blockers strip third-party cookies, so a Meta or Google pixel silently loses conversions. Because dia_vid is a first-party cookie set on the page your shopper is already on, it survives those blockers and your Razorpay sale still ties back to the original click.
No third-party trackers riding on your customers
You aren't dropping an ad network's tracker onto your thank-you page. directinapp reads its own first-party id and posts the conversion server-to-server, so your buyers aren't fingerprinted by outsiders and you have a cleaner privacy story for Indian shoppers who care.
The sale is confirmed by your server, not a browser tag
A pixel can be blocked or double-fire. With the POST /conversions postback (or a signed Razorpay/Stripe/Shopify/WooCommerce webhook), the paid order is recorded server-side in rupees, matched to dia_clid or dia_vid, so your numbers reflect money that actually moved.
Set it up
Three steps, no developer
Share a directinapp link
When someone taps your link (Instagram bio, WhatsApp, an ad), directinapp records the click as dia_clid and, on your landing domain, sets dia_vid, a first-party cookie in that browser. Nothing third-party loads.
Confirm the conversion on your side
On the thank-you page fire the no-code pixel (GET /c), or send a server postback (POST /conversions), or just connect the signed Razorpay/Stripe/Shopify/WooCommerce webhook so paid orders auto-capture without touching your keys.
Read attributed sales in the dashboard
directinapp matches the conversion back to the click via dia_clid or the first-party dia_vid and shows which link, geo and device drove the rupees. It's browser-scoped, so cross-device journeys stay approximate.
Watch it end to end — link, snippet, sale
directinapp.com/diwali-sale
your short link — clicks tracked free
Frequently asked questions
What is first-party conversion tracking and how is it different from third-party?+
First-party conversion tracking uses an id your own site sets (dia_vid) plus a server-side postback to match a sale to a click. Third-party tracking relies on an ad network's cookie shared across other sites, which Safari, Brave and ad blockers increasingly strip out. First-party data lives on your domain, so it survives those blockers.
Does first-party tracking follow the same person across their phone and laptop?+
No. A first-party cookie like dia_vid is scoped to a single browser on a single device, so it can't recognise the same person across devices. If someone clicks on their phone and buys on their laptop, that stitch isn't guaranteed. True cross-device identity is on the roadmap, not shipped.
Will this still work when third-party cookies are blocked?+
Yes. dia_vid is set as a first-party cookie on the page the shopper is already visiting, and the conversion is confirmed server-side via POST /conversions or a signed payment webhook. Neither depends on third-party cookies, so ITP and ad blockers don't wipe your numbers.
Do my customers get tracked by ad networks through directinapp?+
No. directinapp doesn't inject a third-party ad tracker onto your pages. It reads its own first-party id and reports conversions server-to-server, so no outside network is fingerprinting your buyers through us.
Is the server postback signed?+
The payment webhooks from Razorpay, Stripe, Shopify and WooCommerce are signature-verified. The plain POST /conversions postback is currently unsigned, so keep its endpoint on your trusted server rather than exposing it in client-side code.
Which plan includes first-party conversion tracking?+
Conversion tracking sits in the Business tier, which you can try on a free trial. Every link, on any plan, still gets free click, geo and device analytics, QR codes, deep-links and a link-in-bio page.
More on conversion tracking
directinapp Business
The full conversion-tracking product — pricing, setup and a live demo.
Conversion tracking
Conversion tracking is measuring the real outcomes a link drives — a sale, a signup, a lead — not just the clicks. You tell your analytics tool "this counts as a conversion, worth this much," and it ties that outcome back to the link that earned it. directinapp does this on every link: fire a pixel, a postback or our drop-in dia.js script when a sale happens, and see the count, the rupee value and the conversion rate for that exact link — right down to which click and visitor drove it.
Instagram sales tracking
Yes — you can track sales and signups from an Instagram bio link or reel. Put your store or checkout behind a directinapp link, fire our pixel on your payment success page, and the Business report shows the count, rupee value and conversion rate that link drove. Even though a bio or reel is one shared link, per-visitor and per-click attribution shows which visitor and which click drove each sale — the visitor id is cookie-scoped to this browser, not the same person across devices.
vs Linktree
Linktree tells you a link got clicked. directinapp tells you it drove 12 purchases worth Rs 5,988. On any link you can fire our tracking pixel or server postback with a sale value, and the Business tier shows conversion count, total value and conversion rate per link, per currency (INR/USD/EUR/GBP/AED). Attribution now runs per-click and per-visitor (dia_clid and dia_vid), and signed webhook auto-capture for Razorpay, Stripe, Shopify and WooCommerce records a paid order automatically.
Tracking pixel
A tracking pixel for links is a tiny 1×1 image you load when a sale happens. Point an img tag at GET /c?s=SLUG&e=purchase&v=499&cur=INR and directinapp records one conversion — with its rupee value — against the link that drove it. No SDK, no cookie, no code beyond one line of HTML.
Server postbacks
A server postback records a conversion by sending a POST /conversions call from your backend to directinapp. You send JSON with the link's slug, an event name, value and currency, and the dashboard shows counts, total value and conversion rate per link. It is shipped and works today. Signed, HMAC-verified postbacks are on the roadmap.
Lead tracking
Yes — you can track leads and signups from any directinapp link today. Fire a "lead" or "signup" event from your form's thank-you page with our pixel or postback, and each link shows its lead count, conversion rate, and a per-event breakdown. Attribution ties each lead to the click and the visitor — a cookie-scoped id for this browser — that drove it; recognising the same person across devices is still on the roadmap.
Stop losing clicks at the browser
Create your first smart link in under a minute and see where every tap really goes.
Start freeNo credit card required · 7-day free trial