Is there a way to query email delivery from a Sendgrid account which includes the API Key used to send that email? We dont have subusers but a bunch of Keys used by different applications instead.
If you have the extended email activity history add on you can fetch your email activity from the API. One of the query types you can use to filter the results is the api_key_id. So, you can loop through your API key IDs and return the emails sent by each one.
Related
We are having a problem with Individual email results. Our aim is to show individual email results in Salesforce after sending emails from Marketing Cloud.
We sent several emails from Marketing Cloud to the same lead id using template email 'A'. However we noticed that marketing cloud didn't create any individual email results in Salesforce linked to this lead id.
We already verified settings of marketing cloud connector and we didn't find any issue (as a confirm, we sent another email using template email 'B' after the template ‘A’ to the same lead id and IER has been created).
We verified in the Sent Data View (configured using a query) where marketing logs all information related to the email sends and we found out that email sents with template 'A' show the same Job ID, but different Batch ID.
Can the IER creation be affected by this behaviour?
What is the behaviour of Salesforce/Marketing when we have the creation/update of IER? Are there any constraints? (In our example we will probably send the same email template to the same lead id several times in an hour/day).
I have a .NET console application that add a list of users in a selected Yammer group through [/group_memberships.json] endpoint and it works fine.
Anyway the customer wants to avoid the sending of a confirmation email to user that has been added. In fact, after my program runs, all users receive an email like "XXX has added you to the YYY group on Yammer. Go to group".
The only way that I found to avoid this email is disable email notification in user settings.
Is there another simple way? Through Rest API is possible tell to Yammer to do not send email or, otherwise, change the user settings? I'm asking it because there're some hidden Rest API not documented in the official Yammer site.
Thanks
Yammer doesn't have any API endpoint to achieve your objective. Your customer may consider adding a rule in exchange to block emails based on the "from" address and certain keywords in the "subject".
I'm writing a program that should send emails to multiple users with content extracted from an excel spreadsheet. I know how to do this using the net/smtp package in Go, but I would like to know if it's possible to send an email with the sender being a google group (i.e googlegroup#gmail.com) instead of my email without resorting to using the gmail API? Currently I have a working program that can log in through an email and password, which is then used for auth credentials, but seeing as that google groups don't have the same kind of interface I'm not quite sure how to change it so emails are sent from a group instead of an individual user.
Each google group should have an email address associated with it. golang-nuts is golang-nuts#googlegroups.com for example. Any mail sent to that should be posted to the group, assuming it is from a member of the group.
In order to send from your own gmail account, you can use gmail's outgoing smtp feature with the net/smtp package. Configuration is explained better on this digital ocean post
I have a database as part of my web app that stores user emails, age, gender, etc. Is there a way, through the API to send a bulk email to a lsit of users? Previously I've used their API to create new entries from my database in MailChimp's system, and then we'd segment our users through MailChimp's web application. The issue is that sending your data to MailChimp has so many issues. For example, to store a user's age in MailChimp, you have to create an individual "group title" for each age when done thru the API. You can't just specify that the field "age" is a number and then add whatever you like. Also, each user selects a city when they sign up through us, and if we add another city to our selection list, you have to manually add it on MailChimp, otherwise you get an error.
So the simplest solution would be if we could do the segmenting on our side and send an email through the API, unless there is another, easy way to do this. I know that Amazon SES let's you email through an API, but I want other features of MailChimp, such as sent email history, analytics and providing and easy unsubscribe feature for users - Amazon SES doesn't do any of that.
Is there an answer to my conundrum?
Have you checked out Mandrill? It's a newer service from MailChimp that works like SES, but has those incredible MailChimp marketing sensibilities you know and love (open/click tracking, email audit log, plus lots of new stuff.)
It won't connect directly to your data in MailChimp (yet), but it sounds like you've got all the relevant data in your own DB already and can do the segmentation and content generation yourself.
Bonus: you'll also get a discount if you're already a paying MailChimp customer.
I'm generating a bulk mailing each day for users who want to receive the daily deals. I can either send a separate physical email with each user specified on their own unique To header, or I can send one email with all the users on the BCC line.
Obviously if I ever want to create user specific content I will need to customize the emails per user and send them individually, but if I don't want customized email right now, should I just send out the single email with everyone on BCC? Any reason to NOT do that.
Edit: I'm using a third party as my gateway that specializes in delivery with CAN-SPAM compliance, etc.. not trying to do this off my own mail server...
Update: I guess I'm really also looking for some metrics here. Is there a difference in open rates of BCC'ed email vs To field email? What about spam filtering rules that might pre-classify based on the BCC field?
No reason I can think off for NOT doing it. Using BCC is the polite way to send bulk emails.
In this case, it turns out that the correct answer was neither. The gateway provided a custom header API that allowed me to specify all the recipients in a secondary "To" field. The API then handled the blind delivery of the emails, and also did variable substitution for me so I didn't have to transmit all the duplicate content multiple times. The API then handled doing "best practices delivery of the email".