MBmedien Group GmbH

<p>Many website visitors cannot be tracked using conventional tracking methods. Combine 3 different types of web tracking (with cookie, without cookie and server-side) with this plugin to reveal hidden traffic on your website and analyse up to 90% more in Matomo. Scalooper Traffic Insights is installed and ready to use in 5 minutes.<br />
How Scalooper Traffic Insights works<br />
Imagine you invest in marketing activities that drive visitors to your website, but you can only analyse a portion of the traffic. Time and budget are wasted if visitors go uncounted because they block cookies or access your site through platforms that make tracking impossible.<br />
With Scalooper Traffic Insights you can also track these visitors!<br />
If a visitor blocks cookies, in many cases they can still be tracked using cookie-less (i.e. anonymous or pseudonymised, depending on the Matomo setting) tracking. If this is not possible either, you would track the actual server accesses.<br />
With this double fallback you will hardly miss anything that happens on your website.<br />
The Benefits of Scalooper Traffic Insights<br />
Scalooper Traffic Insights provides a number of advantages:<br />
Traceability over days through cookie tracking (consent required)<br />
Capture additional events that only happen in the browser, such as scrolling (setup required)<br />
More accurate page view numbers through server-side tracking<br />
Plausible TimeOnPage measurement through the Matomo HeartBeat timer<br />
With this additional data you can evaluate natural traffic, marketing campaigns and usability optimisations in more detail than ever before. Focus on the true potential and use your time and budget in the most efficient way!</p>


Scalooper Traffic Insights

Discover up to 90% more of your hidden traffic with triple tracking: cookie-based, cookie-less and server-side. Up and running in 5 minutes.

capiflow

<p><strong>CapiFlow</strong> sends supported WooCommerce events from your server to Meta’s Conversions API (CAPI) — helping reduce the impact of browser-side tracking limitations like ad blockers, Safari ITP, and Firefox ETP.</p>
<h4>Why Server-Side Tracking Matters</h4>
<p>When the Meta pixel is blocked, event data may not reach Meta — affecting ad optimization. CapiFlow complements the browser pixel by sending events server-side with a matching <code>event_id</code> for deduplication.</p>
<h4>How It Works</h4>
<ol>
<li><strong>Install & Activate</strong> — Setup wizard launches automatically</li>
<li><strong>Enter Pixel ID + Access Token</strong> — From Meta Events Manager</li>
<li><strong>Click Test Connection</strong> — Events start flowing</li>
</ol>
<p>No theme edits. No GTM server container required. No separate server-container subscription needed for the built-in Meta CAPI workflow.</p>
<h4>Core Features</h4>
<p><strong>Server-Side Event Tracking</strong></p>
<ul>
<li>🎯 <strong>7 Standard Events</strong> — Purchase, InitiateCheckout, AddPaymentInfo, AddToCart, ViewContent, Search, PageView</li>
<li>🔄 <strong>Deduplication</strong> — Browser pixel and server events share the same <code>event_id</code> to support Meta’s deduplication</li>
<li>🛡️ <strong>First-Party Event Endpoint</strong> — Browser events can be delivered through your own domain where configured</li>
<li>🔐 <strong>SHA-256 PII Hashing</strong> — Email, phone, name hashed before leaving your server</li>
</ul>
<p><strong>Event Match Quality Support</strong> — <code>fbc</code>, <code>fbp</code>, <code>external_id</code>, client IP, user agent, and hashed customer data (email, phone, name) for logged-in users.</p>
<p><strong>Analytics & Monitoring</strong></p>
<ul>
<li>📈 Dashboard — event breakdown and source attribution</li>
<li>🔍 Debug console — payloads and Meta API responses</li>
<li>🏥 System health — token, queue, connection test</li>
<li>🛒 Cart monitor — abandoned cart summary</li>
</ul>
<p><strong>Data Quality & Control</strong></p>
<ul>
<li>📞 Phone validation at checkout</li>
<li>🔒 COD Purchase gate — hold events until admin confirms</li>
<li>📋 Order metabox and columns — per-order CAPI status</li>
</ul>
<p><strong>Developer Tools</strong></p>
<ul>
<li>🔧 Code injection — GTM, analytics, chat widgets (admin-only)</li>
<li>🪝 Filter hooks — <code>capiflow_proxy_url</code>, <code>capiflow_has_tracking_consent</code></li>
<li>📦 HPOS compatible — WooCommerce High-Performance Order Storage support</li>
<li>⏱️ Action Scheduler queue — async event delivery with retry logic</li>
</ul>
<h4>CapiFlow Pro</h4>
<p>CapiFlow Pro is a separate addon that extends the free plugin with:</p>
<ul>
<li>Phone reputation scoring and fraud detection</li>
<li>Negative Purchase events for cancelled/refunded orders</li>
<li>Multi-pixel and category-based pixel routing</li>
<li>COD auto-confirm with courier integration</li>
<li>Real-time EMQ score display from Meta API</li>
<li>Blacklist management for known fraud patterns</li>
<li>Advanced order quality tools</li>
</ul>
<p>Learn more on the <a href="https://capiflowpro.com" rel="nofollow ugc">CapiFlow website</a>.</p>
<h4>Compatibility</h4>
<ul>
<li><strong>Gateways:</strong> bKash, Nagad, SSLCommerz, Stripe, PayPal, COD, and all standard WooCommerce gateways</li>
<li><strong>Themes:</strong> Any theme — Classic, Block (FSE), page builders</li>
<li><strong>WooCommerce:</strong> HPOS and legacy post-based orders</li>
<li><strong>Consent:</strong> CookieYes, Complianz, CookieBot, GDPR Cookie Consent, custom filter hook</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>WordPress 6.0+</li>
<li>WooCommerce 7.0+</li>
<li>PHP 7.4+</li>
<li>OpenSSL PHP extension</li>
<li>Meta Pixel ID and System User Access Token</li>
</ul>
<h4>External Services</h4>
<p>This plugin connects to the following third-party services:</p>
<p><strong>Meta (Facebook) Conversions API</strong></p>
<p>CapiFlow sends WooCommerce event data to the Meta Conversions API via: <code>https://graph.facebook.com/</code></p>
<p>This connection is made from your server to Meta’s servers when a configured tracking event occurs. No data is sent until a valid Pixel ID and Access Token are configured.</p>
<p>Data transmitted includes:</p>
<ul>
<li>Hashed email, phone, first and last name (SHA-256)</li>
<li>Client IP address and Browser User Agent</li>
<li>Meta Click ID (_fbc) and Browser ID (_fbp) cookies</li>
<li>Order total, currency, and event metadata</li>
</ul>
<p>All personal data is SHA-256 hashed before transmission.</p>
<ul>
<li><a href="https://www.facebook.com/terms.php" rel="nofollow ugc">Meta Terms of Service</a></li>
<li><a href="https://www.facebook.com/privacy/policy/" rel="nofollow ugc">Meta Privacy Policy</a></li>
<li><a href="https://developers.facebook.com/terms/" rel="nofollow ugc">Meta Platform Terms</a></li>
</ul>
<p><strong>Meta Pixel JavaScript SDK</strong></p>
<p>This plugin loads the Meta Pixel SDK from: <code>https://connect.facebook.net/en_US/fbevents.js</code></p>
<p>Loaded on frontend pages when a Pixel ID is configured. The SDK is hosted by Meta.</p>
<ul>
<li><a href="https://www.facebook.com/terms.php" rel="nofollow ugc">Meta Terms of Service</a></li>
<li><a href="https://www.facebook.com/privacy/policy/" rel="nofollow ugc">Meta Privacy Policy</a></li>
</ul>
<h4>Privacy</h4>
<p>For server-side events, all personal data is SHA-256 hashed before transmission. For browser events, the Meta Pixel SDK handles hashing via Advanced Matching. This plugin does not store raw PII in its own tables. See <a href="https://www.facebook.com/privacy/policy/" rel="nofollow ugc">Meta’s privacy policy</a>.</p>
<h4>Cookies</h4>
<ul>
<li><code>cs_uid</code> — Random visitor identifier for <code>external_id</code> deduplication. 180 days. No PII.</li>
<li><code>_fbc</code> — Meta Click ID. Set by Meta SDK on ad click. CapiFlow reads/extends server-side. 180 days.</li>
<li><code>_fbp</code> — Meta Browser ID. Set by Meta SDK. CapiFlow reads/extends server-side. 180 days.</li>
</ul>
<p>All cookies are first-party and contain no personally identifiable information.</p>
<h4>Data Storage</h4>
<ul>
<li><code>{prefix}_capiflow_events</code> — Queued/sent event payloads. Auto-purged after delivery.</li>
<li><code>{prefix}_capiflow_analytics</code> — Daily aggregated analytics. Auto-purged by retention settings.</li>
<li>Order metadata with <code>_capiflow_</code> prefix. Removed on uninstall if “Keep Data” is disabled.</li>
<li>Logs in <code>wp-content/uploads/capiflow-logs/</code> with <code>.htaccess</code> protection. Auto-cleaned daily.</li>
</ul>
<h4>Consent</h4>
<p>By default, events fire once configured. Enable “Consent Enforcement” in Settings to respect CMP signals for both browser and server events.</p>
<p>Supported CMPs: CookieYes, Complianz, CookieBot, GDPR Cookie Consent. Custom integration via <code>capiflow_has_tracking_consent</code> filter.</p>
<p>When Consent Enforcement is enabled, browser and server-side events are blocked until valid tracking consent is detected.</p>
<p>Store owners are responsible for lawful consent configuration where required by privacy regulations.</p>


CapiFlow – Conversions API (CAPI) Tracking for WooCommerce

Send WooCommerce events to Meta Conversions API with server-side tracking, deduplication, and confirmed Purchase control.

Scalooper Traffic Insights vs CapiFlow – Conversions API (CAPI) Tracking for WooCommerce