Referly.so – Affiliate & Referral Program for WooCommerce

Changelog

2.5.0

• Security: every order, refund, sign-up and coupon call to Referly is now signed with a key issued to this site (HMAC-SHA256 with a timestamp and a single-use nonce), so nobody else can send Referly orders in your store’s name. Referly is ending support for unsigned calls from older versions.
• New “Connect with Referly” button: sign in to Referly, pick your program and approve the store. It connects the program and the signing key in one step, and the key never passes through your browser.
• Can’t use the button? Paste a connection key created in Referly, or request approval from the plugin and approve the store in Referly.
• Calls that fail on the network or while Referly is busy are retried automatically through Action Scheduler (included with WooCommerce).
• The header shows whether this store’s requests are signed, and the Settings tab can test the connection.

2.4.1

• Security: every form handler checks a nonce before it reads submitted data, including the WooCommerce registration and checkout fields used for sign-up tracking.
• The plugin is now listed as Referly.so (text domain referly-so).

2.4.0

• The plugin is now Referly everywhere: the readme, the plugin description and the admin page.
• New dashboard in WordPress with tabs for Overview, Affiliates, Sales, Payouts, Ad tracking and Settings.
• Add a Referly API key on the Settings tab to see revenue from affiliates over the last 30 days, top affiliates, recent sales, commissions owed and payout batches. The data is cached for five minutes; Refresh fetches it again.
• Every form on the Referly page is now protected with a nonce and only works for administrators.
• The tracking script is now loaded through wp_enqueue_script(), and every value read from cookies, forms and request headers is sanitized.
• Requires WordPress 6.5 or newer.
• Removed the developer-only setting that pointed the plugin at a test copy of Referly, and the request relay that came with it. Every request goes to referly.so.
• Removed the unused “NET or GROSS” setting. It had no effect on how sales were recorded.
• Tested up to WordPress 7.1.

2.3.4

• Referly Atlas: changing an order’s status in the WordPress admin no longer tags the order with the shop manager’s own visit. Orders, sign ups and leads only carry the shopper’s identifiers when they come from the shopper’s own browser (the store, the classic checkout or the block checkout).
• Referly Atlas: orders now include WooCommerce’s own order attribution (the page the visit started on and its referrer), so an ad click still counts when an ad blocker stopped the Referly tracker. Needs WooCommerce order attribution turned on (WooCommerce 8.5 or later, on by default).

2.3.3

• Referly Atlas: every Google Ads conversion now fires on WordPress and WooCommerce sites. Sign ups, leads, trials and subscriptions were only sent to Referly from your server, so Google Ads never saw them. The plugin now also announces them in the visitor’s browser.
• Sign ups (any registration form, including “create an account” at checkout) are announced on the next page the new customer sees, for example the order received page.
• Contact Form 7 and WPForms leads are announced right after the form is sent, also when the form is sent without a page reload.
• With WooCommerce Subscriptions, the order received page announces a trial for each subscription that starts with a free trial, and a subscription for each one that does not. Referly Atlas now also records these trials and subscriptions, and a subscription when a trial turns into its first paid period.
• Each event carries the same id Referly Atlas records, so Google Ads never counts it twice and Referly Atlas reporting matches what fired.
• Affiliate tracking is unchanged.

2.3.2

• Referly Atlas: the Google Ads snippet from Referly Atlas now records add to cart, begin checkout and purchase conversions on WooCommerce stores. These events are sent to Referly from your server, so the snippet on your pages never saw them before. The plugin now also announces them in the shopper’s browser, where the snippet picks them up.
• Purchases are announced once per order on the order received page, with the same order id Referly Atlas uses, so Google Ads does not count a reload of that page twice.
• Add to cart and begin checkout events sent to Referly Atlas carry the same id as the ones announced in the browser, so Referly Atlas reporting matches what the Google Ads snippet fired to the right event.
• Nothing extra is sent to Referly Atlas, and affiliate tracking is unchanged.

2.3.1

• Referly Atlas: add-to-cart, checkout, sign-up and lead events are now sent at the end of the request, after the page has gone to the shopper, and the plugin waits for Referly’s reply. Before, they were sent fire-and-forget, and a proxy or host that drops a request whose sender has hung up lost them. Each event keeps the time it happened.
• Referly Atlas: “Verify and Save” accepts a token for a different store (for example after the store was deleted and created again in Referly). It no longer sends the previous store’s id with the new token.

2.3.0

2.2.0

• Referly Atlas: new site accounts (any registration form, including “create an account” at checkout) are sent as sign ups, and sent Contact Form 7 / WPForms forms as leads, with the visitor identifiers from the shopper’s cookies.
• Affiliate tracking is unchanged.

2.1.0

• Referly Atlas (ad tracking): new “Referly Atlas” admin card with a store token and “Verify and Save”.
• When Atlas is enabled the tracker script runs in Atlas mode, orders (with refunds and cancellations), add-to-cart and checkout events are sent to Referly Atlas server-side, and the visitor identifiers are saved on each order.
• Affiliate tracking is unchanged.

1.0.0

• Initial release.