Every conversation the program books is tagged by channel, date, and the letter that preceded it.

This page explains the operational mechanics of attribution, what "originated" means in practice, and how ROI Wire handles the gray zones where a prospect sits in both your referral pipeline and the correspondence sequence.

Attribution Is a Discipline, Not a Dashboard

Most outbound programs report vanity metrics. Opens, clicks, impressions. These numbers describe activity, not origin. ROI Wire tracks whether a specific engagement, a signed matter, or a placed deal came from the program or from somewhere else.

The difference matters for revenue share engagements, where payment depends on proof. It matters for retainer engagements, where you need to know if the fixed cost is producing outcomes. The method is the same in both cases.

What We Track

Every Email Correspondence sequence carries UTM parameters on all call-to-action links. The parameters identify the campaign, the specific message in the sequence, and the channel. When a prospect clicks and lands on your site, that visit is tagged in your analytics.

Phone follow-up uses tracked numbers. When an ROI Wire operator books a conversation, the operator tags the CRM record at the moment of booking. The tag identifies the program, the vertical, and the date of first contact.

Direct Mail pieces include a dedicated response path: a phone number, a QR code, or a landing page URL unique to that mail drop. Retargeting placements are served to named buyer profiles and sequenced with the correspondence program, so the digital touch is never a standalone event.

The Definition of "Originated"

An engagement is originated by the program if one of two conditions is met.

First, the prospect states during the sales conversation that they found your firm through the correspondence, the mail piece, or the follow-up call. This is self-reported attribution. It is the strongest signal.

Second, first-touch attribution shows a program element as the initial contact before any other recorded touch in your CRM. The email click, the mail response, or the booked call appears before the referral introduction, the conference meeting, or the inbound inquiry.

If both conditions are present, the case is clear. If neither is present, the program does not claim the engagement.

The Monthly Attribution Report

Each month, ROI Wire delivers a report with three sections.

The first section lists all booked conversations that month, with the source tag, the date of first program contact, and the date of the booking. The second section lists all engagements originated by the program, with the date of origin and the revenue share or retainer attribution applied. The third section lists the gray zone: prospects who are in both the correspondence sequence and your referral pipeline, with the current status and the rule applied.

How the Report Is Built

The report draws from your CRM, not from ROI Wire's internal systems. ROI Wire does not maintain a separate shadow database. The operator tags are written directly into your records. The UTM data flows into your analytics platform. The monthly report is a reconciliation of your own data, formatted to show what the program produced.

This means the report is only as accurate as your CRM discipline. If your team does not log referral sources, the gray zone grows. If your team does not update deal stages, the report shows stale status. ROI Wire can advise on lightweight CRM setup, but the obligation to maintain the data is yours.

The Gray Zone and How We Handle It

Every active firm has a referral pipeline. Former clients, accountants, attorneys, industry contacts. These sources do not stop producing because a correspondence program begins. The gray zone is the overlap: a prospect who receives the mail and is also introduced by a referral partner, or who clicks the email and then walks into a conference booth.

The Rule for Overlapping Prospects

If a prospect is in the correspondence sequence and a referral arrives simultaneously or earlier, the referral takes precedence. The program does not claim the engagement.

If the correspondence sequence contacts the prospect first, and the referral arrives later, the program claims the engagement. The first touch determines origin.

If the sequence contacts the prospect, the prospect does not respond, and a referral arrives months later, the program does not claim the engagement. The correspondence did not produce the conversation. The referral did.

This rule is applied consistently, not retroactively adjusted to favor either party. The monthly report documents the rule applied to each case.

Why ROI Wire Does Not Overclaim

Overclaiming destroys trust and makes revenue share unsustainable. A firm that attributes every new engagement to the program will eventually face a client who compares the report to their own records and finds discrepancies. The relationship ends there.

Underclaiming is also a failure. A firm that misses its own contributions trains the client to undervalue the program. The correct position is exact: claim what the program produced, nothing more, nothing less.

This discipline is also why ROI Wire declines engagements where the client cannot or will not maintain CRM records. Without a shared record, attribution becomes an argument. The program is designed to prevent arguments.

Your Role in Closing the Loop

Attribution requires action from your side. Three obligations are non-negotiable.

Log the source. When a prospect mentions the correspondence, the mail piece, or the call, record it in the CRM. When a referral arrives, record that too. The monthly report depends on this discipline.

Update the outcome. When a booked conversation becomes a signed engagement, move the record. When a prospect declines, mark it closed. The report cannot show conversion rates if deals sit in limbo.

Report disputes promptly. If you believe a gray-zone case was misclassified, flag it in the month it appears. ROI Wire reviews the timeline and corrects if warranted. Disputes raised six months later are harder to resolve because the operator notes and the sequence logs may have aged out.

What Attribution Does Not Measure

The report does not claim influence it cannot prove. A prospect who sees the mail piece, does not respond, and later searches your firm name and calls from the website is not attributed to the program unless the UTM chain or the self-reported source confirms it. The program may have contributed, but contribution without proof is not origin.

The report also does not measure brand lift, pipeline velocity, or conversation quality. These may improve because of the program. ROI Wire will discuss them in quarterly reviews. They do not appear in the attribution report because they cannot be tied to specific engagements with the same rigor.

The Mechanics in Practice

For a typical engagement, the sequence runs as follows. The Direct Mail piece lands on a Monday. The Email Correspondence begins Wednesday, referencing the mail piece. Retargeting placements activate for the named profile. Phone follow-up begins the following week, with the operator noting the mail and email in the opening.

If the prospect responds to the email, the UTM captures the click. If the prospect calls the mail number, the tracked line captures the response. If the prospect takes the operator's call and books, the operator tags the CRM. If the prospect does nothing for three months and then a referral arrives, the referral is logged and the program claim is removed.

This is the daily work of attribution. It is not automated inference. It is manual tagging, consistent rules, and monthly reconciliation.

---