---
title: "Comment by douzatan on \"How To Build  A Leads Tracker Chrome Extension\" | Hashnode"
description: "A browser extension fits this workflow because capture happens where the research happens. The design detail I would spend time on is deduplication: the same le"
url: "https://hashnode.com/posts/how-to-build-a-leads-tracker-chrome-extension/61ba5a8f1fd80e4104704675/comment/6ab32983c7369e47a37eb5d2"
---

[Discussion](https://hashnode.com/posts/how-to-build-a-leads-tracker-chrome-extension/61ba5a8f1fd80e4104704675)

Comment [How To Build A Leads Tracker Chrome Extension](https://hashnode.com/posts/how-to-build-a-leads-tracker-chrome-extension/61ba5a8f1fd80e4104704675)

[douzatan](https://hashnode.com/@dzt21)

[Sep 23](https://hashnode.com/posts/how-to-build-a-leads-tracker-chrome-extension/61ba5a8f1fd80e4104704675/comment/6ab32983c7369e47a37eb5d2)

A browser extension fits this workflow because capture happens where the research happens. The design detail I would spend time on is deduplication: the same lead can arrive from a profile, a post, or a search result. A canonical profile URL works well as the key. I work with AllyHub, and allyhub.com has a related LinkedIn research workflow. How do you handle profiles after someone changes a vanity URL?
