SessionSight: Attribution

Updated

SessionSight: Attribution

Overview

Use this page to review attribution rollups across channels and campaigns. Attribution is multi-touch: it splits conversion credit across the different interactions a visitor had before converting, rather than crediting only the last click. This answers which marketing channels and campaigns actually contributed to conversions on a monitored site or app.

Attribution builds on session and conversion data SessionSight already tracks for a tenant's container. Before it shows anything meaningful, a Channel Grouping configuration must map UTM tags to named channels on the Configuration: SessionSight: SessionSight page, and SessionSight access must be licensed. Attribution is a terminal report: it has no further platform step after it, feeding decisions about channel and campaign investment instead.

This page lets you filter rollups by tenant, tenant group, and container, pick a time window from preset chips or a custom range, and choose which attribution model credits conversions. Click Refresh to re-query the rollup for your current selections. Until a rollup exists for the chosen scope, the page explains why and links to the Channel Grouping configuration you likely need.

Key concepts

  • Attribution model - A rule for how conversion credit is split across the touchpoints in a visitor's journey, such as crediting only the first interaction, only the last, or spreading credit evenly. (related: SessionSight: Journeys)
  • Channel Grouping - A per-tenant configuration that maps UTM tags (campaign, source, and medium parameters in a URL) onto friendly channel names, so rollups show names like Paid Search instead of raw UTM text. (related: Configuration: SessionSight: SessionSight)
  • Container - The specific monitored site or application whose session and conversion data you are viewing attribution for. (related: SessionSight: Dashboard)
  • Tenant group - A saved collection of tenants that lets you fan an attribution query across every member tenant at once instead of reviewing them one by one.
  • Conversion - A goal completion recorded against a visitor session, such as a purchase or signup, that an attribution model assigns credit for. (related: SessionSight: Funnels)

When to use it

  • When you need to see which marketing channels and campaigns are driving conversions for a monitored site or app.
  • When comparing how crediting the first touch versus the last touch changes which channels look effective.
  • When validating a new Channel Grouping configuration by checking whether named channels, not raw UTM strings, appear in the rollup.
  • When narrowing results to a single tenant, a tenant group, or a specific time window to investigate a conversion spike or drop.
  • When the rollup is empty, to confirm whether it is a data issue (no conversions in the window) or a configuration issue (missing Channel Grouping).

Before you begin

  • A tenant with session tracking already active, since Attribution only shows data once real visits and conversions exist for it.
  • A Channel Grouping configuration created for that tenant on the Configuration: SessionSight: SessionSight page, so UTM tags resolve into named channels instead of leaving the rollup unreadable or empty.
  • At least one container (monitored site or app) that has received traffic in the time window you plan to review.
  • A licensed SessionSight module for your account; an unlicensed session loads no tenant, tenant-group, or attribution data on this page (see Infrastructure: Licensing).

Common workflows

Review attribution for a different scope and period

Persona: Load-test operator or analyst comparing channel performance

  1. Select a different tenant, tenant group, or container from the filter dropdowns to change scope.
    • Expect: The dropdowns show your new selections; the rollup below still reflects the previous query until you refresh.
  2. Select a time range chip (for example 24h or 7d), or Custom to pick an exact period.
    • Expect: The chip highlights as active, setting the period the next refresh will use.
  3. Select an attribution model (First touch, Last touch, or Linear).
    • Expect: The selected model button becomes highlighted and will determine how the next refresh credits conversions.
  4. Click Refresh.
    • Expect: The page re-queries the rollup for the chosen tenant, group, container, time range, and model; the body updates to show matching rollup data or, if nothing matches, the No attribution rollup yet message naming the selected model.

Verify: The body content reflects the newly selected model and scope, and the chip and model you chose remain highlighted, confirming the refresh ran against your selections.

Diagnose an empty attribution rollup

Persona: Operator troubleshooting missing attribution data

  1. Open the Attribution page for the tenant and container you expect to have conversions.
    • Expect: The filter bar loads with your tenant, group, and container, and the body shows either rollup data or the No attribution rollup yet message.
  2. Click Configure channel grouping from the header or the empty-state link.
    • Expect: The Channel Grouping configuration for the tenant opens so you can check whether UTM tags are mapped to channels.
  3. Confirm a channel grouping mapping exists, then return to Attribution and click Refresh.
    • Expect: The rollup re-queries; if conversions existed but were only unmapped, named channels now appear instead of the empty state.

Verify: The body shows channel and campaign rows instead of the empty-state panel, confirming the earlier gap was a mapping issue rather than a lack of conversions.

Steps

Step 1

Open the Attribution page under SessionSight.

Expected result: The page loads with the filter bar scoped to your current tenant and container, the Model toggle set to Last touch, and the body showing the No attribution rollup yet message because no rollup matches yet.

This is the starting view before you narrow the scope or change the attribution model to find relevant rollups.

  • The Model toggle opens with Last touch active; U-shaped and Time decay are grayed out and labeled Soon.
  • No time-range chip is highlighted yet, so no preset period is currently applied.
  • The empty-state message links to Configure channel grouping to fix missing channel mappings. SessionSight: Attribution - step 1

Field reference

Field Purpose Format / Validation Required Default
Tenant selector Scopes the attribution rollup to one customer tenant. Switch tenants to review attribution separately for each customer account rather than combined. Dropdown list of tenant names. No The tenant currently in scope elsewhere in the platform.
Tenant group selector Optionally fans the attribution query across every tenant that belongs to a saved group, so you see combined rollups instead of switching tenants one at a time. Leave it on No groups to stay scoped to the single tenant selected above. Dropdown list of tenant groups, or No groups. No No groups
Container selector Narrows the rollup to one monitored site or application. Switch containers to review attribution for a different property without changing the tenant. Dropdown list of containers. No Production Web App
Date range (time-range chips) Sets the period of conversions the rollup includes. Shorter windows (1h, 4h, 8h) surface near-real-time shifts in channel performance; longer windows (24h, 7d) smooth out noise and show trends across more sessions. Choose Custom to set an exact start and end period. Preset chips: 1h, 4h, 8h, 24h, 7d, Custom. No No preset highlighted until you select one.
Model toggle Determines how conversion credit is split across the touchpoints in a visitor's path. First touch credits only the first interaction, useful for measuring which channels create initial awareness. Last touch credits only the final interaction before conversion, useful for measuring which channels close conversions, and is the default. Linear splits credit evenly across every touchpoint, useful for a balanced view of the whole journey. U-shaped and Time decay are additional weighting models that are not available yet. Button group: First touch, Last touch, Linear, U-shaped (disabled), Time decay (disabled). Yes Last touch

Controls reference

Refresh

Re-queries the attribution rollup using the currently selected tenant, tenant group, container, time range, and model.

When to use: After changing any filter, time range chip, or model so the results on screen match your new selections.

Side effects: Reloads the displayed data only; it does not change any saved configuration, tenant data, or Channel Grouping mapping.

Configure channel grouping (header)

Opens the Channel Grouping configuration for the current tenant, where UTM tags are mapped to named channels.

When to use: Before relying on a rollup, or whenever channel names look wrong or missing, to check or fix the mapping.

Side effects: Read-only navigation from this page; any mapping changes happen on the configuration page itself, not here.

Configure channel grouping (empty state)

Opens the same tenant Channel Grouping configuration as the header button, reached from inside the empty-state message.

When to use: When the rollup is empty and you want a direct shortcut from the explanatory message to fix the mapping.

Side effects: Read-only navigation; identical destination to the header button.

Verify the result

When the Attribution page has matching data, the empty-state panel is replaced by channel and campaign rollup data showing conversions and conversion value credited under the selected model, tenant, container, and time range. The Model toggle shows your chosen option as the active button, confirming which crediting logic produced the results. If you still see No attribution rollup yet, first check whether the inline model name in the message matches what you intended to review, then confirm conversions occurred for the selected tenant and container in that window, and finally confirm the Channel Grouping configuration is populated. A successful refresh keeps your filter selections visible while only the body content below them updates.

Troubleshooting

  • Symptom: The page shows No attribution rollup yet even though you expect conversions. Fix: Confirm the selected tenant, container, and time range actually had conversions, then check that a Channel Grouping mapping exists on the Configuration: SessionSight: SessionSight page so UTM tags resolve into channels.
  • Symptom: The U-shaped and Time decay model buttons cannot be selected. Fix: These models are labeled Soon and are not available yet; use First touch, Last touch, or Linear instead.
  • Symptom: The empty-state message still names a model you did not intend to check, shown inline as last_touch. Fix: Reselect the desired model button and click Refresh; the inline model name updates to match the model actually used for the last query.
  • Symptom: The Tenant group selector shows No groups and you cannot fan the query across multiple tenants. Fix: No tenant group has been set up for this account yet; continue reviewing tenants individually using the Tenant selector until one exists.
  • Symptom: Clicking Refresh does not change anything on screen. Fix: Verify you actually changed a filter, time range, or model first, since Refresh re-runs the same query otherwise; also confirm conversions and a Channel Grouping mapping exist for the active scope.
Was this article helpful?
0 out of 0 found this helpful