Aopy for WooCommerce

By aopy

0+ active installationsVersion 1.15.1

Connect WooCommerce to Aopy for email marketing, abandoned-cart recovery and automation, with a checkout opt-in and one-click cart recovery.

Description

Aopy for WooCommerce connects your store to Aopy (aopy.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

This plugin is an interface to Aopy, a third-party marketing service at 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; and a one-way fingerprint (SHA-256) of the order key, never the key itself.

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 the status of an order Aopy already received changes (only when Aopy reads your store through this plugin): order ID, the new status (for example cancelled, failed, refunded or completed), when it changed, the order’s paid and completed dates, and a one-way fingerprint (SHA-256) of the order key. The order key itself is never sent. This is what keeps a cancelled or failed order out of your sales in Aopy.

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 signs up in the WoodMart theme’s own price tracker (only when you turn this on for your Price Alert flow in Aopy, and only for a sign-up WoodMart accepted): the email address they typed (or, when they are logged in, their account email address), the product ID and the variation ID they chose, the desired price they entered, the language of the confirmation email, and the address of the page they signed up on. Aopy then emails them to confirm before any price alert is sent.

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 or send it your products and reviews, and when this plugin last successfully reached Aopy; when Aopy reads your store through this plugin, also how many approved product reviews your store has. 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.

Products: only when Aopy reads your store through this plugin (because your firewall blocks Aopy) and Aopy asks for it, the plugin sends your product catalogue right after an update, then once a day: for each product and its variations, the same fields WooCommerce’s own REST API returns for it (name, SKU, prices, stock, categories, tags, attributes, image addresses, status and custom fields). Products in the trash are not sent. No customer or order data is part of it.

Product reviews: only when Aopy reads your store through this plugin (because your firewall blocks Aopy) and Aopy asks for them, the plugin sends your approved product reviews in the background when Aopy first asks, and all of them again after each plugin update, when Aopy’s review sending is turned back on, after a new REST key, when the plugin is reactivated, and when too many changes are waiting to be sent one by one. In between it sends each review that is added, edited, approved, held, marked as spam, trashed or deleted, about a minute later. It also sends again the reviews of a product you restore from the trash, the published reviews of a person named in an erasure request, and any changes that waited while tracking was off, when tracking is switched back on. For each review: the product and its name, the reviewer’s name and email address, the review text, the star rating, whether the reviewer is a verified buyer, the date and that it is published. A review you hold, mark as spam, trash or delete, or whose product you trash, is sent only as its review number and its new status, with no text, name or email address, so Aopy stops showing it. What Aopy received while it was published stays in your Aopy account, hidden from shoppers; to have it removed, contact Aopy support. Reviews that were never published are not sent. When tracking is switched off in the plugin’s settings, no reviews are sent.

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

  1. In your Aopy dashboard, open Integrations > WooCommerce and copy your REST key (it starts with rk_).
  2. In WordPress, go to Plugins > Add New, search for “Aopy”, then install and activate it. WooCommerce must already be active.
  3. Go to Settings > Aopy, paste the key and save.
  4. 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.
  5. Place a test order and confirm it appears in your Aopy dashboard.

FAQ

Does this slow down checkout?

No. Nothing a shopper does waits for Aopy. Add-to-cart, checkout and payment events are handed to WooCommerce’s own background scheduler (Action Scheduler) and sent a moment later, with automatic retries if Aopy is unreachable.

Does this work with the new block-based checkout?

Yes — this is one of the two things this plugin was specifically built to get right. It hooks both the classic checkout AND the Checkout Block (Store API), since WooCommerce fires a different action for each.

What happens if a customer has not accepted cookies/tracking?

Their advertising click identifiers and on-site behaviour are not recorded at all — not recorded and then withheld. Their order and any refund on it are still reported to Aopy, carrying their actual consent answer, because reporting a sale you have already made is part of running the shop rather than something a cookie banner governs. Aopy then applies your account’s own consent rules, which by default store nothing for a shopper who has not agreed.

I do not have a cookie consent plugin. Does this work?

Yes, for orders, refunds and the checkout opt-in, and for carts unless your Aopy account uses strict consent (the default), which keeps cart activity only from shoppers who agreed, so the plugin does not send it. Advertising click identifiers and on-site behaviour stay off until you install a consent plugin. Complianz, CookieYes and Cookiebot are read directly; any other consent plugin needs the WP Consent API. The settings screen says so plainly rather than letting you believe everything is running.

Does the opt-in checkbox come pre-ticked?

No, and it cannot be configured to. A pre-ticked marketing box is not valid consent under the GDPR, and that is your liability, not ours.

How do I put a popup on my store?

Build it in Aopy and set it live. Nothing to paste here — the plugin already loads Aopy’s tracker, and the tracker brings every active popup with it. For an embedded sign-up form (one that sits in the page rather than floating over it), copy the popup’s id from Aopy and put [aopy_form id="the-id"] where you want the form, for example a footer widget.

Do I need an Aopy account?

Yes. This plugin is an interface to Aopy (aopy.com) and does nothing without an account and a REST key from it. See “External service: Aopy” above for exactly what data is sent and where.

What happens to my data if I uninstall the plugin?

Uninstalling deletes the plugin’s own settings from your WordPress database, including your stored REST key. It does not touch your orders, products, or customers, and it does not delete anything already sent to Aopy — to remove that, use your Aopy account.

Screenshots

Changelog

1.15.1

  • New: you can change the checkout opt-in wording from Aopy, next to its on/off switch; your store picks it up at its next check-in.
  • Fix: a long opt-in wording is cut at 200 characters, never in the middle of a letter.

1.15.0

  • New: WoodMart price tracker sign-ups can be sent to Aopy price alerts, with the shopper’s desired price, when the store turns it on in Aopy.
  • Changed: cart and checkout activity reaches Aopy only when the shopper’s cookie choice allows it. A shopper who refuses sends nothing more, and that refusal reaches Aopy for the same visitor, retried until Aopy receives it.
  • Fix: the checkout opt-in wording can no longer be an email address (browser autofill from the settings page); a stored email falls back to the default sentence. The checkout opt-in box is now off by default on new installs; stores already connected keep it on.
  • New: the checkout opt-in box can be turned on or off from the store page in Aopy; the plugin applies the change at its next check-in.

1.14.1

  • Fix: the checkout opt-in box never shows an email address as its text, and a browser can no longer fill a login email into the opt-in wording field.

1.14.0

  • New: Complianz, CookieYes and Cookiebot are read directly, even without the WP Consent API plugin. When a shopper accepts or refuses in your cookie banner, Aopy gets that answer.
  • Changed: ad personalization now follows the shopper’s marketing choice, the same way your cookie banner sends it to Google.
  • Fixed: with Complianz set to load statistics without asking, Aopy no longer counts that as the shopper’s consent. It waits for the shopper’s marketing choice.

1.13.0

  • New: Settings > Aopy is rebuilt around your store’s status. It says in plain words whether the connection works, when the last send worked, when Aopy last heard from the store, and how many items wait to be sent again.
  • New: when something is wrong, the reason is written in plain words and the button that fixes it sits next to it. Before connecting, one button opens Aopy and the key arrives on its own.
  • New: a “Notify me when back in stock” button on sold-out products. It stays hidden until you turn the Back in Stock alert on in Aopy. Shoppers leave their email and get a message when the product is available again.
  • Added: the Aopy screen and the new button are also translated into Romanian.

1.12.0

  • Fixed: on stores whose firewall blocks Aopy, a cancelled, failed or refunded order now leaves your sales in Aopy. Before, Aopy kept counting it as a sale.
  • Fixed: an order cancelled in the few seconds before the plugin sent it to Aopy is now reported as cancelled right after it.
  • Added: after you install this update, orders cancelled, failed or refunded in the last 90 days are sent to Aopy once, 50 a minute in the background. Nothing to press.
  • Improved: a status change Aopy refuses now shows on the settings screen and goes again with “Resend rejected orders”.
  • Fixed: the /wp-json/aopy/v1/id endpoint tells page caches, LiteSpeed and CDNs never to store its answer, and no longer echoes a visitor’s cookie without consent, so a cache cannot hand one shopper’s id to another.

1.11.0

  • Fixed: when Aopy is briefly unreachable, the plugin now keeps your orders, refunds, newsletter sign-ups and shoppers’ cookie choices and sends them again automatically, for up to about 31 hours (a cookie withdrawal for up to 30 days). Before, an error page shown instead of Aopy could mark orders as rejected and drop the rest.
  • Fixed: orders that were marked rejected while Aopy was unreachable on 3 November 2026 are sent again once, automatically, when you install this update, if they were rejected in the last 7 days. Nothing to press.
  • Improved: an order that still cannot be sent after all retries now shows under “Orders Aopy rejected” on the settings screen, ready for “Resend rejected orders”, instead of being given up silently. The resend button now also re-sends rejected refunds.
  • Improved: the settings screen shows refunds Aopy rejected and cookie withdrawals still waiting to reach Aopy.
  • Fixed: the “Notify me when the price drops” button no longer shows on your product pages while your Aopy Price Drop automation is off. The plugin now also comes with a Romanian translation.
  • Note: while Aopy is unreachable, the plugin keeps at most 500 waiting sends (5 MB) on your server; past that the oldest cart events are dropped first, never a cookie withdrawal.

1.10.2

  • Added: stores whose firewall blocks Aopy can now send their product reviews to Aopy through this plugin, so reviews work in Aopy there too. When Aopy asks for it, the plugin sends your approved reviews in the background, then each new, edited, hidden or deleted review about a minute later (the data section above lists when all of them go again); your shoppers never wait for it.
  • Note: on those stores the plugin’s daily check-in with Aopy also says how many approved product reviews your store has.
  • Fixed: on stores using the WP Consent API, a cached page could hand one visitor’s anonymous id to other visitors, so their visits were counted as one person. Pages no longer carry any visitor id.

1.10.1

  • Improved: on stores whose Aopy account uses strict cookie consent and that have no consent plugin, adding, changing or removing cart items no longer sends data that Aopy would discard anyway. This makes add-to-cart faster on those stores.
  • Changed: on those stores, the “Consent declined” count in Aopy now reads lower, because those cart events are no longer sent at all.
  • Note: on stores where WordPress reads settings only when needed, each cart action reads up to 3 small plugin settings to decide this.
  • Note: after you switch your Aopy account away from strict consent, cart events can stay unsent for up to 26 hours.

1.10.0

  • Added: stores whose firewall blocks Aopy can now send their products to Aopy through this plugin, so product sets, feeds and product emails work there too. When Aopy asks for it, the plugin sends your whole catalogue in the background right after the update, then once a day, in small batches; your shoppers never wait for it. Products in the trash are not sent.

1.9.1

  • Fixed: the “Notify me when the price drops” button now shows on product pages of block themes such as Twenty Twenty-Five, the WordPress default. Before, it showed only on classic themes.
  • Improved: the plugin now tells WooCommerce it works with the block Cart and Checkout. The newsletter checkbox at checkout already worked there; this only removes the “not confirmed” mark.
  • Tested with WordPress 7.1 and WooCommerce 11.2.

1.9.0

  • Added: stores whose firewall blocks Aopy (for example Cloudflare’s bot protection) can now connect through this plugin. After you connect, the plugin tells Aopy your store’s currency, time zone and name, and Aopy finishes the connection without needing to reach your store.
  • Added: discount codes for your Aopy campaigns and automations are now created by the plugin itself, inside your store, so they work even when your firewall blocks Aopy. The plugin checks for new codes about every 15 minutes in the background; your shoppers never wait for it.
  • Improved: after an update, the plugin tells Aopy its new version on its own, instead of waiting up to a day.

1.8.1

  • Fixed: the plugin no longer treats the mere presence of the WP Consent API as visitor consent. Before, a store with the API installed but no cookie banner configured (or an opt-out banner where the visitor had not chosen yet) could send visitors’ analytics, marketing and preferences as “granted”. Now a purpose counts as granted only when your cookie banner has set a consent type and the visitor explicitly allowed that purpose; a refusal is recorded as a refusal, and anything not answered stays unknown, so Aopy applies your strict consent mode. Each purpose is read on its own: allowing statistics does not allow marketing.

1.8.0

  • Added: the plugin serves a small browser-notification worker file at /aopy-push-sw.js (scope /aopy-push/) so Aopy web push can run on your store. It does nothing until you turn push on in Aopy. If you use a cache plugin, exclude /aopy-push-sw.js from caching: WP Rocket > Advanced Rules > Never Cache URL(s); LiteSpeed Cache > Excludes > Do Not Cache URIs; Cloudflare > a Cache Rule that bypasses cache for that path.

1.7.3

  • Fixed: a shopper who arrives from an ad and accepts your cookie banner on that first page now keeps the ad click on their order. Before, the click was only remembered when consent already existed when the page loaded.
  • Improved: every request this plugin sends to Aopy is now signed with your key and a timestamp, so a copied request cannot be replayed later.
  • Fixed: a store whose clock is wrong now corrects itself from Aopy’s answer and resends, so its orders and refunds are not lost.

1.7.2

  • Fixed: cart events now tell Aopy they come from this plugin, so an abandoned-cart email prices each product at its real unit price and keeps a product whose quantity you lowered, instead of reading them as another store’s events.

1.7.1

  • Fixed: the tracker snippet now actually calls your site’s own /wp-json/aopy/v1/id endpoint (added in 1.7.0) after cookie consent, once per browser visit, so Safari’s 7-day limit on script-set cookies is genuinely bridged rather than only available. Never blocks a page view or an event, and falls back to the previous behaviour on any failure.
  • Fixed: the snippet’s list of Aopy methods was missing checkoutStep, added in the same release as this fix — a theme calling it before the full tracker finished loading would have thrown.

1.7.0

  • Added: removing a product from the cart, changing its quantity in the cart, and undoing a removal are now reported to Aopy, in both the classic and the block cart, through the same background queue as add-to-cart.
  • Added: Aopy’s tracker is excluded from script delaying and combining in WP Rocket, LiteSpeed Cache, SiteGround Optimizer, Autoptimize and Cloudflare Rocket Loader, so a visitor who reads a page and leaves is still counted.
  • Added: with a WP Consent API plugin, a shopper who accepts or withdraws cookies after the page loaded is honoured at once, without a reload.
  • Fixed: a returning visitor’s cart and order events now use the browser’s own persistent identity (the _cdm_aid cookie) when one exists, instead of always minting a fresh WooCommerce session id — previously that split one shopper’s second visit into two separate Aopy profiles.
  • Added: a new /wp-json/aopy/v1/id endpoint on your own site refreshes the visitor identity cookie from your server, so Safari’s 7-day limit on script-set cookies no longer resets a returning shopper’s identity. Runs only with your cookie consent already granted, does not touch your database, and never leaves your site.

1.6.1

  • Faster: adding to cart, checking out and paying no longer wait for Aopy. Events are handed to WooCommerce’s own background queue (Action Scheduler) and sent a moment later, with automatic retries if Aopy cannot be reached.
  • Fixed: deleting the plugin now also removes its pending background retries.

1.6.0

  • Added: one-click “Connect to Aopy”. Press the button, approve this store in Aopy, and your REST key is delivered automatically — nothing to copy or paste. The manual key field still works and now lives under “Advanced” for anyone who prefers it, or whose site cannot reach Aopy directly.

1.5.4

  • Fixed: the price-drop button’s JavaScript is now enqueued through WordPress instead of being printed inline on the product page.

1.5.3

  • Changed: every setting, scheduled task and order note the plugin stores now uses the aopy_ prefix, and the plugin declares WooCommerce as a required plugin.

1.5.2

  • Added: a “Notify me when the price drops” button on every product page, wired to your Price Drop Alert automation. Shows the shopper whether they were subscribed, already subscribed, or need to give their email or accept marketing cookies first — never a silent failure.

1.5.1

  • Improved: when your ad links carry the ad group and the ad name, your orders now bring them to Aopy too, so you can see which products sold through each ad group and each ad, not only each campaign.

1.5.0

  • Added: popups. Every popup you build in Aopy now appears on your store on its own, with nothing to paste and no per-popup setup. Your popup’s own targeting decides where it shows.
  • Added: your store now tells Aopy what kind of page a visitor is on — home page, product, category, cart, checkout, search or blog — so a popup meant for product pages appears only there, whatever your permalinks look like.
  • Added: the shortcode [aopy_form id=”…”] places an embedded sign-up form anywhere you can put a shortcode, for example your footer. Copy the id from the popup’s page in Aopy.

1.4.0

  • Changed: the plugin is now called “Aopy for WooCommerce” (previously “Aopy Tracking”), which describes what it is for: abandoned-cart emails, post-purchase automations and checkout sign-ups.
  • Removed: the self-hosted updater. Updates are now delivered only through WordPress.org, like every other plugin in the directory.

1.3.1

  • Changed: the plugin now tells Aopy each consent purpose separately (statistics, marketing, preferences) instead of one yes/no. A shopper who allowed statistics but refused marketing is measured, but their details are never sent to Meta, Google or TikTok. Orders and refunds carry the same purpose-by-purpose answer frozen at checkout.
  • Fixed: a shopper who accepted, then declined, then accepted, then declined again in one visit now has BOTH refusals delivered; the second used to be dropped.
  • Fixed: an order or refund that Aopy rejected outright (for example while a wrong REST key was saved) used to be marked as tracked and skipped forever. It is now shown on the settings screen as “Orders Aopy rejected”, with a “Resend rejected orders” button that re-queues them once the cause is fixed.
  • Added: orders now carry the visit’s traffic source (WooCommerce’s own Order Attribution: UTM source, medium, campaign, landing page, referrer) and, when the shopper allowed statistics, the Google Analytics client id from your own gtag cookie — so Aopy can report a Google Analytics purchase under the same visitor your GA4 property already knows, instead of inventing a new one.
  • Fixed: when a shopper arrived through several Google ads on different visits, the order used to carry more than one Google click id, which Google rejects. Only the most recent click is kept.

1.3.0

  • Fixed: on a store with no cookie-consent plugin installed, this plugin used to send nothing at all — no orders, no refunds, no carts — while the settings screen said “Tracking is active”. Sales are now always reported, carrying the shopper’s real consent answer, and Aopy applies your account’s own consent rules to it. Advertising click identifiers still require consent and always will.
  • Fixed: the settings screen now tells you the truth. It shows your last successful send, your last error, whether your store is connected to Aopy, whether a consent plugin is present, and your WooCommerce, WordPress and PHP versions.
  • Added: a “Send test event” button. It sends one real event with your saved key and reports exactly what came back, so a wrong key looks different from a blocked connection.
  • Added: an opt-in checkbox at checkout, never pre-ticked, on both the classic checkout and the Checkout Block. Before this, a WooCommerce store could sync thousands of customers into Aopy and email none of them, with nowhere to fix it.
  • Added: one-click cart recovery. A link in your Aopy email can rebuild the shopper’s cart, apply the coupon you promised, and drop them on checkout.
  • Added: the Aopy on-site tracker is loaded for you once your store is connected, so product views and browsing reach Aopy without editing your theme.
  • Added: automatic updates. New versions now appear on your Plugins page instead of waiting for you to notice one and upload it by hand.
  • Fixed: a refund whose delivery failed with a server error was marked as sent and never tried again, leaving a conversion standing at Google Ads and Google Analytics for money you had already given back. Refunds now retry with the same backoff purchases use.
  • Fixed: refunds now carry the date the refund actually happened. They were previously filed on the day Aopy received them, which put a delayed one in the wrong day — and at month end, the wrong month.
  • Fixed: the guard preventing one checkout being reported twice did not cover several of its own exit paths.

1.2.2

  • Added: purchases and refunds now say which store they came from, so a business running more than one WooCommerce site has each sale filed under the right one instead of being rejected.
  • Added: purchases are reported with the time the order was actually placed, so a delayed or backfilled send no longer lands in your reports as “today”.
  • Added: purchases and refunds now carry the shopper’s own visit id, so the sale joins up with the product views and cart activity that led to it. Before this, you kept the order and lost the story behind it.
  • Added: the consent decision recorded at checkout is now sent with the purchase and the refund, so your advertising platforms are told the basis on which the data was shared — and a shopper who says no is honoured everywhere, not just at collection time.
  • Added: when a shopper who had agreed to tracking changes their mind during a visit, that withdrawal is now sent to Aopy. Before this the plugin simply went quiet — and going quiet looks exactly like never having been there, so their earlier “yes” stayed on file and their details could keep being shared with advertising platforms.

1.2.1

  • Cart events now report the parent product id (variation id moved to its own field) so add-to-cart joins the product catalog.

1.2.0

  • Added: refund tracking. When you refund an order — in full or in part — Aopy now tells Google Ads and Google Analytics, so your advertising reports stop counting revenue you gave back. Meta and TikTok are not included because their APIs have no way to reverse a conversion.

1.1.0

  • Fixed: purchases were reported when the order was CREATED, which happens before the customer pays. A declined card or an abandoned payment page counted as a sale. Purchases are now reported only once payment is confirmed, including cash on delivery and bank transfer.
  • Fixed: a failed send is now retried automatically with backoff instead of being lost. Duplicate sends are impossible — Aopy matches on the order number.
  • Added: checkout-started tracking, so abandoned-checkout automations can reach shoppers who got as far as the payment step.
  • Added: the customer’s consent decision is now recorded on the order at checkout, so it is applied correctly later even when payment is confirmed by the gateway or by hand in the admin.
  • Added: ad-campaign attribution. When your Meta/Google/TikTok click information is available, it is forwarded with the purchase so your ad reporting can credit the right campaign.

1.0.0

  • Initial release: order tracking (classic + block checkout), cart-add tracking, WP Consent API integration, HPOS compatible.