Social proof and FOMO popups
A sales popup can load from outside your site
A social-proof popup can show a recent purchase from your WooCommerce orders or from a named notification service. Some plugins keep the order list in WordPress and draw the popup on your site. Others load a widget from TrustPulse, ProveSource, or Fomo. A city in the message is often the buyer's billing location from that order. It does not by itself show that this visitor's location was sent. A script host is the widget, not proof of every order-data endpoint. Popup forms and countdown timers have separate pages. This table describes the setups below; your settings can change which requests run.
Based on plugin documentation, not tests of your site. Your settings can change which requests run. This is not legal advice or a compliance rating.
Scan your site for third-party requestsHow we group social-proof plugins
We compare how the named plugins show recent orders, which host serves the widget, and where order data is documented to go. Orders stored in WordPress do not mean the popup never loads an outside file. A city in a notification is not proof that this visitor's location was sent. Loading a widget script, sending an order through a webhook, and looking up a country on the server are different steps. The sources below do not establish every location-data recipient. Consent timing has not been tested, and vendor data retention has not been assessed.
How a sales popup reaches a visitor
Recent orders from WordPress
NotificationX, FOMO Notifications, and Notivo Notification for WooCommerce can show WooCommerce orders from WordPress. FOMO Notifications and Notivo load their popup scripts from the plugin on your site. NotificationX also loads Open Sans from Google Fonts and Font Awesome from cdnjs by default; those are stylesheets, not order endpoints. A country shown in a FOMO Notifications popup can come from the order billing country. If NotificationX country targeting is set, WordPress can look up this visitor's country on the server. That lookup is not a visitor browser request to the notification service.
A named social-proof service
TrustPulse, ProveSource, and Fomo load a widget from their own hosts. Orders can also be sent to those services through WooCommerce webhooks, a server API, or WooCommerce REST keys. The host column covers documented browser requests only. A widget script host is not by itself an order-submission endpoint.
Before consent
Consent timing is not tested here. A consent checkbox or cookie modal in a plugin is not a test of your site. The Before consent column is not a scan finding. The site scan linked below checks for third-party requests on your pages; it does not access your WordPress database.
Social proof plugins
No paid placement. Plugins that show store orders from WordPress appear first, then named social-proof services, then plugins not yet reviewed. Names are alphabetical within each group.
| Plugin | Documented behavior | Documented outside browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| FOMO Notifications This row covers FOMO Notifications by WP Zinc. The popup CSS and JS load from the plugin on your site and fetch notifications through admin-ajax.php. The location field is the WooCommerce order billing country. That is the buyer's country on the order, not a lookup of this visitor. Consent timing is not tested here. | Shows store orders from WordPress | No outside browser host documented for this setup. Server order sends are separate. | Not assessed | Not tested |
| |
| NotificationX This row covers NotificationX when notifications are enabled. The popup runtime loads from the plugin and reads WordPress REST data. By default it also loads Open Sans from fonts.googleapis.com and Font Awesome from cdnjs.cloudflare.com; those are stylesheets, not order endpoints. If country targeting is set, WordPress can look up this visitor's country on the server through ip-api.com. That lookup is not a visitor browser request. Consent timing is not tested here. | Shows store orders from WordPress | fonts.googleapis.com, cdnjs.cloudflare.com | Not assessed | Not tested |
| |
| Notivo Notification for WooCommerce This row covers Notivo Notification for WooCommerce. The popup script loads from the plugin on your site and requests recent products through admin-ajax.php. Recent orders stay in WooCommerce. No outside browser host is cited for this setup. Consent timing is not tested here. | Shows store orders from WordPress | No outside browser host documented for this setup. Server order sends are separate. | Not assessed | Not tested |
| |
| Fomo for WooCommerce This row covers Fomo for WooCommerce when a Fomo client id is saved. Visitor pages load a widget script from fomo.com/api/v1/{id}/load.js. The plugin also stores WooCommerce REST consumer keys so Fomo can pull orders. That script host is the widget loader; it is not by itself the order-pull endpoint. Consent timing is not tested here. | Connected to a named social-proof service | fomo.com | Not assessed | Not tested |
| |
| ProveSource This row covers ProveSource when an API key is saved. Visitor pages load cdn.provesrc.com/provesrc.js. The plugin posts order first name, last name, email, city, state, country, and products to api.provesrc.com. The customer IP from the order is included only when city or country is missing. That is the buyer on the order, not this visitor. The script host is not the order API. Consent timing is not tested here. | Connected to a named social-proof service | cdn.provesrc.com | Not assessed | Not tested |
| |
| TrustPulse This row covers TrustPulse when the embed is enabled with an account id. Visitor pages load a.trstplse.com/app/js/api.min.js. WooCommerce webhooks can post to app.trustpulse.com/v1/webhook/. The script host is the widget; it is not the webhook. Consent timing is not tested here. | Connected to a named social-proof service | a.trstplse.com | Not assessed | Not tested |
|
What this table does and does not prove
This table describes the named social-proof setups, not requests measured on your site. Orders stored in WordPress can still be paired with an outside stylesheet or a named widget. A city in a notification is often the buyer billing location from that order; it does not prove this visitor's location was sent. The host column covers documented visitor browser requests, not every server webhook or REST pull, and a script host does not by itself establish an order-submission endpoint. Other page requests are not covered. Lead-capture popups and countdown timers have separate pages. Plugins marked Not reviewed have not been assessed. Consent timing has not been tested, and vendor data retention has not been assessed. The linked site scan checks for third-party browser requests; it does not access your WordPress database or verify server-to-server order sends.
Documentation snapshot: Oct 6, 2026. Sources are linked in each reviewed row.
Related pages
Scan your site for third-party requests/wp-social-proof-plugin-privacy