We do not have built-in support for tracking affiliate sub-IDs yet, although this is on the wishlist as a planned new feature.



Affiliates can however append any extra &name=value parameter(s) to the end of their hop link URL, and those same parameters would simply be passed thru the redirection and appended to the merchant's landing page URL for that hop link when the buyer arrives there.



E.g., if an affiliate's hop link URL:

https://www.e-junkie.com/ecom/gb.php?cl=XXXXXX&c=ib&aff=YYYYYY

...redirects to the merchant's landing page at this URL:

http://www.example.com/page.ext

...adding some extra parameter(s) to the hop link URL like so:

https://www.e-junkie.com/ecom/gb.php?cl=XXXXXX&c=ib&aff=YYYYYY&this=that&other=x

...would result in buyers referred through that link landing at the merchant's URL like so:

http://www.example.com/page.ext?this=that&other=x



However, the affiliate can't just add parameters to their hop link and expect to get those reported back to them automatically. Those parameters would have no effect unless the merchant cooperates by programming custom scripting to add in their landing page that could recognize those extra parameters and report them back to the referring affiliate somehow. It's not something .



Furthermore, the merchant's site may be generated by scripting that uses or depends on URL parameters of its own, so passing extra parameters thru the affiliate link to be appended to the merchant's page URL may just confuse the merchant's site management system; this is probably causing the 404 errors you see.

That would require require extensive custom programming in the merchant's site where the cart buttons are placed, which you would probably need to hire a developer to perform. We can recommend the competent, E-junkie-experienced developers listed in our directory here:

2http://www.e-junkie.com/ej/developer-directory.htm2

If each affiliate has a variety of subIDs you need to track (e.g., to identify various sites/campaigns where they've posted their affiliate link), they could add a custom parameter to each of their link URLs as explained previously, which would then be passed thru to your landing page URL.



Then custom scripting in your page could look for the value of that parameter in its URL and dynamically append that value to a &custom= parameter on all of your cart button URLs in your page -- e.g., https://www.e-junkie.com/ecom/gb.php?c=cart&i=XXXXXX&cl=173371&ejc=2&custom=SubIDGoesHere -- so clicking any cart button would pass that value to the cart as a custom parameter for the order.



If you need that custom value to be carried from page to page on your site, so all of your cart button URLs site-wide could have the &custom= value appended, your scripting might set a cookie for the custom value, and then it would read that cookie to get the value to append to the &custom= parameter in your site's cart button URLs.



BTW note that, although this custom value is passed to the cart by clicking an Add to Cart button, the custom value itself is only associated with the whole order, rather than any particular item in the order, so there could be only one custom value per order no matter how many items are ordered. Appending it to every cart button's URL just ensures that the custom value will be passed to the cart no matter which button(s) the buyer clicks.



That custom value would appear in your Transaction Log and can also be inserted in your thank-you pages using the [%custom%] template variable in your Common Thank-you Page HTML field, which would insert the order's custom value when the page is generated. This could even be used to insert that custom value within tracking code in your thank-you page, as the substitution is performed before the page is sent to the buyer's browser. If you have set up our Integration feature to POST order data back to a script URL at your end after checkout, the custom value would be included in those submissions as well.



The custom scripting in your site that I described above is something that would need to be programmed from scratch by an experienced Web developer, who would fully understand everything I've described here and recognize exactly how to implement it. This is not something that can be accomplished with settings in WordPress nor any ready-made WP plugin. Please contact developers in the directory I linked previously for help setting this up.