FANZ
FANZ

Changelog

Bulk edit tickets across multiple dates with previewv3.7.1 • May 26, 2026WhatsApp & Instagram Inbox, Per-Channel Autopilot, Free Ticket Credits Balance, and Onboarding Acquisition Stepv3.7.1 • May 18, 2026AFIP fiscal configuration now goes through a review workflowv3.7.1 • May 17, 2026Calendar-style date selector for multi-date eventsv3.7.1 • May 13, 2026Automatic Ticket Promotionsv3.7.0 • May 5, 2026Chargeback alerts, Meta Conversions API, and Facebook Pixel checkout eventsv3.5.12 • May 3, 2026Automation flow builder: reachability validationv3.5.12 • Apr 28, 2026Price estimates in Sell, onboarding checklist, payout receipts, and validation action logv3.5.11 • Apr 21, 2026Chronological validation audit trail in Validatev3.5.10 • Apr 20, 2026Reference chart and calibration wizard for seat mapsv3.5.9 • Apr 19, 2026Chip-style Chatbot Selections & Card-based Email Composerv3.5.9 • Apr 18, 2026FAQ reordering, ticket entry deadlines, save & exit, email capture preview, and morev3.5.8 • Apr 15, 2026Omnichannel Chatbot, Online Reputation, Sales Breakdown & Morev3.5.6 • Apr 9, 2026Ticket Office: Refund window enforcement, Close Yesterday & Admin image pricingv3.5.7 • Apr 9, 2026Image Carousel Block in Page Builderv3.5.5 • Mar 17, 2026Group Actions in Event Detail Tabsv3.5.4 • Mar 16, 2026Selective Event Duplicationv3.5.3 • Mar 13, 2026Discount Presets in the Promotional Code Formv3.5.2 • Mar 12, 2026Partner Program — Welcome banner, free ticket tracking & activation emailv3.5.1 • Mar 11, 2026Partner Program — Lifetime Partner Programv3.5.0 • Mar 10, 2026Chatbot Training FAQ Manager & Partial Reservation Completionv3.4.1 • Mar 8, 2026Segments, Flows & External Events Improvementsv3.4.1 • Mar 6, 2026Automation Flow Builderv3.4.0 • Mar 4, 2026Bounce & Complaint Tracking with Automatic Email Suppressionv3.3.0 • Mar 4, 2026Require Contact to Chatv3.3.1 • Mar 3, 2026Fanz Invoices Tab in Brand Settingsv3.3.0 • Feb 27, 2026Advanced Email Link Tracking & Recipient Activity Timelinev3.2.0 • Feb 11, 2026Date Generator, RSVP Question Ordering & Fanzly in Navigationv3.1.3 • Feb 10, 2026Events Filter Tabsv3.1.1 • Jan 26, 2026January 2026 Releasev3.1.0 • Jan 6, 2026November 2025 Releasev3.0.0 • Nov 7, 2025Block Purchases with Multiple Ticket Typesv2.6.1 • Oct 30, 2025Custom Web Pagesv2.6.0 • Oct 14, 2025Universal Multi-Event Discountsv2.5.0 • Sep 2, 2025Calendar Invite Customizationv2.4.1 • Jul 29, 2025New Weekly Calendarv2.4.0 • Jul 25, 2025Bulk Ticket Price Editorv2.3.1 • May 21, 2025Location Filter in Purchasesv2.1.2 • Jan 21, 2025Interface and Calendar Improvementsv2.1.1 • Jan 16, 2025Calendar and Location Improvementsv2.1.0 • Jan 10, 2025Fanz Core Featuresv1.0.0 • Jan 1, 2024
ENES
New Feature

Chargeback alerts, Meta Conversions API, and Facebook Pixel checkout events

v3.5.12May 3, 2026

This release gives organizers better visibility into payment disputes and significantly improves the accuracy of Facebook ad conversion tracking through server-side event reporting and standard checkout events.

Chargeback alerts with evidence requests

When a chargeback is filed against a purchase, you now receive an email notification with the evidence needed to dispute it. Previously, chargebacks were processed silently with no notification to the organizer, making disputes difficult to act on in time.

Meta Conversions API (CAPI) support

When adding a Facebook Pixel tracking code in Marketing, you can now optionally include a Meta access token to enable server-side purchase event reporting via the Meta Conversions API. This reduces data loss caused by ad blockers or browser restrictions, and deduplicates browser and server events so your reported conversions are more accurate. A green checkmark is shown next to any tracking code that has a CAPI token configured.

Facebook Pixel checkout events

The ticket purchase flow now automatically fires the standard Facebook Pixel events — PageView, ViewContent, AddToCart, InitiateCheckout, and Purchase — tied to the Pixel ID assigned to each event. When a CAPI token is also configured, these browser events are deduplicated with the server-side Conversions API to avoid double-counting. ===EN_CONTENT===