Connect Your Funnel Builder With Matomo Using Heyflow

What "Connecting a Funnel Builder With Matomo" Actually Means

There is a persistent confusion on this topic worth clearing up immediately. When most people search for "connect funnel builder with Matomo," they are not looking for Matomo's built-in Funnels plugin, which tracks sequential page views based on URL patterns. They want to send granular interaction data from an external, multi-step lead funnel into Matomo for analytics: button clicks, field inputs, step completions, drop-offs, and form submissions, all visible in Matomo as named events tied to visitor profiles.

Matomo's built-in Funnels feature is useful for tracking navigation paths across pages on a website. It cannot, on its own, capture the step-by-step interaction data generated inside an embedded interactive funnel where the URL never changes between steps. That requires a funnel builder with a native Matomo integration that fires custom events directly into your Matomo instance, one event per interaction, per screen.

Heyflow does exactly this. When you connect Heyflow to Matomo, every button click, input change, and screen transition fires as a named event in Matomo, attributed to a visitor profile, with no developer work required.

Why Matomo Is the Right Analytics Layer for Paid Funnel Campaigns

The practical argument for Matomo is data completeness. The UK's Information Commissioner's Office found that their website traffic dropped by 90.8% after displaying a cookie consent banner to visitors. If you are running paid campaigns and relying on GA4 with a consent banner, you are making funnel optimisation decisions based on a fraction of your actual traffic, and that fraction is not representative. Users who decline tracking skew toward mobile, iOS, and privacy-aware demographics, which are often your highest-intent audience segments.

Matomo's cookieless tracking mode uses a server-side hash called config_id, a privacy-friendly identifier that groups page views into sessions without setting any cookies on the visitor's device. Combined with a funnel builder that fires events natively into Matomo, you get complete funnel visibility without a consent wall blocking your data. The CNIL, France's data protection authority, has confirmed that Matomo qualifies for its audience measurement exemption when properly configured, meaning no consent banner is required for French visitors. Similar exemptions apply in Spain and the Netherlands.

For teams in Germany, the picture is more nuanced. A March 2025 ruling by the Hannover administrative court found that Google Tag Manager itself requires explicit consent before activation under Section 25 TDDDG, because it accesses device information during initialisation. This is a significant compliance liability for any team using GTM to load their analytics. A funnel builder with a native Matomo integration, one that loads the Matomo tracker directly without GTM as an intermediary, avoids this problem entirely.

Beyond compliance, Matomo is particularly well-adopted in the markets Heyflow serves. According to 6sense, 30% of Matomo's global user base is based in Germany, making it the single largest country by share. If you are running campaigns in the DACH region, your clients and prospects are more likely to already be using Matomo than almost any other analytics tool.

Matomo Built-In Funnels vs. External Funnel Builder Tracking

The key practical point: if your funnel is embedded on a landing page and does not navigate the user to a new URL between steps, Matomo's built-in Funnels plugin cannot track it. You need event-based tracking, which requires a funnel builder that fires custom events natively into Matomo.

How to Connect Heyflow With Matomo

Heyflow has a native Matomo integration that requires no developer work and no GTM container. The setup takes under five minutes and works with both Matomo Cloud and Matomo On-Premise.

Step 1: Set up your Matomo instance. If you are using Matomo Cloud, your instance URL will be in the format yoursite.matomo.cloud. For On-Premise, use your self-hosted domain. Note your Site ID from the Matomo dashboard under Administration.

Step 2: Add your Matomo credentials to Heyflow. In your Heyflow flow editor, navigate to Integrations, then select the Analytics tab. Scroll to the Matomo section, enter your Matomo URL and Site ID, and click Connect.

Step 3: Republish your flow. After connecting, republish the flow for the integration to take effect.

Step 4: Run a test. Click through your flow as a visitor would. In Matomo, open the Visitor Log or Visitor Profile section (accessible via the ID icon in your dashboard). You should see your test session with event data including button clicks, input changes, and screen transitions. If events are not appearing, check that you have not declined cookie consent during the test and that any ad blockers or browser extensions are disabled.

Once connected, Matomo captures every meaningful interaction in your funnel as a named event. These events appear in visitor profiles and can be used to build segments, configure goals, and feed into Matomo's reporting. For a full walkthrough with screenshots, see the Analyze Heyflow events with Matomo help article.

What Heyflow Sends to Matomo and How to Use It

Heyflow fires events for button clicks, input field changes, screen views, and form submissions. Each event is attributed to a visitor profile in Matomo, which means you can see the complete journey a specific visitor took through your funnel, including which screen they dropped off on and what they had already filled in before leaving.

This data becomes actionable in several ways. You can create Matomo segments based on UTM parameters to compare funnel performance across traffic sources: Meta vs. Google vs. TikTok. You can configure Matomo Goals to trigger on funnel submission events, giving you a conversion rate metric that is independent of ad platform reporting and based on 100% of your traffic rather than the consented subset. And you can use Matomo's heatmaps and session recording plugins alongside funnel event data to diagnose why a specific screen has a high drop-off rate.

For teams using Matomo's premium Funnels plugin, configure funnel steps using event-based matching rather than URL matching. Set the event category to match Heyflow's event taxonomy and define each step by event name. This is the critical implementation detail that most guides miss: because Heyflow is an embedded single-page funnel, URL-based step definitions will not work.

Heyflow's Native Analytics and Matomo Work Together, Not Against Each Other

Heyflow has its own built-in analytics that show per-screen drop-off rates, visit counts, exit rates, and device breakdowns without any additional setup. This is available to all users and requires no third-party integration. The Analyze and Optimize feature gives you a performance breakdown for each individual screen in your funnel, making it straightforward to identify which step is causing the most drop-offs.

Matomo adds a different analytical layer on top of this. Heyflow's native analytics tells you which screen has the problem. Matomo tells you who is dropping off, by segment: which traffic source, which device type, which campaign, which geography. Together, they give you the complete picture. You use Heyflow's per-screen data to identify the problem, and Matomo's visitor-level, campaign-attributed data to understand why it is happening and which audience segments are most affected.

GDPR Compliance: Why This Stack Works for Regulated Industries

Heyflow is SOC 2 Type II certified, ISO 27001 certified, GDPR-compliant, and HIPAA-ready with BAA support. Matomo is an open-source analytics platform with full data ownership: on Matomo Cloud, data is stored in Frankfurt, Germany; on Matomo On-Premise, data never leaves your own infrastructure. The combination creates an end-to-end analytics stack where no lead data touches Google's servers, no consent banner is required for analytics tracking (when Matomo is properly configured for cookieless mode), and all data processing can be fully documented for GDPR compliance purposes.

For teams in insurance, finance, healthcare, or legal verticals, this matters significantly. A Hannover court ruling in March 2025 established that GTM requires explicit consent in Germany before it can activate. A native Heyflow-to-Matomo integration bypasses GTM entirely, which removes this compliance exposure. For healthcare teams specifically, Matomo can be configured to meet HIPAA requirements, and Heyflow's Sensitive Tag feature prevents specified field data from being stored on Heyflow's servers at all, creating a clean chain of data custody.

Agencies building funnels for regulated-industry clients can standardise this stack across accounts: Matomo Cloud instance per client, Heyflow native integration, consistent event taxonomy, GDPR-compliant cookieless configuration. This is a repeatable, auditable setup that can be presented to a client's DPO with confidence. For more on how Heyflow approaches agency-scale lead generation, see the guide on automating and scaling lead generation at your agency.

Combining Matomo With Server-Side Ad Tracking

Matomo handles your owned analytics: funnel performance, visitor behaviour, campaign attribution, and conversion data that you control. But for paid campaigns on Meta, TikTok, Google, or Bing, you also need to feed conversion signals back to the ad platforms for bidding optimisation. These are two separate data flows with different purposes.

Heyflow supports native server-side Conversion API integrations for Meta, TikTok, and Bing, as well as client-side integrations for Google Ads and LinkedIn. Server-side tracking sends conversion data directly from Heyflow's servers to the ad platform, bypassing the browser entirely. This means conversion signals are not affected by ad blockers, iOS privacy restrictions, or consent banner declines. The result is higher match rates and more accurate bidding signals, independent of what Matomo is capturing on the analytics side.

Running both in parallel is the correct architecture for performance marketing teams: Matomo for owned, privacy-compliant funnel analytics, and server-side CAPI for ad platform signal quality. The two do not conflict; they serve different purposes in the measurement stack. For teams evaluating this setup, the performance marketers solution page covers how Heyflow addresses both needs natively.

FAQ

Does Heyflow have a native Matomo integration, or do I need to use Google Tag Manager?

Heyflow has a native Matomo integration built directly into the platform. You add your Matomo URL and Site ID in the Integrations panel under the Analytics tab, and Heyflow loads the Matomo tracker directly without GTM as an intermediary. This is a meaningful compliance advantage, particularly for teams operating in Germany, where a March 2025 court ruling established that GTM itself requires explicit consent before activation.

What events does Heyflow automatically send to Matomo?

Heyflow sends events for button clicks, input field changes, screen views, and form submissions. These events appear in Matomo's visitor profiles, where you can see the complete interaction sequence for each individual visitor. They can also be used to configure Matomo Goals and, if you have the premium Funnels plugin, to define funnel steps using event-based matching rather than URL matching.

Can I use Matomo without a cookie consent banner when tracking Heyflow funnel interactions?

When Matomo is configured in cookieless mode, it uses a server-side session hash rather than cookies, which reduces or eliminates the consent requirement in several EU jurisdictions. The CNIL in France has confirmed Matomo qualifies for its audience measurement exemption under specific configuration conditions, and similar exemptions apply in Spain and the Netherlands. Germany applies a stricter interpretation, so the correct position for German-targeted campaigns is that cookieless Matomo reduces compliance burden but does not eliminate it entirely. Consult legal counsel for your specific situation.

How is Matomo's built-in Funnels plugin different from tracking an external funnel builder in Matomo?

Matomo's built-in Funnels plugin tracks sequential page views based on URL patterns, making it suited for multi-page website navigation flows. An embedded interactive funnel builder like Heyflow does not change the URL between steps, so URL-based funnel tracking does not capture step-level data. To track Heyflow funnel steps in Matomo's Funnels plugin, you need to configure steps using event-based matching, using the custom events Heyflow fires for each screen transition.

Does the Heyflow Matomo integration work with both Matomo Cloud and self-hosted Matomo On-Premise?

Yes, the integration works with both deployment options. For Matomo Cloud, use your yoursite.matomo.cloud URL and the Site ID from your dashboard. For On-Premise, use your self-hosted domain URL. The connection process is identical in both cases.

How does Matomo funnel data complement Heyflow's built-in drop-off analytics?

Heyflow's native analytics shows per-screen drop-off rates, visit counts, and exit rates for every step in your funnel without any additional setup. Matomo adds visitor-level attribution: you can segment drop-off data by traffic source, device type, campaign UTM, or geographic location. The practical workflow is to use Heyflow's built-in analytics to identify which screen has the highest drop-off, then use Matomo segments to determine which audience or campaign is driving that drop-off disproportionately.