WooCommerce Sales Notifications Without Customer Names
Version note: product settings in this guide were checked against the TrueProof 2.4.0 release on September 17, 2026. New-install defaults and upgrade behavior are distinguished below.
Yes: WooCommerce sales notifications can show genuine order activity without publishing a customer name or location. In TrueProof 2.4.0, select Fully anonymous and the notification uses “Someone” while leaving city/country empty. The purchase action, product name when available and relative time can still come from the real WooCommerce order.
This is different from simulated social proof. The identity is suppressed, but the underlying event remains a supported real order with processing or completed status. The message can read “Someone purchased Product” without claiming that a fictional person bought it.
What fully anonymous means in TrueProof
TrueProof provides three identity display choices for real events:
- Fully anonymous (recommended for new installations): displays “Someone” and no city/country.
- Short name: displays a first name and surname initial when both are available—for example, “Anna K.”—and can display the order’s city/country.
- Full name: displays the stored public name and can display city/country.
Email-shaped values are suppressed in every mode. Built-in sources do not place a full address, email address or order total into the notification. Fully anonymous mode goes further by not using the name or location at all.
Existing sites that upgrade from an earlier TrueProof release retain their previous shortened-name or full-name behavior until an administrator changes the setting. This prevents a software update from silently changing already reviewed public output. New installations start with fully anonymous identity display.
How to configure “Someone purchased…”
- Install or update TrueProof from WordPress.org and activate it.
- Open Settings → TrueProof.
- Select Real Data.
- Enable WooCommerce orders under Real data sources.
- Under Privacy, select Fully anonymous (recommended).
- Review the setup check. It should report at least one eligible real event.
- Choose the display scope, position, timing, look-back window and event limit.
- Enable the widget, save, and verify the public endpoint and storefront in a private window.
The built-in WooCommerce source uses orders with processing or completed status. A pending, failed, cancelled or refunded order is not converted into a purchase notification by that source. The first order item supplies the product text when available; otherwise the action is the generic “made a purchase.”
Example data flow
Suppose an eligible order contains these fields:
- billing first name: Anna
- billing surname: Kowalska
- billing city and country: Prague, CZ
- first item: Blue Widget
- created: eight minutes ago
Fully anonymous mode normalizes the public event to an identity of “Someone” and an empty location. The action can remain “purchased Blue Widget,” and the frontend calculates the relative time. The public bubble therefore communicates a real event without exposing Anna’s name or location.
Short-name mode would instead use “Anna K.” and may include Prague, CZ. Full-name mode would use the complete stored name. Those options exist for site owners who have deliberately assessed their use case; they are not required to display a real purchase.
Why anonymous is not the same as fake
There are two independent questions:
- Did the event happen? Real Data Mode reads a supported record from the WordPress site.
- Which identity fields are public? The privacy setting determines whether the visitor sees “Someone,” a shortened name or a full name/location.
An anonymous real event answers the first question with genuine site data and the second with data minimisation. A simulated event does not represent a purchase and is therefore explicitly worded as sample content with a visible Demo label. Do not remove or visually obscure that label.
Anonymous wording must still be accurate. “Someone purchased Blue Widget eight minutes ago” should correspond to an eligible order and its actual relative time. Suppressing identity is not permission to invent recency, product demand or stock pressure.
Privacy questions to assess before publishing
Fully anonymous display reduces the public fields, but no plugin can declare an entire implementation legally compliant. Your organization still decides why it processes order information, what the store discloses, how long records are retained, who can access them and which rules apply in its jurisdictions.
Could a product and time identify a person indirectly?
Sometimes. A rare product, very low order volume, a local service or a visitor who knows the buyer can make “Someone purchased X just now” more revealing than it appears. Consider a longer delay, broader wording, a narrower display scope or leaving the widget off for sensitive products.
Is the product name itself sensitive?
A product title may disclose health, belief, financial, relationship or other sensitive context even when the buyer is unnamed. Review the catalog rather than assuming anonymizing the name solves every disclosure risk. A generic action can be safer for certain stores.
Does the notification leave WordPress?
With TrueProof’s built-in source, supported records are read on the WordPress site and the frontend requests normalized notification data from that same site’s REST endpoint. During normal Free use without licence activation, the plugin’s own code does not call a third-party activity service. Licence activation, periodic validation while active and deactivation contact wptrueproof.com with licence-related information as described in the plugin documentation; notification-source records are not included in that built-in request.
Who can see the REST response?
The TrueProof events endpoint is public because it returns fields intended for public bubbles. Fully anonymous mode makes the returned name “Someone” and location empty. Treat the action and time as public as well. Do not select a field you would be uncomfortable exposing in page content.
Anonymous notification copy: useful and misleading patterns
Clear: “Someone purchased Blue Widget · 8 min ago.” This states an event, product and time without inventing identity.
Clear when item data is unavailable: “Someone made a purchase · 8 min ago.” It is less specific but still tied to the eligible event.
Potentially misleading: “Customers are buying Blue Widget right now” when the data contains one older order. It converts a single event into a broader popularity and immediacy claim.
Not acceptable: “Someone from Prague just purchased…” if the plugin is using a simulated event or if the actual order has no such location. A plausible sentence is not evidence.
Not anonymous enough for some catalogs: “Someone purchased [highly sensitive or uniquely identifying product].” Removing the person’s name does not automatically remove the possibility of inference.
How the setting affects performance and caching
The identity choice does not add an external service. TrueProof normalizes the event on the WordPress site, caches the event list for about three minutes and serves it over a small REST response. Changing the setting clears the event transient when the settings are saved. A page cache or CDN may still have a short-lived older response, so verify with a cache-busted or private request after saving.
Inspect the endpoint at /wp-json/trueproof/v1/events. In fully anonymous mode every real event should have "name":"Someone" and an empty location. If an older name remains, clear the site/CDN cache and confirm that version 2.4.0 or later is active.
Should you ever use shortened or full names?
The answer depends on the context, audience, notices, user expectations and applicable rules. A shortened name may be familiar in public reviews, while order-derived notifications can create different expectations. A full name plus a precise location generally reveals more than a purchase bubble needs.
Use a field only because it serves a defined purpose, not because the order database contains it. If anonymous event wording communicates the intended information, it is a simpler starting point. Document any decision to expose more, including how a customer can understand or object to that use where required.
Measure whether anonymous notifications help
Privacy-minimised does not mean conversion-positive. Run a controlled experiment with a no-widget group and an anonymous-widget group before considering a more identifying variant. Keep the offer, acquisition mix and major page changes stable. Use completed purchases as the primary outcome and watch mobile checkout completion, dismissals, page performance and support complaints as guardrails.
If traffic is low, the result may be inconclusive for weeks. Do not interpret a few purchases as proof that the widget caused them. Our sales-popup test guide explains sample-size checks, instrumentation and stop rules.
Troubleshooting fully anonymous mode
The bubble still shows a name
Confirm that Fully anonymous is selected and settings were saved. Clear the event transient by saving again, then purge only relevant caches and reload in a private window. Check the events endpoint before inspecting the visual widget.
The bubble says “Someone,” but a location remains
Version 2.4.0’s fully anonymous mode explicitly suppresses city/country. If a location remains, verify the active plugin version and rule out an old response cached by a CDN, service worker or reverse proxy.
No events appear after switching to Real Data
Identity display does not create events. Check that WooCommerce is selected, at least one processing or completed order is inside the look-back window, the widget is enabled and the current page matches the display scope. Follow the sales popup troubleshooting checklist.
Can I use anonymous mode in Simulation?
Simulation has its own explicitly worded sample identities and a visible Demo badge. It is for configuration and preview. Use Real Data with Fully anonymous selected when you want real WooCommerce activity without customer names or locations.
Practical default
Start with Real Data, WooCommerce orders, Fully anonymous identity, one honest event type, a conservative display scope and an explicit measurement plan. Check the social proof privacy checklist and the WooCommerce setup guide before publishing. Expand the public fields only after you can explain why each one is necessary and appropriate.