The Flowcode Pixel is fully configurable and allows you to fine-tune which events are tracked, where they are tracked, and whether they count as conversions. This is done using filters and tracker settings that control what data is collected across different parts of your site.
Below is a breakdown of what you can customize:
1. URL Path Filters (for all event types)
You can control tracking by applying path-level filters. These let you restrict events to fire only on specific pages of your site.
Format: Do not include the root domain. Example: use
/products/page-ainstead ofhttps://www.example.com/products/page-a.Matching Options:
Exact match (
/thank-you)Contains (fires on any URL that contains the string)
Regular Expression (RegEx) match (for advanced pattern matching)
2. Visit Length Tracking
Track how long a user stays on a page and if they are still active.
Minimum Length of Visit: The number of seconds a user must remain on a page to count as a “visit” (default: 30s).
Check Interval: The number of seconds between activity checks (default: 5s).
Paths: Optional path filters (default all. Match, contains, or regex).
3. Page Views
Triggered on load, reload, or back navigation.
Paths (default all. Match, contains, or regex)
Is Conversion? (default No. Yes/No?)
4. Forms
Capture interactions with form fields and submissions.
You can configure:
Track Form Focus? (default: No)
Form Focus is Conversion? (default: No)
Track Form Change? (default: No)
Form Change is Conversion? (default: No)
Track Form Submit? (default: Yes)
Form Submit is Conversion? (default: Yes)
Filters available:
Paths (default all. Match, contains, or regex)
HTML Classes (default all. Match, contains, or regex)
HTML IDs (default all. Match, contains, or regex)
HTML Names (default all. Match, contains, or regex)
Note: If your site uses JavaScript frameworks (e.g. in SPAs) that bypass native form submission, Form Submit tracking may not trigger. In these cases, Form Field Focus or Form Field Change should be used instead.
5. Button Clicks
Track clicks on any HTML button element. You can configure:
Paths (match, contains, regex)
HTML Classes (default all. Match, contains, or regex)
HTML IDs (default all. Match, contains, or regex)
HTML Names (default all. Match, contains, or regex)
Button Text (default all. Match, contains, or regex)
Is Conversion? (default No. Yes/No)
Need more advanced setup?
If you need a more granular configuration (e.g. form focus only on /signup but form submit only on /thank-you), please contact your CSM for help.