ImmoWP Estimation vs WP Consent API

ImmoWP Estimation est un plugin WordPress complet qui fournit un formulaire professionnel multi-etapes pour l’estimation de biens immobiliers. Parfait pour les agences immobilieres, les societes de gestion immobiliere et les agents independants. Fonctionnalites principales Formulaire interactif en 6 etapes – Assistant multi-pages convivial avec barre de progression Autocompletion d’adresse – Integration avec l’API gouvernementale francaise (api-adresse.data.gouv.fr) Support API externe – Connectez votre propre API d’estimation Mode de secours – Fonctionne meme sans configuration API Securite : Integration Google reCAPTCHA v3 Limitation de requetes par IP Verification de nonce Validation et assainissement des entrees Notifications par email – Emails automatiques aux utilisateurs et administrateurs Administration : Tableau de bord detaille des estimations Filtres avances (statut, type de bien) Recherche etendue Export CSV Meta box en lecture seule avec notes admin Performance optimisee : Mise en cache de l’API d’adresses Index de base de donnees Chargement conditionnel des assets Accessibilite – Attributs ARIA et conformite WCAG AA Fonctionnement L’utilisateur remplit le formulaire en 6 etapes : Selection de l’adresse avec autocompletion Type de bien (maison/appartement) Surface habitable et terrain Nombre de pieces Etat du bien Coordonnees La soumission declenche : Appel API pour l’estimation (si configure) OU message de secours pour rappel Notifications email a l’utilisateur et l’admin Stockage des donnees dans WordPress Les administrateurs peuvent : Voir toutes les demandes d’estimation Filtrer et rechercher les soumissions Exporter les donnees en CSV Ajouter des notes internes Shortcode Ajoutez simplement [immowp_estimation_form] a n’importe quelle page ou article. Integration API Le plugin peut se connecter a n’importe quel point de terminaison API REST qui accepte les donnees du bien et retourne les valeurs d’estimation. Voir la documentation pour les specifications API. Confidentialite & RGPD Les donnees utilisateur sont stockees localement dans votre base WordPress Aucune donnee n’est envoyee a des tiers (sauf votre API configuree) Les administrateurs peuvent supprimer les soumissions a tout moment Foire Aux Questions Ai-je besoin d’une API externe ? Non ! Le plugin fonctionne en “mode de secours” sans API. Dans ce mode, les soumissions sont enregistrees et vous recevez une notification par email pour contacter l’utilisateur. Puis-je personnaliser le message de confirmation ? Oui ! Allez dans Estimations > Reglages, puis dans la section “Parametres avances”, vous pouvez personnaliser le “Message en mode fallback” affiche aux utilisateurs quand l’API n’est pas configuree. Comment configurer reCAPTCHA ? Obtenez vos cles reCAPTCHA v3 sur https://www.google.com/recaptcha/admin Dans WordPress, allez dans Estimations > Reglages Dans la section “Google reCAPTCHA v3”, cochez “Activer la verification reCAPTCHA v3” Entrez votre Site Key et Secret Key Ajustez le seuil de score si necessaire (defaut 0.5) Cliquez sur “Enregistrer les parametres” Puis-je exporter les demandes d’estimation ? Oui ! Allez sur la page admin Estimations et cliquez sur “Exporter CSV”. L’export respecte vos filtres actuels. Le formulaire est-il adapte au mobile ? Oui ! Le formulaire est entierement responsive et fonctionne parfaitement sur tous les appareils. Puis-je traduire le plugin ? Oui ! Le plugin est pret pour la traduction avec le domaine de texte immowp-estimation. Utilisez Loco Translate ou des outils similaires. Ou trouver les reglages du plugin ? Le menu principal “Estimations” apparait dans la barre laterale de l’administration WordPress apres activation du plugin. Les reglages se trouvent dans : Estimations > Reglages. Testing Test rapide du plugin Pour tester rapidement le plugin sur une installation WordPress fraiche : Installer et activer : Telechargez et activez le plugin Verifier le menu : Le menu “Estimations” apparait dans la barre laterale admin Creer une page de test : Allez dans Pages > Ajouter Titre : “Test Estimation” Contenu : [immowp_estimation_form] Publiez la page Tester le formulaire : Visitez la page publiee Le formulaire d’estimation en 6 etapes s’affiche Etape 1 : Tapez “Paris” dans le champ adresse – des suggestions apparaissent Selectionnez une adresse dans la liste Continuez a travers les 6 etapes (type, surface, pieces, etat, contact) Soumettez le formulaire Verifier l’enregistrement : Allez dans Estimations > Toutes les estimations La demande soumise apparait dans la liste Cliquez dessus pour voir les details complets Fonctionnalites a tester Autocompletion d’adresse : Tapez au moins 3 caracteres pour voir les suggestions Navigation multi-etapes : Utilisez les boutons Precedent/Suivant Validation des champs : Essayez de soumettre avec des champs vides Responsive : Testez sur mobile et desktop Admin : Filtrez par statut, recherchez par email, exportez en CSV Mode fallback : Sans API configuree, un message de rappel s’affiche Captures d’ecran Formulaire d’estimation moderne en 6 etapes avec barre de progression Autocompletion d’adresse avec integration API francaise Collecte des details du bien Tableau de bord admin avec filtres et recherche Page de reglages avec toutes les options de configuration Meta box des details d’estimation avec informations en lecture seule Documentation API Format de requete Votre API doit accepter des requetes POST a {base_url}/api/estimate avec la structure JSON suivante : { "codeCommune": "75001", "surfaceHabitable": 75, "typeLocal": "appartement", "codePostal": "75001", "surfaceTerrain": 0, "voie": "Rue de Rivoli", "numeroVoie": "10" } Reponse attendue { "estimatedPrice": 450000, "estimatedPriceMin": 420000, "estimatedPriceMax": 480000, "confidence": "high", "status": "success" } Voir la documentation complete sur https://immowp.com/docs/api Support Pour le support, les demandes de fonctionnalites ou les rapports de bugs, veuillez utiliser les forums de support WordPress.org. External Services This plugin connects to external third-party services to provide its functionality. Below is detailed information about each service: French National Address API (Base Adresse Nationale) This plugin uses the French government’s address API to provide address autocomplete functionality in the estimation form. What it does: Provides address suggestions when users type in the address field Data sent: The text entered by the user in the address search field When data is sent: Each time the user types at least 3 characters in the address field Service provider: French government (Etalab/DINUM) Service URL: https://api-adresse.data.gouv.fr/search/ Terms of service: https://adresse.data.gouv.fr/cgu Privacy policy: https://adresse.data.gouv.fr/donnees-personnelles Google reCAPTCHA v3 (Optional) If enabled in the plugin settings, this plugin uses Google reCAPTCHA v3 to protect the form against spam and automated submissions. What it does: Validates that form submissions come from real users, not bots Data sent: User’s IP address, reCAPTCHA token, and browser information When data is sent: When the user submits the estimation form (if reCAPTCHA is enabled) Service provider: Google LLC Service URL: https://www.google.com/recaptcha/api/siteverify Terms of service: https://policies.google.com/terms Privacy policy: https://policies.google.com/privacy Your Configured Estimation API (Optional) If you configure an external estimation API in the plugin settings, the plugin will send property data to calculate real estate valuations. What it does: Calculates property estimation based on submitted data Data sent: Property details (address, type, surface area, number of rooms, condition) When data is sent: When the user submits a complete estimation form Service provider: Configured by you in plugin settings Terms and privacy: Depends on your configured API provider

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!