Every email you send is scored on arrival. When a creator's mailbox provider (Gmail, Outlook, Yahoo) receives a message from your domain, it checks the domain's reputation before deciding whether to place it in the inbox, the Promotions tab, or Spam. That reputation is built from your sending history: volume, authentication, bounce rate, and how often recipients hit "Report spam."
Reputation belongs to the domain, not to the campaign or the tool. If outreach damages it, every email leaving that domain is affected. Your normal one-to-one messages to existing partners, clients, and colleagues start landing in their spam folders too, and they may not tell you. Recovery takes weeks of careful low-volume sending.
This applies no matter which tool sends the email. Newsletter platforms like Mailchimp are not an option for creator outreach in any case: their terms prohibit sending to third-party or scraped lists, and a creator export is exactly that. Cold-outreach tools and the Cloutboost Portal both send through your own mailboxes, on behalf of your domain, so the same reputation rules apply.
The working consensus among cold-email tool vendors (Smartlead, Lemlist, Instantly) is 30 to 50 new emails per mailbox per day for new accounts, and about 100 once a mailbox is warmed and getting replies. Cloutboost runs its own campaigns at these levels. With 2 to 3 mailboxes per domain, that means 100 to 300 outreach emails per day per domain. Larger campaigns add domains rather than pushing a single mailbox harder.
The creator contacts in the Portal, and in any creator database, are not an opt-in list. They are business contact emails that creators publish on their YouTube About page, Twitch panel, TikTok bio, or linked social profiles. Nobody on the list has asked to hear from you. This changes three things.
Mailchimp is not the exception. Every major permission-based email platform has the same rule, and each one names scraped or publicly available addresses specifically:
The reason is the same in every case. These platforms send from shared IP pools, so one customer's spam complaints hurt everyone on the platform. They protect that shared reputation by refusing any list where the recipient did not sign up directly. A creator export from any database is, by their definition, a scraped list.
Cold outreach to creators is a normal, legitimate business practice. Creators publish these addresses precisely so that studios and brands can contact them about work. The rules below exist to keep that outreach looking like what it is: a person offering a specific creator a specific opportunity.
Cold email to business contacts is legal in most jurisdictions with conditions. This is general guidance, not legal advice. Confirm with your counsel for the countries you send into.
Practically: target carefully, personalize, keep volume low, include an opt-out line, and remove anyone who asks. The same practices that protect your domain also keep you on the right side of these rules.
Providers publish hard caps. Those caps are the point at which your account is locked, not the point at which your emails start going to spam. Spam filtering starts long before the cap.
Mailchimp, Constant Contact, HubSpot Marketing, and similar platforms are built for permission-based email: recipients who signed up to hear from you. Their terms of service prohibit sending to purchased, rented, scraped, or publicly available contact lists. Creator emails gathered from YouTube About pages, Twitch panels, or a database fall into that category.
Three practical consequences:
Cold-outreach tools such as Lemlist, Instantly, or Smartlead do allow this use case. They work the same way the Cloutboost Portal does: they send through your own Gmail or Microsoft mailboxes, with daily caps and delays between sends. The difference is that the Portal combines sending with the creator database, campaign tracking, and key delivery in one place.
The Portal does not send email from Cloutboost servers or a shared IP. It connects to your Gmail or Google Workspace mailboxes through Google's official API and sends each email individually from your account, exactly as if you had written it in Gmail.
Because the Portal sends from your own mailboxes, your domain reputation is in your hands. The Portal makes it easy to stay within safe limits, but the limits themselves come from Google and Microsoft, not from us.
Connecting a Gmail account to a third-party app is a security decision, so it is fair to ask what Cloutboost has been checked for. The Portal's Gmail integration has passed Google's full OAuth app verification for restricted scopes. In practice this means:
Unverified apps show a warning screen during Google sign-in and are capped at 100 users. Verified apps do not. If you are comparing outreach tools, ask each vendor whether their Gmail integration has passed Google's restricted-scope verification and CASA assessment. Many have not.
Reference: Google OAuth API verification and annual reassessment, App Defense Alliance CASA.
Do not put all outreach volume on your primary company domain. Most teams want to send some emails from their main domain because creators recognize it, and that is fine at low volume. But the bulk of outreach should go through one or more dedicated variants (yourstudio-games.com, yourstudio.co, hello-yourstudio.com) used only for this purpose. If reputation on one of them drops, your main domain and your team's everyday email are unaffected. Set each outreach domain to redirect to your main website so creators can verify it is legitimate.
Create real mailboxes for real people (firstname@outreach-domain.com). Avoid generic addresses like info@ or marketing@. Two to three mailboxes per domain is the practical ceiling before the domain itself starts to look like a sending farm.
Before sending the first email, set up all three DNS records. Google and Yahoo have required these for bulk senders since February 2024 and now reject unauthenticated mail outright.
Google Workspace sets up SPF and DKIM through the admin console. Verify with Google's checker or MXToolbox.
A brand-new mailbox that sends 100 emails on day one gets flagged. Ramp up over two to three weeks:
During warm-up, send some normal one-to-one emails from the mailbox and reply to anything that comes in. Replies and engagement build reputation faster than volume.
Fifty new contacts per mailbox per day is the industry-wide accepted safe limit for cold outreach. Cloutboost runs its own campaigns at 30 to 50 per mailbox and only pushes toward 100-200 on established mailboxes during peak launch windows, with close monitoring. Follow-ups to existing threads count toward the total but carry less risk than first-touch emails.
To reach 3,000 creators in a launch window, do not send 3,000 emails from one address. Use the math below and add domains as needed.
Register each domain in Google Postmaster Tools to see spam rate and domain reputation directly from Google.
Only if the domain is used outside the limits above. The risk comes from volume and list quality, not from the tool. This is true of every outreach tool on the market.
With a Portal subscription, you send from your own mailboxes. Creators reply to you, and the relationship and reply history are yours. Nothing is locked inside the platform.
If you would rather not set up outreach domains, mailboxes, and warm-up yourself, that is what our managed service is for. In a managed campaign, Cloutboost runs outreach from its own domains and mailboxes, which are already authenticated, warmed, and maintained across multiple domains for volume. Our team handles the targeting, sending, follow-ups, negotiation, and key delivery, and you receive the shortlist, replies, and reporting. This is the right option when you need to reach a few thousand creators for a launch without building the infrastructure first.
Google and Microsoft lock sending for up to 24 hours. Repeated violations can lead to account suspension. The Portal's daily cap is there to make sure this never happens.
Yes. The platform where you found the creator does not matter. What matters is that you are sending email to someone who has not opted in, so the same domain-health rules apply.