Start with a completed action
To find which sources bring signups, compare sessions that reach a signup goal with all sessions from each source. Page views alone cannot tell you whether a newsletter, search result, or launch post brought useful results.
In WhoVisited Settings, expand your website and create a goal. Choose an exact success-page path, such as /signup/complete, or a custom event name, such as signup_completed. A page goal uses the path without a query string or fragment. A custom event must be sent by your website after the action succeeds.
// Run after a successful signup, once the tracker has loaded.
window.whovisited?.track("signup_completed");Do not count a click on the signup button as a completed signup unless that is the action you intend to measure. A custom event is a signal from your implementation; WhoVisited does not independently verify the signup or payment.
Tag campaign links consistently
Use UTM parameters on links you publish outside your website. For example, a link from your September newsletter could be:
https://example.com/?utm_source=newsletter&utm_medium=email&utm_campaign=september_launchWhoVisited stores the first session event's entry page and attribution. It accepts utm_source, utm_medium, and utm_campaign, with a limit of 100 characters per value. Choose a consistent naming convention such as lowercase words with underscores. Do not put customer emails or other personal data in campaign tags.
When a UTM source is absent, the report can use the referring origin. If neither is available, it shows Unknown source. That can include direct visits, stripped referrers, and privacy controls; it is not a reliable count of people who typed your URL.
Compare source and landing-page results
Open Growth, choose your website, goal, and a 7-, 28-, or 90-day window. Sources shows sessions and goal sessions by source and campaign. Landing pages groups them by the page where each session started.
A goal session contains at least one matching event in that same session. Repeating the action in one session still counts as one goal session. The conversion rate is goal sessions divided by sessions. Historical retained events can match a newly created goal.
| Source | Sessions | Goal sessions | Rate |
|---|---|---|---|
| Newsletter | 80 | 8 | 10% |
| Launch post | 200 | 6 | 3% |
The report hides percentages for rows with fewer than 20 sessions. Twenty sessions is a display threshold, not proof of statistical significance. Use the raw counts and allow more time before making decisions from a small sample.
Decide what to test next
- Visits, but no goal sessions: test the goal first. Then check the landing page's message, signup form, mobile layout, and link to the next step.
- A source brings goal sessions: review the campaign and entry page together before investing more time or money.
- A high percentage with few visits: collect more data. A single completion can make a small sample look unusually strong.
- Changing a page: record what changed and when. Compare similar periods and note campaigns or traffic changes that could affect results.
This is session-level attribution. It does not trace one person across devices or assign credit across every earlier campaign. For Google visibility before the visit, use Search Console alongside your session report.