[bizmum]

Hi, I’d like the Satellite plugin for WP Affiliate too please. I’ve sent you an email request but haven’t heard anything back. I’ve got estore & affiliate plugin installed on domain.com and would like to have the affiliate program cover a wp installation on both a subdomain and a subdirectory of the main domain.

I’m using the estore & wishlist member on the subdomain and directorypress on the subdirectory.

Thanks!

[bizmum]

Thanks Ivy!

[bizmum]

Thanks Amin,

I’ve put in a request to get the latest version. It seems straightforward enough – I’ll let you know how I get on when I get the updated version of the plugin.

[bizmum]

Thanks Amin!

Through the IPN handling script please.

[bizmum]

It looks like you can add custom fields. I’ve posted the info here just to make sure!

If you use affiliate software, or have back-office routines that need to be notified whenever payment transactions take place, and/or for recurring payments, you’ll want to read this section. This is marked Payment, because the URLs that you list below will be notified each time an actual payment occurs. Depending on your fee structure, this may include a first initial payment that establishes a subscription. But more importantly, this will be triggered on all future payments that are received for the lifetime of the subscription. So unlike the Signup notification, Payment notifications take place whenever actual payments are received, instead of just once after signup is completed. If a payment is required during signup ( e.g. no free trial is being offered ), a signup notification will be triggered, and a payment notification will ALSO be triggered. In other words, a payment notification occurs anytime funds are received, no matter what. Please note, this feature is not to be confused with the PayPal® IPN service. PayPal® IPN integration is already built into s2Member and remains active at all times. These Payment Notifications are an added layer of functionality, and they are completely optional; used primarily in affiliate program integration & other back-office routines.

They allow entry for:

Payment Notification urls

Payment notifications take place silently behind-the-scenes, using a cURL connection. Each URL will be notified every time an initial and/or recurring payment occurs.

You can also use these special replacement codes if you need them:

* %%subscr_id%% = The PayPal® Subscription ID, which remains constant throughout any & all future payments. [ ? ]

* %%txn_id%% = The PayPal® unique Transaction ID, which is always unique for each payment received.

* %%amount%% = The amount of the payment in USD. Most affiliate programs calculate commissions from this.

* %%first_name%% = The first name of the customer who purchased the membership subscription through PayPal®.

* %%last_name%% = The last name of the customer who purchased the membership subscription through PayPal®.

* %%full_name%% = The full name ( first & last ) of the customer who purchased the membership subscription.

* %%payer_email%% = The email address of the customer who purchased the membership subscription through PayPal®.

* %%item_number%% = The item number ( in other words, the membership level: 1, 2, 3 or 4 ) that the payment is for.

* %%item_name%% = The item name ( in other words, the associated membership level label that briefly describes the item number ).

Custom replacement codes can also be inserted using these instructions:

* %%cv0%% = The domain of your site, which is passed through to PayPal® using the custom field in your PayPal® button code.

* %%cv1%% = If you need to track additional custom variables, you can pipe delimit them into the custom field of your button code like this: <input type=”hidden” name=”custom” value=”mysite.com|cv1|cv2|cv3″ />. You can have an unlimited number of custom variables that track IP addresses, affiliate IDs, etc. In some cases you may need to use PHP code to insert a value into the custom field dynamically. Obviously this is for advanced webmasters, but the functionality has been made available for those who need it.

This example uses cv1 to track a user’s IP address:

( The IP address can be referenced in your notification URL using %%cv1%% )

<input type=”hidden” name=”custom” value=”mysite.com|<?php echo $_SERVER[“REMOTE_ADDR”]; ?>” />

The same information is available on the account deletion and payment reversals sections too.

Thanks!

[bizmum]

Hi Amin

Thanks for your reply. I’m not sure if this helps for the best method to use but I got this from the plugin:

You may also want to check the s2Member API Notifications panel. You’ll find additional layers of automation available through the use of the Signup, Payment, EOT/Deletion and Refund/Reversal notifications that are available to you through the s2Member API. These make it easy to integrate with 3rd party applications like affiliate programs and other back-office routines. Since the s2Member API Notifications operate silently on the back-end, in conjunction with the PayPal® IPN system, they tend to be more reliable and also more versatile. That being said, nothing really replaces the simplicity of using Pixel Tracking, and the s2Member API Notifications are not necessarily the best tool for the job in all cases. For instance, API Notifications will NOT work with Google® Analytics, or 1 pixel <img> tags. They operate silently behind-the-scenes, using cURL connections, as opposed to being loaded in a browser.

I’ll be using your affiliate program with your estore plugin too, and want to add s2Member plugin to allow extra features.

Which method would you recommend? I’m happy for you to send me the code if you think this is the best way to go.

Thanks again

[Author]

Posts