# evoOrigin or a third-party analytics tool

> Measuring where your visits come from inside Joomla with evoOrigin versus an external analytics tool: what data each approach keeps and what evoOrigin does not do.

# evoOrigin or a third-party analytics tool

## When each approach fits

**A third-party analytics tool** fits when you need to see behaviour inside the site: journeys between pages, events, funnels, goals, cross-campaign reports, or integration with ad platforms. It is a product built for analysis, and in that it goes much further than evoOrigin.

**evoOrigin** fits when the question is narrower: where did this visitor or this lead come from (source, medium, campaign, referrer), with the minimum of data and none of it leaving the site. It suits anyone who wants to attribute a lead to its origin, or to keep anonymous monthly statistics, without setting up an analytics platform.

They are not mutually exclusive. If you already use an external tool, you can still run evoOrigin for lead attribution inside your own database.

## Comparison

| Criterion | evoOrigin | Third-party analytics |
| --- | --- | --- |
| Getting started | Install the package and session capture works straight away. Database logging ships off and is enabled level by level. | An account, a tracking code on the site and, usually, its own configuration. \[PENDIENTE: verificar según la herramienta\] |
| Data stored | In the site's database: visits per session (90 days by default), lead attribution (24 months) and anonymous monthly statistics. No data leaves the site. | In the external service, by definition of the approach. What is collected and for how long depends on the tool and its configuration. \[PENDIENTE: verificar según la herramienta\] |
| What it measures | Origin: source, medium, campaign, referrer, landing page and click identifiers if enabled. | This is the approach that measures most: behaviour, events and conversions. |
| Attribution of a specific lead | A per-lead summary with first and last origin, visits and dates, readable in the panel, the REST API and evoMCP. | Depends on how the form and the tool are connected. \[PENDIENTE: verificar según la herramienta\] |
| Maintenance | Extension updates; a daily purge task. | Maintaining the tracking code and its configuration. |
| Control | Retention, IP mode and consent are set on the site. A privacy plugin exports and deletes the visits of one user. | Whatever the provider allows. |
| Licence cost | One-off payment with 12 months of updates; see [pricing](https://evoaddons.com/en/pricing). | \[PENDIENTE: verificar según la herramienta\] |

## What evoOrigin does not do

- It does not measure behaviour inside the site: no clicks, no heatmaps, no journeys.
- It does not fingerprint browsers or geolocate by IP.
- It does not send data to third parties or to ad platforms.
- It has no cross-reports or funnels; statistics are monthly counters by source, medium and campaign.
- It does not identify the same person across sessions: it counts sessions, not people.
- With logging off, which is the factory state, it only keeps the origin in the Joomla session.

Visits with an IP and lead attributions are personal data. If you enable logging, the legal basis and the mention in your privacy policy are for whoever processes the data to settle. This is not legal advice; consult your adviser.

More detail: [evoOrigin page](https://evoaddons.com/en/products/evoorigin), [data it handles](https://evoaddons.com/en/documentation/evoorigin-data) and the [minimum-data measurement use case](https://evoaddons.com/en/use-cases/privacy-first).

## Related products

- [evoOrigin](https://evoaddons.com/en/products/evoorigin)

---

https://evoaddons.com/en/comparisons/analytics