<?xml version='1.0' encoding='utf-8' ?>
<iCalendar xmlns:pentabarf='http://pentabarf.org' xmlns:xCal='urn:ietf:params:xml:ns:xcal'>
    <vcalendar>
        <version>2.0</version>
        <prodid>-//Pentabarf//Schedule//EN</prodid>
        <x-wr-caldesc></x-wr-caldesc>
        <x-wr-calname></x-wr-calname>
        
        <vevent>
            <method>PUBLISH</method>
            <uid>LTHRME@@schedule.matomocamp.org</uid>
            <pentabarf:event-id></pentabarf:event-id>
            <pentabarf:event-slug>-LTHRME</pentabarf:event-slug>
            <pentabarf:title>Analytics as Code: Why Your Tracking Plan Belongs in Git</pentabarf:title>
            <pentabarf:subtitle></pentabarf:subtitle>
            <pentabarf:language>en</pentabarf:language>
            <pentabarf:language-code>en</pentabarf:language-code>
            <dtstart>20270318T140000</dtstart>
            <dtend>20270318T143000</dtend>
            <duration>0.03000</duration>
            <summary>Analytics as Code: Why Your Tracking Plan Belongs in Git</summary>
            <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>
            <class>PUBLIC</class>
            <status>CONFIRMED</status>
            <category>Talk</category>
            <url>https://schedule.matomocamp.org/matomocamp-2027/talk/LTHRME/</url>
            <location>Room 1</location>
            
            <attendee>Julien Coquet</attendee>
            
        </vevent>
        
        <vevent>
            <method>PUBLISH</method>
            <uid>U8VKFD@@schedule.matomocamp.org</uid>
            <pentabarf:event-id></pentabarf:event-id>
            <pentabarf:event-slug>-U8VKFD</pentabarf:event-slug>
            <pentabarf:title>The Matomo Partner Programme, Two Years In: Where It Stands and What Comes Next</pentabarf:title>
            <pentabarf:subtitle></pentabarf:subtitle>
            <pentabarf:language>en</pentabarf:language>
            <pentabarf:language-code>en</pentabarf:language-code>
            <dtstart>20270318T100000</dtstart>
            <dtend>20270318T103000</dtend>
            <duration>0.03000</duration>
            <summary>The Matomo Partner Programme, Two Years In: Where It Stands and What Comes Next</summary>
            <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>
            <class>PUBLIC</class>
            <status>CONFIRMED</status>
            <category>Talk</category>
            <url>https://schedule.matomocamp.org/matomocamp-2027/talk/U8VKFD/</url>
            <location>Room 2</location>
            
            <attendee>Ronan Chardonneau</attendee>
            
        </vevent>
        
        <vevent>
            <method>PUBLISH</method>
            <uid>EYPMBQ@@schedule.matomocamp.org</uid>
            <pentabarf:event-id></pentabarf:event-id>
            <pentabarf:event-slug>-EYPMBQ</pentabarf:event-slug>
            <pentabarf:title>Where an Agent Must Stop: Permission Boundaries in a Student-Built Open-Source Runtime</pentabarf:title>
            <pentabarf:subtitle></pentabarf:subtitle>
            <pentabarf:language>en</pentabarf:language>
            <pentabarf:language-code>en</pentabarf:language-code>
            <dtstart>20270318T150000</dtstart>
            <dtend>20270318T153000</dtend>
            <duration>0.03000</duration>
            <summary>Where an Agent Must Stop: Permission Boundaries in a Student-Built Open-Source Runtime</summary>
            <description></description>
            <class>PUBLIC</class>
            <status>CONFIRMED</status>
            <category>Talk</category>
            <url>https://schedule.matomocamp.org/matomocamp-2027/talk/EYPMBQ/</url>
            <location>Room 2</location>
            
            <attendee>Animesh Alang</attendee>
            
        </vevent>
        
        <vevent>
            <method>PUBLISH</method>
            <uid>EJVDFL@@schedule.matomocamp.org</uid>
            <pentabarf:event-id></pentabarf:event-id>
            <pentabarf:event-slug>-EJVDFL</pentabarf:event-slug>
            <pentabarf:title>Pas un hit ne se perd : migrer Matomo sans trou dans les stats</pentabarf:title>
            <pentabarf:subtitle></pentabarf:subtitle>
            <pentabarf:language>en</pentabarf:language>
            <pentabarf:language-code>en</pentabarf:language-code>
            <dtstart>20270318T100000</dtstart>
            <dtend>20270318T103000</dtend>
            <duration>0.03000</duration>
            <summary>Pas un hit ne se perd : migrer Matomo sans trou dans les stats</summary>
            <description>Migrer des sites d&#x27;une instance Matomo à une autre, ça a l&#x27;air simple jusqu&#x27;au moment de toucher au tracking. Les codes de suivi ne sont pas mis à jour partout le même jour, les applications mobiles gardent l&#x27;ancienne URL pendant des mois, et le DNS met du temps à se propager. Pendant ce temps, les visites partent vers l&#x27;ancienne instance, ou nulle part.

Tracking Forwarder est un plugin Matomo qui capte ces hits à la source et les rejoue en direct sur la nouvelle instance, avec l&#x27;IP, le user-agent, la langue et la date d&#x27;origine.</description>
            <class>PUBLIC</class>
            <status>CONFIRMED</status>
            <category>Talk</category>
            <url>https://schedule.matomocamp.org/matomocamp-2027/talk/EJVDFL/</url>
            <location>Room 3</location>
            
            <attendee>Valentin Baraise</attendee>
            
        </vevent>
        
        <vevent>
            <method>PUBLISH</method>
            <uid>JWDGQR@@schedule.matomocamp.org</uid>
            <pentabarf:event-id></pentabarf:event-id>
            <pentabarf:event-slug>-JWDGQR</pentabarf:event-slug>
            <pentabarf:title>Die unsichtbaren Käufer in GA4: Wie Matomo die 30–70% Datenlücke bei Shopify &amp; Co. schließt</pentabarf:title>
            <pentabarf:subtitle></pentabarf:subtitle>
            <pentabarf:language>en</pentabarf:language>
            <pentabarf:language-code>en</pentabarf:language-code>
            <dtstart>20270318T140000</dtstart>
            <dtend>20270318T143000</dtend>
            <duration>0.03000</duration>
            <summary>Die unsichtbaren Käufer in GA4: Wie Matomo die 30–70% Datenlücke bei Shopify &amp; Co. schließt</summary>
            <description>Wenn das Shopify-Dashboard und Google Analytics 4 völlig unterschiedliche Zahlen anzeigen, stehen Online-Händler vor einem Rätsel. Durch Cookie-Ablehnungen verliert das clientseitige Tracking regelmäßig 30 % bis 70 % der Daten. Die Folge sind „unsichtbare Käufer“ und ein verzerrtes Bild der Shopnutzung, wodurch Budgetentscheidungen im Marketing zum reinen Glücksspiel werden. 

In diesem Vortrag wird ein datenanalytischer Blick auf dieses Phänomen geworfen. Vorgestellt wird ein praxiserprobter Infrastruktur-Blueprint, bei dem Matomo als einwilligungsfreie Parallel-Datenquelle läuft, um die echten Zahlen ohne Performance-Verluste bei zeitgleicher Datenschutzkonformität zurückzuholen. Aus der Perspektive einer promovierten Physikerin wird aufgezeigt, wie sich die statistischen Lücken schließen lassen, um Scheinkorrelationen aufzudecken und herauszufinden, welche Marketing-Maßnahmen tatsächlich für die Umsätze verantwortlich sind.

Die 3 wichtigsten Takeaways:
1. Das verzerrte Bild: Warum fehlende Daten die Statistik im Shop verfä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ür Conversions und Umsätze zu identifizieren.</description>
            <class>PUBLIC</class>
            <status>CONFIRMED</status>
            <category>Talk</category>
            <url>https://schedule.matomocamp.org/matomocamp-2027/talk/JWDGQR/</url>
            <location>Room 3</location>
            
            <attendee>Dr. Mira Kossow</attendee>
            
        </vevent>
        
    </vcalendar>
</iCalendar>
