Search results

Thats a good question and this is the healthy way to do it: Safer alternatives: Lead forms on your own website Content downloads (ebooks, offers) Webinars or events with your brand name clearly shown Double opt-in (recommended) That way: Consent is clear Engagement is higher Deliverability...

Yes, Ofcourse this is a very common Mumara workflow: - Import contacts into Lists Use lists purely for organization (source-based). - Create one master “Send-Ready” Segment Conditions like: Subscription status = Subscribed Email status = Active Not in suppression list Send all campaigns via...

Yes, exactly. The moment you add marketing content, the email is no longer purely transactional. Mailbox providers don’t judge intent generously they judge content. Example 3: Still Transactional (Safe Version) Subject: Your invoice is ready ✔ Informational ✔ No marketing CTA ➡ Safe to send...

Yes if the client absolutely wants outreach, it is suggested to adopt risk-reduction options: Send to very small batches Use a separate domain (never your main brand) Avoid shared sending IPs No promotional language initially One-to-one style messaging only Even then, it’s still risky just...

Thats correct but not directly. Purchased lists typically cause: Spam complaints Hard bounces Low engagement Mumara actively monitors: Complaint rates Bounce behavior Engagement patterns Accounts sending purchased data usually don’t last long even if the data “looks clean”.

They’re automatically excluded. That’s the biggest advantage. That’s why experienced Mumara users: ❌ avoid sending campaigns to raw lists ✅ always send using segments

Absolutely. Let’s look at real examples below Example 1: Transactional Email Subject: Your password has been reset successfully ✔ Triggered by user action ✔ No marketing language ✔ No upsell ➡ Clearly transactional Example 2: Transactional + Promotional (Be Careful) Subject: Your invoice is...

That’s where most people get into trouble. What usually happens: Low open rates High spam complaints Immediate reputation damage Even a small test can: Trigger spam filters Flag your domain/IP Affect future campaigns to real subscribers I’ve seen users with clean accounts struggle for weeks...

In real scenarios: Open rates look “okay” at first Complaints and bounces rise quickly Inbox placement drops Yahoo / Gmail throttling starts IP or domain reputation gets damaged Recovery takes weeks or months, not days.

Segments are what actually make Mumara powerful. Use Segments whenever: You’re sending campaigns You’re running automations You care about subscription status, activity, or behavior Examples of commonly used Mumara segments: Subscribed contacts only Opened last campaign Clicked a specific...

Sure, why not. In MumaraONE, the distinction matters because: Transactional emails Triggered by a user action Expected by the recipient Can be sent even if the user is unsubscribed from marketing Promotional emails Sent for marketing, upsell, or engagement Require explicit subscription...

That’s the tricky part and usually it becomes a reason behind putting a bad impact on your account's reputation. Even if the client accepts the risk: Spam complaints affect sending infrastructure Blacklists don’t care who approved it One bad campaign can impact future inboxing So the risk...

That’s the most common claim and also the biggest red flag as this cannot be trusted. Here’s the key rule Mumara follows - The user must have opted in specifically to receive emails from you. “Opted in elsewhere” usually means: They signed up on a different brand’s website They agreed to...

Use contact lists when you want to organize or import contacts, not when you want to decide who receives an email. Typical Mumara list use cases: Imported contacts from a CSV or by any other way supported by Mumara Webinar registrations Event signups Contacts synced from an external source...

This is a very common situation and you’re not alone with this problem However, MumaraONE is built for permission-based emailing, not cold outreach. Cold emailing puts your domain, IP, and platform reputation at risk, even if the client insists.

Thats very important to understand and quite a great question However, this is one of the most misunderstood areas in email marketing. The key thing to remember is this: It’s not about when the email is sent it’s about why it’s sent. I can break it down the MumaraONE way upon your request.

Well, this is something very important to understand and I’m glad you’re asking before importing anything. If you are a MumaraOne user then I would say purchased data is not allowed in Mumara, even if users opted in elsewhere. I can explain why, based on real usage scenarios for you to...

Thats quite a great question this confusion is very common, especially for users who are scaling. In a shorter version like how Mumara can handle: Lists are for storage Segments are for targeting But I can break it down for your better explanation if you want to.

Exactly. Mumara gives you all the controls the key is using segments as guardrails. One missed exclusion won’t break your reputation, but repeating it will. Fix the workflow once, and you’re safe going forward. However, the best guide is to go through the documentation. Here is the link for it...

Here’s a simple rule you can remember: If the email has a date or deadline → Scheduled If the email depends on user behavior or timing → Evergreen Most mature setups use both, but for different jobs.