Paid-media funnel analytics - archived source
94 nodes · 90 non-note nodes
Open read-only HTML explorer →Download explicitly sanitized review JSON
Revenue and acquisition
Paid-media and funnel reporting: Bring advertising and funnel performance into the same decision.
Paid-media and funnel reporting connects Meta, Google and funnel context across collection, attribution, compilation and reporting. The system carries account and journey configuration into reviewable performance analysis, giving operators and creative teams a shared basis for deciding what to investigate next.
About this view
Local import only
94-node archived workflow imported locally. Inactive; original per-node flags retained, credentials removed.
About this view
Local import only
Native local source detail, not a live campaign or an entire-platform execution receipt.
1 / 2
What it does
- Business and funnel configuration linking accounts, page order and journey stages.
- Paid-media and event collection with attribution and funnel analytics compilation.
- Reporting and creative handoffs carrying analysis into requested draft material.
Why it matters
Gives media and creative teams a connected view of the inputs behind funnel diagnosis and the next review decision.
- Meta, Google and funnel performance in the documented system
- 3 reporting contextsSource scope. This view is backend evidence, not a newly recovered populated frontend or measured return on ad spend.
Under the hood
Technology stack
n8n
Airtable
Google Docs
Google Analytics
Google Ads- JavaScript
- OpenAI
Anthropic- Meta
Build note
Meta, Google and funnel data. One reporting loop.Source & context
Based on historical operating documentation and archived implementation evidence. Current end-to-end execution and business results were not independently retested.
Native n8n imports are local and inactive, not production execution. Historical recording capture dates are unknown; a displayed report period is not its capture date. Local source review: October 27, 2026. Public release and client-material clearance remain separate.
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.
Inside the system
- Business and funnel configuration Defines accounts, page order and journey stages.
- Paid-media and event collection Connects advertising and funnel evidence to the business.
- Diagnosis and reporting Creates reviewable performance and creative context.
- Custom advertising copy Produces requested draft material inside the full operating system.
The handoff
- Business and funnel configuration
- Meta, Google and page-journey reporting
- Creative diagnosis and linked documents
- Context-aware copy requests
Technology stack
Workflow source and integrations
- n8n
- Airtable
- Google Docs
- Google Analytics
- Google Ads
- JavaScript
- OpenAI
- Anthropic
- Meta
Recovered compilation source and documented paid-media inputs.
Not established
- Production hosting is not established.
Source & context
| View | Provenance and limitation | Evidence class |
|---|---|---|
| Fig. 1 | Original paid-media funnel compilation source 94-node archived workflow imported locally. Inactive; original per-node flags retained, credentials removed. | Local import only |
| Fig. 2 | Funnel analytics and reporting branch Native local source detail, not a live campaign or an entire-platform execution receipt. | Local import only |
Based on historical operating documentation and archived implementation evidence. Current end-to-end execution and business results were not independently retested.
Native n8n imports are local and inactive, not production execution. Historical recording capture dates are unknown; a displayed report period is not its capture date. Local source review: October 27, 2026. Public release and client-material clearance remain separate.
Reviewed: 2026-10-27
Map your version of this system
Bring the workflow your team is struggling to complete. We can map the inputs, integrations, review decisions and usable outputs before defining implementation scope.