Flutter plugin: matomo_tracker is sending information, but there is nothing logged

Describe the bug
I set up a basic installation of a flutter app, added some parts of the example code. The console shows expected output:

[Matomo] Matomo Initialized: firstVisit=2024-03-27 09:30:05.789Z; lastVisit=2024-03-27 09:36:08.090201Z; visitCount=2; visitorId=null; contentBase=https://com.example.flutter_new_build_gradle; resolution=1080.0x2208.0; userAgent=Android 11 (SDK 30), Google sdk_gphone_x86
[Matomo] Processing queue 1
[Matomo]  -> {requests: [?idsite=4&rec=1&new_visit=1&action_name=Flutter+Demo+Home+Page&url=https%3A%2F%2Fcom.example.flutter_new_build_gradle%2Fhomepage%3F&_id=77df4c6fbe6349bd&rand=568357132&apiv=1&_idvc=2&_viewts=1711532168&_idts=1711531805&res=1080x2208&h=9&m=36&s=9&cookie=1&ua=Android+11+%28SDK+30%29%2C+Google+sdk_gphone_x86&lang=en_US&uid=Nelson+Pandela&pv_id=V1Ex5r&cdt=2024-03-27T09%3A36%3A09.163850Z]}
[Matomo]  <- 200
[Matomo] Processing queue 2
[Matomo]  -> {requests: [?idsite=4&rec=1&ca=1&url=https%3A%2F%2Fcom.example.flutter_new_build_gradle%2Fhomepage%3F&_id=77df4c6fbe6349bd&rand=122132530&apiv=1&_idvc=2&_viewts=1711532168&_idts=1711531805&res=1080x2208&h=9&m=36&s=19&cookie=1&ua=Android+11+%28SDK+30%29%2C+Google+sdk_gphone_x86&lang=en_US&uid=Nelson+Pandela&pv_id=V1Ex5r&e_c=Main&e_a=Click&e_n=IncrementCounter&cdt=2024-03-27T09%3A36%3A19.000227Z, ?idsite=4&rec=1&ca=1&url=https%3A%2F%2Fcom.example.flutter_new_build_gradle%2Fhomepage%3F&_id=77df4c6fbe6349bd&rand=97035459&apiv=1&_idvc=2&_viewts=1711532168&_idts=1711531805&res=1080x2208&h=9&m=36&s=26&cookie=1&ua=Android+11+%28SDK+30%29%2C+Google+sdk_gphone_x86&lang=en_US&uid=Nelson+Pandela&pv_id=V1Ex5r&e_c=Main&e_a=Click&e_n=IncrementCounter&cdt=2024-03-27T09%3A36%3A26.050347Z]}
[Matomo]  <- 200
[Matomo] Processing queue 0

The ← 200 indicates that the server received the post request successfully.

On our Matomo installation I do not see any logging though. It appears as if nothing has been received.
I suspect that this is not a problem with the library, but I also set up tracking for a website on the same matomo installation and it works fine.

Any hints, how I could progress with debugging the problem, or if I might need to fulfill some steps in matomo would be very appreciated :slight_smile:

To Reproduce
Steps to reproduce the behavior:

My app code:

import 'package:flutter/material.dart';
import 'package:matomo_tracker/matomo_tracker.dart';

const String _matomoEndpoint = 'https://MYMATOMOPAGENAME.com/';
const int _matomoSiteId = 4;
const _testUserId = 'Nelson Pandela';

// Use this as dispatchSettings in MatomoTracker.instance.initialize()
// to test persistent actions. Then run the example, cause some actions
// by clicking around, close the example within 5min to prevent the
// dispatchment of the actions, run the example again, wait at least 5min,
// finally check the Matomo dashboard to see if all actions are there.
const DispatchSettings dispatchSettingsEndToEndTest =
    DispatchSettings.persistent(dequeueInterval: Duration(minutes: 5));

void main() async {
  await MatomoTracker.instance.initialize(
    siteId: _matomoSiteId, url: _matomoEndpoint, verbosityLevel: Level.all,
    // dispatchSettings: dispatchSettingsEndToEndTest,
  runApp(const MyApp());

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  // This widget is the root of your application.
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      navigatorObservers: [matomoObserver],
      theme: ThemeData(
        // This is the theme of your application.
        // TRY THIS: Try running your application with "flutter run". You'll see
        // the application has a purple toolbar. Then, without quitting the app,
        // try changing the seedColor in the colorScheme below to Colors.green
        // and then invoke "hot reload" (save your changes or press the "hot
        // reload" button in a Flutter-supported IDE, or press "r" if you used
        // the command line to start the app).
        // Notice that the counter didn't reset back to zero; the application
        // state is not lost during the reload. To reset the state, use hot
        // restart instead.
        // This works for code too, not just values: Most code changes can be
        // tested with just a hot reload.
        colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
        useMaterial3: true,
      home: const MyHomePage(title: 'Flutter Demo Home Page'),

class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key, required this.title});

  // This widget is the home page of your application. It is stateful, meaning
  // that it has a State object (defined below) that contains fields that affect
  // how it looks.

  // This class is the configuration for the state. It holds the values (in this
  // case the title) provided by the parent (in this case the App widget) and
  // used by the build method of the State. Fields in a Widget subclass are
  // always marked "final".

  final String title;

  State<MyHomePage> createState() => _MyHomePageState();

class _MyHomePageState extends State<MyHomePage> with TraceableClientMixin {
  int _counter = 0;

  void _incrementCounter() {
      eventInfo: EventInfo(
        category: 'Main',
        action: 'Click',
        name: 'IncrementCounter',
    setState(() {
      // This call to setState tells the Flutter framework that something has
      // changed in this State, which causes it to rerun the build method below
      // so that the display can reflect the updated values. If we changed
      // _counter without calling setState(), then the build method would not be
      // called again, and so nothing would appear to happen.

  Widget build(BuildContext context) {
    // This method is rerun every time setState is called, for instance as done
    // by the _incrementCounter method above.
    // The Flutter framework has been optimized to make rerunning build methods
    // fast, so that you can just rebuild anything that needs updating rather
    // than having to individually change instances of widgets.
    return Scaffold(
      appBar: AppBar(
        // TRY THIS: Try changing the color here to a specific color (to
        // Colors.amber, perhaps?) and trigger a hot reload to see the AppBar
        // change color while the other colors stay the same.
        backgroundColor: Theme.of(context).colorScheme.inversePrimary,
        // Here we take the value from the MyHomePage object that was created by
        // the App.build method, and use it to set our appbar title.
        title: Text(widget.title),
      body: Center(
        // Center is a layout widget. It takes a single child and positions it
        // in the middle of the parent.
        child: Column(
          // Column is also a layout widget. It takes a list of children and
          // arranges them vertically. By default, it sizes itself to fit its
          // children horizontally, and tries to be as tall as its parent.
          // Column has various properties to control how it sizes itself and
          // how it positions its children. Here we use mainAxisAlignment to
          // center the children vertically; the main axis here is the vertical
          // axis because Columns are vertical (the cross axis would be
          // horizontal).
          // TRY THIS: Invoke "debug painting" (choose the "Toggle Debug Paint"
          // action in the IDE, or press "p" in the console), to see the
          // wireframe for each widget.
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            const Text(
              'You have pushed the button this many times:',
              style: Theme.of(context).textTheme.headlineMedium,
      floatingActionButton: FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'Increment',
        child: const Icon(Icons.add),
      ), // This trailing comma makes auto-formatting nicer for build methods.

  String get actionName => widget.title;

  String? get path => '/homepage';

Expected behavior
I expect Matomo to log the received post request

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser: Firefox
  • Version 124.0.1

Smartphone (please complete the following information):

  • Device: Emulator, Smartphone was also tested inbetween
  • OS: Android 11

Additional context
We currently use Matomo 5.0.2

If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser: Firefox
  • Version 124.0.1

Smartphone (please complete the following information):

  • Device: Emulator, Smartphone was also tested inbetween
  • OS: Android 11

Additional context
We currently use Matomo 5.0.2

The problem was that we needed to use

const String _matomoEndpoint = 'https://MYMATOMOPAGENAME.com/matomo.php';

instead of

const String _matomoEndpoint = 'https://MYMATOMOPAGENAME.com/';
1 Like