Nimbata’s Matomo integration sends your calls and form submissions to your own Matomo, self-hosted or Matomo Cloud, as goal conversions. When Nimbata’s tracking code saw the visitor’s Matomo cookie, the conversion lands on the visit that brought the caller, next to the pages they viewed, so Matomo’s reports credit the channel and campaign behind each call. Each conversion sends to one goal of one Matomo site, and a workflow decides which calls and forms are sent.
Before you start
- Permissions
- Matomo, under Integrations, in your Nimbata role
- A Matomo, self-hosted or Matomo Cloud, that answers over https from the internet.
- A Matomo user with write or admin access to the sites you want to send to, to create the API key.
- Matomo’s tracking code and Nimbata’s tracking code on your website, to join calls and forms to the visits that brought them. Without them, conversions still reach Matomo, each as a visitor of its own.
- The Matomo tile on your Integrations page. Matomo comes with the same plans as Google Ads. On a plan that does not include it, Go to integration offers an upgrade instead.
- The Nimbata project whose calls and forms you want to send: the integration is set up per project.
Connect Matomo
Matomo has no sign-in. Nimbata sends conversions with an API key that you create in Matomo, to the address of your Matomo.
Open the Matomo integration
Go to Integrations and click Go to integration on the Matomo tile (1).
Integrations
MatomoSend calls and form submissions to Matomo as goal conversions, joined to the visit where possible.Open the Matomo tile (1). Create an API key in Matomo
In Matomo, click the gear icon (Administration), then go to Personal > Security and click Create new token. Matomo asks for your password. Give the token a description (such as
Nimbata) and copy it: Matomo shows it only once.Note
The key works with the access of the Matomo user who created it. Create it as a user with write or admin access to the sites you send to, and keep that user’s access.
Enter the address and the key
Enter your Matomo’s address in Matomo address (1), the address you open Matomo at, such as
https://your-name.matomo.cloudorhttps://matomo.example.com. A copied address that ends inindex.phpworks too. Paste the key in API key (2) and click (3). Nimbata checks the key with Matomo and says “Matomo connected.”Matomo
Send calls and form submissions to Matomo as goal conversions, joined to the visit where possible.
Account Credentials:Calls and form submissions are sent to your Matomo as goal conversions. Enter the address of your Matomo and an API key.
Matomo addresshttps://matomo.example.com1API keyPaste a Matomo API key2Enter the address (1) and the API key (2), then click Connect (3).
Once connected, the card shows Connected to and your Matomo’s address, with , Replace key and Disconnect. Check connection reads from Matomo only and says “Matomo accepted the API key.” when all is well.
Add your conversions
A conversion sends calls and forms to one goal of one Matomo site. Click and fill in the new row. A row is saved as soon as it has a site and a goal, and every change after that saves on its own: Nimbata says “Matomo conversions saved.”
Choose the site
In Site (1), choose the Matomo site the calls and forms come from. The list shows the sites the API key can send to: those where its user has write or admin access.
Choose the goal, or create one
In Goal (2), choose the Matomo goal a call or form counts as. If the site has no goal for calls yet, click Create Phone call goal (3): Nimbata adds a goal named “Phone call” to the site in Matomo, or picks the site’s “Phone call” goal if it has one.
To use a goal of your own, create it in Matomo first (Administration > Websites > Goals > Add a new Goal). Set Goal is triggered to manually, and allow the goal to be converted more than once per visit, so two calls in one visit both count. Then click Refresh sites & goals above the conversions to see it in the list.
Choose whether to send the value
Tick Include value (4) to send the call’s or form’s value as the conversion’s revenue in Matomo. A call or form without a value is sent without revenue.
Each conversion counts a call or form as a conversion of one goal on one Matomo site, joined to the caller’s visit where the tracking code saw it. A workflow step chooses which calls and forms reach these conversions.
example.com · Phone callSiteexample.com1GoalPhone call24Include valueCreate Phone call goal3Choose the site (1) and the goal (2), or create a Phone call goal (3), and choose whether to include the value (4).
A project can have up to 20 Matomo conversions, one per site and goal. A second row for the same site and goal says “Another conversion already sends to this goal of this site.” and is not saved.
How calls are joined to visits
Matomo knows a visitor by its visitor cookie, which Matomo’s tracking code sets on your website. When you save a conversion, Nimbata adds that cookie to the cookies its tracking code collects (it shows in Organize › Fields as _pk_id.<site id>.*) and republishes your tracking code. From then on, each call and form carries the visitor’s Matomo cookie, and its conversion lands on that visitor’s visit.
If Nimbata cannot collect the cookie, the page says “Calls are sent to Matomo, but not yet joined to the visitor’s visit.” with the reason, such as “Visitor matching starts once the tracking code is published.”, and a button. Changing the tracking code needs Tracking Code access, so if the page asks for it, someone with that access presses Retry.
Note
Calls and forms are sent even when they cannot be joined to a visit: each one is then a visitor of its own in Matomo.
What Matomo receives
For each call or form a workflow sends to a conversion, Matomo receives one goal conversion with:
- The time of the call or form. A call counts at the time it started, and a form when it was submitted, even when you send it later with a re-run.
- The visitor. With the visitor’s Matomo cookie, the conversion joins that visitor’s visit, if it is still open: Matomo starts a new visit after 30 minutes without activity. Without the cookie, the call or form is a visitor of its own.
- The page and the referrer of the visit, and the visitor’s IP address and browser, when Nimbata knows them. When a call or form starts a new visit in Matomo, Matomo takes its campaign from the page’s UTM tags.
- The revenue, when the conversion has Include value and the call or form has a value.
A call to a number that is not on your website (a static number) has no visit: it is a visitor of its own, shown in Matomo as a direct entry from a mobile Chrome browser, located where Nimbata’s servers are, since such a call has no browser or IP address of its own. Nothing derived from the caller’s phone number is sent.
Each call or form is sent to each conversion once. A send that fails is not tried again on its own: see Re-run calls that did not reach Matomo.
Send calls and forms with a workflow
Nothing is sent to Matomo until a workflow sends it. For calls, create a workflow on Inbound Call that fires when the Call Ends, add a Matomo action and choose its conversions, then click (1). Each conversion is listed by its goal and site, such as Phone call · example.com. Add filters before the action to send only some calls, such as calls with a value.
For forms, create a workflow on Form Submission that fires when a form is received, and add a Matomo action the same way. Matomo is offered in inbound call and form workflows. It is not offered on Call Starts, since a call is counted once and its value is known only when it ends, nor on outbound calls.
Detailed guide: Conversion workflows.
Check it worked
The Matomo page now shows Used in 1 workflow, and the conversion lists the workflow that sends to it.
Matomo
Send calls and form submissions to Matomo as goal conversions, joined to the visit where possible.
Used in 1 workflow
Events are sent when an inbound call ends.
Then, in Matomo, open Visitors > Visits Log for the day of the call. Each call or form shows as a goal conversion, with its revenue, on the visit that brought it or as a visit of its own. The Visits Log can take a few minutes to show it. The Goals reports count the conversions once Matomo has processed the day, which for a past day (a re-run) can take some hours.
Re-run calls that did not reach Matomo
A call or form that did not reach Matomo (a rejected key, Matomo not answering, Matomo disconnected for a while) is not sent again on its own. Once the cause is fixed, re-run the workflow for those days (Re-run a workflow). Only the calls and forms Matomo has not accepted yet are sent, each at its original time.
Warning
Leave Force re-run integrations off when you re-run a Matomo workflow. With it on, Nimbata sends calls and forms Matomo already accepted again, and Matomo counts them twice.
Troubleshooting
Nimbata does not accept the address or the key
- “No Matomo answered at this address”: check the address, for example
https://matomo.example.com. Matomo must answer over https from the internet. - “An API key has no spaces”: copy the key again from Matomo and paste it with nothing before or after it.
- “Matomo rejected the API key, or the key lacks access to the site”: create a new key in Matomo (Personal > Security) and save it.
- “This API key cannot write to any Matomo site”: create the key as a Matomo user with write or admin access to the site.
- “This Matomo does not have the sites your conversions send to”: the conversions belong to another Matomo, or a site was renamed in Matomo. Connect the Matomo they belong to, or remove those conversions first.
The page says Matomo rejected the API key
The key was deleted in Matomo, expired, or its user lost access. The card shows a warning in place of its green check: “Matomo rejected the API key, or the key lacks access to the sites.” Nimbata sends no email about it, so check the page when conversions stop showing in Matomo.
- Create a new key in Matomo (Personal > Security > Create new token).
- On the Matomo page, click Replace key, paste the new key and click .
- Re-run the workflows for the days the key was rejected, so those calls and forms reach Matomo (see Re-run calls that did not reach Matomo).
A conversion shows Site not writable or Goal not found
After Check connection, Nimbata says “Some conversions below need attention.” and marks each conversion it cannot send:
- Site not writable: the site was deleted in Matomo, or the key’s user lost write access to it. Give the user access again, or choose another site.
- Goal not found: the goal was deleted in Matomo. Choose another goal, or click Create Phone call goal.
A goal you created in Matomo is not in the list
The page reads the sites and goals when it opens. Click Refresh sites & goals above the conversions to read them again.
Calls are not joined to the visit
Each call or form shows in Matomo as a visit of its own instead of joining the visitor’s visit:
- Check the warning on the Matomo page, and press Retry if it offers it.
- Check that Matomo’s tracking code and Nimbata’s tracking code are both on the page the caller visited, and that Nimbata’s tracking code is published (Install the tracking code).
- Load Matomo’s tracking code before Nimbata’s. Nimbata reads the visitor cookie when the visit starts, so a cookie Matomo sets later is not always picked up.
- A visitor who blocked cookies, or a Matomo set up without cookies, has no visitor cookie to read.
- A call more than 30 minutes after the visitor’s last page view starts a new visit in Matomo.
Matomo counts some calls twice
A workflow was re-run with Force re-run integrations on, which sends calls and forms Matomo already accepted again. Matomo cannot tell them apart from new ones. Keep the switch off for Matomo workflows.
You disconnected Matomo for a while
While Matomo is disconnected, the conversions stay but send nothing. Connect the same Matomo again: Nimbata accepts it only when it has the sites your conversions send to, under the same number and name. Then re-run the workflows for the days it was disconnected, so those calls and forms reach Matomo.
You cannot remove a conversion
Nimbata shows Workflow Attached with the workflows that send to it. Remove the conversion from those workflows’ Matomo action first, then remove it.