Matching engine

Match every lead to the revenue path buyers actually trust.

See how SIRJ connects ad spend, calls, forms, deals, jobs, invoices, and payments into one source-backed revenue path.

Buyer questions

Answer the matching question before the client review.

Lead-to-revenue matching is where vague attribution either becomes credible or falls apart. These answers make the product path explicit before a buyer trusts a campaign number.

Public answer

What is lead-to-revenue matching?

Lead-to-revenue matching is the chain that connects demand events to downstream business outcomes: spend to lead, lead to deal or job, and deal to payment. SIRJ stores those links as scoped attribution matches instead of relying on a blended channel summary.

A buyer can ask where a revenue number came from and see whether it was backed by a campaign match, a source-time match, an operational identifier, contact evidence, or lower-confidence context.

Inspect related proof

Public answer

How does SIRJ keep client revenue from mixing across accounts?

Every event and attribution match carries account and client scope. The runtime asserts that source and target records share the same tenant scope before a match can be created or persisted.

Agency reporting can roll up portfolio attention without letting one client's payment make another client's campaign look successful.

Inspect related proof

Public answer

What happens when the payment arrives after the job or deal?

SIRJ can count a matched deal as attributed revenue while payment evidence is not yet present. When a matched payment arrives, payment revenue replaces the deal amount so the same opportunity is not counted twice.

The report can show revenue progress without turning an open deal and a collected payment into duplicate revenue.

Inspect related proof

Public answer

What if some leads cannot be matched?

Unmatched leads can receive statistical source context from the matched source mix, but that context stays low confidence and separate from deterministic lead, deal, payment, revenue, and ROAS counts.

SIRJ can explain possible source mix without pretending uncertain leads are invoice-backed proof.

Inspect related proof

Match path

One scoped graph connects demand to revenue.

The path starts with spend and leads, moves through operational work, reaches invoices or payments, then feeds only supported outcomes into dashboards, Ask Data, reports, and exports.

Spend source Lead event Deal or job Invoice or payment Report output

Match stages

What each source contributes to the revenue path.

Each stage has a different job. The page separates demand evidence, lead capture, operational work, collected revenue, and the final surfaces buyers use to review the result.

Stage	Source records	Product surface
Spend source	Campaign spend, campaign name, UTM source, UTM campaign, provider identity, and event date.	Ad-source connector pages show the imported spend objects and dashboard cards that can start the revenue path.
Lead event	Calls, forms, messages, contacts, or bookings that become typed lead events inside the client workspace.	Call, form, and messaging connector pages show the lead objects that can be matched to spend or later operational outcomes.
Deal or job	CRM opportunities, jobs, appointments, bookings, or operational records with contact, customer, deal, job, or appointment identifiers.	CRM and operations connector pages explain how downstream work records become the middle of the revenue proof chain.
Invoice or payment	Invoices, charges, payments, collected amounts, payment ids, invoice ids, and customer identifiers.	Payments and books connector pages explain which collected revenue records can replace open deal value in attributed revenue.
Report output	Attribution matches, confidence, dashboard metrics, cited Ask Data rows, report snapshots, and export history.	Dashboards, Ask Data, weekly insights, and reports show the result only when the source path can support the claim.

Graph rules

The matching engine has to earn every edge.

These rules keep the graph from becoming a sales story. Credit depends on window, scope, identifiers, time order, payment precedence, and whether modeled context is being kept separate.

Rule	Evidence	Buyer value
Spend can credit a lead only inside the attribution window	The default window is seven days, spend after the lead is excluded, and stale spend falls out before campaign or source matching is considered.	Campaigns cannot keep taking credit forever, which makes client budget conversations easier to defend.
Campaign evidence outranks source-only timing	A shared UTM campaign receives stronger confidence than a source-and-time match when both are available.	The buyer can tell the difference between exact campaign proof and broader source context.
Operational identifiers beat contact-only evidence	Shared contact, customer, deal, job, appointment, invoice, or payment identifiers receive stronger confidence than email or phone fallback matches.	The strongest revenue path uses the business objects operators already trust, not a vague channel label.
Matches move forward through time	Lead-to-deal and deal-to-payment candidates must occur after the source event before a downstream match can be selected.	The chain explains a real customer journey instead of backfilling revenue into a convenient campaign story.
Payment revenue replaces open deal value	When a matched deal has a matched payment, the summary counts payment revenue and excludes that deal from open attributed deal revenue.	Reports avoid double counting while still showing progress before every payment has arrived.
Modeled context stays separate from source-backed proof	Statistical lead allocations use low confidence and do not change deterministic lead, deal, payment, revenue, or ROAS counts.	A buyer can discuss likely source mix without confusing modeled context with invoice-backed results.

Workflow

From provider event to report-ready proof.

The workflow shows how matching stays constrained before numbers reach the surfaces a client, operator, or agency owner will inspect.

Step	System role	User-visible proof
Ingest typed events	Connectors convert provider payloads into typed spend, lead, deal, payment, and communication events with account, client, provider, date, and source context.	Integration pages show imported objects and source fields before those records become dashboard or report inputs.
Assert tenant scope	The matching engine checks account and client scope across every candidate event before it creates or stores an attribution relationship.	Client workspace and security pages explain why one client's data cannot support another client's revenue claim.
Build the match graph	SIRJ builds spend-to-lead, lead-to-deal, and deal-to-payment links with method and confidence so every downstream claim has an explicit edge.	The attribution methodology page shows the evidence ladder behind campaign, source, id, email, phone, and statistical relationships.
Summarize supported revenue	Attributed leads, deals, payments, spend, revenue, and ROAS are computed from the graph, with payment revenue taking precedence over open deal value.	Metric definitions explain which source records unlock each number and what stays absent when evidence is missing.
Send proof into product surfaces	Dashboards, Ask Data, weekly insights, report snapshots, and exports consume supported match results while unsupported questions remain refused or flagged.	Reports and Ask Data pages show cited answers, chart rows, frozen snapshots, and export paths instead of unsupported certainty.

Proof standards

The safeguards that keep match results believable.

Lead-to-revenue matching needs restraint as much as coverage. These standards protect the buyer from incomplete sources, mixed scope, hidden confidence, and overconfident outputs.

StandardSource completeness

A lead-to-revenue path can look complete while a required source, such as payments or operations, is missing from the client workspace.

SIRJ keeps unavailable numbers absent, null, flagged, or routed to setup guidance until the connected source path supports the claim.

StandardScope isolation

Portfolio reporting loses trust immediately if a campaign from one client can borrow revenue from another client.

Attribution events and persisted matches must pass account and client scope checks before they can affect a dashboard or report.

StandardConfidence visibility

A report that hides match method makes source-only context feel as strong as a shared job, invoice, or payment identifier.

Attribution match records persist method and confidence so downstream pages can distinguish exact, fallback, and modeled evidence.

StandardOutput restraint

AI answers, dashboards, or exports can overstate performance if modeled leads are blended into deterministic revenue.

Statistical allocation remains low confidence and separate, while Ask Data and disclosures explain unsupported states before the buyer relies on them.

FAQ

Questions buyers ask when the revenue path gets challenged.

The page gives sales, search, and answer engines the short version, then routes deeper questions to methodology, integrations, and proof surfaces.

FAQ

Is lead-to-revenue matching the same as last-click attribution?

No. Last-click attribution usually stops at the demand source. SIRJ follows the downstream path into deals, jobs, invoices, and payments, then keeps match method and confidence visible.

FAQ

Can matching work with calls and service jobs?

Yes. Call-heavy workflows can use phone, contact, customer, job, appointment, invoice, and payment identifiers when those records are available in the connected stack.

FAQ

What does a buyer see when the match path is incomplete?

The product should show the supported surface, flag or withhold unsupported numbers, and route the buyer to the source or setup page that explains the missing evidence.

FAQ

Where does the matching result appear?

Matching results appear in dashboards, metric definitions, Ask Data answers, weekly insights, report snapshots, sample reports, exports, and data-lineage proof paths.

Ready when the numbers need to hold up

Now inspect the exact attribution rules.

Use the methodology page to see windows, confidence levels, identifier matching, payment precedence, and statistical boundaries in more detail.

Open methodology See data routing

What is lead-to-revenue matching?

A buyer can ask where a revenue number came from and see whether it was backed by a campaign match, a source-time match, an operational identifier, contact evidence, or lower-confidence context.

Inspect related proof

How does SIRJ keep client revenue from mixing across accounts?

Every event and attribution match carries account and client scope. The runtime asserts that source and target records share the same tenant scope before a match can be created or persisted.

Agency reporting can roll up portfolio attention without letting one client's payment make another client's campaign look successful.

Inspect related proof

What happens when the payment arrives after the job or deal?

The report can show revenue progress without turning an open deal and a collected payment into duplicate revenue.

Inspect related proof

What if some leads cannot be matched?

SIRJ can explain possible source mix without pretending uncertain leads are invoice-backed proof.

Inspect related proof

Stage

Source records

Product surface

Spend source

Campaign spend, campaign name, UTM source, UTM campaign, provider identity, and event date.

Ad-source connector pages show the imported spend objects and dashboard cards that can start the revenue path.

Lead event

Calls, forms, messages, contacts, or bookings that become typed lead events inside the client workspace.

Call, form, and messaging connector pages show the lead objects that can be matched to spend or later operational outcomes.

Deal or job

CRM opportunities, jobs, appointments, bookings, or operational records with contact, customer, deal, job, or appointment identifiers.

CRM and operations connector pages explain how downstream work records become the middle of the revenue proof chain.

Invoice or payment

Invoices, charges, payments, collected amounts, payment ids, invoice ids, and customer identifiers.

Payments and books connector pages explain which collected revenue records can replace open deal value in attributed revenue.

Report output

Attribution matches, confidence, dashboard metrics, cited Ask Data rows, report snapshots, and export history.

Dashboards, Ask Data, weekly insights, and reports show the result only when the source path can support the claim.

Rule

Evidence

Buyer value

Spend can credit a lead only inside the attribution window

The default window is seven days, spend after the lead is excluded, and stale spend falls out before campaign or source matching is considered.

Campaigns cannot keep taking credit forever, which makes client budget conversations easier to defend.

Campaign evidence outranks source-only timing

A shared UTM campaign receives stronger confidence than a source-and-time match when both are available.

The buyer can tell the difference between exact campaign proof and broader source context.

Operational identifiers beat contact-only evidence

Shared contact, customer, deal, job, appointment, invoice, or payment identifiers receive stronger confidence than email or phone fallback matches.

The strongest revenue path uses the business objects operators already trust, not a vague channel label.

Matches move forward through time

Lead-to-deal and deal-to-payment candidates must occur after the source event before a downstream match can be selected.

The chain explains a real customer journey instead of backfilling revenue into a convenient campaign story.

Payment revenue replaces open deal value

When a matched deal has a matched payment, the summary counts payment revenue and excludes that deal from open attributed deal revenue.

Reports avoid double counting while still showing progress before every payment has arrived.

Modeled context stays separate from source-backed proof

Statistical lead allocations use low confidence and do not change deterministic lead, deal, payment, revenue, or ROAS counts.

A buyer can discuss likely source mix without confusing modeled context with invoice-backed results.

Step

System role

User-visible proof

Ingest typed events

Connectors convert provider payloads into typed spend, lead, deal, payment, and communication events with account, client, provider, date, and source context.

Integration pages show imported objects and source fields before those records become dashboard or report inputs.

Assert tenant scope

The matching engine checks account and client scope across every candidate event before it creates or stores an attribution relationship.

Client workspace and security pages explain why one client's data cannot support another client's revenue claim.

Build the match graph

SIRJ builds spend-to-lead, lead-to-deal, and deal-to-payment links with method and confidence so every downstream claim has an explicit edge.

The attribution methodology page shows the evidence ladder behind campaign, source, id, email, phone, and statistical relationships.

Summarize supported revenue

Attributed leads, deals, payments, spend, revenue, and ROAS are computed from the graph, with payment revenue taking precedence over open deal value.

Metric definitions explain which source records unlock each number and what stays absent when evidence is missing.

Send proof into product surfaces

Dashboards, Ask Data, weekly insights, report snapshots, and exports consume supported match results while unsupported questions remain refused or flagged.

Reports and Ask Data pages show cited answers, chart rows, frozen snapshots, and export paths instead of unsupported certainty.

Match every lead to the revenue path buyers actually trust.

Answer the matching question before the client review.

What is lead-to-revenue matching?

How does SIRJ keep client revenue from mixing across accounts?

What happens when the payment arrives after the job or deal?

What if some leads cannot be matched?

One scoped graph connects demand to revenue.

What each source contributes to the revenue path.

The matching engine has to earn every edge.

From provider event to report-ready proof.

The safeguards that keep match results believable.

A lead-to-revenue path can look complete while a required source, such as payments or operations, is missing from the client workspace.

Portfolio reporting loses trust immediately if a campaign from one client can borrow revenue from another client.

A report that hides match method makes source-only context feel as strong as a shared job, invoice, or payment identifier.

AI answers, dashboards, or exports can overstate performance if modeled leads are blended into deterministic revenue.

Questions buyers ask when the revenue path gets challenged.

Is lead-to-revenue matching the same as last-click attribution?

Can matching work with calls and service jobs?

What does a buyer see when the match path is incomplete?

Where does the matching result appear?

Now inspect the exact attribution rules.

Preparing the source route.

Match every lead to the revenue path buyers actually trust.

Answer the matching question before the client review.

What is lead-to-revenue matching?

How does SIRJ keep client revenue from mixing across accounts?

What happens when the payment arrives after the job or deal?

What if some leads cannot be matched?

One scoped graph connects demand to revenue.

What each source contributes to the revenue path.

The matching engine has to earn every edge.

From provider event to report-ready proof.

The safeguards that keep match results believable.

A lead-to-revenue path can look complete while a required source, such as payments or operations, is missing from the client workspace.

Portfolio reporting loses trust immediately if a campaign from one client can borrow revenue from another client.

A report that hides match method makes source-only context feel as strong as a shared job, invoice, or payment identifier.

AI answers, dashboards, or exports can overstate performance if modeled leads are blended into deterministic revenue.

Questions buyers ask when the revenue path gets challenged.

Is lead-to-revenue matching the same as last-click attribution?

Can matching work with calls and service jobs?

What does a buyer see when the match path is incomplete?

Where does the matching result appear?

Now inspect the exact attribution rules.