Changelog
- January 12, 2026
Purchase Attribution Analytics
Purchase Attribution Analytics helps you understand the complete customer journey from first interaction to final purchase.
Instead of relying only on the last click, this report connects sessions that occurred before checkout and shows how traffic sources appeared across multiple visits leading up to an order.
What This Report Shows
For each order, Analyzify captures the full sequence of sessions associated with that purchase and presents it as a single journey.
This includes:
- The first recorded marketing session linked to the customer
- All subsequent sessions before the order was placed
- The final session where the purchase occurred
- A chronological timeline with timestamps and source details for each visit
Using this same underlying session history, you can view the data through different attribution models:
- First Click assigns the order to the earliest recorded marketing session
- Last Non-Direct Click (default) assigns the order to the last marketing session, excluding direct traffic
- Last Click assigns the order to the final session, including direct
- Any Click shows all sessions involved, with each channel listed separately
Changing the attribution model does not change the captured journey. It only changes how credit is summarized based on the same session data.
Where You Can See the Data
Attribution data is available in two places:
- Analyzify dashboards, where you can review orders, campaign-level summaries, and full session timelines
- Shopify order notes, where journey details can optionally be written for direct access when viewing orders in the Shopify admin
Purchase Attribution Analytics helps you:
- See how many sessions typically occur before an order is placed
- Identify which channels appear earlier or later in the purchase journey
- Compare different attribution views using the same underlying data
- Review complete order-level timelines instead of isolated attribution fields
This provides a clearer representation of how orders form across sessions and channels, rather than relying on a single touchpoint.


