Connect Your Funnel Builder With Outbrain Using Heyflow

Why Outbrain Campaigns Need More Than a Pixel

Outbrain's Conversion Bid Strategy (CBS) is the platform's core optimization engine. It automatically shifts budget toward publisher placements and audience segments most likely to convert. But CBS only works as well as the conversion data feeding it. Run pixel-only tracking and you're under-reporting conversions by 15–30%, according to native advertising benchmarks for lead generators. The algorithm trains on incomplete data, misallocates budget, and your Outbrain campaigns appear to underperform relative to Meta or Google, even when they're actually generating solid leads.

The root cause is client-side tracking. The Outbrain pixel depends on the browser loading the JavaScript, reading the Outbrain cookie, and firing the event before the user navigates away. Ad blockers, iOS privacy settings, and cookie restrictions all interrupt this chain. For a multi-step lead funnel where the conversion happens several screens after the initial click, the failure rate compounds at every step.

Server-to-server (S2S) tracking solves this by moving the conversion signal from the browser to your server. When a user completes your funnel, your server fires directly to Outbrain's endpoint, passing the ob_click_id that was captured when the user first clicked the ad. No browser dependency, no ad blocker vulnerability, no cookie requirement. The conversion is recorded reliably, CBS gets accurate data, and the algorithm can actually do its job.

How Heyflow Connects With Outbrain

Heyflow includes a native Outbrain server-side integration, available on Agency and Business plans as part of the Core Bundle. There is no GTM server container to configure, no third-party middleware to pay for, and no custom code to maintain. The integration fires conversion events directly from Heyflow's servers to Outbrain using S2S, which means it works regardless of what's happening in the user's browser.

The setup takes four steps. First, create a conversion event in your Outbrain Campaign Manager under Conversions, selecting "Server to Server" as the data source and assigning an event name (for example, "Lead" or "qualified_lead"). Note the exact event name, including capitalisation, because the match is case-sensitive. Second, open your flow in Heyflow, click Connect, and select Outbrain under Tracking. Enter the event name exactly as it appears in Outbrain. Third, optionally configure a conversion value and currency if you want Outbrain to measure ROI by lead value. Fourth, click Connect and republish your flow. That's the complete integration.

For a detailed walkthrough with screenshots, see the Heyflow Outbrain tracking guide in the help center.

Three Ways to Connect a Funnel Builder With Outbrain

There are three practical approaches to sending conversion data from a lead funnel to Outbrain. They differ significantly in setup complexity, data accuracy, and ongoing cost.

The pixel-only approach is the most common starting point and the most problematic at scale. Third-party tracking tools like AnyTrack or RedTrack can bridge the gap, but they add monthly cost, introduce latency, and create another vendor relationship to manage. A native S2S integration inside the funnel builder itself eliminates the middleware entirely: the conversion event fires directly from Heyflow's server to Outbrain the moment a user completes the funnel step you've designated as a conversion.

The Advertorial-to-Funnel Workflow for Native Ads

Outbrain's inventory sits on premium editorial sites. Users arrive from news articles, lifestyle content, and finance publications, not from a search query with declared intent. This changes how your post-click experience needs to be structured. A hard-sell form immediately after a native ad click typically converts poorly because the user hasn't been warmed up. The pattern that works is: Outbrain ad → advertorial pre-lander → interactive funnel → CRM.

The advertorial page does the trust-building work. It mirrors the editorial context the user just left, educates them on the problem your product solves, and creates a natural transition into the funnel. The funnel then qualifies the lead through a sequence of questions before asking for contact information. This multi-step structure, rather than a single form, consistently produces higher-quality leads from native traffic because users who complete a longer qualification flow are genuinely interested.

Heyflow is built specifically for this pattern. You can embed a Heyflow flow directly on an advertorial page or host it as a standalone flow on a custom domain. The native advertising workflow with Heyflow covers both approaches. Either way, the Outbrain ob_click_id is captured on arrival and persisted through every step of the multi-screen funnel, so the conversion signal can be matched back to the original click regardless of how many screens the user navigates.

Sending Better Signals to Outbrain's Algorithm

Most Outbrain setups fire a single "form complete" event and stop there. This gives CBS a small dataset to learn from, especially in the first two weeks of a campaign when conversion volume is low. Sending intermediate events, what Heyflow calls partial submits, gives the algorithm more signal data faster.

A partial submit captures the data a user has entered when they abandon the funnel before reaching the final step. For Outbrain's purposes, you can send a "funnel_started" or "reached_step_4" event as a micro-conversion. CBS learns which publisher placements and audience segments produce users who engage deeply with your funnel, even if they don't complete it. This is directly analogous to using "Add to Cart" events in Meta campaigns to accelerate algorithm learning before "Purchase" volume is sufficient.

Phone network validation adds another layer of signal quality. If your funnel verifies that a submitted phone number is a real, active number before firing the Outbrain conversion event, you're teaching CBS to find users who provide legitimate contact information rather than junk entries. Over time, this shifts your Outbrain traffic toward higher-quality segments. You can also use Heyflow's analytics and optimization features to identify exactly which funnel screen loses the most Outbrain traffic, then test changes to that specific step rather than rebuilding the entire funnel.

Cross-Platform CAPI Coverage for Native and Paid Social

Most performance teams running Outbrain are also running Meta, Google, TikTok, or Bing. Managing server-side tracking across all of these platforms typically means either a custom engineering project or a stack of third-party tracking tools, each adding cost and complexity.

Heyflow covers server-side tracking natively for Meta CAPI, TikTok Events API, Bing CAPI, Taboola CAPI, and Outbrain S2S, with client-side support for Google Ads and LinkedIn. This means a single flow can fire conversion signals to every platform your media budget touches, from one configuration interface, with no external tools required. For agencies managing native campaigns across multiple clients, this removes the per-client tracking setup overhead that makes scaling painful.

If you're currently running Outbrain alongside Meta and using Typeform or Jotform for lead capture, neither tool has a native Outbrain integration. You're either relying on pixel-only tracking or routing data through a middleware layer. Try Heyflow to consolidate your conversion tracking across all platforms into a single funnel builder.

Vertical-Specific Considerations for Outbrain Lead Gen

Outbrain's premium publisher network skews toward users who consume editorial content on major news, finance, and lifestyle sites. This demographic profile, often 45 and older with higher household income, maps well to specific lead generation verticals where Heyflow funnels are most commonly used.

In insurance and Medicare, the qualification funnel typically runs 7–10 steps: age, zip code, coverage type, current provider, health conditions, contact information, and phone validation. The Outbrain S2S event should fire only after phone validation succeeds, so CBS learns to find users who provide real contact details rather than placeholder entries. In solar and home improvement, a calculation block showing estimated savings before the contact step significantly improves completion rates because native users are in discovery mode and respond to concrete value demonstration. In legal lead generation, longer qualification flows filter out unqualified inquiries before they reach a case intake team, making the conversion signal sent to Outbrain a more accurate proxy for actual case value.

Across all verticals, setting a conversion value in the Heyflow Outbrain integration lets CBS optimize toward higher-value leads rather than treating all conversions equally. If your insurance leads are worth $150 and your solar leads are worth $300, passing these values to Outbrain allows the algorithm to weight its optimization accordingly. The B2C lead generation use case in Heyflow is designed specifically for these high-value, multi-step qualification flows.

Performance Marketers Running Outbrain at Scale

If you're spending $10,000 or more per month on Outbrain and still using pixel-only tracking, the under-reporting problem directly affects your budget decisions. Outbrain shows a higher CPA than your CRM data reflects, which makes the channel look less efficient than it actually is. Teams routinely cut Outbrain budgets or reallocate to Meta based on this distorted view, when the real problem is a tracking gap rather than a channel performance problem.

Fixing S2S tracking through Heyflow closes this gap within the first reporting cycle. You'll typically see reported conversions increase by 15–30% with no change in actual lead volume. CBS then has accurate data to work with, and the algorithm can begin optimizing effectively. Outbrain has reported CPA reductions of up to 49% with CBS running on complete conversion data, though results vary significantly by vertical and campaign structure.

For performance marketers who want a single tool that handles funnel building, multi-platform CAPI, A/B testing, and per-screen drop-off analytics without requiring a developer, Heyflow is built for that workflow. Get started with Heyflow and connect your first Outbrain flow in under 30 minutes.

FAQ

Does Heyflow integrate natively with Outbrain, or do I need a third-party tool?

Heyflow includes a native server-to-server Outbrain integration, available on Agency and Business plans. You configure it directly in the Heyflow Connect panel, no GTM server container, no AnyTrack, no custom code required. Conversion events fire from Heyflow's servers directly to Outbrain's S2S endpoint in real time.

What conversion events can I send from Heyflow to Outbrain?

You can send any event that corresponds to a conversion action in your flow, including full form submissions, partial submits (users who abandon mid-funnel), and phone-validated leads. The event name you configure in Heyflow must match exactly the event name in your Outbrain conversion setup, including capitalisation. You can also pass a static conversion value and currency to enable ROI tracking in CBS.

Why is my Outbrain dashboard showing fewer conversions than my CRM?

This is almost always caused by pixel-only tracking. The Outbrain pixel relies on the browser loading correctly, the user not having an ad blocker, and the Outbrain cookie being readable. In multi-step funnels, these conditions fail often enough to cause 15–30% under-reporting. Switching to server-side tracking via Heyflow's native S2S integration closes this gap because the conversion signal is sent from Heyflow's server rather than the user's browser.

Do I need to install the Outbrain pixel if I'm using Heyflow's S2S integration?

No. Heyflow's server-side integration bypasses the pixel entirely, which is the recommended approach for lead generation funnels. If you want to run both during an initial validation period to compare counts, you can, but once you've confirmed the S2S integration is firing correctly, the pixel adds no additional value and risks double-counting conversions in your Outbrain dashboard.

How do I make sure the ob_click_id is captured through a multi-step funnel?

Heyflow handles ob_click_id capture and persistence automatically. When a user lands on your flow from an Outbrain ad, the click ID is captured from the URL parameter and stored throughout the entire funnel session, including across conditional logic branches and back-navigation. You don't need to write any custom JavaScript to persist the parameter between steps.

Which Heyflow plan includes the Outbrain integration?

The Outbrain S2S integration is available on the Agency and Business plans as part of the Core Bundle. It is not available on the Starter plan. If you're unsure which plan you're on, you can check your subscription in your Heyflow account settings.