FlowserySoporte
← Todas las categorías

🛡️Proxy Guides13
  • Proxying Flowsery Analytics with Astro
  • Proxying Flowsery Analytics with Caddy
  • Proxying Flowsery Analytics with DigitalOcean
  • Proxying Flowsery Analytics with Express.js
  • Proxying Flowsery Analytics with FastAPI
  • Proxying Flowsery Analytics with Firebase Hosting
  • Proxying Flowsery Analytics with Flask
  • Proxying Flowsery Analytics with Laravel
  • Proxying Flowsery Analytics with Next.js
  • Proxying Flowsery Analytics with Nginx
  • Proxying Flowsery Analytics with PHP
  • Setting up a proxy (code required)
  • Proxying Flowsery Analytics with Vue.js
📦Installation Guides23
  • Set up Flowsery Analytics in an Astro project
  • Set up Flowsery Analytics in a Bolt application
  • Set up Flowsery Analytics in a Bubble.io app
  • Set up Flowsery Analytics in a Django project
  • Set up Flowsery Analytics on a Framer site
  • Set up Flowsery Analytics on a Ghost CMS site
  • Deploy Flowsery Analytics via Google Tag Manager
  • Get Flowsery Analytics running in 2 minutes
  • Set up Flowsery Analytics on a Kajabi site
  • Set up Flowsery Analytics in a Laravel project
  • Set up Flowsery Analytics in a Lovable website
  • Set up Flowsery Analytics in a Next.js App Router project
  • Set up Flowsery Analytics on a Podia site
  • React Native / Expo
  • Set up Flowsery Analytics in a React Router project
  • Set up Flowsery Analytics in a Replit project
  • Set up Flowsery Analytics on your Shopify store
  • Set up Flowsery Analytics on a Squarespace site
  • Set up Flowsery Analytics in a Vercel v0 project
  • Set up Flowsery Analytics in a Vue.js project
  • Set up Flowsery Analytics on a Webflow site
  • Set up Flowsery Analytics on a Wix site
  • Set up Flowsery Analytics on a WordPress site
💰Revenue Attribution24
  • Attribute revenue with Bolt
  • Attribute revenue with Ghost
  • Attribute revenue with Kajabi
  • Attribute revenue with Lovable
  • Attribute revenue with Podia
  • Attribute revenue with Replit
  • Attribute revenue with Vercel v0
  • Attribute revenue with Dodo Payments
  • Attribute revenue with LemonSqueezy Checkout API
  • Attribute revenue with LemonSqueezy (other methods)
  • Attribute revenue with LemonSqueezy Payment Links
  • Attribute revenue with Paddle Checkout API
  • Attribute revenue with Paddle (other methods)
  • Attribute revenue with Paddle Overlay Checkout
  • Attribute revenue with custom payment providers
  • Attribute revenue with Polar Checkout API
  • Attribute revenue with Polar Checkout Links
  • Attribute revenue with Polar (other methods)
  • Revenue attribution guide
  • Attribute revenue with Stripe Checkout API
  • Attribute revenue with Stripe (other methods)
  • Attribute revenue with Stripe PaymentIntent API
  • Attribute revenue with Stripe Payment Links
  • Connect Flowsery Analytics to your WooCommerce store
🚀Getting Started4
  • Connect your payment provider
  • Track conversion funnels
  • Analyze your data with Flowsery filters
  • Improve your analytics with URL tracking parameters
⚙️Advanced Features8
  • Track visitors across different domains
  • Exclude your own visits, IPs, countries, hostnames, or paths
  • Hashed page paths tracking
  • Reduce your Flowsery Analytics usage
  • Track scroll events
  • Track visitors across subdomains
  • User identification
  • Web to app funnel tracking
🔧Troubleshooting2
  • Flowsery Analytics script blocked by Content Security Policy (CSP)
  • Why are payments appearing twice?
Soporte/Revenue Attribution
Revenue Attribution

Attribute revenue with Paddle Overlay Checkout

Before proceeding, confirm that you have linked your Paddle account.

JavaScript
Paddle.Checkout.open({
  items: [...],
  customData: {
    website_id: 'flid_******',
  },
});

Flowsery routes Paddle webhook events with custom_data.website_id. Do not rely on _fs_vid or _fs_sid here.

Atribuir ingresos con Paddle (otros metodos)
Attribute revenue with custom payment providers
Flowsery

Flowsery

Flowsery reúne analítica centrada en la privacidad, analítica sin cookies, análisis de embudos, seguimiento del recorrido del cliente y atribución de ingresos en un panel sencillo.

Contáctenos
Correo: contact@flowsery.com

Taras Shynkarenko (operando como Flowsery)

IVA: PL9571091905

Dirección: Heweliusza 11/811, 80-890, Gdansk

Funcionalidades
  • Analítica en tiempo real

  • Privacidad ante todo

  • Seguimiento de ingresos

  • Embudos

  • Seguimiento de objetivos

  • Script ligero

  • UTM y campañas

  • Alternativa a GA

  • Agentes IA

  • Integración OpenClaw

Empresa
  • Acerca de

  • Precios

  • Blog

  • Datos de marca

  • Kit de prensa

Recursos
  • Documentacion

  • Centro de soporte

  • Cómo se compara Flowsery

  • Alternativas

  • Mejores herramientas de analítica web

  • Casos de uso

  • Contacto

Legal
  • Política de privacidad

  • Términos de servicio

  • Política de cookies

  • GDPR

Contáctenos
Correo: contact@flowsery.com

Taras Shynkarenko (operando como Flowsery)

IVA: PL9571091905

Dirección: Heweliusza 11/811, 80-890, Gdansk


2026 Taras Shynkarenko Todos los derechos reservados.