ThirstyAffiliates vs Pretty Links: test if Amazon tags stay with cloaked links

Part of our guide on create amazon affiliate website

Direct tests using developer tools and controlled environments show how redirect type, plugin settings, and server-side caching determine whether your Amazon associate tag survives cloaking.

The differences at a glance

Both ThirstyAffiliates and Pretty Links are popular WordPress plugins used to cloak affiliate links, including Amazon links. Cloaking replaces a long affiliate URL with a shorter, branded one and performs a redirect to the merchant.

The most relevant differences for Amazon affiliates are how each plugin treats query parameters (where the Amazon associate tag lives), whether they support automatic marketplace localization, and which redirect implementations they provide.

ThirstyAffiliates includes automatic marketplace localization features in its premium version and provides options intended to forward query strings. Pretty Links focuses on offering a choice of redirect types (301, 302, meta refresh) and broad redirect options but does not include built-in Amazon localization.

Redirect behavior differs: some implementations rely on HTTP header redirects (301/302), others inject a meta refresh into HTML, and some use JavaScript. HTTP header redirects typically forward query strings when configured correctly; meta refresh and JavaScript redirects are more likely to lose parameters unless explicitly handled. For the detail, see our notes on diagnosing affiliate tag problems.

How cloaking can affect Amazon associate tag retention

Amazon associate tags are query parameters appended to product URLs (for example, ?tag=yourtag-20). If a redirect removes or fails to forward query parameters, the sale may not be credited to your associate account.

When a cloaked link is clicked, the web server or plugin redirects the browser to the Amazon URL. The redirect can be implemented in different ways: an HTTP header redirect (301 or 302), an HTML meta refresh that tells the browser to go to a new URL, a JavaScript redirect that changes window.location, or a server-side rewrite. Each method has implications for whether the original query string is preserved.

Examples of how specific redirects can cause tag loss: Before you commit to anything, it is worth looking at configuring plugins to keep tags.

– HTTP 301/302 header redirects: When implemented by sending a Location header that includes the full URL with query string, browsers follow the redirect and the query string remains. Problems arise when the plugin issues a Location header without appending the original query string or when server-side rules override the outgoing Location value.

– Meta refresh redirects: These use an HTML meta tag to tell the browser to navigate to a different URL. If the plugin outputs a meta refresh that reconstructs the destination URL but omits query parameters, the tag will be lost. Some themes or caching layers can strip or alter the generated HTML, removing the appended query string.

– JavaScript redirects: JavaScript-based redirects often read window.location and then set the destination. If the script does not reconstruct or forward the query string, or if JavaScript is blocked, parameters may be lost. We cover verify associates link in its own article.

– Server-side rewrites and proxying: If the server rewrites the URL internally (for example, using nginx try_files or Apache mod_rewrite) and does not include the query string in the rewrite rule, the tag is removed before the redirect is issued.

A concrete example: a cloaked link points to /go/productA and the plugin is supposed to redirect to https://www.amazon.com/dp/B07XYZ?tag=mytag-20. If the plugin issues a Location: https://www.amazon.com/dp/B07XYZ (without ?tag=…), or if a caching layer serves a cached page that hardcodes only the base URL, the ?tag parameter is lost and commissions may not be tracked.

It’s important to note plugin behavior can vary across versions and configurations. ThirstyAffiliates documents its query string forwarding option in its support materials; Pretty Links documents its redirect methods and notes that meta refresh operates in HTML rather than via header. See plugin documentation (links in the references section below) for exact implementation details. We cover localize amazon affiliate links in its own article.

How caching, CDNs, and server environment interfere with tag preservation

Beyond the plugin, the hosting environment, caching plugins, and CDNs can change how redirects behave and whether query parameters are forwarded.

Caching plugins that serve static responses may cache the HTML output of a redirect page (especially meta refresh pages) without the dynamic query string, or they may cache a redirect that lacks the ?tag parameter. For example, some page caches ignore query strings and serve the same cached page for all requests to a given cloaked URL; if the cached version contains a destination URL without query parameters, the tag is lost for every visitor served by the cache.

CDNs and reverse proxies (Cloudflare, Fastly, Akamai) can also normalize or strip query strings when configured to do so, or when using certain caching rules. Cloudflare’s caching by default considers the full URL (including query string) when set to 'Standard', but custom rules or page rules can override this and cause parameter stripping. Similarly, some CDNs offer query string sorting or removal to increase cache hits, which interferes with affiliate parameters. Before you commit to anything, it is worth looking at big affiliate tables comparison.

Server-level redirects or rewrites may run before the plugin and alter the request URL. For example, an nginx configuration using rewrite without the $is_args$args token will drop query strings when performing an internal rewrite. Apache’s mod_rewrite requires the [QSA] flag to append query strings on substitution—without QSA, the query string is not forwarded.

Some hosts use aggressive caching proxies that do not forward query strings between internal layers. Even if the plugin is configured to forward parameters, the proxy may intercept and remove them, resulting in tag loss. Likewise, security modules or WAFs that sanitize URI strings can inadvertently remove affiliate parameters.

Practical troubleshooting steps:

– Test cloaked links on a fresh install or a staging site with caching and CDN disabled to determine baseline plugin behavior.

– If a tag is preserved on the staging site but lost on production, systematically enable caching/CDN features one at a time and test after each change to identify the interfering layer.

– Check server rewrite rules (nginx.conf, .htaccess) for missing flags that forward query strings (QSA for Apache, $is_args$args for nginx).

– Consult your CDN provider’s documentation for query string handling and configure page rules to pass or include query strings for cloaked paths.

– If using a caching plugin (WP Rocket, W3 Total Cache, etc.), configure it to not cache cloaked redirect endpoints or to cache by query string where appropriate.

Testing methodology and references for comparative tests

To make meaningful comparisons between plugins, a repeatable test methodology is necessary. The tests referenced here used the following approach so readers can reproduce them:

– Create identical cloaked links in each plugin pointing to the same Amazon product URL with your associate tag appended (for example, https://amazon.com/dp/B07XYZ?tag=yourtag-20&otherparam=value).

– Test each cloaked URL in an incognito/private browser window to avoid cached client-side redirects and with browser devtools open to view the network redirect chain.

– Record the exact redirect responses (HTTP status codes, Location headers) and the final destination URL string after all redirects complete.

– Repeat tests across multiple environments: local development (no caching/CDN), shared host with common caching plugin enabled, and a production environment using a CDN. Also test with different redirect types offered by the plugin (301, 302, meta refresh, JavaScript) where applicable.

– Document results: whether the Location header included the query string, whether any intermediate response stripped parameters, and whether the final Amazon URL contained the tag.

Reference materials used for understanding plugin behavior and server effects:

– ThirstyAffiliates support and documentation pages describing query string forwarding and localization features (ThirstyAffiliates official docs).

– Pretty Links documentation on redirect types and implementation details (Pretty Links support articles).

– WordPress caching plugin documentation (e.g., WP Rocket, W3 Total Cache) and CDN provider docs (Cloudflare) on query string behavior and page rules.

– General HTTP redirect and server configuration references: Apache mod_rewrite QSA flag documentation and nginx rewrite variable usage.

Rather than quoting a single numeric success rate, these test steps describe how to measure retention in your environment. Published user reports and plugin discussions on WordPress.org support forums and plugin docs indicate that ThirstyAffiliates' design includes explicit query string forwarding options that make it less likely to lose tags in many common setups; Pretty Links' wider choice of redirect methods means correct configuration is more important to avoid tag loss. Specific results will vary by host, plugin version, and CDN/caching setup—so reproduce the above tests to confirm behavior for your site.

1. Create identical cloaked links with a sample Amazon URL and ?tag parameter.
2. Open in incognito/private mode and use developer tools network tab.
3. Record HTTP redirect status codes and Location headers.
4. Confirm final URL contains ?tag parameter.
5. Repeat across redirect types and hosting configurations.

Clear comparison of tag retention between ThirstyAffiliates and Pretty Links

Summary of practical findings based on design differences, documentation, and user reports:

– ThirstyAffiliates: includes query string forwarding options and a premium localization feature. Because of those features and default behavior emphasizing HTTP redirects that include query strings, it is commonly reported to preserve tags more consistently in standard hosting environments without additional configuration. However, it can still lose tags if a caching layer or server rewrite strips parameters before the plugin executes.

– Pretty Links: provides multiple redirect methods. When configured to use HTTP header redirects and when server/CDN rules allow query strings, Pretty Links preserves tags. But because it offers meta refresh and JavaScript redirects, incorrectly selected redirect types or misconfigured caching can increase the chance of tag loss.

Edge cases to watch for:

– Chains of redirects (plugin redirect + CDN redirect + server redirect) that re-encode or truncate the URL can lose parameters even if each step looks correct in isolation.

– Complex tracking parameters (multiple ampersands, encoded characters) can be mangled by layers that re-serialize query strings improperly, leading to loss of some parameters including the ?tag value.

Practical recommendation: prefer HTTP header redirects that include the full destination URL in the Location header. If using meta refresh or JavaScript redirects, verify they include the query string and test under your live caching/CDN configuration.

How link localization and tag preservation interact

Link localization changes the destination domain based on the visitor’s country so they see the correct Amazon marketplace (for example, amazon.com vs amazon.co.uk). Proper localization also needs to use the corresponding associate tag for each marketplace.

ThirstyAffiliates (premium) includes localization support intended to swap marketplace domains and the corresponding associate tag so the commission can be tracked correctly for visitors from different countries. That requires the plugin to rewrite or construct a destination URL that includes the correct regional ?tag parameter and then forward it via a redirect that preserves query strings.

Pretty Links lacks built-in marketplace localization. If you implement localization through a separate plugin or custom code, you must ensure that the localization step appends the appropriate regional tag and that the final redirect preserves it.

Important distinction: localization changes the final destination and the tag itself; preservation ensures that that tag is actually sent to Amazon during the redirect. You need both working together to get commissions in each marketplace.

Which should you buy for Amazon cloaking and tag preservation

If your primary need is an out-of-the-box solution that handles localization and includes options to forward query parameters, ThirstyAffiliates (especially its premium features) is a solid choice in common hosting environments — but remember to test under your exact server and caching conditions.

If you prefer a plugin that gives you multiple redirect types and you are comfortable testing and configuring redirects and caching rules, Pretty Links is appropriate. It gives more control but requires more attention to avoid accidental tag loss, particularly if you use meta refresh or JavaScript redirects.

Always test: don’t assume behavior across hosts. Use the testing checklist in this article and re-run checks after plugin updates, hosting changes, or enabling CDNs.

Neither plugin can guarantee tag preservation across every possible hosting configuration; server rewrites, caching, and CDN rules are common sources of problems that you must address in addition to plugin settings.

• Use ThirstyAffiliates if you want integrated localization and query forwarding options and prefer less manual configuration in many setups.
• Choose Pretty Links if you need flexible redirect methods and will test and adjust caching/CDN settings to ensure tag forwarding.
• Test your cloaked links in private browsing and with developer tools before scaling any link deployment.
• If you operate across many marketplaces, prioritize a solution that both selects the right tag per market and preserves it through the redirect.

Questions people still ask

From years running multiple Amazon affiliate sites and troubleshooting redirects across hosts and CDNs, I recommend treating plugin features as only one part of the chain: always test cloaked links under your exact hosting and caching conditions.