O que construímos depois.
Proponha ideias, vote nas que você precisa e acompanhe o status. As mais votadas sobem na lista.
- 0
Link: Let search engines index a short link with a per-link indexing switch
Dub exposes a doIndex boolean per link and sends noindex by default (https://dub.co/docs/concepts/links/introduction). Link redirects in app/r/[slug]/route.ts sent no X-Robots-Tag, so short URLs could end up in search results. Built: redirects carry X-Robots-Tag: noindex unless the link turns on doIndex, with a checkbox in EditLinkForm and the field in the API.
Link: Change the destination by date range with time-based redirect rules
Lyncks lets one link change its destination automatically based on the time or date you set (https://www.hunted.space/product/lyncks). Link targeting covers country, device and A/B variants in lib/link-targeting.ts, with nothing based on time. A restaurant or a webinar team reuses one printed QR code and swaps the destination by hand each time. First scope: an ordered list of date range rules in the targeting JSON, checked before A/B, with the base URL as the fallback.
Link: Email a weekly digest with total clicks and the top links
Linkbreakers sends weekly and monthly digests with total visits, top country and top link (https://linkbreakers.com/help/article/weekly-and-monthly-email-digests). Link has analytics pages and CSV export (app/[locale]/app/links/analytics) but nothing reaches the owner unless they open the app. A small team with a few campaign links wants one Monday email with clicks against the previous week. First scope: an hourly tick job that sends one email per workspace owner who opted in from settings, built from the queries in lib/link-analytics.ts.
Link: Check destinations daily and flag links that return 404 or 5xx
Redirect and URL monitors such as Pagecrawl check a destination on a schedule and alert when it breaks, shortened links included (https://pagecrawl.io/tools/monitor-website-redirects-url-changes.html). Link never fetches a destination after creation: lib/links.ts only validates the URL syntax, so a printed QR can point at a dead page for weeks. First scope: a daily cron under app/api/cron that sends a HEAD request for links with clicks in the last 30 days, stores last_check_status and last_checked_at, shows a warning in components/link/LinksTable.tsx and the link detail, and emits a link.broken webhook event.
Link: Add a start date so a link only goes live from a set time
The Expired Link Redirection plugin schedules a link between two dates with a before, during and after URL (https://wordpress.org/plugins/expired-link-redirection/), and Lyncks changes a link destination by date (https://www.hunted.space/product/lyncks). Link only supports an end: expires_at and max_clicks in lib/links.ts, enforced in app/r/[slug]/route.ts. A small team printing a QR code ahead of a launch has to create the link on launch day. First scope: a nullable starts_at column, a datetime field next to expiry in components/link/EditLinkForm.tsx, and the redirect answering with the link fallback or a not-live-yet reason on /gone before that time.
Link: Add a count endpoint to the v1 API with the same filters as the list
Dub has GET /links/count that accepts the list filters and returns only the total (https://dub.co/docs/api-reference/endpoint/retrieve-links-count). Our API only returns total inside the paginated list, so a dashboard that wants a number must fetch a page of links too. First scope: GET /api/v1/links/count reusing parseLinkListQuery in lib/link-api-query.ts, links:read scope, grouped by an optional groupBy of tag or folder.
Link: Add bulk create, update and delete endpoints to the v1 API
Dub exposes POST, PATCH and DELETE on /links/bulk with up to 100 links per request (https://dub.co/docs/concepts/links/bulk-operations). We have bulk create and bulk actions in the app (app/api/links/bulk/route.ts) but they use the session, and the public v1 API creates one link per call. A team migrating thousands of links or tagging a campaign from a script hits the rate limit quickly. First scope: bulk create and bulk delete under links:write, up to 100 per request, with a per-item result so one bad row does not fail the batch.
Link: Add an upsert endpoint to the v1 API that creates or updates a link in one call
Dub offers PUT /links/upsert, which creates the link or updates the one with the same URL (https://dub.co/docs/api-reference/endpoint/upsert-a-link). Today an integration must GET by externalId, then POST or PATCH (app/api/v1/links/route.ts and lib/routes/v1/links/[id]/route.ts), with a race between the two calls. For a small team syncing links from a CMS or a database, one idempotent call is simpler and safer. First scope: PUT /api/v1/links/upsert keyed on externalId, falling back to destination URL, returning 200 when updated and 201 when created.
- 0
Link: Filter the v1 API links list by search, tag, folder, archived state and sort
Dub's list endpoint filters by search, tag, domain, folder and archived state (https://dub.co/docs/api-reference/endpoint/retrieve-a-list-of-links). Our GET /api/v1/links in app/api/v1/links/route.ts only accepted page, pageSize and creator, so an integration had to page through everything to find one link. First scope: q, tag, folder, archived and sort query params on the same endpoint, documented in the API reference.
Link: Daily click rollups for analytics and record clicks after the redirect
/api/links/analytics takes 23 ms with only 6,000 clicks, 5 times slower than any other list endpoint (measured). The plan joins links and clicks and builds a temp B-tree for GROUP BY, so it grows linearly with clicks. recordClick (lib/track.ts:145) also writes synchronously before the 302, which on Turso adds a round-trip to every redirect. Dub keeps clicks in a separate events store. First scope: a link_clicks_daily(link_id, day, country, device, referrer, count) table updated in the same batch, analytics reading from it, and the clicks INSERT moved into after(). Priority: medium. Effort: M.
Link: One-click DNS setup for custom domains
Dub added Domain Connect for one-click DNS on Vercel and Cloudflare in August 2026 (https://dub.co/changelog/domain-connect). Our domain setup shows records to copy and a verify button. Scope: detect the DNS provider, offer Domain Connect or the Cloudflare API with a token, then trigger verification automatically. Priority: low. Effort: M. Compared with Dub.
- 0
Link: Show a live stream of clicks as they happen
Dub analytics include a real-time event stream (https://dub.co/links). Our click log is paginated and only updates on reload. Scope: a live mode on the click log and workspace analytics that polls or uses server-sent events every few seconds, highlighting new rows with country, referrer and device. Priority: low. Effort: S. Compared with Dub.
- 0
Link: Keep an activity log of link changes per workspace
Dub includes audit logs on Enterprise (https://dub.co/pricing). We record who created a link but not who changed its destination, slug or targeting later, which matters when the link is printed on a QR. Scope: write an entry on create, update (field diff), archive and delete, show a History tab in link detail and a workspace-wide log filterable by member. Priority: low. Effort: M. Compared with Dub.
- 0
Link: Add link cloaking to keep the short domain in the address bar
Dub offers link cloaking on all plans (https://dub.co/pricing), which serves the destination inside a frame so visitors keep seeing the branded domain. We always redirect with 301/302. Scope: a per-link 'Cloak' option that serves a full-page iframe for destinations that allow framing (check X-Frame-Options/CSP at save time and warn), still recording the click. Priority: low. Effort: S. Compared with Dub.
- 0
Link: Give the bio page a live preview, themes and external links
Bitly Pages offers link-in-bio pages on paid plans (https://bitly.com/pages/pricing) and Dub has none, so this is our edge. Our BioEditor has no preview, no theme or social icons, and only lists existing short links. Scope: side-by-side live preview, a few themes using brand tokens, a social icon row, and adding a URL directly (we create the short link behind it so clicks still count). Priority: medium. Effort: M. Compared with Bitly.
- 0
Link: Import from Rebrandly, Short.io and any CSV
Dub imports from Bitly, Rebrandly, Short.io and CSV (https://dub.co/help/article/migrating-from-rebrandly.md, https://dub.co/help/article/migrating-from-short.md, https://dub.co/help/article/how-to-import-csv.md). Our ImportLinksPanel only takes a Bitly token or a Bitly CSV. Scope: Rebrandly and Short.io importers by API key (links, tags, domains), and a generic CSV with column mapping that reuses lib/link-bulk-csv.ts. Priority: medium. Effort: S. Compared with Dub.
- 0
Link: Support deferred deep linking after app install
Dub deep links include deferred deep linking and a migration path from Firebase Dynamic Links (https://dub.co/docs/concepts/deep-links/quickstart.md). Our targeting.ios / targeting.android open the app or fall back to the store, but the destination is lost after install. Scope: store the click id with device hints on redirect, expose an endpoint the app calls on first open to retrieve the original destination, and document the iOS and Android snippets. Priority: medium. Effort: L. Compared with Dub.
- 0
Link: Add row keyboard shortcuts and '/' to focus search in the links list
Dub supports c to create, e to edit and x to delete on the hovered link, plus single-key shortcuts in the link builder (https://dub.co/changelog/keyboard-shortcuts). In our list only C works; '/' does not focus the search and there is no '?' help. Scope: j/k or arrow navigation with a visible focused row, e opens Settings, x opens the delete confirm, a archives, '/' focuses search, '?' shows the shortcut sheet. Priority: medium. Effort: S. Compared with Dub.
Link: Publish a TypeScript SDK and an MCP server for links
Dub ships SDKs in TypeScript, Python, Ruby, PHP and Go (https://dub.co/docs/sdks/overview.md) and an MCP server (https://dub.co/docs/mcp-server.md). We publish openapi.json under /api/v1 but no client or MCP. Scope: generate a typed TS client from openapi.json, publish it to npm, and expose create, list, update and analytics tools through an MCP server authenticated with workspace API keys. Priority: high. Effort: M. Compared with Dub.
Link: Ship Zapier and Make apps plus Slack alerts for links
Dub lists Zapier, Make, Segment and Slack among its native integrations (https://dub.co/integrations). We only expose the REST API and webhooks, so non-technical teams cannot connect link events to their other tools. Scope: a Zapier app with triggers (link clicked, link created) and actions (create link, update link) on top of /api/v1 and existing webhooks, a Make module with the same, and a Slack incoming-webhook destination for click milestones. Priority: high. Effort: M. Compared with Dub.
- 0
Link: Add internal comments and a duplicate action to links
Dub lets teams add comments to a link, shown as a bubble on the link card, and stores them as a comments field in the API (https://dub.co/help/article/link-comments); Short.io exposes duplicate link actions in its API (https://help.short.io/en/articles/9790533-how-to-delete-links). Our links have only a title (lib/links.ts schema) and LinksTable row actions are copy, QR, edit, archive and delete with no duplicate. Notes like 'used in the October print flyer' and cloning a link to vary the UTM are routine for marketers. First scope: a comments text column editable in EditLinkForm with an icon in the row, and a Duplicate row action that opens the create form prefilled. Priority: low. Effort: S. Compared with Bitly / Dub.
- 0
Link: Allow domain choice and per-row slug and title in bulk create
Bitly Growth offers bulk link and QR creation from an upload, and Dub's bulk endpoints accept the full link payload per row, including domain and key (https://bitly.com/pages/pricing, https://dub.co/docs/api-reference/endpoint/create-a-link). Our createLinksBulk in lib/links.ts only takes a list of URLs plus one tag and UTM set, always on the default domain, with random slugs; BulkCreateForm has no domain selector. Teams with a branded domain have to create campaign links one by one to keep them on brand. First scope: a domain select in BulkCreateForm and CSV paste with url,slug,title columns reusing the bitly-import parser. Priority: low. Effort: S. Compared with Bitly / Dub.
- 0
Link: Capture city, region and full referrer URL on each click
Dub exposes regions, cities and referer_urls as analytics dimensions, and Bitly keeps city-level data as a premium upsell (https://dub.co/docs/api-reference/endpoint/retrieve-analytics, https://bitly.com/pages/pricing). contextFromHeaders in lib/track.ts stores only the referrer hostname and country, although Vercel already sends x-vercel-ip-city and x-vercel-ip-country-region headers on the same request. Local businesses and event promoters care more about the city than the country. First scope: add city, region and referrer_url columns to clicks, fill them from the platform headers, and show them in breakdowns and CSV exports. Priority: low. Effort: S. Compared with Bitly / Dub.
- 0
Link: Group links into folders with view or edit access per folder
Dub Pro includes folders, and Business adds per-folder access (can edit, can view, no access) with members added to private folders (https://dub.co/help/article/link-folders, https://dub.co/help/article/folders-rbac). Bitly Campaigns groups links by channel for side by side comparison (https://support.bitly.com/hc/en-us/articles/115001195167). We only have up to 5 free-text tags per link (lib/links.ts), no folder entity and no permission below workspace level. First scope: a link_folders table, folder picker in create/edit, folder filter in the list and analytics; access levels can follow later. Priority: low. Effort: M. Compared with Bitly / Dub.
- 0
Link: Record who created each link and filter the list by creator
Dub workspaces show the creator on each link card and support role-based access across team members (https://dub.co/data-model, https://dub.co/help/article/folders-rbac). Our links table only stores user_id, which is the workspace owner (lib/session.ts resolves the effective user to the owner), so in a shared workspace nobody can tell who made a link or find their own. This is the first thing a 5 to 20 person team asks for after inviting colleagues. First scope: created_by column filled from the acting user, avatar in LinksTable, and a 'created by' filter in FilterBar and the API. Priority: medium. Effort: S. Compared with Bitly / Dub.
- 0
Link: Publish a shareable read-only analytics page for a link or tag
Dub lets you publish a public analytics dashboard for a link or folder, optionally password protected, so clients and stakeholders see results without an invite (https://dub.co/help/article/share-analytics). Our analytics live only behind the session in app/[locale]/app/links/[id] and app/api/links/[id]/analytics; there is no public token. Agencies and small teams reporting to a client today export CSVs or screenshots. First scope: a share toggle that mints a token URL rendering the existing per-link chart and breakdowns read-only, with optional password reuse from the gate. Priority: medium. Effort: M. Compared with Bitly / Dub.
- 0
Link: Extend v1 API create with UTM, expiry, password, OG, targeting and externalId
Dub's create link endpoint accepts utm_*, expiresAt, expiredUrl, password, preview fields, geo/ios/android, A/B variants, tagNames, folderId and an externalId for upserts (https://dub.co/docs/api-reference/endpoint/create-a-link). Our POST /api/v1/links createSchema only takes url, domain, slug, title and tags, even though createLink supports UTM, expiry, password, max clicks and OG; it even maps an invalid_date error it can never produce. There are also no v1 endpoints for tags, domains or bulk create. First scope: pass every CreateLinkInput field through v1, add externalId with lookup and upsert, and expose GET /api/v1/links/domains and bulk create. Priority: medium. Effort: S. Compared with Bitly / Dub.
- 0
Link: Emit link.updated and link.deleted webhooks and scope click webhooks
Dub emits link.created, link.updated, link.deleted and link.clicked, and since July 2026 click webhooks can target all links, selected folders or selected links (https://dub.co/docs/concepts/webhooks/event-types, https://dub.co/changelog/improve-link-clicked-webhook). Our WEBHOOK_EVENTS in lib/webhooks-events.ts has only link.created and link.clicked; applyLinkPatch, the DELETE routes and bulkLinkAction emit nothing. Anyone syncing links to a sheet, CRM or Flow cannot see edits or deletions, and click webhooks fire for every link in the workspace. First scope: emit link.updated and link.deleted (single and bulk) and add an optional tag filter on link.clicked subscriptions. Priority: medium. Effort: S. Compared with Bitly / Dub.
- 0
Link: Add utm_term/utm_content and saved workspace UTM templates
Dub's UTM builder covers all five UTM params plus ref and lets teams save workspace-level UTM templates applied from the link builder; templates are on the free plan (https://dub.co/help/article/how-to-create-utm-templates, https://dub.co/pricing/links). Our applyUtm in lib/links.ts only handles source, medium and campaign, and every link or bulk run retypes them by hand. Consistent UTM naming is the main reason small marketing teams adopt a shortener. First scope: utm_term and utm_content fields, a link_utm_templates table, and a template picker in NewLinkForm, QuickLinkModal and BulkCreateForm. Priority: medium. Effort: M. Compared with Bitly / Dub.
- 0
Link: Make UTM fields editable and keep them in sync with the destination URL
UTM params are baked into links.url at creation (applyUtm in lib/links.ts) and also stored in utm_source/medium/campaign, but linkPatchSchema has no UTM fields and EditLinkForm has no UTM inputs. If a user edits the destination and removes or changes the utm params, the stored utm_* columns and the API DTO keep reporting the old values, so the data is inconsistent. Dub treats UTM as editable link fields that set or override params in the destination (https://dub.co/docs/api-reference/endpoint/create-a-link). First scope: add utm fields to linkPatchSchema and the edit form, and re-derive the utm_* columns from the final URL on every URL change. Priority: medium. Effort: S. Compared with Bitly / Dub.
- 0
Link: Let expired and missing links redirect to a custom URL per link and domain
Dub supports expiredUrl per link and expiredUrl/notFoundUrl defaults per domain, so a dead campaign link lands on a useful page instead of an error (https://dub.co/help/article/link-expiration, https://dub.co/help/article/setting-not-found-url). In app/r/[slug]/route.ts every expired, limit-reached, archived or unknown slug goes to the zerosoft /gone page, even on a customer's own branded domain; link_domains only has root_url. Printed QR codes and old campaign emails keep getting traffic long after expiry, and a zerosoft error page on a customer domain looks broken. First scope: expired_url column on links, expired_url and not_found_url on link_domains, used by the gone() branches. Priority: high. Effort: S. Compared with Bitly / Dub.
- 0
Link: Add filters (tag, domain, link, country, device) and timezone to analytics
Dub analytics can filter and group by tag, folder, domain, link, country, region, city, device, browser, OS, referrer URL and UTM values, with an IANA timezone for day buckets (https://dub.co/docs/api-reference/endpoint/retrieve-analytics). Our workspace dashboard in lib/link-analytics.ts takes only a date range and the per-link view in lib/track.ts getAnalytics only a preset range; both bucket days in UTC and the workspace view omits OS. A small team running a campaign cannot answer 'how did links tagged launch perform in Brazil on mobile'. First scope: tag, domain, country and device filters on the workspace dashboard and API, OS breakdown, and day buckets in the workspace timezone. Priority: high. Effort: M. Compared with Bitly / Dub.
- 0
Link: Track leads and sales per link and attribute them to CRM contacts and deals
Dub Conversions records lead and sale events against the click that produced them (client SDK plus /track/lead and /track/sale, Stripe integration) and shows clicks to leads to sales funnels per link (https://dub.co/help/article/dub-conversions, https://dub.co/docs/integrations/stripe). We only record clicks (lib/track.ts recordClick); there is no click id, no conversion table and no lead/sale event. We already own a CRM, so this is a strong differentiator: a click id cookie on redirect, a lightweight track endpoint, and CRM form submissions or deal won events attributed back to the originating link. First scope: set a zs_click id on redirect, accept POST /api/v1/track/lead with that id, and show leads per link in analytics and on the CRM contact timeline. Priority: high. Effort: L. Compared with Bitly / Dub.
- 0
Link: Forward query parameters from the short link to the destination URL
Dub appends any query string on the short link (for example ?utm_source=newsletter) to the destination, with the short link value winning on conflicts, so one link can be reused across channels (https://dub.co/help/article/parameter-passing). Our middleware already forwards req.nextUrl.search into /r/<slug>, but app/r/[slug]/route.ts redirects to link.url or the targeting destination and drops every incoming param except reading ?qr=1. Marketers who tag a short link per channel silently lose that attribution today. First scope: merge incoming params into the resolved destination (strip our internal qr param), apply to deep link fallbacks too, and add a per-link toggle defaulting to on. Priority: high. Effort: S. Compared with Bitly / Dub.