Aopy for WooCommerce

com), the email marketing and automation platform. It powers abandoned-cart emails, post-purchase automations and newsletter sign-ups from your checkout, and it reports your orders and refunds to Aopy directly from your WordPress server — no browser snippet to paste, no third-party cookies, and nothing an ad blocker can stop.

What it does

• Sends a purchase event to Aopy once payment is actually confirmed — including cash on delivery and bank transfer, which never involve a payment gateway. An order that was created but never paid is never counted as a sale.

• Works with BOTH the classic checkout and the newer Checkout Block, so no order is silently missed regardless of which one a customer used.

• Retries automatically if Aopy cannot be reached — for purchases AND refunds — so a momentary network problem does not silently lose a sale or leave a refunded one standing.

• Sends an “added to cart” event so Aopy’s abandoned-cart automations have real signal to work with — something no order-only integration can provide.

• Adds an opt-in checkbox at checkout, never pre-ticked, on both the classic checkout and the Checkout Block. Only shoppers who tick it become mailable contacts in Aopy; placing an order alone never does.

• Recovers carts in one click. Links in your Aopy emails can rebuild the shopper’s cart and apply the coupon you promised, then drop them straight on checkout.

• Loads Aopy’s on-site tracker for you once your store is connected, so product views and browsing sessions reach Aopy without you editing your theme.

• Adds a “Notify me when the price drops” button under the Add to Cart button on every product page, so shoppers can sign up for your Price Drop Alert automation without you wiring anything yourself.

• Shows the popups you build in Aopy — sign-up forms, discount offers, spin-to-win — with nothing to paste. The plugin tells Aopy what kind of page each visitor is on, so a popup meant for product pages appears only there. Use the shortcode [aopy_form id="..."] to place an embedded sign-up form in your footer or anywhere else.

• Reports refunds, whole or partial, so your Google Ads and Google Analytics reporting stops counting revenue you gave back.

• Tells you whether it is actually working. The settings screen shows your last successful send, your last error, and a “Send test event” button that reports exactly what Aopy answered.

• Respects your site’s cookie/consent banner. If a consent plugin (Complianz, Cookiebot, CookieYes, or any plugin implementing the WP Consent API) is active, advertising click identifiers and on-site behaviour are recorded only for shoppers who granted consent. Orders, refunds and carts are reported either way, carrying the shopper’s actual consent answer, because an order is a contract you already perform under — and Aopy applies your account’s own consent rules to it.

• Fully compatible with WooCommerce’s High-Performance Order Storage (HPOS). Every order value is read and written through WooCommerce’s own API, never raw post meta.

External service: Aopy

com. The plugin does nothing on its own — it requires an Aopy account and a REST key from that account. Order and cart data from your store is transmitted to Aopy’s servers so it can power your segments, automations, and advertising conversion reporting.

Data sent to Aopy when an order is paid: order ID, order total, currency, and for each line item its product ID, SKU, name, category, quantity and unit price; plus the billing email address, and — when present on the order — the billing phone number, first name, last name, and the customer’s IP address and browser user-agent as recorded by WooCommerce on the order.

Advertising click identifiers, when present: the values of your own Meta Pixel’s _fbp and _fbc cookies, and any fbclid, gclid, gbraid, wbraid or ttclid parameter present in the address the visitor arrived on. These identify the ad click, not the person, and are forwarded so your Meta, Google Ads and TikTok reporting can credit the correct campaign for the sale. They are only ever recorded for a visitor who has granted statistics consent.

Data sent to Aopy when a customer starts checkout: order ID, order total, currency, line items as above, and the billing email address, so that abandoned-checkout automations can reach customers who did not complete payment.

Data sent to Aopy when an order is refunded: order ID, refund ID, currency, the amount refunded, the order’s remaining value, and the billing email address. This is what lets Aopy tell Google Ads and Google Analytics that a sale was returned, so your advertising reports stop counting revenue you gave back.

Data sent to Aopy when a product is added to the cart, removed from it, or its quantity changes in the cart: product ID, SKU, name, the quantity added or removed, price and store currency.

Popups: the on-site tracker asks Aopy which of your popups are active, identified only by your own public tracking key. When a shopper fills one in, what they typed — their email address, and a phone number or name if your popup asks for one — is sent to Aopy as a sign-up. Nothing is sent for a popup a shopper only sees and closes, beyond the anonymous count that tells you how often it was shown.

Data sent to Aopy when a shopper ticks the checkout opt-in box: their email address, name and phone number as entered on the order, together with the order number and your store address, recorded as the source of their consent.

Data sent about your installation, daily and after each plugin update: the versions of this plugin, WooCommerce, WordPress and PHP, your site address, your store’s currency, time zone and site title, whether High-Performance Order Storage is on, whether a consent plugin is present, whether the checkout opt-in is enabled, whether this plugin can create discount codes for Aopy, and when this plugin last successfully reached Aopy. This describes the software and your store’s settings, never your shoppers.

Discount codes: once your store is connected, the plugin asks Aopy about every 15 minutes (every 30 seconds while codes are waiting) whether there are discount codes to create for your campaigns or automations. These requests carry only your REST key and a signature.

When Aopy answers with codes, the plugin creates them as WooCommerce coupons with exactly the limits Aopy sent (discount, expiry date, one use per code, minimum order), then tells Aopy which codes were created, which were refused and which it did not get to. Nothing is downloaded and run: Aopy can only ask for coupons.

No payment details are ever transmitted, and no browsing history is collected by this plugin. The plugin sends nothing at all until you enter a valid REST key.

By using this plugin you agree to Aopy’s Terms of Service and Privacy Policy.

Setup

• In your Aopy dashboard, open Integrations > WooCommerce and copy your REST key (it starts with rk_ ).

• In WordPress, go to Plugins > Add New, search for “Aopy”, then install and activate it. WooCommerce must already be active.

• Go to Settings > Aopy, paste the key and save.

• Press Send test event and confirm it reports success. This is the fastest way to tell a mistyped key apart from a server that cannot reach Aopy.

• Place a test order and confirm it appears in your Aopy dashboard.