You can have Mystrika ready to run cold email campaigns in a single working session. Connect your sending accounts, complete the warm-up period, build your first campaign sequence, and launch—this guide walks through each stage so nothing is missed.
What You Need Before You Start
Getting started with Mystrika goes faster when the pieces below are already in place. The table covers each requirement, a quick self-check, and where to source anything that is missing. Work through the checklist before opening the platform and you will avoid the most common setup delays.
| Requirement | Have It? | Where to Get It |
|---|---|---|
| Mystrika account (free plan available; paid plans start at $30/mo for Growth) | Yes / No | Create an account at mystrika.com — a free plan exists so you can explore before committing to a paid tier |
| Dedicated sending domain(s) separate from your main business domain | Yes / No | Register via any domain registrar; use a variation of your brand name (e.g., getbrand.com) |
| Email accounts on those domains (Google Workspace or Microsoft 365 recommended) | Yes / No | Google Workspace admin console or Microsoft 365 admin center |
| SPF, DKIM, and DMARC DNS records published for each sending domain | Yes / No | DNS provider control panel; Google Workspace and Microsoft 365 both provide setup guides in their admin documentation |
| Verified prospect list in CSV format (name, email, any merge fields you plan to use) | Yes / No | CRM export, LinkedIn Sales Navigator export, or a verified list from a reputable data provider |
| Campaign copy drafted: subject lines, body variants, and at least one follow-up message | Yes / No | Internal copywriting or a collaborative document reviewed by your team before upload |
| Unsubscribe and legal compliance language reviewed for each target region | Yes / No | Legal counsel or your internal compliance checklist for CAN-SPAM, GDPR, or CASL as applicable |
| Goal defined: reply rate target, meeting booked threshold, or pipeline value per campaign | Yes / No | Internal planning document; set this before launch so you have a clear success benchmark |
Expected Outcome When This Tutorial Is Complete
By the end of this guide you will have a fully configured Mystrika workspace with at least one sending email account connected and progressing through its warm-up schedule, a verified prospect list uploaded and mapped to your campaign fields, a multi-step email sequence active with at least one follow-up touchpoint, and your campaign in live or scheduled status. Analytics will begin populating within the first send window so you can monitor open, reply, and bounce data from day one.
Explore Mystrika Through Our Partner Link
Setup tip: Domains used exclusively for cold outreach should be at least two to four weeks old before your first send. A brand-new domain paired with no warm-
How to Set Up Mystrika for Marketing Campaigns: Steps 1–3
Getting the foundation right matters more than moving fast. These first three steps shape how every subsequent campaign behaves, so rushing through them typically costs more time than it saves. Whether you are running outreach for three sites or coordinating sending across dozens of client domains, the setup sequence below applies the same way — the scale just changes how many inboxes and sender profiles you configure along the way.
Step 1: Create Your Account and Choose the Right Plan
Start by opening a new account at mystrika.com. Mystrika offers a free plan, which gives you a practical way to explore the interface and confirm the workflow fits your team before any billing starts. No free trial period applies — the free plan is simply available as a standing option alongside the paid tiers.
Once you are in the account creation flow, you will need to decide which plan suits your current sending volume and team size. Owner-confirmed pricing as of August 20, 2026 shows three paid options:
How to verify: After account creation, confirm your email address through the verification link Mystrika sends. Check that your dashboard loads without access errors and that the plan shown in your account settings matches what you selected. If the plan name displayed does not match the three options above, contact Mystrika support before adding any payment method.
Pro tip: Start on the free plan even if you intend to upgrade quickly. Spending fifteen minutes clicking through the interface before entering billing details helps you confirm the sending workflow and contact import process match your team's expectations — not just the marketing copy.
Step 2: Connect and Warm Up Your Sending Domains
Cold email deliverability depends almost entirely on sender reputation, and that reputation lives at the domain level. This step is where most teams either build a durable campaign foundation or quietly sabotage their own results before a single message goes out.
The recommended approach is to use dedicated sending domains rather than your primary business domain. If your main domain is yourcompany.com, outreach should go from something like outreach.yourcompany.com or a purpose-registered variant. This keeps any deliverability friction away from transactional email and customer-facing correspondence.
Inside Mystrika, navigate to the email account or sender settings area and add each sending mailbox. You will need to provide SMTP credentials or connect through your email provider's authorization flow, depending on what Mystrika supports for your provider at the time of setup. After connecting each mailbox, enable the warmup feature for that account. Warmup gradually increases sending volume over time, building a reputation with receiving mail servers before your campaigns start in earnest.
The questions worth asking at this stage:
- Do you have SPF, DKIM, and DMARC DNS records in
Steps 4 to 6: Configuring Campaigns, Sequences, and Deliverability in Mystrika
With your account foundation in place, this phase is where the actual marketing work happens. Steps 4 through 6 move you from general setup into campaign-specific configuration — defining who you are reaching, how the conversation unfolds across multiple touchpoints, and whether your sending infrastructure can support it reliably. Each step builds directly on the last, so working through them in order prevents the kind of misalignment that causes sequences to underperform before they have a fair chance.
Step 4: Build Your First Campaign and Define the Target Audience
Creating a campaign in Mystrika is where your earlier preparation — verified sending domains, warmed-up mailboxes, imported contact lists — gets translated into an active outreach unit. A campaign holds your sequence logic, your sender identity, your contact pool, and your scheduling preferences in one place, which makes it easier to manage multiple simultaneous campaigns without them bleeding into each other.
When naming your campaigns, use a convention that immediately tells anyone on your team what the campaign does: the target segment, the offer angle, and roughly when it launched. A label like "SaaS-Founders-Q3-Partnership" carries more operational meaning than "Campaign 12," especially once you are running several campaigns in parallel across different site verticals.
Audience Segmentation Before You Add Contacts
One of the most consequential decisions at this stage is which contacts go into which campaign. Sending the same message to every prospect in your database is a common shortcut that consistently reduces reply rates and damages sender reputation over time. Before you assign a contact list to a campaign, work through these segmentation questions:
- Does this group share a meaningful pain point that your message addresses specifically?
- Are the domains in this list from a consistent industry vertical, making personalization realistic?
- Has this list been validated for deliverability — bounced addresses removed, catch-all domains flagged?
- Evaluate the workflow benefit against your own baseline rather than assuming a specific measured outcome.
- Is the list size proportionate to the number of warmed mailboxes you plan to use as senders?
That last point matters more than most teams expect. Sending volume is not unlimited by mailbox — healthy deliverability depends on daily send limits that reflect what a real human sender would produce. When you assign contacts to a campaign, Mystrika distributes sends across your connected mailboxes. If your contact pool is large relative to your sending capacity, the campaign will take longer to cycle through, and you need to plan your follow-up timing with that reality in mind.
See How Mystrika Fits Your Workflow
Campaign Settings Worth Reviewing at Creation
Most campaign dashboards surface a handful of settings that are easy to skip past during setup but difficult to adjust cleanly once a campaign is running. Take time to review:
- Daily send limits per mailbox: Keeping this conservative during the first week of any new campaign protects your sender reputation while you verify that reply rates and bounce rates are within acceptable ranges.
- Timezone and sending window: Emails sent during the recipient's working hours consistently outperform those landing at 2 a.m. If your contact list spans multiple time zones, check whether Mystrika lets you send relative to each recipient's inferred timezone rather than a single fixed window.
- Tracking preferences: Open tracking via pixel is useful for measuring engagement, but in campaigns targeting privacy-conscious technical audiences, it can also trigger spam filters. Decide deliberately rather than leaving defaults in place.
- Unsubscribe handling: Confirm that opt-out requests are honored automatically and that unsubscribed contacts are suppressed across all active campaigns, not just the one they responded to.
Troubleshooting Common Mystrika Setup Problems
Even when you follow every step carefully, cold email infrastructure can surface frustrating issues at the worst moments — usually right before a campaign is scheduled to launch. The problems that come up most often when working through how to set up Mystrika for marketing campaigns fall into four categories: email authentication failures, deliverability drops after launch, sending account disconnections, and campaign configuration errors. Working through each category methodically saves time and prevents the kind of guesswork that leads teams to restart campaigns unnecessarily.
Email Authentication Failures
Authentication problems are the most consequential issue to catch before sending begins. If your SPF, DKIM, or DMARC records are not resolving correctly, emails will land in spam folders or be rejected outright, and no amount of copy optimization will fix that.
The most common root cause is DNS propagation delay. After adding or editing a TXT record in your domain registrar or DNS host, changes can take anywhere from a few minutes to 48 hours to propagate globally. Many teams check their records immediately after saving and see failures that are not actually failures — they are simply seeing a cached state.
A second common cause is a conflicting SPF record. SPF allows only one TXT record per domain. If you already had a sending provider's include statement in your SPF record and added another without merging them into a single record, both records will be present and mail receivers will treat the configuration as invalid. Combine all include statements and mechanisms into one SPF TXT record, then verify with an SPF syntax checker before considering it resolved.
DKIM selector mismatches are another frequent issue. When Mystrika provides a DKIM key, the selector name it specifies must match exactly what you enter in your DNS record's subdomain label. A single character difference — including a trailing period in some interfaces — will cause DKIM to fail. Copy the selector name directly from the Mystrika interface rather than retyping it.
Authentication Validation Checklist
- Confirm only one SPF TXT record exists on your sending domain
- Verify the SPF record includes all authorized sending services, not just Mystrika
- Check the DKIM selector name matches exactly what Mystrika specifies, character for character
- Run a DMARC lookup to confirm the policy record is present and syntactically valid
- Use a third-party DNS propagation checker from at least two geographic regions before declaring the record failed
- Re-verify authentication after any DNS edit, even minor ones
Warming Period Disruptions
If you are using Mystrika's built-in email warmup functionality and the warmup process stalls, pauses unexpectedly, or shows declining reputation signals, the most common culprit is a sending account that was disconnected and reconnected mid-warmup. Reconnecting an account resets certain session tokens. Check whether the account still appears as active and connected in your Mystrika dashboard, and review whether warmup activity resumed after any credential refresh.
Sending from a warmed account before the warmup period is complete is the second most common warmup-related mistake. Introducing real campaign volume on a partially warmed account can trigger spam filters that the gradual ramp was specifically designed to avoid. Treat the warmup completion status in the dashboard as a hard gate, not a suggestion.
Did It Work? Verifying Your Mystrika Campaign Setup
Before you call the configuration complete, run through a set of binary checks. Each item below has a clear pass or fail state — no judgment calls. If any check fails, stop and resolve it before moving to the readiness assessment.
Binary Verification Checklist
- Email warm-up status shows as active for every sending mailbox you added — not pending, paused, or errored.
- At least one sending account has completed its initial warm-up phase and is cleared for campaign sends, not still cycling through warm-up-only mode.
- Your campaign sequence has at least one step saved, with a subject line, body copy, and a configured send delay between steps.
- Personalization variables in your email body resolve correctly in the preview — no broken merge tags showing raw placeholder syntax.
- Your lead list imported without critical errors; any rows flagged during import have been reviewed and either corrected or excluded.
- Bounce handling is configured — your campaign settings specify what happens when an email hard-bounces rather than leaving that behavior at default or unset.
- Unsubscribe handling is active and the opt-out mechanism in your emails links to a functional opt-out path.
- A test send to a mailbox you control arrived in the inbox, not spam, and all links in the email resolved to the correct destinations.
- Campaign scheduling reflects your intended send window — days, hours, and time zone are all explicitly set and not left at a system default you have not reviewed.
- Analytics are reporting — after your test send, open-tracking or activity data appeared in the dashboard rather than showing zero activity across the board.
Common Check Failures and What They Signal
The three checks that most commonly fail at this stage are the personalization preview, the test-send inbox placement, and the analytics data appearing after the test. If merge tags break in the preview, the issue is almost always a mismatch between the column headers in your imported list and the variable names referenced in your email template — review your column naming in the import file before re-uploading. If the test email lands in spam, the warm-up phase either has not completed or the sending domain's DNS records — SPF, DKIM, and DMARC — were not published correctly when the mailbox was added. If analytics show zero activity after the test, confirm that tracking is enabled at the campaign level, not just at the account level, since the two settings are independent.
Checking that unsubscribe and bounce handling are correctly configured is worth treating as non-negotiable before a live send. These are not polish items — leaving them at defaults without reviewing what those defaults actually do can cause deliverability problems across your entire sending infrastructure, not just the current campaign. With multiple websites under management, each potentially requiring its own sending identity, a deliverability problem on one mailbox can affect the warm-up progress and sender reputation of others sharing the same infrastructure setup.
Ready to Go Live? Subjective Readiness Assessment
The binary checks above tell you whether the technical configuration is functional. This section asks whether the campaign itself is ready — a separate question that requires judgment rather than pass/fail tests.
Sequence Logic and Follow-Up Coverage
Review your sequence end-to-end and ask whether each follow-up step makes sense if the previous one received no response. A common mistake at this stage is building a three-step sequence where every step assumes the recipient read the previous one, which produces follow-up emails that feel disconnected to recipients encountering them cold. Each step
Check Mystrika Fit and Current Options
Frequently Asked Questions
Current plans and pricing: Use our partner link to view current plans, pricing, and any available offers. Final pricing and promotional terms are set by the provider and may vary by plan, billing cycle, usage, region, and eligibility.
How long does the Mystrika warm-up period take before I can start sending cold emails?
Most practitioners allow three to four weeks of warm-up before treating a mailbox as fully ready for campaign volume. The warm-up process gradually increases daily send counts so receiving mail servers build a positive reputation for your domain rather than flagging a sudden spike in activity. Rushing this window is one of the most reliable ways to tank deliverability before a single prospect reads your message, so budget the time upfront rather than retrofitting it after problems appear.
Which Mystrika plan makes sense for a small team just starting cold outreach?
The free plan lets you explore the interface and confirm the workflow fits before spending anything. When you are ready to scale, the Growth plan at $30 per month is the natural next step for smaller sending volumes. If you commit to a full year, it drops to $192, which works out to $16 per month. Upgrade to Dominate at $85 per month only when your campaign volume or team size genuinely pushes against Growth plan limits — buying headroom you do not need yet adds cost without adding results.
Can I run campaigns for multiple client domains inside a single Mystrika account?
The general setup architecture supports connecting multiple sending mailboxes and domains within one workspace, which is how agencies typically manage outreach across several clients. Each client's sending domains and mailboxes stay logically separate through the campaign structure, so a deliverability problem on one client's domain does not automatically bleed into another's. Confirm the specific mailbox and campaign limits that apply to whichever plan you are on before onboarding multiple clients simultaneously.
What happens to a contact who unsubscribes mid-sequence — do I have to remove them manually from other campaigns?
Unsubscribe suppression should work automatically across your active campaigns, not just the one where the opt-out was triggered. Before launching any campaign, test this behavior by sending yourself through a sequence and clicking the unsubscribe link, then checking whether that address is suppressed account-wide. Manual removal processes create compliance risk, particularly under CAN-SPAM and GDPR, so verifying automatic suppression during setup rather than assuming it works protects you from regulatory exposure later.
My SPF record was set up correctly but emails are still landing in spam — what should I check next?
SPF alone is rarely sufficient. Check that DKIM signatures are publishing and validating correctly for each sending domain, and confirm your DMARC policy is in place even if it starts in monitoring mode. Beyond authentication, look at your sending volume relative to how long the mailbox has been warmed up — a sudden jump in daily sends after a quiet period can trigger spam filters regardless of authentication status. Also review your email copy for phrases that commonly trigger content filters and check whether your sending IP appears on any blocklists using a tool like MXToolbox.