<?xml version='1.0' encoding='utf-8' ?>
<!-- Made with love by pretalx v2023.1.3. -->
<schedule>
    <generator name="pretalx" version="2023.1.3" />
    <version>0.4</version>
    <conference>
        <acronym>matomocamp-2027</acronym>
        <title>MatomoCamp 2027</title>
        <start>2027-03-18</start>
        <end>2027-03-18</end>
        <days>1</days>
        <timeslot_duration>00:05</timeslot_duration>
        <base_url>https://schedule.matomocamp.org/matomocamp-2027/schedule/</base_url>
        <time_zone_name>Europe/Madrid</time_zone_name>
    </conference>
    <day index='1' date='2027-03-18' start='2027-03-18T04:00:00+01:00' end='2027-03-19T03:59:00+01:00'>
        <room name='Room 1'>
            <event guid='381e2c09-6c71-5b36-beda-3375cda6b48a' id='232'>
                <date>2027-03-18T14:00:00+01:00</date>
                <start>14:00</start>
                <duration>00:30</duration>
                <room>Room 1</room>
                <slug>matomocamp-2027-232-analytics-as-code-why-your-tracking-plan-belongs-in-git</slug>
                <url>https://schedule.matomocamp.org/matomocamp-2027/talk/LTHRME/</url>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <title>Analytics as Code: Why Your Tracking Plan Belongs in Git</title>
                <subtitle></subtitle>
                <track>Digital Analytics</track>
                <type>Talk</type>
                <language>en</language>
                <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.</abstract>
                <description>Where does your analytics strategy actually live? Scattered across chat channels, in a &quot;Tracking Plan v3 - FINAL&quot; 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.

This talk presents an &quot;analytics as code&quot; framework built on just three hand-written files in a Git repository:

- product-model.yaml: what the product is (entities, screens, funnels, squads);
- tracking-plan.yaml: what we measure (events, properties, owners, governance tags);
- validation-rules.yaml: what must hold true, checked on every commit.

Through 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.

We will also cover:

- why executives never need to open Git (Git is infrastructure, not interface);
- portability: one neutral spec, platform adapters for Matomo, GA4, Piano, Piwik Pro, PostHog and Snowplow, so changing platform stops being a rewrite;
- automated tests that assert every tracked hit matches the plan, including consent-granted and consent-denied journeys.

Takeaways: 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.</description>
                <logo></logo>
                <persons>
                    <person id='216'>Julien Coquet</person>
                </persons>
                <links></links>
                <attachments></attachments>
            </event>
            
        </room>
        <room name='Room 2'>
            <event guid='eaed4ef3-8820-5b15-a1d2-1c5fca09a70b' id='230'>
                <date>2027-03-18T10:00:00+01:00</date>
                <start>10:00</start>
                <duration>00:30</duration>
                <room>Room 2</room>
                <slug>matomocamp-2027-230-the-matomo-partner-programme-two-years-in-where-it-stands-and-what-comes-next</slug>
                <url>https://schedule.matomocamp.org/matomocamp-2027/talk/U8VKFD/</url>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <title>The Matomo Partner Programme, Two Years In: Where It Stands and What Comes Next</title>
                <subtitle></subtitle>
                <track>Business</track>
                <type>Talk</type>
                <language>en</language>
                <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.</abstract>
                <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.

I will cover:
- How the programme works today: partner types, requirements and benefits.
- Who the partners are and which services they offer around Matomo.
- What the programme changes for Matomo users looking for help with implementation, training or support.
- What we learned since the launch: what worked, what we changed, and what we would do differently.
- What comes next for the programme and for the Matomo ecosystem.

This 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.</description>
                <logo></logo>
                <persons>
                    <person id='198'>Ronan Chardonneau</person>
                </persons>
                <links></links>
                <attachments></attachments>
            </event>
            <event guid='12fd554d-3d35-5a20-ac44-035c9dfb5ae3' id='234'>
                <date>2027-03-18T15:00:00+01:00</date>
                <start>15:00</start>
                <duration>00:30</duration>
                <room>Room 2</room>
                <slug>matomocamp-2027-234-where-an-agent-must-stop-permission-boundaries-in-a-student-built-open-source-runtime</slug>
                <url>https://schedule.matomocamp.org/matomocamp-2027/talk/EYPMBQ/</url>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <title>Where an Agent Must Stop: Permission Boundaries in a Student-Built Open-Source Runtime</title>
                <subtitle></subtitle>
                <track>Artificial Intelligence</track>
                <type>Talk</type>
                <language>en</language>
                <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.</abstract>
                <description></description>
                <logo></logo>
                <persons>
                    <person id='218'>Animesh Alang</person>
                </persons>
                <links></links>
                <attachments></attachments>
            </event>
            
        </room>
        <room name='Room 3'>
            <event guid='03f20962-281c-5b43-8b74-765a1f30abc9' id='231'>
                <date>2027-03-18T10:00:00+01:00</date>
                <start>10:00</start>
                <duration>00:30</duration>
                <room>Room 3</room>
                <slug>matomocamp-2027-231-pas-un-hit-ne-se-perd-migrer-matomo-sans-trou-dans-les-stats</slug>
                <url>https://schedule.matomocamp.org/matomocamp-2027/talk/EJVDFL/</url>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <title>Pas un hit ne se perd : migrer Matomo sans trou dans les stats</title>
                <subtitle></subtitle>
                <track>System administration</track>
                <type>Talk</type>
                <language>en</language>
                <abstract>Codes de suivi pas &#224; 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&apos;IP, le user-agent, la langue et la date d&apos;origine.</abstract>
                <description>Migrer des sites d&apos;une instance Matomo &#224; une autre, &#231;a a l&apos;air simple jusqu&apos;au moment de toucher au tracking. Les codes de suivi ne sont pas mis &#224; jour partout le m&#234;me jour, les applications mobiles gardent l&apos;ancienne URL pendant des mois, et le DNS met du temps &#224; se propager. Pendant ce temps, les visites partent vers l&apos;ancienne instance, ou nulle part.

Tracking Forwarder est un plugin Matomo qui capte ces hits &#224; la source et les rejoue en direct sur la nouvelle instance, avec l&apos;IP, le user-agent, la langue et la date d&apos;origine.</description>
                <logo></logo>
                <persons>
                    <person id='215'>Valentin Baraise</person>
                </persons>
                <links></links>
                <attachments></attachments>
            </event>
            <event guid='682f41fd-5757-5386-bc6d-0f6159ab11c9' id='233'>
                <date>2027-03-18T14:00:00+01:00</date>
                <start>14:00</start>
                <duration>00:30</duration>
                <room>Room 3</room>
                <slug>matomocamp-2027-233-die-unsichtbaren-kufer-in-ga4-wie-matomo-die-30-70-datenlcke-bei-shopify-co-schliet</slug>
                <url>https://schedule.matomocamp.org/matomocamp-2027/talk/JWDGQR/</url>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <title>Die unsichtbaren K&#228;ufer in GA4: Wie Matomo die 30&#8211;70% Datenl&#252;cke bei Shopify &amp; Co. schlie&#223;t</title>
                <subtitle></subtitle>
                <track>Business</track>
                <type>Talk</type>
                <language>en</language>
                <abstract>GA4 verliert 30-70% der Daten durch Cookie-Ablehnung. Das Problem: Die verbleibenden Daten zeigen ein v&#246;llig verzerrtes Bild der Shopnutzung. Wir zeigen auf, wie Matomo parallel die Datenbasis rettet und echte Kausalit&#228;t im E-Commerce beweist.</abstract>
                <description>Wenn das Shopify-Dashboard und Google Analytics 4 v&#246;llig unterschiedliche Zahlen anzeigen, stehen Online-H&#228;ndler vor einem R&#228;tsel. Durch Cookie-Ablehnungen verliert das clientseitige Tracking regelm&#228;&#223;ig 30 % bis 70 % der Daten. Die Folge sind &#8222;unsichtbare K&#228;ufer&#8220; und ein verzerrtes Bild der Shopnutzung, wodurch Budgetentscheidungen im Marketing zum reinen Gl&#252;cksspiel werden. 

In diesem Vortrag wird ein datenanalytischer Blick auf dieses Ph&#228;nomen geworfen. Vorgestellt wird ein praxiserprobter Infrastruktur-Blueprint, bei dem Matomo als einwilligungsfreie Parallel-Datenquelle l&#228;uft, um die echten Zahlen ohne Performance-Verluste bei zeitgleicher Datenschutzkonformit&#228;t zur&#252;ckzuholen. Aus der Perspektive einer promovierten Physikerin wird aufgezeigt, wie sich die statistischen L&#252;cken schlie&#223;en lassen, um Scheinkorrelationen aufzudecken und herauszufinden, welche Marketing-Ma&#223;nahmen tats&#228;chlich f&#252;r die Ums&#228;tze verantwortlich sind.

Die 3 wichtigsten Takeaways:
1. Das verzerrte Bild: Warum fehlende Daten die Statistik im Shop verf&#228;lschen und wie dieser Fehler identifiziert wird.
2. Das Parallel-Setup: Wie cookieless Matomo Tracking nahtlos direkt an den Shopify-DataLayer angebunden wird.
3. Echte Umsatztreiber: Die wissenschaftliche Methode, um die wahren Ursachen f&#252;r Conversions und Ums&#228;tze zu identifizieren.</description>
                <logo></logo>
                <persons>
                    <person id='217'>Dr. Mira Kossow</person>
                </persons>
                <links></links>
                <attachments></attachments>
            </event>
            
        </room>
        
    </day>
    
</schedule>
