Find the story
behind the traffic.

What a traffic source can tell you

A traffic source describes information associated with the origin of a visit or user interaction. It helps you connect activity to search engines, other websites, campaigns, or situations where the reporting tool has no usable referral information. How a tool assigns that source depends on its collection and reporting rules.

A channel groups sources into broader categories. A source might name a particular referring website, while a channel groups it with other referrals. Keep this difference in mind when a detailed report and a summary report use different labels.

Read the main traffic categories

Do not assume direct traffic always means somebody typed your address. Missing or unavailable referral and campaign context can also affect attribution. Investigate a rise in direct traffic alongside link distribution, redirects, and changes in campaign tagging.

Keep scope consistent

The source associated with a user’s first visit and the source associated with a later session answer different questions. Mixing the two can make a channel appear to perform differently even when both reports are working as intended.

The official Google Analytics traffic-source guide explains its source dimensions and scopes. In your own report, write down whether you are examining first-user acquisition, session acquisition, or event attribution.

Use campaign labels deliberately

UTM parameters add reporting context to a destination URL. Establish a small naming convention before links are distributed. Consistent lowercase labels, meaningful campaign names, and a shared record make results easier to group later.

For example, a hypothetical seasonal guide promoted through an email could use a source identifying the mailing list, a medium of email, and a campaign label describing the launch. Keep personal details and sensitive information out of these labels. See the UTM tracking guide for a practical naming and testing workflow.

Combine source with destination and outcome

A source report is more useful when it includes what happened after arrival. Compare the landing page, the relevant audience segment, and a clearly defined action. A channel that brings many visits to a poor match may be less useful for a particular goal than a smaller, more relevant source.

Use counts and rates together. A higher rate based on a handful of sessions can be less stable than a lower rate based on many more. Keep the denominator visible and avoid declaring a winner before you have enough context to explain the difference.

Investigate a change one step at a time

1. Confirm the reporting window, timezone, and scope.
2. Check whether the change affects one source or several.
3. Compare landing pages and device categories.
4. Review campaign distribution and recent site changes.
5. Separate a collection problem from a real change in activity.

End the investigation with a specific next step. You might repair a broken destination, improve a campaign label, clarify a landing page, or continue monitoring an uncertain pattern. Record the reasoning in your weekly analytics report.