Owner: Paul
We need a definitive, written map of how money actually moves through our systems before we wire SegMetrics to any of it. Current understanding is assembled from conversation, not verified against the configs.
Questions to answer
GHL invoices — confirm the Authorize.net gateway is connected under Payments → Integrations, and that invoices/order forms route through it. Are there other gateways connected (Stripe, etc.) and if so, what is the default for order forms vs. invoices? Lovable funnels — confirm exactly how the Authorize.net integration is built (Accept.js? direct API? embedded GHL order form?). Confirm it creates no invoice or order record in GHL, only a contact update. If it does create anything in GHL, that changes the whole routing plan. TicketSpice — confirm which gateway the Bootcamp page and the account default run on. Check per-form payment settings, not just the account default — TicketSpice allows per-page processor assignment. Tell: custom third-party processors carry an extra 1% fee on the TicketSpice invoice; Webconnex Payments (in-house) does not. Does anything push TicketSpice orders into GHL as invoices or orders? If yes, we have a double-count risk the moment we turn on the GHL orders import. Manual / off-platform transactions — where are manual Authorize.net invoices actually created: through GHL's invoicing, or directly in the Authorize.net merchant portal? Same question for Facebook payments and Unique Genius. Revenue share — roughly what percentage of company revenue flows through each of: GHL invoices, Lovable funnels, TicketSpice, manual/off-platform. Rough is fine; we need order of magnitude to prioritize build effort.
Why this is the gating subtask
Every other subtask depends on the answer. Q2 in particular determines whether Lovable revenue is currently invisible to every reporting system we have — including the manual scorecard.
Constraint
Read-only investigation. Do not modify any live GHL workflows or Bootcamp intake before Aug 24.
Due 2026-08-04