Constant Contact Integration

Issue Summary

I am going to be writing an API for integration with Constant Contact (CC) and would like to know the benefits of writing a module using EMF vs just writing a standalone module. I know that EMF's purpose is to standardize an API across any provider but I need to know if all the functionality is possible for what we want to do:

1. Be able to pull basic list/user information

2. Be able to push/pull new users automatically (auto-subscribed after drupal confirmation/login)

3. Be able to push/pull unsubscribed
a. delete account in drupal removes from CC
b. unsubscribe from CC directly will allow an arbitrary update on the drupal side (allow for custom changes to user account; not just a hard-coded delete, downgrade, role change, etc)

4. Be able to handle custom fields from profile, tokens, and PHP code (bonus)

5. Be able to automatically (on cron) update CC user account whenever Drupal profile fields, tokens, etc are updated
a. if there is no easy way to handle this automatically, it is acceptable to have a manual "Sync All Changed Users" (including custom fields) button
b. clicking that button would "know" which users had changed/upgraded/etc and would sync all data with CC

6. Be able to do a one-time push of users from drupal into CC
a. alternatively output an Excel file containing all necessary user info w/ selected custom field data

7. Be able to insert a referral/partner link into the module to earn back some of our investment when people sign up for CC

All other functions (that we can think of for now) should be handled from within CC itself. This includes list/user management, campaign management, emails, etc.

I realize from reading a lot about EMF and testing it out that it already does a lot of this for the mailchimp module. However, I could not find answers to all of my needs above. Please me know if this is possible with EMF as-is or if it would be better to handle as a standalone CC project.

If any one of those bullets is not possible, then it is a deal-breaker for us and we will just go it alone with a standalone module.

Thanks,

Brandon