To track referral traffic from a SaaS directory listing, confirm that the listing is live, note where its link sends visitors, then compare that record with your website analytics for the same period. A matching directory source is evidence of traffic from that source—not necessarily from that exact listing page. If the live link has a unique campaign tag, you can make a more specific assessment. Keep submissions, published listings, visits and completed signups as separate results.
Start with live links and a defined reporting window
Make one assessment row per live listing. Record its public listing URL, the destination reached by its product link, the date you checked both pages, the analytics provider and the period you will inspect. Note any campaign parameters actually present on the live outbound link. If a directory sends visitors through a redirect, record the final destination you observe rather than assuming the submitted URL is still in use.
Ranks shows which directory submissions are awaiting approval and which listings are live; publishers decide approval and timing. Its optional traffic connection reports visitors and traffic sources from either GA4 or Vercel Web Analytics, with provider processing delays. Use Ranks to bring the listing record and traffic overview together, then inspect the connected provider when you need to assess a particular source or listing. For the separate job of maintaining approval records and checking public URLs, use the directory submission-tracking guide.
Look for the directory in your traffic provider
In GA4, open Reports → Acquisition → Traffic acquisition, set the period you recorded, and inspect Session source / medium. Search the table for the directory’s domain or your known campaign source, then record the Sessions figure for the matching row. GA4 describes this as session-source data: do not relabel the figure as unique people, clicks on the listing page or signups. A source match identifies the reported source; if the same domain links to your site from multiple pages, it does not isolate one listing.
If your site uses Vercel Web Analytics instead, select the assessment period in its Visitors tab and examine the referrers panel. Vercel also describes referrers for a specific page, which can help when the listing points to a distinct destination. Record the displayed visitor figure as visitors, not GA4 sessions; the two providers use different measures. A referrer domain still does not identify which page on that domain contained the link.
If you can choose or update the directory’s outbound URL, a distinct tagged destination can give GA4 a clearer campaign match. Google documents adding utm_source, utm_medium and utm_campaign to destination URLs and viewing their values in Traffic acquisition. For a hypothetical listing, https://example.com/?utm_source=launchboard&utm_medium=referral&utm_campaign=atlas_profile identifies that campaign only if the published listing actually uses that URL and the campaign value is reserved for that link. Check the live link after an edit; a tag in your spreadsheet cannot identify earlier visits or traffic through an untagged link.
Turn source rows into a defensible listing assessment
Here is a hypothetical assessment for one week. Both listing pages and their outbound links were checked during that week; the figures below are invented GA4 session counts, not measured results. The team has also found a separate editorial link on catalog.example pointing to the same feature page. GA4’s Session source / medium and Sessions provide the source-level inputs, but the team must use its own link inventory to judge whether a source is exclusive to a listing.
The first row supports “8 sessions from the directory domain,” not proof of eight clicks on that particular profile: another link on that domain might exist. The second supports “5 sessions from the domain, listing contribution uncertain” because two known links could have sent them. Do not split those five between links without evidence, and do not turn either figure into a signup count. If a uniquely tagged live link later appears as its own GA4 campaign, report the tagged campaign’s sessions separately for the period when that link was in use.
| Live listing and destination | Reported source and sessions | Assessment |
|---|---|---|
https://launchboard.example/products/atlas → https://example.com/ | launchboard.example / referral: 8 sessions | Observed domain-source traffic; exact listing-page attribution unconfirmed. |
https://catalog.example/tools/atlas → https://example.com/features | catalog.example / referral: 5 sessions | Domain traffic observed; listing contribution uncertain because an editorial link shares the source. |
Report what each stage proves
A submitted listing is an outreach record, not a visit. A live listing proves that a public page and outbound route were observed, not that someone followed the link. A matching source row establishes reported traffic from that source during your chosen period; an exclusive, verified tag gives you a stronger link-level match. Completed signups require separate evidence from the signup process. Even a signup-button click is not a completed signup; the Vercel signup-click guide covers that distinction.
If no matching source appears, mark the listing “no identifiable traffic in this report and period,” not “zero visits.” Recheck the provider, dates, live destination and any tag before drawing a conclusion. Ranks notes that connected traffic reports depend on provider processing delays, so a newly live listing deserves a later check rather than an immediate verdict. Preserve uncertain rows: they tell you exactly where a distinct destination or publisher-approved tagged link could improve the next assessment.



