Affiliate plugin data paths
Where WordPress affiliate plugins keep or send click data
Affiliate and link plugins exist to track clicks. Some keep click records on your WordPress host and set first-party cookies for unique-click counting. Others send product or affiliate traffic through an outside network. This table summarizes the documented setups below. Your settings can change where data goes.
Based on plugin documentation, not tests of your site. Your settings can change what loads. This is not legal advice or a compliance rating.
Scan your site for third-party requestsHow we group affiliate plugins
We compare the affiliate and link setups named below. A plugin can keep click records on your server and still set first-party cookies for unique-click counting. Outside commerce networks appear when product or affiliate traffic is sent off-site. We have not tested when cookies start relative to consent or assessed how long data is kept.
Affiliate and link plugins
No paid placement. On your server first, then outside networks, then plugins not yet reviewed. Names are alphabetical within each group.
| Plugin | Documented behavior | Cookies / receiving domains | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| AffiliateWP (referral cookies on) AffiliateWP docs: first-party cookies affwp_ref, affwp_ref_visit_id, and affwp_campaign (campaign URLs only) credit affiliates when a visitor arrives via a referral link. Referral records are stored in your WordPress database. Consent timing is not tested here. | On your server (first-party cookies) | Cookies: affwp_ref, affwp_ref_visit_id, affwp_campaign | Not assessed | Not tested |
| |
| Pretty Links (click tracking on) Pretty Links docs: first-party cookies prli_visitor (1 year), prli_click_* (30 days), and prli_dedup_* (10 seconds) count unique clicks. Click rows are stored in your WordPress database. Docs state these cookies are not shared with third parties. Consent timing is not tested here. | On your server (first-party cookies) | Cookies: prli_visitor, prli_click_*, prli_dedup_* | Not assessed | Not tested |
| |
| AAWP (geo-targeting on) With geo-targeting enabled, AAWP uses an outside service to look up the visitor's country from their IP address, then stores the country in the aawp-geotargeting cookie. Consent timing is not tested here. | Outside service | Cookies: aawp-geotargeting · Receiving domains not verified | Not assessed | Not tested |
| |
| Affiliates Manager We have not reviewed this plugin's affiliate data path yet. | Not reviewed | Documentation not reviewed yet. | Not assessed | Not tested |
| |
| EasyAzon We have not reviewed this plugin's affiliate data path yet. | Not reviewed | Documentation not reviewed yet. | Not assessed | Not tested |
| |
| Lasso We have not reviewed this plugin's affiliate data path yet. | Not reviewed | Documentation not reviewed yet. | Not assessed | Not tested |
| |
| Link Whisper We have not reviewed this plugin's affiliate data path yet. | Not reviewed | Documentation not reviewed yet. | Not assessed | Not tested |
| |
| SliceWP We have not reviewed this plugin's affiliate data path yet. | Not reviewed | Documentation not reviewed yet. | Not assessed | Not tested |
| |
| ThirstyAffiliates We have not reviewed this plugin's affiliate data path yet. | Not reviewed | Documentation not reviewed yet. | Not assessed | Not tested |
| |
| WP Affiliate Manager We have not reviewed this plugin's affiliate data path yet. | Not reviewed | Documentation not reviewed yet. | Not assessed | Not tested |
|
What this table does and does not prove
This table describes the named affiliate setups. It does not show what loads on your site. First-party cookies and outside networks can both apply. We have not tested consent timing, and we have not assessed how long data is kept. This scan does not read click records inside your database.
Documentation snapshot: Sep 29, 2026. Sources are linked in each reviewed row.
Scan your site for third-party requests/wp-affiliate-plugin-privacy