{"schedule": {"version": "0.4", "base_url": "https://schedule.matomocamp.org/matomocamp-2027/schedule/", "conference": {"acronym": "matomocamp-2027", "title": "MatomoCamp 2027", "start": "2027-03-18", "end": "2027-03-18", "daysCount": 1, "timeslot_duration": "00:05", "time_zone_name": "Europe/Madrid", "rooms": [{"name": "Room 1", "guid": null, "description": null, "capacity": null}, {"name": "Room 2", "guid": null, "description": null, "capacity": null}, {"name": "Room 3", "guid": null, "description": null, "capacity": null}], "days": [{"index": 1, "date": "2027-03-18", "day_start": "2027-03-18T04:00:00+01:00", "day_end": "2027-03-19T03:59:00+01:00", "rooms": {"Room 1": [{"id": 232, "guid": "381e2c09-6c71-5b36-beda-3375cda6b48a", "logo": "", "date": "2027-03-18T14:00:00+01:00", "start": "14:00", "duration": "00:30", "room": "Room 1", "slug": "matomocamp-2027-232-analytics-as-code-why-your-tracking-plan-belongs-in-git", "url": "https://schedule.matomocamp.org/matomocamp-2027/talk/LTHRME/", "title": "Analytics as Code: Why Your Tracking Plan Belongs in Git", "subtitle": "", "track": "Digital Analytics", "type": "Talk", "language": "en", "abstract": "Tracking plans rot in spreadsheets while tags drift in production. Treat yours as code: three YAML files in Git, CI checks on every push, pull requests as governance records, and one spec generating implementations for Matomo, GA4 and more.", "description": "Where does your analytics strategy actually live? Scattered across chat channels, in a \"Tracking Plan v3 - FINAL\" spreadsheet last edited months ago, and in the memory of people who have since left. Audits help, but an audit is a snapshot, and drift is continuous.\r\n\r\nThis talk presents an \"analytics as code\" framework built on just three hand-written files in a Git repository:\r\n\r\n- product-model.yaml: what the product is (entities, screens, funnels, squads);\r\n- tracking-plan.yaml: what we measure (events, properties, owners, governance tags);\r\n- validation-rules.yaml: what must hold true, checked on every commit.\r\n\r\nThrough a not-so-fictional SaaS case study, we follow a request end to end: a product manager files a ticket, an analytics engineer updates the YAML and opens a pull request, CI validates schema, naming, owners and PII rules, a lead reviews and merges, and the implementation guide and tag configuration are generated and deployed. One week later, a reconciliation audit catches what nobody announced: deprecated events still firing, events that were never in the plan, and git blame tells who, when and why.\r\n\r\nWe will also cover:\r\n\r\n- why executives never need to open Git (Git is infrastructure, not interface);\r\n- portability: one neutral spec, platform adapters for Matomo, GA4, Piano, Piwik Pro, PostHog and Snowplow, so changing platform stops being a rewrite;\r\n- automated tests that assert every tracked hit matches the plan, including consent-granted and consent-denied journeys.\r\n\r\nTakeaways: your tracking plan is infrastructure, pull requests enable governance (review, not restriction), and Git is your audit trail. Start small: one repository, three YAML specs, a handful of validation rules.", "recording_license": "", "do_not_record": false, "persons": [{"id": 216, "code": "WSH9YP", "public_name": "Julien Coquet", "biography": "Julien Coquet is a digital analytics consultant and evangelist at N7 Data, based in Mont\u00e9limar, France, with more than 25 years of experience in analytics. Julien is also an author, trainer, blogger and translator, and a regular speaker on the conference circuit, including Superweek, MeasureCamp and MeasureSummit. Away from data, Julien cooks and practises martial arts. At MatomoCamp 2027, Julien presents \"Analytics as Code\": how to keep a tracking plan in Git, validate it on every commit and generate implementations for Matomo and other analytics platforms from a single spec.", "answers": []}], "links": [], "attachments": [], "answers": []}], "Room 2": [{"id": 230, "guid": "eaed4ef3-8820-5b15-a1d2-1c5fca09a70b", "logo": "", "date": "2027-03-18T10:00:00+01:00", "start": "10:00", "duration": "00:30", "room": "Room 2", "slug": "matomocamp-2027-230-the-matomo-partner-programme-two-years-in-where-it-stands-and-what-comes-next", "url": "https://schedule.matomocamp.org/matomocamp-2027/talk/U8VKFD/", "title": "The Matomo Partner Programme, Two Years In: Where It Stands and What Comes Next", "subtitle": "", "track": "Business", "type": "Talk", "language": "en", "abstract": "Launched on April 1st, 2025, the Matomo Partner Programme is now up and running. An honest update: where it stands today, what it brings to agencies and Matomo users, what worked, what did not, and what comes next.", "description": "At MatomoCamp 2024 I explained why Matomo needed a strong partner programme. At MatomoCamp 2025 I shared its first months. This talk is the follow-up: a clear picture of the programme as it runs today.\r\n\r\nI will cover:\r\n- How the programme works today: partner types, requirements and benefits.\r\n- Who the partners are and which services they offer around Matomo.\r\n- What the programme changes for Matomo users looking for help with implementation, training or support.\r\n- What we learned since the launch: what worked, what we changed, and what we would do differently.\r\n- What comes next for the programme and for the Matomo ecosystem.\r\n\r\nThis talk is for agencies and consultants who are considering becoming a Matomo partner, and for Matomo users who want to know who can help them.", "recording_license": "", "do_not_record": false, "persons": [{"id": 198, "code": "PCM8GS", "public_name": "Ronan Chardonneau", "biography": "Partner Programme Manager at Matomo.\r\nCo-Organizer of MatomoCamp (2021\u20132027).\r\nAuthor of many books about Matomo so as videos on YouTube and Udemy courses.", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 234, "guid": "12fd554d-3d35-5a20-ac44-035c9dfb5ae3", "logo": "", "date": "2027-03-18T15:00:00+01:00", "start": "15:00", "duration": "00:30", "room": "Room 2", "slug": "matomocamp-2027-234-where-an-agent-must-stop-permission-boundaries-in-a-student-built-open-source-runtime", "url": "https://schedule.matomocamp.org/matomocamp-2027/talk/EYPMBQ/", "title": "Where an Agent Must Stop: Permission Boundaries in a Student-Built Open-Source Runtime", "subtitle": "", "track": "Artificial Intelligence", "type": "Talk", "language": "en", "abstract": "ClawForge is a UCSC open-source agent builder. This talk covers sandboxing, policy checks, human approval, and auditing; offers an action-boundary checklist; and clarifies limits of small-runtime security claims. No Matomo implementation claimed.", "description": "", "recording_license": "", "do_not_record": false, "persons": [{"id": 218, "code": "JGMK7A", "public_name": "Animesh Alang", "biography": "Animesh Alang is a University of California, Santa Cruz undergraduate (Computer Engineering + Technology & Information Management) and the founder and lead engineer of dino.study, an adaptive-learning platform. He also builds ClawForge, an open-source agent builder with a sandboxed runtime, policy controls, human-approval gates, and an audit dashboard. First-time speaker. https://dino.study \u00b7 https://github.com/animvsh/clawforge", "answers": []}], "links": [], "attachments": [], "answers": []}], "Room 3": [{"id": 231, "guid": "03f20962-281c-5b43-8b74-765a1f30abc9", "logo": "", "date": "2027-03-18T10:00:00+01:00", "start": "10:00", "duration": "00:30", "room": "Room 3", "slug": "matomocamp-2027-231-pas-un-hit-ne-se-perd-migrer-matomo-sans-trou-dans-les-stats", "url": "https://schedule.matomocamp.org/matomocamp-2027/talk/EJVDFL/", "title": "Pas un hit ne se perd : migrer Matomo sans trou dans les stats", "subtitle": "", "track": "System administration", "type": "Talk", "language": "en", "abstract": "Codes de suivi pas \u00e0 jour, applis mobiles, DNS lent : migrer Matomo fait perdre des visites. Tracking Forwarder, un plugin Matomo, capte ces hits et les rejoue sur la nouvelle instance, avec l'IP, le user-agent, la langue et la date d'origine.", "description": "Migrer des sites d'une instance Matomo \u00e0 une autre, \u00e7a a l'air simple jusqu'au moment de toucher au tracking. Les codes de suivi ne sont pas mis \u00e0 jour partout le m\u00eame jour, les applications mobiles gardent l'ancienne URL pendant des mois, et le DNS met du temps \u00e0 se propager. Pendant ce temps, les visites partent vers l'ancienne instance, ou nulle part.\r\n\r\nTracking Forwarder est un plugin Matomo qui capte ces hits \u00e0 la source et les rejoue en direct sur la nouvelle instance, avec l'IP, le user-agent, la langue et la date d'origine.", "recording_license": "", "do_not_record": false, "persons": [{"id": 215, "code": "USLFAS", "public_name": "Valentin Baraise", "biography": "Valentin Baraise, sp\u00e9cialiste DevOps, intervient au MatomoCamp depuis sa toute premi\u00e8re \u00e9dition en 2021. Chez Empreinte Digitale, Valentin a d\u00e9ploy\u00e9 et maintenu l'essentiel de l'infrastructure cloud SaaS, une exp\u00e9rience de terrain partag\u00e9e sur sc\u00e8ne : ce que demande c\u00f4t\u00e9 infrastructure le passage de Matomo de 100 \u00e0 1 million de visites (2021), et comment g\u00e9rer 1 000 sites, des dizaines de serveurs Matomo et plus de 100 utilisateurs depuis une seule plateforme (2023). Au MatomoCamp 2027, Valentin pr\u00e9sente Tracking Forwarder, un plugin Matomo qui permet de ne perdre aucun hit lors de la migration d'une instance Matomo vers une autre.\r\n\r\n**English**\r\n\r\nValentin Baraise is a DevOps engineer who has been speaking at MatomoCamp since its first edition in 2021. At Empreinte Digitale, Valentin deployed and maintained most of the cloud SaaS infrastructure, and has shared that hands-on experience on stage: what it takes on the infrastructure side to grow Matomo from 100 to 1 million visits (2021), and how to manage 1,000 websites, dozens of Matomo servers and more than 100 users from a single platform (2023). At MatomoCamp 2027, Valentin presents Tracking Forwarder, a Matomo plugin that makes sure no hit is lost when migrating from one Matomo instance to another.", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 233, "guid": "682f41fd-5757-5386-bc6d-0f6159ab11c9", "logo": "", "date": "2027-03-18T14:00:00+01:00", "start": "14:00", "duration": "00:30", "room": "Room 3", "slug": "matomocamp-2027-233-die-unsichtbaren-kufer-in-ga4-wie-matomo-die-30-70-datenlcke-bei-shopify-co-schliet", "url": "https://schedule.matomocamp.org/matomocamp-2027/talk/JWDGQR/", "title": "Die unsichtbaren K\u00e4ufer in GA4: Wie Matomo die 30\u201370% Datenl\u00fccke bei Shopify & Co. schlie\u00dft", "subtitle": "", "track": "Business", "type": "Talk", "language": "en", "abstract": "GA4 verliert 30-70% der Daten durch Cookie-Ablehnung. Das Problem: Die verbleibenden Daten zeigen ein v\u00f6llig verzerrtes Bild der Shopnutzung. Wir zeigen auf, wie Matomo parallel die Datenbasis rettet und echte Kausalit\u00e4t im E-Commerce beweist.", "description": "Wenn das Shopify-Dashboard und Google Analytics 4 v\u00f6llig unterschiedliche Zahlen anzeigen, stehen Online-H\u00e4ndler vor einem R\u00e4tsel. Durch Cookie-Ablehnungen verliert das clientseitige Tracking regelm\u00e4\u00dfig 30 % bis 70 % der Daten. Die Folge sind \u201eunsichtbare K\u00e4ufer\u201c und ein verzerrtes Bild der Shopnutzung, wodurch Budgetentscheidungen im Marketing zum reinen Gl\u00fccksspiel werden. \r\n\r\nIn diesem Vortrag wird ein datenanalytischer Blick auf dieses Ph\u00e4nomen geworfen. Vorgestellt wird ein praxiserprobter Infrastruktur-Blueprint, bei dem Matomo als einwilligungsfreie Parallel-Datenquelle l\u00e4uft, um die echten Zahlen ohne Performance-Verluste bei zeitgleicher Datenschutzkonformit\u00e4t zur\u00fcckzuholen. Aus der Perspektive einer promovierten Physikerin wird aufgezeigt, wie sich die statistischen L\u00fccken schlie\u00dfen lassen, um Scheinkorrelationen aufzudecken und herauszufinden, welche Marketing-Ma\u00dfnahmen tats\u00e4chlich f\u00fcr die Ums\u00e4tze verantwortlich sind.\r\n\r\nDie 3 wichtigsten Takeaways:\r\n1. Das verzerrte Bild: Warum fehlende Daten die Statistik im Shop verf\u00e4lschen und wie dieser Fehler identifiziert wird.\r\n2. Das Parallel-Setup: Wie cookieless Matomo Tracking nahtlos direkt an den Shopify-DataLayer angebunden wird.\r\n3. Echte Umsatztreiber: Die wissenschaftliche Methode, um die wahren Ursachen f\u00fcr Conversions und Ums\u00e4tze zu identifizieren.", "recording_license": "", "do_not_record": false, "persons": [{"id": 217, "code": "MENMNH", "public_name": "Dr. Mira Kossow", "biography": "Physicist, Full-Stack Dev, and Founder of https://sigmerra.de. Providing consulting and implementation for privacy-compliant Matomo tracking architectures.\r\n\r\nHappy to connect on LinkedIn: https://www.linkedin.com/in/dr-mira-kossow/", "answers": []}], "links": [], "attachments": [], "answers": []}]}}]}}}