What Is a Fusion Relay? TUOCA's Multi-Source Revenue Attribution

A Fusion Relay is TUOCA’s signature feature — a specialized relay pipeline that combines data from two separate sources to create complete, revenue-attributed conversion records. It’s the technology that connects the dots between “which ad click generated this call” and “how much revenue that call produced.”

For The Upload Offline Conversions App (TUOCA), Fusion Relays solve the fundamental problem of service business conversion tracking: the click data and the revenue data live in different systems.

The Problem Fusion Relays Solve

In a typical service business:

System	Has Click ID (GCLID)?	Has Revenue?	Has Phone Number?
CallRail / CTM	✅ Yes	❌ No	✅ Yes
ServiceTitan / Jobber	❌ No	✅ Yes	✅ Yes
Google Ads	Needs both	Needs both	—

No single system has both pieces of data. Call tracking knows which ad click triggered the call. The CRM/FSM knows how much revenue the resulting job generated. Google Ads needs both to optimize for revenue.

How Fusion Relays Work

The Matching Process

Source A: CallRail
┌──────────────────────────────────────────────┐
│ Phone: (555) 123-4567                        │
│ GCLID: EAIaIQobChMI8dml_ePi9gIV...          │
│ Call Date: 2026-04-01                        │
│ Revenue: ???                                 │
└──────────────────────────────────────────────┘

Source B: ServiceTitan
┌──────────────────────────────────────────────┐
│ Phone: (555) 123-4567                        │
│ GCLID: ???                                   │
│ Job Completed: 2026-04-10                    │
│ Revenue: $4,500                              │
└──────────────────────────────────────────────┘

Fusion Result → Google Ads
┌──────────────────────────────────────────────┐
│ GCLID: EAIaIQobChMI8dml_ePi9gIV...          │
│ Conversion Name: Booked Job                  │
│ Conversion Time: 2026-04-10 14:30:00         │
│ Conversion Value: $4,500                     │
│ + Hashed Phone: d4f5c3b1e72a... (backup)     │
└──────────────────────────────────────────────┘

The Fusion Relay matches on phone number — the one field that exists in both systems. The result: a complete conversion record with the GCLID (for click attribution) and the revenue (for Value-Based Bidding).

The Pipeline Stages

1. Fetch from Source A — Pull recent call records (with GCLIDs) from call tracking
2. Fetch from Source B — Pull recent job/sale records (with revenue) from CRM/FSM
3. Normalize phone numbers — Both sources may format phones differently: (555) 123-4567 vs 5551234567
4. Match on shared identifier — Find records where the phone number matches
5. Merge fields — Combine GCLID from Source A + revenue from Source B
6. Handle unmatched records — Upload with Enhanced Conversions (hashed PII) if no GCLID match
7. Deduplicate — Prevent re-uploading previously sent conversions
8. Upload — Send to Google Ads, Meta, Microsoft, or TikTok
9. Log — Record outcomes for every record

Fusion Relay Match Scenarios

Scenario	Source A (Call Tracking)	Source B (CRM)	Result
Full match	✅ Phone + GCLID	✅ Phone + Revenue	GCLID + Revenue uploaded (best case)
Call only	✅ Phone + GCLID	❌ No matching job	GCLID + $0 value (or skip)
CRM only	❌ No matching call	✅ Phone + Revenue	Hashed phone + Revenue (ECL fallback)
Organic lead	❌ No call tracked	✅ Phone + Revenue	Hashed phone + Revenue (no GCLID)

Why This Matters for Smart Bidding

Without Fusion Relays, you have two options — both bad:

Option 1: Upload Calls Only (Standard Relay from CallRail)

Google Ads receives: "GCLID: EAI... → Conversion (no value)"
Smart Bidding signal: "This click generated a call"
Result: Google optimizes for call volume, not revenue

Option 2: Upload CRM Data Only (No GCLID)

Google Ads receives: "Hashed phone → $4,500 conversion"
Smart Bidding signal: "Someone with this phone generated revenue" (weaker match)
Result: Lower match rates, modeled attribution

Option 3: Fusion Relay (Best of Both)

Google Ads receives: "GCLID: EAI... → $4,500 conversion + hashed phone"
Smart Bidding signal: "THIS SPECIFIC CLICK generated $4,500 in revenue"
Result: Google optimizes for high-revenue clicks with deterministic attribution

Real-World Example

An HVAC agency manages 20 clients, each with CallRail (call tracking) and ServiceTitan (field service management):

Per-Client Fusion Relay Setup

CallRail (Client A) ──┐
                       ├──▶ Fusion Relay ──▶ Google Ads (Client A)
ServiceTitan (Client A)┘

CallRail (Client B) ──┐
                       ├──▶ Fusion Relay ──▶ Google Ads (Client B)
ServiceTitan (Client B)┘

Monthly Results (Per Client)

Metric	Calls-Only Relay	Fusion Relay
Conversions uploaded	85 calls	42 booked jobs
Revenue data	$0	$147,000
Smart Bidding data	“85 conversions”	“$147,000 from 42 jobs”
Bidding strategy available	Target CPA only	Target ROAS, Maximize Conv. Value
Match quality	Click-level	Click-level + revenue

Supported Source Combinations

Source A (Click ID)	Source B (Revenue)	Match Field
CallRail	ServiceTitan	Phone number
CallRail	Jobber	Phone number
CallRail	HubSpot	Phone number or email
CallTrackingMetrics	ServiceTitan	Phone number
CallTrackingMetrics	Jobber	Phone number
Webhooks (any)	Webhooks (any)	Configurable field

Availability

Fusion Relays are available on:

Tier	Fusion Relays
Free	❌
Solo	❌
Pro	✅ (up to 5)
Agency	✅ (unlimited)

Getting Started

1. Connect Source A — Authenticate your call tracking tool (CallRail, CTM)
2. Connect Source B — Authenticate your CRM/FSM (ServiceTitan, Jobber, HubSpot)
3. Configure the Fusion — Select the match field (phone number), map revenue field
4. Set your destination — Google Ads, Meta, Microsoft, or TikTok
5. Activate — The Fusion Relay runs on schedule, matching and uploading automatically

See the Fusion Relays product page for the full walkthrough.