Preta connects your WordPress site to the Preta personalization and targeting platform.<\/p>\n\n
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.<\/p>\n\n
Examples of targetable attributes include:<\/p>\n\n
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.<\/p>\n\n
The private signing key is never sent to Preta.<\/p>\n\n
After activation, open:<\/p>\n\n
Preta > Settings<\/p>\n\n
The settings page allows administrators to:<\/p>\n\n
Only users with the required WordPress administrator capability can access the plugin settings.<\/p>\n\n
The plugin connects to the Preta service.<\/p>\n\n
A Preta account is required to configure campaigns and targeting.<\/p>\n\n
After installing the plugin:<\/p>\n\n
For more information about Preta, visit:<\/p>\n\n
https:\/\/pretasystems.com\/<\/p>\n\n
Preta can discover supported attributes from the WordPress installation.<\/p>\n\n
Supported sources include:<\/p>\n\n
The discovery process identifies attributes that can safely be represented as scalar targeting values.<\/p>\n\n
Potentially sensitive or unsuitable values are excluded from discovery and transmission.<\/p>\n\n
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.<\/p>\n\n
New attributes discovered later can be reviewed and added without automatically changing the existing saved configuration.<\/p>\n\n
The plugin uses RS256 signed context tokens to send selected user attributes to Preta.<\/p>\n\n
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.<\/p>\n\n
The public key can be registered with Preta to verify signatures.<\/p>\n\n
The plugin limits attribute values to supported scalar types and excludes sensitive or unsuitable fields from discovery and transmission.<\/p>\n\n
The plugin does not intentionally send passwords, session tokens, or other sensitive authentication data to Preta.<\/p>\n\n
Only selected attributes are included in the signed user context.<\/p>\n\n
Administrators should review the attributes selected for transmission and ensure that their site's privacy and data-processing requirements are satisfied.<\/p>\n\n
This plugin connects to the Preta service operated by Preta Systems.<\/p>\n\n
The service is used to:<\/p>\n\n
When the plugin is configured and active, selected user attributes may be transmitted from the WordPress site to Preta in a signed context token.<\/p>\n\n
Service:<\/p>\n\n
https:\/\/pretasystems.com\/<\/p>\n\n
Privacy Policy:<\/p>\n\n
https:\/\/pretasystems.com\/privacy\/<\/p>\n\n
Please review the Preta service privacy policy before enabling the integration.<\/p>\n\n
This plugin is licensed under the GNU General Public License version 2 or later.<\/p>\n\n
https:\/\/www.gnu.org\/licenses\/gpl-2.0.html<\/p>\n\n\n
After configuration, the plugin loads the Preta loader on the site and provides signed context for logged-in users.<\/p>\n\n\n
No. The private signing key is generated and kept on the WordPress site (encrypted in the database, or in a file you manage yourself via PRETA_PRIVATE_KEY_PATH). Preta receives only the public key, for signature verification.<\/p><\/dd>\n
Yes. The plugin provides attribute discovery and allows administrators to select which supported attributes are included in the signed context.<\/p><\/dd>\n
Yes. When Advanced Custom Fields is active, supported ACF user fields can be discovered and selected.<\/p><\/dd>\n
No. User meta values are filtered and only suitable attributes are made available for selection.<\/p><\/dd>\n
The logged-in user's signed context is removed and Preta can evaluate the visitor without that authenticated user context.<\/p><\/dd>\n
Yes. A Preta account is required to configure targeting campaigns and use the Preta service.<\/p><\/dd>\n
Yes. Debug logging can be configured from the Preta settings page.<\/p><\/dd>\n
Deleting the plugin is permanent. It removes all Preta data, including the automatically-generated private signing key and the plugin settings. This cannot be undone and the private key cannot be recovered. After deletion you would need to reinstall, generate a new signing key, and register its new public key in Preta. A key you manage yourself via PRETA_PRIVATE_KEY_PATH is never touched. Deactivating the plugin (instead of deleting it) is non-destructive and keeps your key and settings.<\/p><\/dd>\n\n<\/dl>\n\n\n