The source system brings paid-media and funnel context into shared attribution, reporting and creative handoffs across the client workspace.
3 reporting contexts; Meta, Google and funnel performance in the documented system. Source scope. This view is backend evidence, not a newly recovered populated frontend or measured return on ad spend.
Start with the source workflows
The original archive includes advertising attribution, funnel analytics, weekly reports and creative-strategy components. The recovered view focuses on the ninety-four-node funnel analytics compilation and report source.
Do not confuse a shared trigger with the whole platform
A trigger dispatcher is one layer. The case also identifies the collection, attribution, compilation and next-review responsibilities rather than presenting a seventeen-node dispatcher as the entire system.
Keep the next decision visible
The reporting layer is meant to supply a reviewable next action for the operator and creative team. The source captures establish structure, not current provider authorization, campaign health or causal revenue improvement.
Supporting views
About this view
94-node archived workflow imported locally. Inactive; original per-node flags retained, credentials removed.
About this view
Native local source detail, not a live campaign or an entire-platform execution receipt.