UCP Adapter For WooCommerce vs WP Consent API

UCP Adapter For WooCommerce is a powerful WordPress plugin that provides REST API endpoints for Universal Commerce Platform (UCP) integration. It enables seamless communication between your WordPress site and external commerce platforms through secure, standardized API endpoints. Thank you for using our plugin! This add-on connects your WordPress site to the powerful world of WordPress’s Agentic Commerce, allowing you to create automated shopping assistants for your users. 🚀 Core Features Our plugin leverages WordPress’s MCP (Model Context Protocol) servers plugin and the open Universal Commerce Protocol (UCP) standard to enable secure, intelligent commerce actions. Here’s what you can build: Smart Product Discovery: Enable agents to search products across WordPress merchants, apply filters, and display interactive product cards directly within a chat interface on your site. Seamless Checkout: Allow agents to create checkout sessions, collect buyer information, attach payment details, and complete purchases on behalf of users. Order Tracking: After a purchase, agents can track order status, fulfillment updates, and post-purchase events like refunds or returns. 🔗 How It Works The plugin acts as a Platform within the UCP framework, facilitating secure communication between your users (buyers), WordPress Merchants, and payment or credential providers. It implements these key UCP capabilities: Discovery → Checkout: An agent can help a user find a product and instantly retrieve the necessary details to start a checkout session. Checkout Completion: The agent can securely submit the checkout. If further user action is needed, it can gracefully open a web checkout page. Post-Purchase: The agent provides ongoing value by fetching real-time updates on order delivery and status changes. 💡 Use Case Example Imagine a user in your site’s chat asking, “Find me a red coffee mug under $20.” The plugin-powered agent can: * Query the WordPress Catalog across multiple stores. * Return filtered, interactive results. * Guide the user through selecting a variant, adding it to cart, and checking out—all without leaving your WordPress environment. * Get this client https://github.com/dhirajpatra/adk-agent-gcp/tree/main/ai-agents-adk/ucp_recommendation_system to connect your site with AI agent. Key Features Session Management: Create and manage user sessions with automatic expiration REST API Endpoints: Three core endpoints (Session, Update, Complete) for UCP communication Security First: API key authentication, rate limiting, and IP whitelisting Developer Friendly: Clean, extensible code following WordPress coding standards Extensible: Hooks and filters throughout for custom implementations Admin Interface: Easy-to-use settings and session monitoring dashboard Database Storage: Efficient session storage with automatic cleanup REST API Endpoints POST /wp-json/ucp/v1/session – Create a new session PUT /wp-json/ucp/v1/update/{session_id} – Update session data POST /wp-json/ucp/v1/complete/{session_id} – Complete a session GET /wp-json/ucp/v1/status/{session_id} – Check session status GET /wp-json/ucp/v1/sessions – List all sessions GET /wp-json/ucp/v1/product/search – Search for products Use Cases E-commerce platform integration Third-party checkout systems Payment gateway connections Order management systems Multi-platform commerce solutions Developer Resources Build custom UCP adapters for platforms like: * Custom e-commerce solutions * Membership plugins * Digital product handlers * MemberPress API Documentation Create Session Endpoint: POST /wp-json/ucp/v1/session Headers: Content-Type: application/json X-UCP-API-Key: your-api-key Body: json { "platform": "woocommerce", "user_data": { "user_id": 123, "email": "[email protected]" } } Response: json { "success": true, "session_id": "ucp_abc123...", "expires_at": 1234567890, "message": "Session created successfully." } Update Session Endpoint: PUT /wp-json/ucp/v1/update/{session_id} Body: json { "action": "add_item", "data": { "product_id": 456, "quantity": 2 } } Complete Session Endpoint: POST /wp-json/ucp/v1/complete/{session_id} Body: json { "status": "completed", "metadata": { "order_id": 789 } } List Sessions Endpoint: GET /wp-json/ucp/v1/sessions Parameters: * page: Page number (optional, default 1) * limit: Results per page (optional, default 10) Response: json { "success": true, "data": [ { "session_id": "ucp_abc123...", "status": "active", "created_at": "2024-01-01 12:00:00", "expires": 1234567890 } ], "meta": { "page": 1, "limit": 10, "total": 5 } } Product Search Endpoint: GET /wp-json/ucp/v1/product/search Parameters: * search: Search query (required) * page: Page number (optional, default 1) * limit: Results per page (optional, default 10) Response: json { "success": true, "data": [ { "id": 123, "name": "T-Shirt", "price": "20.00", "image": "https://example.com/image.jpg", "permalink": "https://example.com/product/t-shirt" } ], "meta": { "page": 1, "limit": 10, "search": "shirt", "count": 1 } } Actions Available add_item – Add an item to the session update_item – Update an existing item remove_item – Remove an item from the session set_data – Set custom session data Custom actions via filters Privacy Policy UCP Adapter For WooCommerce stores session data temporarily in your WordPress database. This data is automatically cleaned up based on your configured retention settings. The plugin does not send any data to external services. Session data may include: * User identifiers * Platform information * Custom data provided via API calls It is your responsibility to ensure compliance with privacy regulations (GDPR, CCPA, etc.) when using this plugin. Credits Developed with WordPress coding standards and best practices in mind. Support Support Forum: https://wordpress.org/support/plugin/ucp-adapter-for-woocommerce

WP Consent API is a plugin that standardizes the communication of accepted consent categories between plugins. It requires a cookie banner plugin and, at least, one other plugin that supports the WP Consent API. With this plugin, all supporting plugins can use the same set of methods to read and register the current consent category, allowing consent management plugins and other plugins to work together, improving compliance with privacy laws. WARNING: the plugin itself will not handle consent. It will show you how many plugins you have without Consent API support and will improve compliance on your site by ensuring smooth communication between cookie banner plugins and plugins that set cookies or track user data. What problem does this plugin solve? Currently, it is possible for a consent management plugin to block third-party services like Facebook, Google Maps, Twitter, etc. But if a WordPress plugin places a PHP cookie, a consent management plugin cannot prevent this. Secondly, some plugins integrate the tracking code on the clientside in javascript files that, when blocked, break the site. Or, if such a plugin’s javascript is minified, causing the URL to be unrecognizable and won’t get detected by an automatic blocking script. Lastly, the blocking approach requires a list of all types of URL’s that tracks data. A generic API where plugins adhere to can greatly facilitate a webmaster in getting a site compliant. Does usage of this API prevent third-party services from tracking user data? Primary this API is aimed at compliant first-party cookies or tracking by WordPress plugins. If such a plugin triggers, for example, Facebook, usage of this API will be of help. If a user embeds a Facebook iframe, a blocking tool is needed that initially disables the iframe and or scripts. Third-party scripts have to blocked by blocking functionality in a consent management plugin. To do this in core would be to intrusive, and is also not applicable to all users: only users with visitors from opt-in regions such as the European Union require such a feature. Such a feature also has a risk of breaking things. Additionally, blocking these and showing a nice placeholder requires even more sophisticated code, all of which should in my opinion not be part of WordPress core, for the same reasons. How does it work? There are two indicators that together tell if consent is given for a specific consent category, e.g., “marketing”: 1) the region based consent_type, which can be opt-in, opt-out, or other possible consent_types; 2) and the visitor’s choice: not set, allow, or deny. The consent_type is a function that wraps a filter, “wp_get_consent_type”. If there’s no consent management plugin to set it, it will return false. This will cause all consent categories to return true, allowing cookies to be set on all categories. If opt-in is set using this filter, a category will only return true if the value of the visitor’s choice is “allow”. If the region based consent_type is opt-out, it will return true if the visitor’s choice is not set or is “allow”. Clientside, a consent management plugin can dynamically manipulate the consent type and set several cookie categories. A plugin can use a hook to listen for changes or check the value of a given category. Categories and most other stuff can be extended with a filter. Existing integrations Categorized, and sorted alphabetically Example plugin Example plugin. The plugin basically consists of a shortcode, with a div that shows a tracking or not tracking message. No actual tracking is done 🙂 Consent Management Providers Abconsent Sirdata CMP. Beautiful Cookie Consent Banner. Clickio Consent Cookie Consent CMP. Complianz GDPR/CCPA. Consent Studio. consentmanager. Conzent. Cookiebot. CookieFirst. CookieHub. CookieTractor. CookieYes – Cookie Banner for Cookie Consent. GDPR Cookie Compliance. GDPR Cookie Consent Plugin – CCPA Ready. GetTerms. iubenda | All-in-one Compliance. Lawwwing. Pressidium Cookie Consent. TrustArc Cookie Consent Manager Consent Requiring Plugins AddToAny. AFL UTM Tracker Plugin. Burst Statistics. Google Site Kit. Pixel Manager for WooCommerce. Woo. WP Statistics. Demo site wpconsentapi.org Below are the plugins used to set up the demo site: Complianz The example plugin javascript, consent management plugin //set consent type window.wp_consent_type = 'optin' //dispatch event when consent type is defined. This is useful if the region is detected server side, so the consent type is defined later during the pageload let event = new CustomEvent('wp_consent_type_defined'); document.dispatchEvent( event ); //consent management plugin sets cookie when consent category value changes wp_set_consent('marketing', 'allow'); javascript, tracking plugin //listen to consent change event document.addEventListener("wp_listen_for_consent_change", function (e) { var changedConsentCategory = e.detail; for (var key in changedConsentCategory) { if (changedConsentCategory.hasOwnProperty(key)) { if (key === 'marketing' && changedConsentCategory[key] === 'allow') { console.log("just given consent, track user") } } } }); //basic implementation of consent check: if (wp_has_consent('marketing')){ activateMarketing(); console.log("set marketing stuff now!"); } else { console.log("No marketing stuff please!"); } PHP //declare compliance with consent level API $plugin = plugin_basename( __FILE__ ); add_filter( "wp_consent_api_registered_{$plugin}", '__return_true' ); /** * Example how a plugin can register cookies with the consent API * These cookies can then be shown on the front-end, to the user, with wp_get_cookie_info() */ function my_wordpress_register_cookies(){ if ( function_exists( 'wp_add_cookie_info' ) ) { wp_add_cookie_info( 'AMP_token', 'AMP', 'marketing', __( 'Session' ), __( 'Store a unique User ID.' ) ); } } add_action('plugins_loaded', 'my_wordpress_register_cookies'); if (wp_has_consent('marketing')){ //do marketing stuff } Service-level consent In addition to category-based consent, the API supports service-level consent control. This allows consent management plugins to grant or deny consent for specific services (like ‘google-analytics’ or ‘facebook-pixel’) independently from their category. When checking service consent with wp_has_service_consent(), the API first checks if explicit consent exists for that service. If no explicit consent is set, it falls back to the consent status of the service’s category. This enables fine-grained control: a user might accept statistics cookies in general, but explicitly deny a specific analytics service. Service consent can be checked and set both server-side (PHP) and client-side (JavaScript): PHP: //check if a specific service has consent if ( wp_has_service_consent( 'google-analytics' ) ) { //activate google analytics } //check if a service is explicitly denied if ( wp_is_service_denied( 'facebook-pixel' ) ) { //service was explicitly denied by user } //set service consent wp_set_service_consent( 'google-analytics', true ); //grant consent wp_set_service_consent( 'facebook-pixel', false ); //deny consent //listen for service consent changes add_action( 'wp_consent_service_changed', function( $service, $consented ) { error_log( "Service {$service} consent changed to: " . ( $consented ? 'granted' : 'denied' ) ); }, 10, 2 ); JavaScript: //check service consent if ( wp_has_service_consent( 'youtube' ) ) { //activate tracking } //check if explicitly denied if ( wp_is_service_denied( 'facebook-pixel' ) ) { //service denied } //set service consent wp_set_service_consent( 'youtube', true ); //listen for service consent changes document.addEventListener( 'wp_consent_api_status_change_service', function( e ) { console.log( 'Service: ' + e.detail.service + ', consented: ' + e.detail.value ); }); Any code suggestions? We’re on GitHub as well!