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.
Ad platforms report clicks and forms. The CRM reports opportunities. Scheduling reports appointments. Operations reports completed work. Accounting reports revenue. No system connects the full path.
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
Ad platform / form
Emits a lead event with campaign, ad-group, and creative attribution.
The Forge
Preserves the acquisition source on the customer record throughout the operating lifecycle.
The Forge
Connects the lead to appointments, opportunities, and delivered work as they happen — the attribution follows the customer.
Accounting system → The Forge
Invoice status, payments, and refunds return to the operating record with source attribution intact.
The Forge → Ad platform
Sends offline conversion events (deal won, work completed, revenue) back to the ad platform for smarter bidding.
Executive dashboard
Shows revenue by campaign, cost per acquired customer, and lifetime value by acquisition source.
Exceptions
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.
Source of truth
Data domain
Revenue
Authoritative system
Accounting system
Read source
Accounting API
Conflict policy
Accounting is authoritative for revenue amount. The Forge holds the source attribution.
Data domain
Acquisition source
Authoritative system
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
Roles
Industries
Other workflows
Lead to Appointment
A lead arrives from an ad, form, or referral and sits unattended while someone remembers to book them.
Job to Invoice
Completed work sits for days before it is billing-ready. Field notes, photos, change orders, and hours live in different places, and the office assembles the invoice by hand.
Schedule to Payroll
Schedules, time entries, approvals, and job context live in separate systems, so payroll runs without the operational picture behind the hours.