Meta Ads Integration

Meta is where most affiliate operations still find scale, and it's also where attribution has got hardest to do well. The browser pixel sees less than it used to since iOS 14.5, ad blockers keep eating into what's left, and the in-platform reporting in Ads Manager only shows you what Meta's own pixel happened to see. The result is that Meta is often the channel where you're spending the most and trusting the data the least.

The Routy integration with Meta Ads handles both sides of that problem. It pulls your spend and performance data out of Ads Manager and into Routy on a continuous basis, and it sends your downstream conversions back to Meta through the Conversions API. The CAPI uploads survive the things the pixel doesn't: tracking prevention, ad blockers, cross-device journeys. The Meta algorithm gets cleaner signal to optimise against, and you get a complete view of what each campaign actually produced.

The integration covers Facebook and Instagram from the same connection, since both run through Meta Ads Manager under the hood.

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

• Spend at the campaign, ad set, and ad level for both Facebook and Instagram, so you can see exactly where the budget is going across both surfaces
• Clicks, impressions, reach, frequency, and CTR, plus the platform-specific engagement metrics Meta exposes
• Conversion attribution that ties each conversion Routy tracks back to the Meta campaign, ad set, and ad behind the click
• Server-side conversion uploads to Meta through the Conversions API, with the events deduplicated against your existing pixel events so you don't double-count

Plus, because the Meta data sits next to whatever other traffic sources you've connected, you can compare Meta head-to-head with Google, TikTok, native, and everything else without juggling Ads Manager tabs.

You connect your Meta Business account through Meta's standard OAuth flow. From there, you pick which ad accounts you want Routy to pull data from (most agencies and larger operations end up with several). The integration pulls performance data from the Marketing API on a regular schedule throughout the day and writes conversion events to the Conversions API as they happen.

A few things worth knowing before you connect:

• Meta requires Business Manager access to authorise the connection. If your ad account is owned by an agency or a client, you'll need them to grant you (or Routy) the right permissions through Business Manager. This is a Meta requirement that applies to any third-party integration.
• CAPI events take a few minutes to appear in Events Manager, and Meta applies its own deduplication rules when an event arrives with the same event ID as a pixel event. Routy sends event IDs by default so this works correctly out of the box.
• Meta's attribution windows are shorter than they used to be, with a default 7-day click and 1-day view as of 2021. Conversions that fall outside this window won't influence Meta's bidding even if Routy sees them. This is a Meta-side rule, not a Routy limitation.

The Meta pixel was never going to keep doing what it used to do. iOS 14.5 was the big change, but the direction of travel was set well before that: less browser-side tracking, more reliance on server-side signal. The platforms that adapted earliest are the ones that still bid efficiently; the operations still running on pixel-only setups are the ones quietly burning budget on audiences that don't convert.

Connecting Routy to Meta and feeding conversions back through CAPI puts you firmly in the first camp. The algorithm gets a stream of real conversion events with the right matching parameters, which lets it find more of the people who actually buy rather than the people who happened to fire the pixel. Over a few weeks, this usually shows up as a cleaner cost per acquisition and a more stable performance profile, particularly on campaigns optimising for purchase or conversion events.

On the reporting side, the Meta data sitting in the same dashboard as everything else makes the cross-channel comparison honest. You stop having to explain why Ads Manager says one thing and your affiliate platform says another. The numbers reconcile because they're being read from the same source.