Conversions in Real Time. Not on a Schedule.
When your CRM sends a qualified lead or completed-job event, TUOCA can trigger its conversion relay. Connect the event to your upload workflow and reduce the wait for the next scheduled batch.
Available on: Pro, Agency tiers
Scheduled Batches Mean Delayed Intelligence
Every hour your conversion data sits unprocessed is an hour Google Ads optimizes on stale signals. For fast-moving campaigns, that delay costs real money.
Hourly Batches = Hourly Blind Spots
A lead comes in at 9:05 AM. Your relay doesn't run until 10:00 AM. For 55 minutes, Google Ads has no idea that click converted — and it's making bidding decisions without that data.
Emergency Services Can't Wait
Legal firms, plumbers, and emergency HVAC services need real-time lead processing. A customer calling for a burst pipe at 2 AM won't wait for your 6 AM scheduled batch.
Disconnected Workflows
Your CRM records the outcome, but getting it to an ad platform still takes a separate export. A webhook gives that event a direct route into your conversion workflow.
Four Steps. Zero Delay.
From incoming event to uploaded conversion — here's the real-time path.
Unique Webhook URL
TUOCA generates a unique endpoint URL for each client. Copy it into your CRM, form builder, or any system that supports webhook callbacks.
Event Received
Your CRM POSTs to the URL when a lead arrives — new call, form submission, booked appointment. TUOCA stores the event and triggers processing.
Relay Fires Instantly
No waiting for the next batch. TUOCA runs the full relay pipeline — filter, deduplicate, transform, upload — the moment the event arrives.
Conversion Uploaded
The conversion appears in Google Ads, Meta, or Microsoft Ads within each platform's processing window. Every record logged with success/failure status.
From CRM Event to Conversion Upload
Connect incoming events to a relay, apply your rules, and review the upload outcome.
Map Your Fields
Map incoming field names to the data your conversion needs, such as its identifier, timestamp and value.
Apply Your Rules
Use relay filters to select the events that represent a meaningful conversion before uploading them.
Review Execution History
Check relay runs and their upload outcomes so you can investigate failures and keep your conversion workflow moving.
Legal Firm: Real-Time Lead Qualification
The scenario: A personal injury law firm runs Google Ads campaigns targeting high-intent queries — "car accident lawyer near me," "slip and fall attorney." Every qualifying call is worth $3,000–$25,000 in potential case value. The firm uses CallTrackingMetrics to track inbound calls.
The problem with batches: Running relays hourly means a lead that calls at 9:15 AM doesn't show up in Google Ads until the 10:00 AM batch. During that 45-minute window, Google's Smart Bidding doesn't know that keyword just produced a high-value conversion — and it might underbid on the next identical search.
With real-time webhooks:
- 9:15:03 AM — Potential client calls from a Google Ad. CTM captures the GCLID and call data.
- 9:15:05 AM — CTM's webhook fires to TUOCA with the call details — duration, caller ID, tag, GCLID.
- 9:15:06 AM — TUOCA applies filters (call duration > 120s, tag = "Qualified Lead"), deduplicates, transforms, and uploads to Google Ads.
- 9:15:08 AM — Conversion is in Google's processing queue. Smart Bidding has the signal for the next auction.
The result: Google Ads receives conversion data in seconds, not hours. Over 90 days, the firm's tROAS strategy improved by 34% because Smart Bidding could react to high-value conversions within the same bidding cycle — not the next day's.
Webhook Questions
Incoming events trigger connected relays without waiting for the next scheduled run. TUOCA briefly batches events arriving together before processing them. Upload timing also depends on connection health, platform limits and processing; an accepted upload may take longer to appear in ad reports.
Yes — and many agencies do exactly this. Use webhooks for time-sensitive conversions (new lead qualification, emergency service calls) and scheduled relays for batch processing (daily revenue imports from your CRM). Both relay types share the same filter rules, deduplication, and activity logs.
TUOCA's hash-based deduplication catches duplicates regardless of how they arrive. If the same conversion was already uploaded (via a previous webhook, scheduled relay, or manual upload), it will be detected and skipped. Every duplicate is logged in your activity history for transparency.
Keep an event history in your source system if you need to resend data later. TUOCA processes incoming webhook events through your relay; it is not a long-term archive of your original payloads. Check the relay execution history to review upload outcomes.
Real-time webhooks are available on the Pro and Agency tiers. The Solo tier uses scheduled relays only. If you need real-time processing for even one client, the Pro tier is the right starting point — it includes up to 10 relays and 3 clients.