Is it possible to provide a value for |UNSUB| directing the audience to our own unsubscribe web service.
I have a mandate to not store the subscriber list on MailChimp but rather upload it when required. The reader of the email would then click the unsubscribe link and be directed to our own unsubscription service.
I know this may sound unconventional, I am really just looking to see if this is an option or not.
Thanks
This isn't possible for the obvious reason: MailChimp (and any other worthwhile ESP) needs to be able to ensure you're not spamming people, so if someone requests to be removed from the list, MailChimp will need to remove them.
If you're not permitted to store the list at an ESP, you'll probably need to roll your own newsletter service rather than using a SaaS product.
Related
I was looking at the Mailchimp API documentation because I want do an implementation where I list all the messages per subaccount. This doesn't seem possible. You get all the messages from every subaccount. Same if you use a webhook. The subaccount API options seem very limited.
I'm using the Mailchimp Transactional PHP lib. I tried using the messages->search() method where I set senders param but that doesn't really capture everything linked to the subaccount. It would be great if you could add a subaccount param to the messages->search() method. You can filter afterwards by looping through every result and checking the subaccount but that seems like a crappy workaround.
Anyone have another workaround? I see there is no way to report bugs or feature request on their Github? Or know how to contact the developers?
We want to start a service with Mailchimp where every subscriber will get a customized link in the email she receives. The Subscription Form will be on a wordpress website (not my decision).
There is a pool of thousand of links with a unique parameter, which we have stored on our webserver, like these examples
https://example.com/link?code=a25b1d085f3aec4b256
https://example.com/link?code=32219abb336de28a103
etc
Every code parameter should only be used once and should be kept as secret as possible. So I don't think it is a good idea to send the code from the form to mailchimp in a hidden field.
I don't know, if this is possible. Is Mailchimp even the right tool to do this?
I'm not sure, where to start the journey.
I don't think webhooks will help me here, as those are only one-way communication without a backwards channel, as far as I understand.
I checked the Mailchimp API documentation, but I might be too foolish to understand, which of the multiple options I need to use.
I found this answer here: https://stackoverflow.com/a/53096852/476951, but I don't know, if this will suit my needs. As I understand it, this will chhange the mail template in Mailchimp UI with an API request and store it. The successive emails will all use this changed template until I change the template again. This seems not to be the correct way.
So, here are the two workflows that might be possible, but I don't know if they are.
Have a form created in Wordpress (not the embedded Mailchimp form), and create a custom form handler with admin-post.php like described here. Then use the API to send the email through the Mailchimp service with my dynamic link in it. But how. Every tuorial I found sends campaigns via the API, not individual mails to single recepients
Somehow manage Mailchimp to get the dynamic content via some sort of webhooks or the likes.
Is any of these workflows suitable to do this?
If yes, who should I set these up?
Is there anything else I might have missed?
Edit
Or do I need to use Mailchimp Transactional Email service (former called Mandrill)?
I need to implement PayPal payment in my Laravel site. I was going for the server side integration, in order to save all the data, transactions and know what they actually bought. But turns out that [the older] server-side integration method [that I was looking at] is archived, and not really the preferred method anymore. Instead, they suggest using the smart buttons, with front end integration only.
Questions:
Is front end only safe? what prevents the user from messing with the JavaScript and editing the sum with whatever they want?
How do I know what they ordered if it is all front end?
What would I have to do if the payed sum does not correspond to the articles in the cart?
What should I be aware of with this system?
Smart Payment Buttons can be used with or without a server-side component.
Here is the front-end pattern that communicates with a server-side integration: https://developer.paypal.com/demo/checkout/#/pattern/server
Notice the fetches to two '/demo/...' placeholder endpoints, which need to be replaced with actual routes of yours. The first should create a v2/order via API and return the orderID. The second should capture that order after the payer approves it via Smart Payment Buttons.
The answers to your questions re: a serverless (client-side only) pattern are:
Nothing
Only what you program the JavaScript to tell you and which it actually successfully tells you, or what you read via email or in your PayPal account or app notifications
Refund the transaction
It's for people who don't want to do the work of implementing server-side routes and API calls.
I am working on a POC to proof out the ability to get a list of all the new users who have been added to a specific Slack Channel. From my initial review of the Slack API I am not seeing anything that showcases this ability, I was curious to see if anyone had worked on something similar or could point me to resources that would be a viable solution.
I believe there is no ready-made API method available, that will give you that specific information. However, Slack is very flexible and you can use the existing building blocks to easily add additional features as needed.
E.g. To get the requested information you can develop a small Slack app that listens to the member_joined_channel and member_left_channel events to keep track of when members joined a channel.
If you need a historical record of membership in a channel, you could use the Slack API's groups.history method, page through results, and build a membership log by looking for events of type member_joined_channel and member_left_channel through time.
How to let visitors of the website provide their email ids, optionally, for further future communication with them. Its not specifically a newsletter subscription or anything (but could as well be) but just a polite pop-up on visiting a page, asking them to provide their email address, if they wish to be contacted sometime in future.
this is to run on a Joomla based website.
just a simple form (can be a pop-up) that asks for user email ids and then stores it in the database.
Not a Mailing List subscription or anything like it (so no auto-responder subscription needed)
Thanks
This should be very easy for the people that know !
I don't think there is a ready-made extension available for this, but there are some extensions that you can use as examples to put together something yourself. You could look at newsletter subscription components and modules to see how they make a form for receiving a name and email address, and how they save it to the database. You could also look into extensions that use Squeezebox, the built-in Lightbox look-alike, or you could check one of the login modules that popup.
However, I think you would be ready most quickly if you would just install a newsletter component, change the text of the subscription module (and possibly corresponding changes to front-end component output), and then you simply don't send newsletters. In this way you would start building a database table with names and email adresses as you seem to want.
I beleive sm2email can do it:
http://sm2extensions.com/content/view/143/105/