
Preta settings showing secure signing key configuration and public key.
Preta connects your WordPress site to the Preta personalization and targeting platform.
The plugin securely sends selected attributes from the logged-in WordPress user to Preta as a signed context token. Preta can then use those attributes to evaluate campaigns and personalize or target on-page elements for each visitor.
Examples of targetable attributes include:
The plugin does not require clients to manually create or paste private signing keys. Preta generates a 2048-bit RSA signing key automatically and stores it, authenticated-encrypted, in the WordPress database. Administrators who prefer to manage their own key can instead configure PRETA_PRIVATE_KEY or PRETA_PRIVATE_KEY_PATH in wp-config.php, which the plugin only ever reads.
The private signing key is never sent to Preta.
After activation, open:
Preta > Settings
The settings page allows administrators to:
Only users with the required WordPress administrator capability can access the plugin settings.
The plugin connects to the Preta service.
A Preta account is required to configure campaigns and targeting.
After installing the plugin:
For more information about Preta, visit:
https://pretasystems.com/
Preta can discover supported attributes from the WordPress installation.
Supported sources include:
The discovery process identifies attributes that can safely be represented as scalar targeting values.
Potentially sensitive or unsuitable values are excluded from discovery and transmission.
Discovered attributes are not automatically added to the signed context after discovery. Administrators must review and save the attributes they want the plugin to send.
New attributes discovered later can be reviewed and added without automatically changing the existing saved configuration.
The plugin uses RS256 signed context tokens to send selected user attributes to Preta.
The private signing key is generated automatically and stored authenticated-encrypted (AES-256-GCM, with a key derived from this WordPress installation’s own secrets) in a plugin-owned database option. It is never written to a file, never stored in plaintext, and never sent to Preta. Administrators may instead configure PRETA_PRIVATE_KEY or PRETA_PRIVATE_KEY_PATH in wp-config.php to manage the key themselves; the plugin only ever reads these.
The public key can be registered with Preta to verify signatures.
The plugin limits attribute values to supported scalar types and excludes sensitive or unsuitable fields from discovery and transmission.
The plugin does not intentionally send passwords, session tokens, or other sensitive authentication data to Preta.
Only selected attributes are included in the signed user context.
Administrators should review the attributes selected for transmission and ensure that their site’s privacy and data-processing requirements are satisfied.
This plugin connects to the Preta service operated by Preta Systems.
The service is used to:
When the plugin is configured and active, selected user attributes may be transmitted from the WordPress site to Preta in a signed context token.
Service:
https://pretasystems.com/
Privacy Policy:
https://pretasystems.com/privacy/
Please review the Preta service privacy policy before enabling the integration.
This plugin is licensed under the GNU General Public License version 2 or later.
https://www.gnu.org/licenses/gpl-2.0.html