Linux 软件免费装

在这里免费安装WordPress以及其他软件

Preta

开发者 pretasystems
更新时间 2026年9月21日 13:49
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

optimization personalization targeting experimentation

下载

3.2.1

详情介绍:

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.

安装:

  1. Install and activate the Preta plugin.
  2. Open the Preta settings page in WordPress administration.
  3. Generate or configure the signing key when prompted.
  4. Copy the displayed public key.
  5. Register the public key in your Preta account.
  6. Discover the available WordPress, ACF, and user-meta attributes.
  7. Select the attributes you want Preta to receive.
  8. Save the selected attributes.
  9. Configure your targeting campaigns in Preta.
After configuration, the plugin loads the Preta loader on the site and provides signed context for logged-in users.

屏幕截图:

  • WordPress and ACF attributes selected for the signed user context.
  • Test token showing selected attributes and generated signed user context.
  • Preta campaign Logic Builder targeting a WordPress user attribute.
  • Live WordPress page showing personalized content for a targeted user role.

常见问题:

Does the plugin send the private signing key to Preta?

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.

Can I choose which user attributes are sent?

Yes. The plugin provides attribute discovery and allows administrators to select which supported attributes are included in the signed context.

Does the plugin work with ACF?

Yes. When Advanced Custom Fields is active, supported ACF user fields can be discovered and selected.

Are all user meta fields automatically sent?

No. User meta values are filtered and only suitable attributes are made available for selection.

What happens when a user logs out?

The logged-in user's signed context is removed and Preta can evaluate the visitor without that authenticated user context.

Does the plugin require a Preta account?

Yes. A Preta account is required to configure targeting campaigns and use the Preta service.

Can I disable debug logging?

Yes. Debug logging can be configured from the Preta settings page.

What happens if I delete the plugin?

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.

更新日志:

3.2.1 3.2.0