You will find the principles as well as the technical implementation of the connector.
Basically, the main use cases served after the connector has been implemented are:
profile synchronization from v7 to ACS
audience synchronization from v7 to ACS
landing page synchronization from v7 to ACS
You can as well ask consulting to configure extra synchronizations in case you need more data.
Once you have your v7 data in ACS, the main benefits are that you can leverage the improved UI of ACS to design emails and workflows. You will also benefit from the ACS MTA which has higher capacity in terms of throughput (because more recent mainly). You will also be able to use the ACS dynamic reports, etc.
Let me know if you need more details on a specific use case or feature,
There are no official numbers regarding the MTA as there are big impacts depending on the quantity of personalization, dynamic content to compute, etc. I have seen numbers way above that (like 10-15M/hour) but I cannot tell for sure what amount you'll be able to reach.
That would more likely be an information you get during the sales/assessment process.
Thank you I will read this today. It looks very useful.
Sorry for the additional question, perhaps I should start a new thread but you mention the MTA.
Where can I find any info about the scalability of the ACS MTA? This is a very important point for my company. We have deployed 8 MTAs at present and with our larger campaigns we send in the region of 2MM emails per hour. Going forward we need to support 3MM++ per hour.
Is this achievable with ACS? Is there an SLA which states this?