User data Not mapped

The user data is not immediately pushed to VerticalResponse. The updates are pushed in a batch operation that is triggered by an administrator on a list management page or when a campaign is launched. Have you run the list update process for the list that you described?

As a reminder, I want to say that mapping Drupal user properties to fields in VerticalResponse will dramatically increase the amount of time required to launch an email campaign; especially for larger mailing lists. This is because list member records can only be updated one at a time. However, the API provides a method that can create a large mailing list in a single transaction which is preferable. In future versions of this module, a new list will be generated for each email campaign, which is what I recommend doing here.

Another point, the list map was included in the module so that administrators could use tokens in the email or segment the lists through VerticalResponse in a meaningful way. After careful consideration, it doesn't make sense to attempt to maintain current information across several lists in VerticalResponse because there is no master record for a user. Therefore, Drupal must notify VerticalResponse of every change to every user for every list the user is a member, which as you can imagine adds up to many API transactions and increases network traffic exponentially. So, once again, I strongly recommend setting up Drupal to be the master of all list management.

You have identified an interesting issue in that removing a user account will not remove that individual from a mailing list.

Navigate to the "VerticalResponse" list manager and select the list that you want to "edit." There should be a tab on this page that reads "Update List." Use that link to push locally mapped data to VerticalResponse.