Title: Preta Author: pretasystems Published: 2026년 9월 21일 Last modified: 2026년 9월 21일 --- 플러그인 검색 ![](https://ps.w.org/preta/assets/icon-256x256.png?rev=3704894) # Preta 작성자: [pretasystems](https://profiles.wordpress.org/pretasystems/) [다운로드](https://downloads.wordpress.org/plugin/preta.3.2.1.zip) * [세부사항](https://ko.wordpress.org/plugins/preta/#description) * [평가](https://ko.wordpress.org/plugins/preta/#reviews) * [설치](https://ko.wordpress.org/plugins/preta/#installation) * [개발](https://ko.wordpress.org/plugins/preta/#developers) [지원](https://wordpress.org/support/plugin/preta/) ## 설명 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: * WordPress role * Signup month * Locale * Selected ACF user fields * Selected safe user meta fields 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. ### Configuration After activation, open: Preta > Settings The settings page allows administrators to: * Configure the signing key. * View the public key. * Review key storage and verification status. * Discover available user attributes. * Select which attributes are sent to Preta. * Test the generated user context token. * Configure debug logging for troubleshooting. Only users with the required WordPress administrator capability can access the plugin settings. ### Preta Account and Setup The plugin connects to the Preta service. A Preta account is required to configure campaigns and targeting. After installing the plugin: 1. Generate the WordPress signing key. 2. Copy the public key from the plugin settings. 3. Add the public key to your Preta project. 4. Verify the WordPress integration. 5. Review the discovered attributes. 6. Select and save the attributes that should be available for targeting. 7. Create and configure campaigns in Preta. For more information about Preta, visit: https://pretasystems.com/ ### Attribute Discovery Preta can discover supported attributes from the WordPress installation. Supported sources include: * WordPress core user information. * Active Advanced Custom Fields (ACF) user fields. * Safe user meta values. 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. ### Security and Privacy 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. ### External Services This plugin connects to the Preta service operated by Preta Systems. The service is used to: * Verify signed user context. * Evaluate targeting rules. * Determine which configured campaign experiences apply to a visitor. * Deliver the Preta loader used for campaign evaluation and personalization. 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. ### License This plugin is licensed under the GNU General Public License version 2 or later. https://www.gnu.org/licenses/gpl-2.0.html ## 스크린샷 [⌊Preta settings showing secure signing key configuration and public key.⌉⌊Preta settings showing secure signing key configuration and public key.⌉[ Preta settings showing secure signing key configuration and public key. [⌊WordPress and ACF attributes selected for the signed user context.⌉⌊WordPress and ACF attributes selected for the signed user context.⌉[ WordPress and ACF attributes selected for the signed user context. [⌊Test token showing selected attributes and generated signed user context.⌉⌊Test token showing selected attributes and generated signed user context.⌉[ Test token showing selected attributes and generated signed user context. [⌊Preta campaign Logic Builder targeting a WordPress user attribute.⌉⌊Preta campaign Logic Builder targeting a WordPress user attribute.⌉[ Preta campaign Logic Builder targeting a WordPress user attribute. [⌊Live WordPress page showing personalized content for a targeted user role.⌉⌊Live WordPress page showing personalized content for a targeted user role.⌉[ Live WordPress page showing personalized content for a targeted user role. ## 설치 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. ## FAQ ### 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. ## 후기 이 플러그인에 대한 평가가 없습니다. ## 기여자 & 개발자 “Preta”(은)는 오픈 소스 소프트웨어입니다. 다음의 사람들이 이 플러그인에 기여하였습니다. 기여자 * [ pretasystems ](https://profiles.wordpress.org/pretasystems/) [자국어로 “Preta”(을)를 번역하세요.](https://translate.wordpress.org/projects/wp-plugins/preta) ### 개발에 관심이 있으십니까? [코드 탐색하기](https://plugins.trac.wordpress.org/browser/preta/)는, [SVN 저장소](https://plugins.svn.wordpress.org/preta/) 를 확인하시거나, [개발 기록](https://plugins.trac.wordpress.org/log/preta/)을 [RSS](https://plugins.trac.wordpress.org/log/preta/?limit=100&mode=stop_on_copy&format=rss) 로 구독하세요. ## 변경이력 #### 3.2.1 * Changed automatically-generated signing keys to be stored authenticated-encrypted in the WordPress database instead of the filesystem. * Removed the filesystem-based key storage used on some restrictive hosts in earlier versions. * Fixed all inline scripts and styles to use the WordPress script/style APIs. * Updated diagnostics for the new key-storage architecture. #### 3.2.0 * Added automatic user attribute discovery. * Added support for discovering supported WordPress, ACF, and user-meta attributes. * Added secure signing-key fallback storage for supported hosting environments. * Added protected token refresh for logged-in users. * Added security validation for user attributes. * Improved administrator-only settings access. * Improved key storage verification and security checks. * Improved WordPress hosting compatibility. * Added integration and security regression coverage. ## 기초 * 버전 **3.2.1** * 최근 업데이트: **2주 전** * 활성화된 설치 **10보다 적음** * 워드프레스 버전 ** 5.5 또는 그 이상 ** * 다음까지 시험됨: **7.1.2** * PHP 버전 ** 7.4 또는 그 이상 ** * 언어 * [English (US)](https://wordpress.org/plugins/preta/) * 태그: * [experimentation](https://ko.wordpress.org/plugins/tags/experimentation/)[optimization](https://ko.wordpress.org/plugins/tags/optimization/) [personalization](https://ko.wordpress.org/plugins/tags/personalization/)[targeting](https://ko.wordpress.org/plugins/tags/targeting/) * [고급 보기](https://ko.wordpress.org/plugins/preta/advanced/) ## 평점 아직 제출된 리뷰가 없습니다. [Your review](https://wordpress.org/support/plugin/preta/reviews/#new-post) [모든 리뷰 보기](https://wordpress.org/support/plugin/preta/reviews/) ## 기여자 * [ pretasystems ](https://profiles.wordpress.org/pretasystems/) ## 지원 할 말 있으신가요? 도움이 필요하신가요? [지원 포럼 보기](https://wordpress.org/support/plugin/preta/)