Search results

Make sure that webhooks are used to send delivery status notifications (DSN), e.g. if an email has been delivered or bounced, or received, or spammed etc.

If you have the programming skills, you can do an API integration with Mumara addContact endpoint. Otherwise, a quick solution would be to create a zap using zapier.com between Facebook and Mumara.

Mumara Campaigns edition is the latest product that is undergoing updates. We do have an ESP edition for Mumara Campaigns that we don't sell commercially on the website. You can private message me, and I'll give you details about it. Or add me to your skype -> wasif.ahmad86.

For further discussion, I would suggest opening a new topic.

Btw you can also signup for a 14-day free trial and test it before you proceed with the purchase. The trial comes up with the server and will be automatically deployed. To deploy a trial, navigate to https://www.mumara.com/campaigns/pricing/ and click the Deploy Trial button.

I would suggest you to go with Mumara Campaigns as it's more latest copy and undergoing frequent updates!

You can create a segment based on the custom field value and create a trigger on it that should send the drip/broadcast. So when there is a new contact added and it matches the segmented criteria, the trigger should fire the action on it. And this action will be performed once, as it will take...

Are you using Mumara Classic or the Campaigns? If you are using Mumara Campaigns, then you can add a segment based on recipient engagement and then create a trigger on it to notify you. Make sure that the next version is coming up with more options for segmentation.

1. Can you explain the case of the one-time email delivery? Are you referring to one-time birthday emails or simple newsletters? 2. For the recurring birthday emails, we have packed up a new module for the triggers, which is coming in v5.4.3

Few things you need to keep in mind You always need to wait for a justified time for the team to reproduce the case, especially on the weekends. Nothing is super quick! There are hundreds of criteria, and every filter changes how it works. So a technician needs to test it on your installation...

@rehan reproduce this case and verify the issue.

1. You should always use the domain instead of the IP address, as it will not work for the tracking domains. 2. Tell me the exact filters you used for the segment criteria? Based on the email sent or the recipient's engagements? Please share the criteria snapshot so I can try to find the issue.

As you said, you created the trigger based on a segment. Can you provide me with the criteria for the segment? I mean, what filters did you use for the segment? And also, what version of Mumara you are using?

@marakonek you can skip the db issues as it will keep giving the alter queries as the MySQL version mismatches. Regarding your drips issue, can you tell me the exact criteria of your segment?

Is it related to Mumara? Always give maximum information. I cannot assume where you are getting this error, in what application, on what step, etc.

It's already there on the dashboard where you get to see this in the Live Events.

Are you referring to editing a trigger or segment? Trigger can be edited, but segment not.

If you are a Mumara user, you should be able to do it using the Mumara wizard to configure the PMTA server. The sample code for the rotation is <virtual-mta my_mta> smtp-source-host mta01.domain.com smtp-source-host mta02.domain.com </virtual-mta> <smtp-user smtp_username> password...

If you know how pmta config works, you can create a vmtp-pool of your two virtual-mta and use that. PMTA will handle the rotation

If you want to run this every 24h, you can open a support ticket and give them this query to set for every 24h.