How to Set Up Native Ad Conversion Tracking With Heyflow

Why Native Ad Conversion Tracking Breaks (and Why It Matters More Than You Think)

Native ad platforms like Taboola and Outbrain run on algorithmic bidding. Their ability to find users who convert depends entirely on the conversion signals you send back. When those signals are incomplete, the algorithm optimizes for cheap clicks instead of qualified leads, CPLs rise, and campaigns stall in the learning phase.

The core problem in 2026 is that browser-based pixel tracking, which is still the default setup for most native ad advertisers, misses a significant share of conversions. Research from AdBid documents a 20–30% improvement in tracked conversions when server-side tracking is added alongside a pixel. On Safari specifically, client-side cookies expire in as little as one to seven days due to Intelligent Tracking Prevention. Ad blockers compound the problem further, particularly for the 50+ demographic that native ads reach most effectively, a group that over-indexes on privacy-focused browsers.

The result: your Taboola or Outbrain account shows a higher CPA than your campaigns are actually delivering, the algorithm reduces spend on campaigns that are working, and your reported ROI understates the real impact of native. The fix is server-side Conversions API tracking, configured directly through your funnel builder, with no third-party tracker or GTM server container required.

Pixel vs. Server-Side CAPI vs. Third-Party Tracker: Which Setup Is Right for You?

Most native ad guides present pixel installation as the primary tracking method, with server-side tracking as an advanced option for enterprise teams. That framing is outdated. Here is how the three approaches compare in practice:

The practical recommendation: if your funnel builder has native server-side CAPI integrations for Taboola and Outbrain, use them. You get better data accuracy than a pixel, lower complexity than a third-party tracker, and no redirect latency affecting conversion rates. A third-party tracker only adds value if you are running traffic across networks that your funnel builder does not natively support.

One misconception worth addressing: standard Google Tag Manager is entirely client-side. Using GTM to deploy a Taboola pixel is not server-side tracking. Server-side GTM (sGTM) is a separate infrastructure requiring a cloud server, typically hosted via Stape or Google Cloud, and adds meaningful setup and maintenance overhead. Stape's own documentation for Outbrain sGTM confirms the complexity involved. A funnel builder with native CAPI eliminates this entirely.

How to Set Up Taboola Server-Side Conversion Tracking with Heyflow

Heyflow's Taboola integration sends conversion data server-to-server directly from your flow to your Taboola Ads account. No GTM container, no postback URL configuration, no third-party connector. The full setup takes under fifteen minutes.

Step 1: Create Your Conversion Event in Taboola Realize

Log into your Taboola Realize dashboard and click Tracking in the left navigation. If you are creating a new event, click Account Tracking Setup in the top right and select Server to Server as the tracking method. Under Campaign Setup, click Create Conversion. Give the event a Conversion Name, set the Conversion Type to Event, and select the event category (for example, Lead). Note the exact Event Name you assign, because it must match precisely in Heyflow. If you are using an existing conversion event, find its name under Conditions in the events overview, and note the Account ID shown at the top of the Tracking page or in the URL.

Step 2: Connect Taboola in Heyflow

In Heyflow, open your flow and click Connect to access the integrations panel. Under Tracking, select Taboola. Enter your Account ID and your Event Name exactly as configured in Taboola Realize, including case. Optionally, set a static Conversion Value and Currency if you want to pass revenue data to Taboola for value-based bidding. Click Connect, then republish your flow.

For a detailed walkthrough with screenshots, the Heyflow Taboola integration guide covers every configuration option including how to map multiple conversion events across funnel steps.

Step 3: Verify Data Flow

After republishing, submit a test entry through your flow. In Taboola Realize, check the Tracking section to confirm the event is registering. Allow up to 30 minutes for the first event to appear. Once confirmed, your conversion data is flowing server-side and the algorithm can begin using it for bidding optimization.

How to Set Up Outbrain Server-Side Conversion Tracking with Heyflow

Outbrain (now Outbrain by Teads following the 2025 merger) supports server-to-server tracking through its Campaign Manager. Heyflow's native Outbrain integration follows the same pattern as the Taboola setup, with one key difference: you only need the Event Name, not a separate Account ID.

Step 1: Create Your Conversion Event in Outbrain Campaign Manager

In Outbrain Campaign Manager, click Conversions in the left navigation. To create a new event, click Create Conversion in the top right and select Server to Server as the data source. Click Next. Under Conversion Type, select the event category (for example, Lead) and assign a unique Event Name. Click Create Conversion. If using an existing event, find its name in the conversions overview.

Step 2: Connect Outbrain in Heyflow

In Heyflow, click Connect and select Outbrain under Tracking. Enter the Event Name exactly as it appears in Outbrain (case-sensitive). Optionally add a Conversion Value and Currency. Click Connect and republish your flow.

The Heyflow Outbrain integration guide covers advanced configuration including how to run Outbrain tracking alongside Meta CAPI and TikTok Events API from a single flow, with no conflicts between integrations.

Beyond the Basic Conversion: Signals That Actually Train the Algorithm

Most native ad advertisers track one event: the final lead submission. This is a missed opportunity, particularly for campaigns generating fewer than 50 conversions per week, which is the threshold Taboola and Outbrain algorithms typically need to exit the learning phase and optimize effectively.

Track Micro-Conversions at Intermediate Funnel Steps

A five-step qualification funnel (for example: insurance type, vehicle details, driving history, coverage preferences, contact information) generates four meaningful intermediate events before the final submit. Tracking step completions as secondary conversion events, set to "inform but not optimize" in Taboola Realize, gives the algorithm four times the signal volume. This is particularly valuable during campaign launch, when the algorithm is still learning which audience segments convert.

The Taboola Realize tracking documentation confirms that S2S is specifically designed for advertisers who need to fire conversion events from systems outside the browser, including downstream CRM qualification events fired hours or days after the initial lead submission.

Use Partial Submits as High-Intent Signals

Users who complete 60–80% of a funnel before abandoning are high-intent prospects. A funnel builder that captures partial submit data (name and email from earlier steps, for example) and fires a separate "partial conversion" event to the native ad platform serves two purposes: it provides additional algorithm training data, and it enables retargeting of users who demonstrated real intent. For native ad audiences, which skew older and often have higher abandonment rates due to device and connectivity factors, partial submit tracking can recover a meaningful share of otherwise invisible conversions.

Pass Lead Quality as Conversion Value

Not all leads are equal. A funnel that qualifies users by budget, timeline, or property type generates leads with different downstream close rates. By assigning a conversion value based on qualification score, and passing that value via Heyflow's optional Conversion Value field, you enable value-based bidding. The algorithm learns to target users who become high-value leads, not just users who submit any form. This is the difference between optimizing for volume and optimizing for revenue.

Drop-Off Analytics for Campaign-Level Optimization

Per-screen drop-off data tells you exactly where native ad traffic leaks. If 60% of users entering from Taboola abandon at screen three (the phone number field, for example), that is a specific, actionable optimization target. Heyflow's screen-level analytics show visits, exits, and drop-off rates per step, so you can prioritize A/B tests on the screens with the highest abandonment rather than guessing.

A/B Testing Funnel Variants Without Breaking Conversion Attribution

Running A/B tests on funnel design or copy while maintaining clean conversion tracking back to native ad platforms requires one discipline: both variants must fire identical conversion events with identical event names. If variant A fires a "LeadSubmit" event and variant B fires a "FormComplete" event, your Taboola data becomes uninterpretable.

The practical setup: use Heyflow's built-in A/B testing to split traffic between variants, ensure both variants use the same Taboola and Outbrain integration configuration, and measure results in both Heyflow's analytics and the native ad platform's conversion reports. Test one variable at a time (headline, question order, CTA copy) and allow each test to run until you have at least 100 conversions per variant before drawing conclusions. For more on structuring these tests, Heyflow's guide to funnel builders with built-in A/B testing covers statistical significance and test design in detail.

Privacy and Compliance Considerations for Native Ad Tracking

Server-side conversion tracking is more privacy-compliant than client-side pixels for a specific reason: data can be filtered and anonymized before it reaches the ad platform. With a client-side pixel, the browser sends raw data to the platform's servers regardless of what your consent management platform (CMP) has captured. With server-side tracking, your funnel builder's server receives the data first, applies consent filtering, and only forwards events for users who have granted the appropriate permissions.

For EU advertisers, this matters under GDPR. TCF v2.3 (which replaced v2.2 in February 2026) requires that tracking pixels only fire after explicit consent for the relevant purpose. A server-side setup with proper consent gating is more defensible than a client-side pixel that relies on the browser to enforce consent decisions.

For regulated industries running native ads, including insurance, healthcare, and financial services, the compliance stakes are higher. Heyflow is SOC 2 Type II certified and HIPAA-compliant across all plans, which matters when funnel data includes health-related or financial qualification questions. This is a practical differentiator for performance marketers in these verticals, where a data breach or compliance violation can be far more costly than the ad spend itself.

Common Mistakes That Break Native Ad Conversion Tracking

Firing the conversion event on page load instead of form submission. This is the most common error in URL-based conversion setups. If your "thank you page" is accessible via direct URL, or if a user refreshes it, you will record phantom conversions. Event-based triggers tied to the actual form submission action are the correct approach.

Not deduplicating when running pixel and S2S simultaneously. If you run both the Taboola Pixel and Heyflow's S2S integration without deduplication, the same conversion will be counted twice. Proper deduplication requires a shared unique event ID passed in both the pixel event and the S2S postback, so the platform can match and discard duplicates. Check Taboola's and Outbrain's deduplication documentation before running both methods simultaneously.

Using one conversion event for all lead types. If a phone-validated lead and an unvalidated lead both fire the same "LeadSubmit" event with the same value, the algorithm cannot distinguish between them. Set up separate conversion events (or use conversion value differentiation) to train the algorithm toward the lead types your sales team can actually close.

Switching to conversion-based bidding too early. Taboola's automated bidding strategies require sufficient conversion volume to function. Switching from CPC to Maximize Conversions before you have 50+ conversions per week will result in erratic delivery. Use the micro-conversion tracking strategy described above to accelerate the learning phase before switching bidding strategies.

FAQ

Do I need a third-party tracker like Voluum or AnyTrack if my funnel builder has native Taboola and Outbrain CAPI?

No. If your funnel builder sends conversion data server-side directly to Taboola and Outbrain, a third-party tracker adds complexity and a data hop without improving accuracy. Third-party trackers are valuable for affiliate operations or multi-network setups where the funnel builder lacks native integrations, but for direct-to-platform native ad campaigns, native CAPI is the cleaner and more reliable solution.

How many conversions does Taboola need before I can use conversion-based bidding?

Taboola's automated bidding strategies, including Maximize Conversions and Target CPA, generally require a minimum of 50 conversions per week to optimize effectively. Campaigns below this threshold tend to show erratic delivery. Tracking micro-conversions at intermediate funnel steps, in addition to the final lead submit, is the most practical way to accelerate this threshold during campaign launch.

Can I track native ad conversions if my funnel is embedded on an existing advertorial page?

Yes, but the setup requires attention to click ID passthrough. Taboola appends a tclid parameter and Outbrain appends an ob_click_id parameter to the landing page URL. If your funnel is embedded via iframe on the advertorial, verify that the parent page passes these URL parameters to the embedded flow. Heyflow's server-side integrations capture URL parameters automatically, but you should confirm the click ID is present in the URL when the funnel loads. For a detailed look at embedding options, see Heyflow's guide to embedding a funnel on an existing website.

What is the difference between the Taboola Pixel and Taboola's server-to-server tracking?

The Taboola Pixel is a JavaScript snippet that fires from the user's browser when a conversion event occurs. It is subject to ad blockers, Safari's ITP cookie restrictions, and page speed constraints. Server-to-server (S2S) tracking sends the same conversion data from a server (your funnel builder's server, in Heyflow's case) directly to Taboola's API, bypassing browser limitations entirely. Taboola's own documentation recommends using both methods together for maximum conversion coverage, with deduplication to prevent double-counting.

How do I track native ad conversions across multiple funnel steps, not just the final submission?

Configure separate conversion events for each meaningful funnel step in your native ad platform's dashboard, then connect each event to the corresponding trigger in your funnel builder. In Heyflow, you can fire different tracking events at different screens within the same flow. Set intermediate step events as secondary conversions in Taboola or Outbrain (so they inform the algorithm without becoming the primary optimization target), and reserve your primary conversion event for the final lead submission or phone-validated lead. This approach is particularly effective for native ad funnels targeting longer consideration journeys, where users often engage deeply before converting.

Is server-side conversion tracking for native ads only feasible for large advertisers?

It used to require developer resources or a cloud-hosted sGTM container, which made it impractical for smaller teams. Funnel builders with native CAPI integrations have changed this. With Heyflow, server-side conversion tracking for Taboola and Outbrain is a configuration task in the Connect panel, with no code, no GTM server container, and no third-party middleware required. The setup is accessible to any advertiser, regardless of technical resources, and is specifically designed for performance marketers managing campaigns independently.