Hooks And Filters

This page intentionally does not enumerate the plugin's internal action and filter names, arguments or firing locations.

Extension philosophy

The plugin uses WordPress's standard actions and filters internally. Some of these are explicitly documented as extension points in the "extension points" pages of this section (for example for lead processing, imports or analytics). Those documented extension points are the supported way to extend the plugin from external code.

Any action or filter that is not explicitly documented as an extension point is considered internal. It may be renamed, removed or have its arguments changed between releases. External code should not hook into undocumented internals.

If you need an integration that is not currently supported through a documented extension point, please raise it as a feature request describing the use case.

Supported public integration surfaces

When integrating with the plugin, prefer these stable surfaces:

• The plugin admin settings UI.
• The documented shortcodes.
• Theme-level template overrides as described in Template System And Overrides.
• The general Developer Overview for orientation.

Internal class names, option keys, database tables, REST and AJAX endpoints, cron hook names, capability and nonce identifiers, and release / update infrastructure are treated as implementation details. They may change between releases without notice and are not part of the public integration contract.

Stability and change policy

Anything not listed as a supported public surface above is considered an internal implementation detail. Internal APIs, storage layout and security implementation may change between releases. Do not depend on them from third-party code, themes or external systems. Direct database writes are not supported.

Public documentation notice. This page provides a high-level integration overview only. Internal implementation details, private APIs, storage internals and security-sensitive release infrastructure are maintained separately and are not part of the public documentation. Supported integration surfaces are the documented shortcodes, template overrides, settings UI and any extension points explicitly published in this section.