Why Activity Is Missing from a Contact Detail Page

If a contact's detail page in Sparkforge is missing expected activity, attribution failed at form submission. Sparkforge stores a session ID in the visitor's browser local storage and attaches it to the contact record on submit. When that session ID can't be read, the activity isn't tied to the contact.

Most common causes

Safari / iOS cookie blocking

If the visitor uses Safari with the Block All Cookies setting enabled, Sparkforge cannot store or read the session ID. See Apple's documentation on Safari privacy settings for the user-side detail.

The URL contained ?notrack=true

Any URL with the notrack=true query parameter is intentionally excluded from tracking. Example:

https://example.com/?notrack=true

If you're sending traffic from your own campaigns, make sure that parameter isn't being appended.

Local storage disabled or inaccessible

Sparkforge stores the user's activity and session ID in browser local storage. If local storage is disabled, blocked, or unreachable (private browsing in some browsers, locked-down kiosk modes, embedded webviews), session data can't be saved or retrieved.

What gets recorded vs. attributed

Activity is still being captured at the system level — it just can't be linked back to a specific contact when the session ID is unavailable. The form submission itself still creates the contact; only the pre-submit browsing activity goes unattributed.