Auto login conflicts w/ tracking/notification

I put in the auto-login hack mentioned several times on this forum (e.g. http://www.s2member.com/forums/topic/auto-login-code-question/). I use PayPal Pro Forms. In addition to interrupting redirection to the url in the “success” parameter, I found that it also gets in the way of tracking and notifications.

I assumed that tracking stopped working because the redirection didn’t work, so the javascript I use for tracking (under API Tracking) is never shown. Even before this, javascript tracking of purchases only worked about 1/2 of the time.

To get around this limitation, I tried using API Notifications. However this would only work when a user is already registered and logged in *before* checking out with PayPal Pro Forms. If they were registering at the same time, then the notification urls are never hit. I set notification urls for both Sign Up Notifications and Payment Notifications. Neither are hit.

When I delete the auto-login hack, the Payment Notification is hit. Which is good. Surprisingly, the Sign Up Notification isn’t hit. I thought that if a user signed up and paid in one go then both notifications would be hit?

Questions:

1. Is there a way have auto-login AND notifications at the same time? Any leads I should investigate?

2. Is there a chart somewhere that lays out which notification and tracking will be hit for a particular action. For example, a table with all the notifications and tracking triggers in the first row, user events like registration and payment on the first column, then true/false in the table indicating whether the given user event will trip the given trigger. This would be enormously helpful in understanding if I am seeing expected behavior or if something is wrong.

Hi Alan.

1. Is there a way have auto-login AND notifications at the same time? Any leads I should investigate?

No, that hack has that problem. What you could try is, instead, use the [hilite mono]success[/hilite] attribute in your shortcode pointing to a page, where you then have a hack to log him in and redirect him to the page you want.

2. Is there a chart somewhere that lays out which notification and tracking will be hit for a particular action. For example, a table with all the notifications and tracking triggers in the first row, user events like registration and payment on the first column, then true/false in the table indicating whether the given user event will trip the given trigger. This would be enormously helpful in understanding if I am seeing expected behavior or if something is wrong.

No, there isn’t a chart like that… But if you read the documentation for each notification, they say when they’d happen.

The payment notification should happen everytime a payment happens that’s tied to s2Member, e.g.: new paying user, recurring payment, upgrade. The registration one happens when there’s a registration, paid or free. The signup one happens when there’s a paid registration. And so on… [hilite path]Dashboard -› s2Member® -› API / Notifications[/hilite]

This video may help: Video » s2Member (API Tracking/Notifications)

I thought that if a user signed up and paid in one go then both notifications would be hit?

When there’s a paid registration, all should happen: signup, payment and registration. (Not sure about the order, though.)