Configure Matomo as a Source in your Pipeline

Perform the following steps to configure your Matomo Source:

1. Click Pipelines in the Navigation Bar.

2. Click + Create Pipeline in the Pipelines List View.

3. On the Select Source Type page, select Matomo.

4. On the Select Destination Type page, select the type of Destination you want to use.

5. In the Configure Source screen, specify the following:

   

   • Source Name: A unique name for your Source, not exceeding 255 characters. For example, Matomo Source.

   • In the Connect to Matomo section, specify the following:

     • Subdomain: The part before .matomo.cloud in the URL of your Matomo Cloud account. For example, acme for https://acme.matomo.cloud. If you enter the full URL, Hevo uses only the subdomain from it. You cannot change this value after the Pipeline is created.

     • Auth Token: The Auth Token that you created in your Matomo account. You can change this value after the Pipeline is created.

6. Click Test & Continue to test the connection to your Matomo Source. Once the test is successful, you can proceed to set up your Destination.

   When you click this button, Hevo checks that it can connect to the Matomo Reporting API of your account with the specified subdomain and Auth Token.

---

Data Replication

Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline.

Hevo ingests the following types of data from your Source objects:

• Historical Data: The first run of the Pipeline ingests the reports of the last 365 days for each site in your Matomo account and loads them into the Destination.

• Incremental Data: Once the historical load is complete, new and updated report data is ingested as per the sync frequency.

Hevo ingests incremental data for the objects as follows:

• Event Action, Event Category, Event Name, and Visitor Interest: These objects contain daily reports. In each run, Hevo ingests the reports from the most recent date ingested for each site up to the current date. As a result, the report of the current day is updated in each run until the day ends.

• Insight Overview and Visit Time: These objects contain reports for a date range, which is stored in the date field in the format start date,end date. The first run ingests the report for the last 365 days. Each subsequent run ingests the report for the range from the end date of the previous run to the current date. The records of earlier date ranges are retained in the Destination. Each record is the report for its own date range, so filter on a single date value when you query these objects, instead of adding up the records of different date ranges.

• Multi Site: Hevo ingests the entire data of this object in each run. The visit, action, page view, and revenue values in this object are for the last 365 days.

Note: You can create a Pipeline with this Source only using the Merge load mode. The Append mode is not supported for this Source.

Currently, Matomo Cloud enforces a rate limit of 350 requests per minute or 2,000 requests every ten minutes, whichever is reached first, for each IP address. If this limit is exceeded, a rate limit exception occurs. To understand how Hevo handles such scenarios, read Handling Rate Limit Exceptions.

---

Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.

---

Data Model

The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:

---