Type of information
Revenue
System that keeps the official record
Accounting system
Read source
Accounting API
Conflict policy
Accounting keeps the official record for the revenue amount. The Forge holds the source attribution.
Marketing Campaign to Revenue
A campaign generated inquiries. The next question is who followed up and what happened afterward. Review the supported record connections below before treating a campaign click as revenue.Illustrative workflow to assess, not a ready-made connection. Confirm each supported action, plan and setup before use. The QuickBooks Pro import reads customers and invoices and does not write back.
Trigger
A campaign impression, click, or form submission attributed to a source.
Participating systems
Ad platforms · Website forms and landing pages · The Forge · CRM (if retained) · Calendar / scheduling · Accounting system
Steps
What happens at each handoff
Ad platform / form
The Forge
The Forge
Accounting system → The Forge
The Forge → Ad platform
Executive dashboard
- A customer converts outside the platform's attribution window. — The Forge stores the attribution locally so revenue-per-source is accurate even when the ad platform can't accept the conversion.
- A form submission has no campaign metadata. — The customer is preserved with source = organic / direct rather than dropped; downstream reporting distinguishes attributed from non-attributed revenue.
Source of truth
Which system keeps the official record
Type of information
Acquisition source
System that keeps the official record
The Forge
Read source
Form / ad-platform lead event
Write destination
Ad platform (offline conversion)
Conflict policy
First attributable source wins; downstream touches are supporting.
Metrics unlocked
- Revenue by campaign and creative
- Cost per acquired customer
- Time from click to revenue
- Lifetime value by acquisition source
Roles
- Sales and marketing leader
- Owner / executive
- Finance and accounting
Industries
- Home services
- Dental
- Insurance
- Schools
- Professional services
Exceptions
When things go wrong
When
A customer converts outside the platform's attribution window.
Then
The Forge stores the attribution locally so revenue-per-source is accurate even when the ad platform can't accept the conversion.
When
A form submission has no campaign metadata.
Then
The customer is preserved with source = organic / direct rather than dropped; downstream reporting distinguishes attributed from non-attributed revenue.
When
The ad platform's offline-conversion write fails.
Then
The event is queued and retried; the internal revenue-by-source report is not delayed by the ad platform's availability.
Other workflows
Lead to Appointment
A customer asks for an appointment, but their request waits between the form, the office and the schedule. Give the handoff a clear owner before the customer has to ask again.
Job to Invoice
The job is complete, but billing still needs the hours, materials and approved changes. Keep those details with the work so the office can review the invoice handoff.
Schedule to Payroll
The week’s shifts and the hours actually worked do not always match. Bring the exceptions into review before payroll preparation becomes a last-minute reconciliation.