X
min read
·
Updated
Sat Aug 22 2026 00:00:00 GMT+0000 (Coordinated Universal Time)
Published ProfitJam pages automatically keep a first-party trail of how a visitor arrived and what they did next. That trail helps keep a form lead or catalog order connected with the visit that produced it, without extra tracking setup on the page.
When someone lands on a published page, ProfitJam looks for useful source information in the visit:
ProfitJam keeps two touch points in that browser:
Internal page-to-page navigation does not replace the saved source. ProfitJam also uses browser and session identifiers to keep events from the same visit together.
The tracker is added to the live published page, not its editor preview. It records page views, scroll milestones, and meaningful link or button clicks. ProfitJam forms add a form-submission event, and catalog checkout adds a checkout-start event.
When a visitor submits a ProfitJam form, the saved attribution trail is attached to the lead. If the same lead submits again, the original first touch is retained and the later touch is refreshed. A catalog checkout attaches the available trail and originating page to the order.
Open Reports → Overview to see the current reporting view. It combines daily results into period totals, channel totals, a trend, top performers, and source freshness.
Overview is an aggregate results view. It does not currently display the saved first-touch and last-touch fields or turn them into a person-by-person journey. Use it to compare where activity is accumulating; the lead or order remains the record tied to the saved conversion context.
Overview updates daily, so a new page event, lead, or order can take until the next collection and rollup to affect the dashboard.
Use consistent UTM values on links you control. For example, keep one spelling for a source such as LinkedIn and one campaign name across the related links. Consistent tags make the saved arrival context easier to understand later.
Attribution is browser-based and best effort. A different device or browser, cleared storage, browser restrictions, or a blocked request can break the trail, so do not expect every visit to connect perfectly.
No. The ProfitJam tracker is added to the published page, not the editor preview.
It means the earliest qualifying touch saved in that browser. A different browser or device starts a separate trail.
The page captures events during the visit, but Overview reads the daily reporting rollup. Check again after the next daily update.
Support answers in under a business day, and reads your workspace before replying.