Search results

Neat! We'll give that a try soon, thanks!

Thanks for your advice! The "delete" option seems to work. But... if there's an autoresponder series that they've already received, they'll start receiving all those emails again. So I don't think that's a great option. We're not sure how to just "reactivate" the user on the same list, so...

Awesome, that'll be really useful!

So, say we're using a custom field called [FIRST_NAME] in a campaign. Like: Hi [FIRST_NAME]! Is there a way to set a fallback, in case that field is empty for a specific subscriber? In this case, it would be great if 'there' would be the fallback, so it would become: Hi there! Rather than...

Is it possible to change the status of a subscriber on a specific list from 'Unsubscribed' to 'Confirmed', using the API?

FYI, we solved this by adding a line to the TransactionalEmail model to delete the TransactionalEmail record if it's found to be a blacklisted email address. if (EmailBlacklist::isBlacklisted($this->to_email)) { $this->delete(); return false; } Do you think this is...

Ok we've determined that it's because the process is running into blacklisted emails. The problem is though...say it's set to send 100 emails. If all 100 of those are blacklisted, it actually will send 0 emails. This seems like a bug...it should keep processing the queue until it SUCCESSFULLY...

Can you think of any reason why, when manually running the command via SSH, there's still a bunch of Unsent items? And it completes in like 1 second...almost like it does nothing.

How do we debug the "send-transactional-emails" command? Adding --verbose=1 just gives an errror. Our transactional email queue sometimes is backed up for 20 min, and when I manually run the process there's still a bunch of items stuck at "Unsent". I can't figure out what's going on. Also...

Ok that sounds like a bad solution, as far as upgrades go. I guess we'll just use a custom field.

We're adding subscribers via the API. But the IP address of each is being set to the IP address of our web server, not the actual users/subscribers IPs. So they're currently all the same. Is there a way to manually set the IP address via the API, without having to use a custom field?

Heh, no apologies necessary, I'm impressed with the support! I'll add it to Feature Requests. The additions to the segment conditions allow us to do what we need to do for this case, anyways.

So the new fields on "Subscriber Confirmation" page allow you to only choose Subscribers that Opened / Unopened a campaign. It would be more useful (at least for us) to choose subscribers that were Sent / Not Sent a campaign. For email deliverability, it can be bad to send the exact same...

We see it now in the new version - thanks!

See attached screenshot. Those options don't exist. FYI I haven't upgraded to the latest version yet...in progress right now...

Have you considered adding negatives for all Condition Operators? For example, you have "starts with" but not "doesn't start with". You also have "ends with", but not the inverse of "doesn't end with". If "doesn't start with" was an option, it'd be easy for me to handle my problem, prior to...

Ahh didn't know that! In other email marketing systems I've been able to setup a segment that targeted (or avoided) a previous broadcast. I just assumed it was common functionality. I'll check out 1.3.5 - thanks!

Is there really no way to set up a segment to exclude subscribers who have received a previous campaign? Like, I wanted to first send to ~1000 subscribers, so I created a segment where their email started with the letter "b". Now I want to send to EVERYONE ELSE. How can I do this?