evoLeadGate: reference

The "Lead magnet" element

The builder labels are in Spanish. English glosses are given in brackets. Defaults are those of a freshly added element.

Formulario tab (Form)

Textos tab (Texts)

Entrega y avisos tab (Delivery and notices)

Consentimiento tab (Consent)

The exact text of each checkbox is stored with the lead at the moment of submission.

Analítica tab (Analytics)

Ajustes and Avanzado tabs (Settings and Advanced)

The usual YOOtheme options: top and bottom margin, maximum width, block and text alignment, animation and visibility. Margins default to "default" at the top and bottom. The Advanced tab holds the standard builder options.

The "Campo" child element (Field)

Server-side validation, always against the signed definition of the form:

Delivery modes

In both modes:

• the notice goes to the form's notification emails or, if there are none, to the default email in the options. With no recipient at all, the notice status is stored as skipped;
• the delivery email goes to the address typed in that same form;
• a mail failure does not stop the lead from being saved; it is recorded as failed in the lead's status;
• the download link works as many times as needed until it expires. Each download is logged;
• the file is served by PHP as an attachment, without exposing its real path. An expired link answers 410; an unknown link, or a file that is gone, answers 404.

Analytics events

After a successful submission, the form script does this in the browser:

event_id is the lead's UUID, so it matches the event_id shown in the lead detail and can be used to deduplicate conversions.

The script does not read the consent state. It checks whether gtag and fbq exist: your site loads the pixels, for example from YOOtheme's scripts panel in the marketing category, and they only exist if the visitor accepted them. The script does not load third-party scripts; what gtag and fbq do depends on how you load them.

Joomla event for integrations

Each new lead fires a Joomla event after it is saved and the emails have been sent:

The argument also carries the stored IP, the user agent, the consents, the attribution data and the download token. Treat it as personal data and as a credential. If your plugin throws an exception, it is ignored and the lead is still saved.

A minimal subscribed plugin:

public static function getSubscribedEvents(): array
{
    return ['onEvoleadgateLeadCreated' => 'onLead'];
}

public function onLead(\Joomla\Event\Event $event): void
{
    $lead = $event->getArgument('lead'); // ['id' => ..., 'email' => ..., 'form_id' => ..., ...]
}

REST API (read-only)

Provided by the package's web services plugin. It uses the X-Joomla-Token header and needs a user with the core.manage permission on com_evoleadgate. Responses are not cached.

Neither includes the IP or the user agent. There are no write routes. A user without the permission gets 403.

Tools for evoMCP (optional)

If you have evoMCP installed, the package's evomcp plugin registers these tools under the "evoLeadGate" component. They need core.manage on com_evoleadgate plus the permissions of the MCP connection.

Component entry points

For information only: the form script uses them, and they are not meant to be called by hand.

The form configuration travels in a hidden field signed with HMAC-SHA256 using the site secret, with no expiry. Changing Joomla's secret invalidates any form still in a cache until it is rendered again.

Limits