Your IP warming process is very surgical and it requires some detailed information in order to really outlay a plan. Ultimately the idea is that you build up your sender reputation with the ISP's on your sender IP so it won't get blocked.
A proper warming plan can consists of several pieces of information
- Send volume
- Engagement
- Are you transitioning from another ESP or are you simply adding another IP
- Segmentation
In order to properly warm an IP you will have to have enough through put, each ISP has their own formula and the SFMC deliverability team should be able to share that with you. You will need to segment out your domains (gmail, yahoo, etc.) each has their own threshold and it could look something like this week 1 - gmail 20K, yahoo 20K, aol - 10k; week 2 gmail - 40K, yahoo 40K, aol 20k. So you will have to segment your lists according to those specs and in addition you would want to send to your highest engagers as they can speed up the process some.
I would assume that your "triggered" sends are transactional? or are they simply action based? either way it wouldn't matter since the initiation of send is irrelevant since you are needing to build up your IP.
If you are using another system, I would route your highest engaged, segmented by ISP to the warming IP and keep the others in the old system until you warmed.
Also be sure to practice proper list hygiene which is what can cause your spam traps, blocking issues and delay your warming process. An ideal time span should be between 6 - 8 weeks. If you do everything correctly you can start seeing positive results in as fast as 4 weeks.
So when you say creating 2 domains, not sure exactly what you mean? Anytime you are using a new IP it has to be warmed otherwise you run into issues regardless of the type email you send.
You might need to raise a support case to have your new Private Domain configured.
Before doing that, however, you will need to delegate the domain to the name servers of SFMC, by creating NS records pointing to:
• ns1.exacttarget.com
• ns2.exacttarget.com
• ns3.exacttarget.com
• ns4.exacttarget.com
Once case is closed, you will be able to select this new domain when creating new Cloud Pages. Please do keep in mind, that existing Cloud Pages need to be rebuilt on this new domain, as it is not automatically updating for existing assets. You can read more about Private Domains here.
Best Answer
You will be able to send from the top level domain of your company (e.g. as john@company.com) by purchasing and configuring a Private Domain on your company.com domain. Assuming you already have your SAP in place on e.g. marketing.company.com. Those need to be within same top domain as DMARC will otherwise fail.
As in most cases for SAP, the subdomain in delegated to Salesforce name servers, and all DNS configuration is managed by their team. This is obviously not possible with regards to you top domain, so you will be provided with a set of DNS records to be updated in your existing zone of company.com
Also managing RMM in SFMC will not be possible, as MX records for company.com already point to your existing mail servers