Affiliatant for WooCommerce
| 开发者 | havenswift-hosting |
|---|---|
| 更新时间 | 2026年10月28日 23:54 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Click capture, server side. A shopper arriving with
?aftid=is recorded by PHP on the landing request. The click id is kept in a first-party cookie, for thirty days by default, and on the WooCommerce session. - A beacon for cached pages. A cached page never runs PHP, and some edge
caches strip the query string before the request reaches the origin. A small
script reads the address bar and posts the click id to your own site's
admin-ajax.php. It posts to your site, not to ours, and it sends nothing when there is no click id in the URL. - Classic checkout and Blocks. The referral is bound to the order on both the classic checkout hooks and the Store API hooks the Blocks checkout uses.
- Sales. An order reaching a status you count as paid is reported once. The default is whatever WooCommerce itself calls paid.
- Refunds and cancellations. A refund or a cancellation is reported as a reversal, so a commission can be withdrawn.
- Subscription renewals. Renewal payments taken by WooCommerce Subscriptions are reported, carrying the id of the order that started the subscription.
- Coupon codes. Codes used on the order are sent, so a sale can be attributed to a code when there was no click to follow.
- sub1 to sub5. Five pass-through parameters are carried from the landing URL to the conversion.
- A local queue. Every event is written to a table in your own database first and sent afterwards by a background job, through Action Scheduler where it is available and WP-Cron where it is not. A checkout is never held up by a network call, and an event that cannot be sent is retried rather than lost.
- Reconciliation. The server report and the receipt pixel carry the same deterministic event id, so one sale is counted once.
- A receipt pixel, which can be switched off.
- A connection test that sends a real conversion marked as test data, so pressing it proves the key, the programme id, the signature and the network at once without creating a commission.
- A status panel showing the queue, the last event sent and the last error, with retry and clear.
- An order meta box showing the click id bound to that order, and letting you set one by hand.
- Test mode, which marks everything sent as test data.
- HPOS and Blocks compatibility, declared. Order data is read and written through the WooCommerce CRUD API only.
安装:
- Install and activate WooCommerce first. This plugin records nothing without it.
- Upload the folder to
/wp-content/plugins/and activate it, or install it from the Plugins screen. - Create a programme at https://affiliatant.com and generate an API key for it.
- Go to WooCommerce > Affiliatant and enter the API key, the key prefix, the signing secret and the programme id.
- Press "Send a test conversion". It sends one conversion marked as test data and tells you what came back.
- Place a test order on your store with
?aftid=on the landing URL and check that it appears in the status panel.
屏幕截图:
常见问题:
Does it need an Affiliatant account?
Yes. The plugin reports to Affiliatant and has no function without an account there. See "External services" above for exactly what is sent and when.
Does it work without WooCommerce?
No. It reads WooCommerce orders and hooks WooCommerce events. With WooCommerce inactive it records nothing and shows a notice saying so.
Does it expire, or stop working?
No. There is no trial, no licence check and no feature in this plugin that waits for a payment. What is in the description is what it does, permanently.
Can it slow down or break my checkout?
The event is written to a table in your database during the request and sent afterwards by a background job, so a normal checkout makes no outbound call at all. Nothing in the sending code is allowed to throw out of a WooCommerce hook: if Affiliatant is unreachable the checkout completes and the event waits in the queue.
What customer data leaves my site?
The numeric WordPress customer id, where the shopper has an account, and nothing else about the person. No name, email, address, telephone number or IP address is sent from your server. The receipt pixel is a request from the shopper's own browser, so it carries their IP address the way any third-party image does; turn the pixel off if you do not want that.
Does it set a cookie?
Only for a shopper who arrives with a referral in the URL. The cookie holds a token that points at the click, is first-party, HTTP-only, secure on HTTPS, and lasts thirty days by default. You can set it between one and 365 days.
What happens to my data if I delete the plugin?
The settings are deleted. The queue table is left in place, because it is the
record of which orders were reported and which were not. Drop it by hand if
you want it gone; the name is in uninstall.php.
Does it work with the Blocks checkout and with HPOS?
Yes. Compatibility with high-performance order storage and with the cart and checkout blocks is declared, and order data is read and written only through the WooCommerce CRUD API.
Does it support WooCommerce Subscriptions?
Renewal payments are reported when WooCommerce Subscriptions is active. The plugin does not require it.
更新日志:
- The bundled API client no longer contains cURL or stream fallbacks. All HTTP goes through the WordPress HTTP API.
- First release.