SessionSight: Attribution
Overview
Use this page to review multi-touch attribution rollups by channel and campaign. Attribution assigns credit for a conversion to the marketing channels and campaigns a visitor touched before converting, using an attribution model you choose, such as crediting only the first channel, only the last channel, or splitting credit evenly across every touchpoint. Without this view, a raw conversion count can't tell you which channel or campaign actually justified the spend that produced it.
Attribution depends on data collected elsewhere in SessionSight: a container must already be tracking visitor sessions and conversions, and the UTM tags on your campaigns must be mapped to channel names through the Channel Grouping configuration before rollups can resolve to anything meaningful. The backend computes rollups periodically rather than live, so what you see reflects whatever period the attribution job has already processed for the selected container. The figures here typically inform decisions made outside the platform, such as reallocating marketing spend across channels.
On this page you select a Tenant, optional Tenant group, Container, and Date range to scope the data, then choose an attribution model to control how credit is distributed across touchpoints. Refresh re-runs the query against your current filters, and Configure channel grouping takes you to where UTM-to-channel mappings are maintained when results are missing or unattributed.
Key concepts
- Attribution model - A rule for assigning conversion credit across the touchpoints in a visitor's journey. First touch credits the earliest channel the visitor used, Last touch credits only the most recent channel before conversion, and Linear splits credit evenly across every touchpoint.
- Channel Grouping - The per-tenant configuration that maps UTM tags on your campaign links to friendly channel names. Without it in place, conversions can't be rolled up into named channels on this page. (related: Configuration: SessionSight: SessionSight)
- Container - The tracked site or app instance that SessionSight collects session and conversion data for. Attribution rollups are always scoped to one container at a time. (related: SessionSight: Dashboard)
- Rollup - A precomputed summary of attribution results produced periodically by a backend job, rather than calculated live when you open the page. A rollup can lag behind recent conversions until the job next runs.
When to use it
- Before reallocating marketing spend, to see which channels and campaigns are actually credited with conversions.
- To compare how credit distribution shifts between attribution models, such as First touch versus Linear, for the same period.
- Right after setting up Channel Grouping, to confirm that UTM tags are resolving to the channel names you expect.
- When investigating why a container shows no attributed conversions, to rule out a missing or incomplete Channel Grouping configuration.
- When reviewing results across several related tenants at once using a Tenant group.
Before you begin
- The Container you want to analyze must already be collecting SessionSight session and conversion data, configured under Configuration: SessionSight: SessionSight.
- Channel Grouping must be set up so UTM tags on your campaigns map to channel names; configure it from the Configure channel grouping link or Configuration: SessionSight: SessionSight.
- Conversions must have actually occurred, with UTM-tagged traffic, within the date range you plan to select.
- You need access to the Tenant (or Tenant group) whose data you want to view.
Common workflows
Review which channels get credit for conversions
Persona: Marketing or test operator reviewing SessionSight results
- Select the Container you want to analyze from the filter bar.
- Expect: The page re-queries rollups scoped to that container, showing either attribution data or the No attribution rollup yet empty state.
- Choose a wider Date range, such as 7d.
- Expect: The page re-queries rollups for the wider window, which is more likely to contain conversions than the default 1h window.
- Click Refresh.
- Expect: The rollup query reruns; the panel either lists channel and campaign credit or continues to show No attribution rollup yet if still no data exists.
Verify: The empty state is replaced by a Channel x Campaign credit view, including Top channels and a Channel + Campaign breakdown with Conversions and Conversion Value figures. If it still reads No attribution rollup yet, widen the date range further or confirm Channel Grouping is configured.
Compare attribution models for the same period
Persona: Operator deciding how to credit marketing channels
- With a date range already selected, click First touch.
- Expect: The First touch button becomes the active model and the page re-queries credit distribution based on each visitor's earliest channel.
- Click Linear to compare.
- Expect: The Linear button becomes active and, where data exists, conversion credit is redistributed evenly across every touchpoint instead of concentrating on one channel.
Verify: Comparing the channel and campaign figures across models shows whether credit concentrates on top-of-funnel or bottom-of-funnel channels, confirming which model best matches how you want to evaluate channel performance.
Steps
Step 1
Open the Attribution page under SessionSight.
Expected result: The page loads with the default filters: Tenant LoadGen B.V., Container Production Web App, Date range 1h, and Model Last touch. Because no conversions have been rolled up for that window, it shows a No attribution rollup yet empty state.
This default view establishes the current filters and shows whether rollup data already exists before you adjust anything.
- The Model toggle shows Last touch selected, with U-shaped and Time decay shown but disabled.
- Date range defaults to 1h.
-
Configure channel grouping links to where UTM-to-channel mappings are maintained.
Step 2
Click Refresh.
Expected result: The page re-runs the attribution query using the same Tenant, Container, Date range, and Model values. Since no new conversions have been rolled up for this container and period, it continues to show No attribution rollup yet.
Refreshing confirms whether the backend's attribution job has produced new rollups since you opened the page, without changing any filter.
-
Refresh uses the Tenant, Tenant group, Container, Date range, and Model values currently shown above it.
Field reference
| Field | Purpose | Format / Validation | Required | Default |
|---|---|---|---|---|
| Tenant | Selects which tenant's conversion data the rollup is scoped to. Switching tenants changes the entire dataset shown on the page. | dropdown | No | LoadGen B.V. |
| Tenant group | Optional. When set, fans the attribution query across every member tenant of the group instead of a single tenant, useful for a combined view across related sites. Leave it on No groups to see one tenant at a time. | dropdown | No | No groups |
| Container | Selects which tracked site or app's conversions to attribute. Each container has independent conversion tracking, so switching it changes the entire result set. | dropdown | No | Production Web App |
| Date range | Controls the time window of conversions included in the rollup. Shorter presets like 1h surface the most recent activity but are more likely to show no data for low-traffic containers; wider presets like 7d include more conversions and smooth out short-term gaps. Custom lets you set a window outside the presets. | segmented preset buttons: 1h, 4h, 8h, 24h, 7d, Custom | No | 1h |
| Model | Determines how conversion credit is split across a visitor's touchpoints. First touch credits the channel that originally brought the visitor; Last touch (the default) credits only the most recent channel before conversion; Linear divides credit evenly across every touchpoint. U-shaped and Time decay are visible but disabled and can't be selected. | segmented toggle buttons: First touch, Last touch, Linear, U-shaped, Time decay | No | Last touch |
Controls reference
Refresh
Re-runs the attribution rollup query using the current Tenant, Tenant group, Container, Date range, and Model selections.
When to use: After changing any filter, or simply to check whether the backend's attribution job has produced new rollups since you opened the page.
Side effects: Read-only: it re-fetches and redisplays data for the current filters without changing any stored configuration.
Configure channel grouping
Navigates to the Channel Grouping configuration area where UTM-to-channel mapping rules are maintained.
When to use: When the page shows no attributed data, or when channel and campaign names in the rollup look wrong or incomplete.
Side effects: Navigation only: it leaves the Attribution page and does not change any data shown here.
Verify the result
When rollups exist for the selected Tenant, Container, Date range, and Model, the empty state is replaced by a Channel x Campaign credit view, with Top channels and a Channel + Campaign breakdown listing Conversions and Conversion Value per channel and campaign. If the page still shows No attribution rollup yet after clicking Refresh, first check that Channel Grouping is configured, then widen the Date range before assuming conversions are missing. The selected Model (shown next to Model:) stays highlighted in the toggle so you can confirm which attribution logic produced the figures you're reviewing.
Troubleshooting
- Symptom: The page still shows No attribution rollup yet after clicking Refresh. Fix: Widen the Date range (try 7d or Custom) since the default 1h window may contain no conversions, and allow time for the backend's attribution job to process the container.
- Symptom: Conversions exist but the breakdown doesn't show recognizable channel names. Fix: Open Configure channel grouping and confirm your UTM tags are mapped to channel names; unmapped UTM tags won't resolve to friendly channels.
- Symptom: U-shaped and Time decay can't be selected in the Model toggle. Fix: These models are not available; use First touch, Last touch, or Linear instead.
- Symptom: Results look incomplete after selecting a Tenant group. Fix: Confirm each tenant in the group is actually collecting SessionSight conversions for the selected Container and Date range; tenants without rollups contribute nothing to the combined view.
Related articles
- Prerequisite: Configuration: SessionSight: SessionSight - Channel Grouping must map UTM tags to channel names before rollups resolve to anything meaningful
- See also: SessionSight: Funnels - conversions tracked through funnels are the events that attribution rollups credit to channels
- See also: SessionSight: Dashboard - overview of session and conversion activity for the same container
- See also: SessionSight: Journeys - shows the full touchpoint sequence that multi-touch attribution models summarize into channel credit