Know where each lead comes from
The situation
A site gets traffic from search engines, social networks, paid campaigns and links from other sites. Leads come in through a download form. The team wants to know, for each lead, where they came from the first time and where they came from the last time, because weeks can pass between the two. They do not want to set up an analytics platform or send that data off the site.
How it is solved
Two pieces play different roles.
evoLeadGate stores with each lead what the submission URL carried: utm_source, utm_medium, utm_campaign, utm_term, utm_content, gclid and fbclid, plus the source page and the referrer. That answers "what did they arrive with at the moment they left their email".
evoOrigin answers the other half: where they came from before. Its system plugin captures the visit's origin in the Joomla session (source, medium, campaign, referrer) with no cookies of its own and no JavaScript. If you switch on the lead attribution level, it stores a summary tied to an external reference: first origin, last origin, number of visits and dates. You can read that summary in the evoOrigin panel, through the REST API, or with evoMCP tools, which never return the full IP.
The link between a lead and its summary is a Joomla event, onEvooriginLead, carrying a type and a reference ID. The extension that creates the lead fires it. Today evoLeadGate does not fire it by itself: a plugin of your own can listen to the event evoLeadGate dispatches when it creates a lead and fire evoOrigin's with the lead's ID. [PENDIENTE: confirmar si se publicará un plugin de enlace entre ambos productos]
evoOrigin's database logging ships switched off. You enable it level by level, each with its own retention: visits (90 days by default), lead attribution (24 months from the last interaction by default) and anonymous monthly statistics, with no limit.
What is involved
- evoLeadGate: stores the campaign parameters of the submission.
- evoOrigin: origin in the session, attribution summary, statistics.
- Documentation: evoOrigin first steps, evoOrigin reference and data evoOrigin handles.
Limits
- If nothing fires
onEvooriginLead, the attribution level stays empty. - If the session carries no origin, or the level is off, the event does nothing.
- evoOrigin does not measure behaviour inside the site (clicks, heatmaps), does not fingerprint browsers and does not geolocate by IP.
- The origin lives in the Joomla session and there is no persistent visitor identifier: someone who returns with a new session counts as a new visit. [PENDIENTE: confirmar con el equipo si la cookie de visitante opcional del diseño llegará a publicarse]
- The legal basis and the retention periods are set by whoever processes the data, with their adviser. This is not legal advice; consult your adviser.