Get/Tracked turns every campaign link into clear click, source, device, location and destination intelligence.
Replies
Best
Maker
📌
Hey Product Hunt! 👋
I’m Naman, the founder of Get/Tracked.
I started building Get/Tracked after repeatedly facing one simple problem: campaign links were being shared across creators, social platforms, communities and placements, but it was difficult to clearly understand which link was actually generating traffic.
Get/Tracked gives every campaign and placement its own measurable tracking link. It records:
• Total and unique clicks
• Source, medium and placement
• Date and time
• Device, browser and operating system
• Referrer and approximate location
• Unique versus repeat visitors
• The destination connected to each link
Campaign owners can also share selected results with clients or collaborators through private, time-limited access, without exposing their entire workspace.
We’ve intentionally kept Campaign Tracking focused on what can be verified: the journey from a valid tracking-link click to the destination redirect. Website behaviour is handled separately through Website Analytics.
Get/Tracked is still evolving, and your feedback would genuinely help shape what we build next.
I’d especially love to know:
1. What campaign data do you normally struggle to collect?
2. Would you use Get/Tracked for clients, creators or your own brand?
3. What feature would make it more useful for your workflow?
Thanks for checking it out! 🚀
Report
dumping raw UTM logs in Claude already gives clean campaign summary and attribution breakdowns, unless this syncs live platform spend to recalcualte true CAC on fly it just feels like UI wrapper over basic prompt ) what context you feeding model that CSV export lacks
Report
Maker
@konstantin_tikhaev Fair point as we don’t currently sync live ad spend or calculate CAC, so I wouldn’t claim that yet.
The context beyond a basic UTM CSV is first-party click-level data: unique vs repeat clicks, timestamp, source, medium, placement, referrer, device, browser, OS, location, tracking-link relationships and campaign history.
The goal isn’t just to send logs to an AI for a summary. It’s to collect, structure and retain that data automatically, then let teams query and compare it without repeatedly cleaning and uploading CSVs.
Live platform-cost sync and CAC/ROAS calculation are logical next steps, though. Which ad platforms would make that most useful for you?
Report
@namansinha23 shifts it from prompt wrapper to automated traking pipeline. auto data collection solves manual export headache. but live cost data still missing for true attribution decisions
Report
Maker
@konstantin_tikhaev Yes so that’s the missing layer for now. Live spend from platforms such as Meta and Google Ads, combined with verified conversion outcomes, would let Get/Tracked calculate CAC and ROAS instead of stopping at traffic attribution.
The current version focuses on automated first-party click collection and campaign analysis. Cost and conversion integrations are the next major step!
Report
@namansinha23 Meta and Google spend sync is real "unlock" there. Cost data joins first-party click stream, then becomes actaul attribution engine.
Replies
dumping raw UTM logs in Claude already gives clean campaign summary and attribution breakdowns, unless this syncs live platform spend to recalcualte true CAC on fly it just feels like UI wrapper over basic prompt ) what context you feeding model that CSV export lacks
@konstantin_tikhaev Fair point as we don’t currently sync live ad spend or calculate CAC, so I wouldn’t claim that yet.
The context beyond a basic UTM CSV is first-party click-level data: unique vs repeat clicks, timestamp, source, medium, placement, referrer, device, browser, OS, location, tracking-link relationships and campaign history.
The goal isn’t just to send logs to an AI for a summary. It’s to collect, structure and retain that data automatically, then let teams query and compare it without repeatedly cleaning and uploading CSVs.
Live platform-cost sync and CAC/ROAS calculation are logical next steps, though. Which ad platforms would make that most useful for you?
@namansinha23 shifts it from prompt wrapper to automated traking pipeline. auto data collection solves manual export headache. but live cost data still missing for true attribution decisions
@konstantin_tikhaev Yes so that’s the missing layer for now. Live spend from platforms such as Meta and Google Ads, combined with verified conversion outcomes, would let Get/Tracked calculate CAC and ROAS instead of stopping at traffic attribution.
The current version focuses on automated first-party click collection and campaign analysis. Cost and conversion integrations are the next major step!
@namansinha23 Meta and Google spend sync is real "unlock" there. Cost data joins first-party click stream, then becomes actaul attribution engine.