YouTube Ads Integration

YouTube is the world's second-largest search engine, the dominant video platform, and one of the only places where you can run real video at performance-channel prices. The challenge has always been measurement. Video metrics live on YouTube, your conversions live in your affiliate platform, and the connection between a fifteen-second skippable ad and a sale a week later is rarely obvious from either side alone. Many operations end up running YouTube as a brand channel by default because they can't make a clean performance case for it.

The Routy integration with YouTube Ads ties video performance to real revenue. YouTube campaigns run through Google Ads under the hood, so the connection is the same as the Google Ads one: a single Google authentication covers both. Spend and performance data for your video campaigns pull into Routy, and downstream conversions get sent back to Google so YouTube's Smart Bidding has real outcome data to optimise against.

After connecting, the following becomes available in your Routy reports:

• Spend at the campaign, ad group, and ad level for your YouTube and video campaigns
• Impressions, views, view-through rate, click-through rate, and the video-specific engagement metrics YouTube exposes (25%, 50%, 75%, and 100% completions)
• Conversion attribution that ties every conversion Routy tracks back to the YouTube campaign, ad group, and creative behind the original view or click
• Server-side conversion uploads via the Google Ads Conversions API, with both click-through and view-through events sent where applicable

Plus, since YouTube performance lives next to your search, display, and other Google Ads spend in the same dashboard, you can finally answer the question of whether video is genuinely earning its place in the mix or just absorbing budget that could go elsewhere.

YouTube campaigns are managed through Google Ads, so you connect your Google Ads account through Google's standard OAuth flow — the same connection that powers the Google Ads integration. From there, Routy pulls performance data for your video campaigns from the Google Ads API on a regular schedule and posts conversion events back through the Conversions API as conversions come in.

A few things worth knowing before you connect:

• View-through conversions are credited differently from click-through conversions. Google's default attribution window for YouTube view-throughs is 30 days, but this is configurable in Google Ads. Whatever window you've set, Routy respects it.
• The line between a YouTube conversion and a Google Search conversion can blur when the user sees a YouTube ad and then searches for the brand later. Google's attribution model decides how that credit gets split; Routy surfaces what Google reports and doesn't override the attribution logic.
• Video campaigns generate more impression data and less click data than search campaigns. If you're used to evaluating performance primarily on clicks, the YouTube reports will look unfamiliar at first. The view-through and completion metrics are where the video story actually lives.

The case for YouTube as a performance channel rests on whether the video you're producing converts at a cost that justifies the production effort. Without proper attribution, that question can't be answered honestly — you can see what YouTube spent and you can see what total conversions happened, but the connection between the two stays fuzzy, and "fuzzy" is the kind of data that leads to YouTube budgets quietly shrinking every quarter.

Connecting Routy and feeding conversions back into the Google Ads Conversions API gives YouTube the same quality of bidding signal that your search campaigns get. Smart Bidding learns which audiences and placements actually drive revenue and pushes the budget that way. And the reporting side, with YouTube sitting next to search and display in the same dashboard, lets you make the cross-format comparison honestly. If video is working, you'll see it; if it isn't, you'll see that too, and you can act on it before the quarterly review forces the conversation.