9
votes
Accepted
Customer wants to use a new sending domain but with the same IP - will this require an additional SAP package?
It might be useful to list few differences (and similarities) between SAP and a Private Domain, prior to getting to the point.
Sender Authentication Package (SAP) is best thought of as an account
“...
4
votes
Accepted
Marketing Cloud - IP Addresses Warming
Recommendation from this table is per send - and it is recommended to have 3 sends per week, doubling the volume week on week.
However, I have seen several issues with ISPs (e.g. Hotmail) which will ...
3
votes
Dynamic SQL Top() clause in SFMC
You could do use the row_number() window function to assign a sequential number to each row (in random order) and then only select rows that less than or equal to your volume value. Something like ...
3
votes
Reduce volumes for specific domain during IP warmup
Normally you would divide your entire base, and not only particular email domains. As long as the sends to individual email domains don't exceed the recommended limit.
You can use this query in Query ...
3
votes
Accepted
IP Warming small email domains
The main reason for doing IP warmup is to gradually increase your volume, without hitting the daily capping limits for ISPs. I.e. you don't want to hit Hotmail with 25.000 email on the first day of ...
3
votes
Accepted
IP warming without an existing contact database
In this case, I will actually recommend to send from a shared IP address. Since you are starting with an empty database, your volumes will probably not reach 100.000 emails per month, being the very ...
3
votes
Accepted
Setting up a different marketing platform while working in Salesforce Marketing Cloud
If you've delegated a subdomain to Salesforce using NS records, you'd not be able to do anything with the subdomain... ExactTarget.com's nameservers are the authority and manage the entire zone file ...
2
votes
Accepted
Is there an authoritative source of all email domains and where they fit into the IP warming "domain" buckets?
I am not aware of any list, but typically you have around 10 - 15 large domains worth monitoring. Once you get down into the range of around 1000 addresses, it's ok to miss a domain or two, when ...
2
votes
Accepted
Ip Warm Up - Send flow
The method of send is largely irrelevant for IP warm-up. All of the above can potentially work - what is important is what you are sending and who you are sending it to. I would probably lean towards ...
2
votes
Random Data Extensions: Need to split larger audience into 20 different DEs
The way to get the most accurate split of your audience would be to use a rank() and count() to a staging table and then use math in the following queries to build out your segments.
Staging Query:
...
2
votes
Accepted
Dynamic SQL Top() clause in SFMC
Nice solution by Adam.
a different alternative I sometimes use is to store the "TOP" number in a control table with key/value pairs, and look it up based on some condition (e.g. id could be ...
2
votes
Accepted
Adding private domains for sending without additional dedicated IP
This is normally not a huge issue. You are however not mentioning any details on domain structure nor specific volumes.
Given you are sending e.g. 100.000 emails per week on your old PD, and want to ...
2
votes
Warm up for a new long code in MobileConnet?
It’s not officially advised anywhere by Salesforce, but there are some external sources that recommend doing it:
Warm up your sending reputation
Similar to warming up your email sending reputation, ...
1
vote
Accepted
IP warming basic
Let me answer your questions in reverse order. Why? Since if you are using shared IP, and especially if your volumes are quite low, IP warmup should not be necessary. At least not in full scale - so ...
1
vote
Question about the sending schedule (Warmup)
It is not uncommon during IP warmup process to switch sending days around to accommodate for more time critical sends from an existing platform. The risk of sending emails two days in a row is really ...
1
vote
Accepted
Do we need do to IP warming for additional dedicated IP we bought outside of SAP
Tl;dr: Yes.
Why:
One main point for a dedicated IP is to control your own sender reputations at the various email providers like gmail, yahoo.
A new IP is cold, i.e. has no reputation anywhere.
The ...
1
vote
Accepted
IP warm up and leverage on previous email send system
You cannot reuse/migrate an IP address to Marketing Cloud, and should focus on IP warmup instead. You will need to split your sends between the old system in place today, and Marketing Cloud, as ...
1
vote
Accepted
Can dedicated IP applies to non-SAP domains in a Salesforce Marketing Cloud Business Unit?
The short answer is: Nope!
Especially if you by a non-SAP domain mean a domain which is neither an SAP domain, nor a private domain. This would mean, that there is absolutely nothing which tells the ...
1
vote
Random Data Extensions: Need to split larger audience into 20 different DEs
You can do it at least in 2 ways:
Split the audience within the Journey. You would create the first Random Split to have 50% + 50% and then from each branch of 50%, you would have another Random ...
1
vote
Accepted
IP Warmup Simple Approach question
General note: If unsure, start slow.
General note #2: plan your sendout increases so they suit the slowest of your domains and adjust the others to the slow pace, not the opposite. Spoiler: in your ...
1
vote
Accepted
New subdomain sending issues through Marketing Cloud Shared IP
Assumption:
you are talking about the client's own infrastructure, as in your client is "company" and you are seeing issues on mails sent from SFMC to inboxes "[email protected]",...
Only top scored, non community-wiki answers of a minimum length are eligible
Related Tags
marketing-cloud × 21ip-warming × 21
deliverability × 12
email × 6
sender-authentication-package × 5
sfmc-business-unit × 2
ip × 2
journeybuilder × 1
dataextensions × 1
sql × 1
marketing-cloud-connect × 1
automationstudio × 1
mobileconnect × 1
documentation × 1
split × 1
sap × 1
reputation × 1
domain-layer × 1
email-settings × 1