Forms and Attribution Now Work Together More Cleanly
Forms and attribution workflows are now positioned as related surfaces inside SGEN. Submissions and source context sit in the same platform pass, so your team reviews lead data with the context it needs — without crossing between disconnected tools.
What changed
In a plugin tower, forms ship from one plugin and attribution from another. The gap shows up as submissions with no source context — you know someone filled out the form, but not where they came from. SGEN's scoped component system has always kept forms and attribution conflict-free in a single platform, but the two surfaces were not clearly presented as a pair. That positioning is now explicit.
Forms handling is no longer treated as a disconnected feature. It is part of a broader reporting and attribution layer. Submissions and their source context can be reviewed together, giving teams a cleaner operational story for lead capture.
Where it fits
This improvement touches two SG-Module surfaces that platform users already work in.
The Forms surface now surfaces source attribution alongside each submission. Your Store's team, for example, can see whether a contact came in through the homepage enquiry form or a campaign landing page — without leaving the Forms admin.
Attribution reporting is aligned with form submission data. Source context — where a visitor came from before filling out a form — is part of the same platform layer, not a separate tool requiring its own import or sync.
Why it matters
Lead capture only tells half the story if source context is missing. Teams that rely on submissions to qualify leads need to know where those leads came from — not as a bonus, but as part of the operational workflow. Aligning the two surfaces removes the friction of cross-referencing data from separate tools or plugins.
Because forms and attribution live in the same scoped component system, there is no sync delay, no import step, and no plugin conflict to manage.
Submissions and source context are reviewed in the same place. The team does not need to cross between tools to answer "where did this lead come from?"
