Every Record. Every Outcome. Full Transparency.
When a client asks 'are you sure my conversions are uploading?' — you have the receipts. Every relay run, every record, every success and failure logged with timestamps, error messages, and platform responses.
Available on: All paid tiers
Conversion Uploads Are a Black Box
Most tools process your data and return a generic "success" — but what actually happened inside? When conversions go missing, you're left guessing.
"Did My Upload Work?"
You hit upload and get a green checkmark. But 3 days later, Google Ads shows no new conversions. Was it a platform delay? A silent failure? You have no way to know.
Silent Failures Hide
An expired GCLID. A malformed phone number. A rate limit. Any of these can cause individual records to fail — and most tools don't tell you which ones or why.
No Performance Baseline
Without execution history, you can't establish what "normal" looks like. You don't know your average success rate, typical record counts, or how execution duration trends over time.
Complete Visibility Into Every Run
Six layers of transparency, from relay summary down to individual record outcomes.
Full Execution History
Every relay run is recorded with start time, end time, duration, and outcome. Browse past runs chronologically, filter by relay or status, and see at a glance which runs succeeded, partially succeeded, or failed.
Per-Record Status
Drill into any run to see the outcome of every individual record. Green for success, red for failure — with the platform's specific error code and message. Know exactly which conversion failed and why, not just "3 errors occurred."
Pipeline Metrics
See how data flows through each stage: records fetched → filtered → deduplicated → uploaded. Understand exactly how many records were removed at each step and why. Spot filter rules that are too aggressive or deduplication catching excessive repeats.
Filterable & Searchable
Filter logs by relay, date range, and status (success, partial, failed). Find specific runs instantly. When a client asks about a specific date's conversions, you can pull up the exact run in seconds — not minutes of scrolling.
Automatic Retry Queue
Records that fail due to transient errors (rate limits, temporary outages) are automatically queued for retry on the next run. Three consecutive failures trigger a manual review flag. No conversions slip through the cracks quietly.
OAuth Token Monitoring
Every OAuth token refresh is logged — when it happened, whether it succeeded, and the token's expiration. If a connection's token fails to refresh (user revoked access, platform changed scopes), you'll see it in the log before it causes a relay failure.
The Activity Log in Action
Real execution data. Per-record outcomes. Full pipeline transparency.
Activity Log Questions
Every relay execution records: start time, end time, duration, records fetched, records filtered, records deduplicated, records uploaded, records failed. Each individual record within a run shows its own status (success/failure), the error message if it failed, and the platform response. You can drill from a run summary down to a specific record.
Activity logs are retained for 90 days on all paid plans. The Free tier retains logs for 30 days. You can filter by relay, status (success/partial/failed), and date range. Export to CSV is available if you need longer retention or external reporting.
When a record fails to upload (rate limit, transient API error, temporary platform outage), it enters the retry queue. TUOCA automatically retries failed records on the next relay run with exponential backoff. Records that fail 3 consecutive times are flagged for manual review — you'll see them highlighted in your activity log with the specific error.
Yes — every failed record includes the platform's error response. For Google Ads, this means codes like CLICK_NOT_FOUND or INVALID_USER_IDENTIFIER with human-readable explanations. TUOCA also adds context about what TUOCA sent vs. what the platform expected, making debugging straightforward.
TUOCA tracks the health of every OAuth connection. The activity log shows token refresh events — when tokens were refreshed, whether the refresh succeeded, and alerts when a token approaches expiry. If a refresh fails (e.g., the user revoked access), the log surfaces it immediately so you can re-authorize before the next relay run.