This repository has been archived by the owner on Aug 27, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 966
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1924 from sendgrid/develop
6/13/16 Docs Updates
- Loading branch information
Showing
82 changed files
with
397 additions
and
61 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,148 @@ | ||
--- | ||
layout: page | ||
title: Alerts API | ||
weight: 100 | ||
navigation: | ||
show: true | ||
--- | ||
|
||
Alerts allow you to specify an email address to receive notifications regarding your email usage or statistics. | ||
<br> | ||
<ul> | ||
<li>Usage alerts allow you to set the threshold at which an alert will be sent. For example, if you want to be notified when you've used 90% of your current package's allotted emails, you would set the "percentage" parameter to 90.</li> | ||
<li>Stats notifications allow you to set how frequently you would like to receive email statistics reports. For example, if you want to receive your stats notifications every day, simply set the "frequency" parameter to "daily". Stats notifications include data such as how many emails you sent each day, in addition to other email events such as bounces, drops, unsubscribes, etc.</li> | ||
</ul> | ||
<br> | ||
For more information about alerts, please visit our <a href="{{root_url}}/User_Guide/Settings/alerts.html">User Guide</a>. | ||
|
||
|
||
FORMAT: 1A | ||
|
||
## Alerts Collection [/alerts] | ||
|
||
### Get All Alerts [GET] | ||
|
||
Retrieve all alerts. | ||
|
||
+ Response 200 (application/json) | ||
+ Body | ||
|
||
[ | ||
{ | ||
"created_at": 1451498784, | ||
"email_to": "[email protected]", | ||
"id": 46, | ||
"percentage": 90, | ||
"type": "usage_limit", | ||
"updated_at": 1451498784 | ||
}, | ||
{ | ||
"created_at": 1451498812, | ||
"email_to": "[email protected]", | ||
"frequency": "monthly", | ||
"id": 47, | ||
"type": "stats_notification", | ||
"updated_at": 1451498812 | ||
}, | ||
{ | ||
"created_at": 1451520930, | ||
"email_to": "[email protected]", | ||
"frequency": "daily", | ||
"id": 48, | ||
"type": "stats_notification", | ||
"updated_at": 1451520930 | ||
} | ||
] | ||
|
||
### Create a New Alert [POST] | ||
|
||
Create a new alert. You can create the same alert multiple times, but with different email addresses specified in the "email_to" parameter. This is useful if you have multiple users on the same account who would like to receive the same alerts. | ||
<br> | ||
<br> | ||
|
||
+ Attributes (object) | ||
+ type usage_alert (required, string) - The type of alert you want to create. Can be either usage_alert or stats_notification. | ||
+ email_to [email protected] (required, string) - The email address the alert will be sent to. | ||
+ percentage 90 (optional, number) - Required for usage_alert. When this usage threshold is reached, the alert will be sent. | ||
+ frequency daily (optional, string) - Required for stats_notification. How frequently the alert will be sent. | ||
|
||
|
||
+ Request (application/json) | ||
|
||
+ Body | ||
|
||
{ | ||
"type": "stats_notification", | ||
"email_to": "[email protected]", | ||
"frequency": "daily" | ||
} | ||
|
||
+ Response 201 (application/json) | ||
|
||
+ Body | ||
|
||
{ | ||
"created_at": 1451520930, | ||
"email_to": "[email protected]", | ||
"frequency": "daily", | ||
"id": 48, | ||
"type": "stats_notification", | ||
"updated_at": 1451520930 | ||
} | ||
|
||
## Alerts Collection [/alerts/{alert_id}] | ||
|
||
### Get an Alert [GET] | ||
|
||
Retrieve a specific alert. | ||
|
||
+ Response 200 (application/json) | ||
|
||
+ Body | ||
|
||
{ | ||
"created_at": 1451520930, | ||
"email_to": "[email protected]", | ||
"frequency": "daily", | ||
"id": 48, | ||
"type": "stats_notification", | ||
"updated_at": 1451520930 | ||
} | ||
|
||
### Delete an Alert [DELETE] | ||
|
||
Delete an alert. | ||
|
||
+ Response 204 | ||
|
||
### Update an Alert [PATCH] | ||
|
||
Update an alert. | ||
<br> | ||
<br> | ||
|
||
+ Attributes | ||
+ email_to [email protected] (optional, string) - The new email address you want your alert to be sent to. | ||
+ frequency monthly (optional, string) - The new frequency at which to send the stats_notification alert. | ||
+ percentage 90 (optional, number) - The new percentage threshold at which the usage_limit alert will be sent. | ||
|
||
+ Request (application/json) | ||
|
||
+ Body | ||
|
||
{ | ||
"email_to": "[email protected]" | ||
} | ||
|
||
+ Response 200 | ||
|
||
+ Body | ||
|
||
{ | ||
"created_at": 1451520930, | ||
"email_to": "[email protected]", | ||
"frequency": "daily", | ||
"id": 48, | ||
"type": "stats_notification", | ||
"updated_at": 1451522691 | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -17,4 +17,4 @@ EXAMPLE: | |
|
||
If you request a refund on your $79.95/mo Pro account, and your monthly invoice totals $117.00 due to a combination of overages and contact storage, you are only eligible for a refund of up to 79.95. The remaining 37.05 cannot be refunded in this scenario. | ||
|
||
If you need to request a refund, please email <[email protected]>. | ||
If you need to request a refund, please email [[email protected]](mailto:[email protected]). |
39 changes: 39 additions & 0 deletions
39
source/Classroom/Basics/Marketing_Campaigns/how_to_remove_unusable_contacts.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
--- | ||
seo: | ||
title: How to Remove Unusable Contacts | ||
description: Learn how you can delete contacts that result in bounces or spam reports. | ||
keywords: marketing, campaign, unusable, unwanted, contacts | ||
title: How to Remove Unusable Contacts | ||
weight: 0 | ||
layout: page | ||
navigation: | ||
show: true | ||
--- | ||
|
||
It is common to have contacts that result in a group unsubscribe, block, bounce, invalid email address, or spam report. Attempting to send email to these contacts can negatively impact your reputation since these contacts do not want to (and will not) receive your marketing emails. By continuing to store these contacts, you are being charged for recipients that will automatically be dropped. | ||
|
||
The following steps will show you how to remove all of your unusable Marketing Campaigns contacts so that you won't continue to be charged for their storage. | ||
|
||
1. When viewing your dashboard, navigate to the left hand menu and click **Suppressions**. | ||
|
||
2. Open a specific group, such as Bounces or Spam Reports, click the settings cog in the upper right corner, then select **Download as CSV**. | ||
|
||
![]({{root_url}}/images/remove_unusable_contacts_1.png) | ||
|
||
3. Repeat step 2 for each of the groups that you want to remove (e.g. unsubscribes, spam reports etc.) and merge each of those lists into a single CSV file. | ||
|
||
* *Alternatively, you can download all of your contacts from Marketing Campaigns (create a segment defined by "created at" "is after" with a date from 1999 to capture all contacts, and then export that segment).* | ||
* *Next, upload that CSV of all contacts to our [List Assist](https://sendgrid.com/docs/Utilities/list_assist.html) tool. This will give you a CSV of all of your Marketing Campaigns contacts that exist on any of the Suppression lists.* | ||
* *Use that list to follow steps 4-8 below. You can find a video tutorial explaining how to use List Assist [here](https://www.youtube.com/watch?v=FiyDgCl78dk).* | ||
|
||
4. Return to your dashboard, navigate to the left hand menu and select **Marketing**, then **Contacts**. | ||
|
||
5. In the upper right corner click **Add List or Segment** and select **Upload CSV**. | ||
|
||
6. You will be presented with a dialogue box. Select the option to **Create New List** and name it something obvious, like "Remove Invalid Emails." | ||
|
||
7. Once uploaded, click the cog to the right of that new list and select **Delete**. | ||
|
||
8. Another dialogue box will open asking if you wish to delete "all contacts associated with this list". Make sure that box is checked, and then you're good to go! | ||
|
||
![]({{root_url}}/images/remove_unusable_contacts_2.png) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
39 changes: 39 additions & 0 deletions
39
source/Classroom/Deliver/Sender_Authentication/microsoft_dmarc_changes.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
--- | ||
st: | ||
published_at: 2016-06-13 | ||
type: Classroom | ||
seo: | ||
title: Microsoft DMARC Changes | ||
description: 550 5.7.1 The messages violates the DMARC policy of... | ||
keywords: dmarc, microsoft, live, outlook, from, spf, dkim, hotmail, msn | ||
title: Microsoft DMARC Changes | ||
weight: 0 | ||
layout: page | ||
zendesk_id: 202449646 | ||
navigation: | ||
show: true | ||
--- | ||
|
||
Miscrosoft has recently decided to embrace [DMARC](http://sendgrid.com/blog/dmarc-domain-based-message-authentication-reporting-conformance/) more explicitly, much like their email brethren, Yahoo, AOL, and GMail. You may have started seeing bounce messages with the following reasons: | ||
|
||
Hotmail / Outlook / MSN / Live: | ||
|
||
**550 5.7.1 The messages violates the DMARC policy of domain.tld (1b6c35a4-2c11-11e6-ab23-549f350a57e2)** | ||
|
||
**550 5.2.0 54Qa1t0144ZKE95014QaMR Message rejected due to DMARC. Please see http://postmaster.comcast.net/smtp-error-codes.php#DM000001** | ||
|
||
**550 5.2.0 54QF1t03z3oQ44H014QGZ3 Message rejected due to DMARC.** | ||
|
||
This is because Microsoft will no longer be accepting messages where the From domain is a Microsoft domain address and the message originates from a non-approved Microsoft mail domain server/service. This is a security measure they have implemented to help reduce potential address spoofing of their mail domains. | ||
|
||
|
||
|
||
**What this means:** As of June, 2016, you can no longer send with the From address being anything from a Microsoft address when sending to a domain that checks DMARC before accepting mail. | ||
|
||
**What you can do: ** You will need to change the From address you use in emails to a non-Microsoft address. We recommend using one at your own mail domain, or one you control that is legitimate. You can then set the Reply-To field to be the original Microsoft address that previously was used in the From field. | ||
|
||
**What about these messages, are they lost?** : Yes, any send with this bounce message is discarded and tracked as a [Block](http://sendgrid.com/blocks). You will need to adjust your From address field settings, and then try resending from your side. | ||
|
||
|
||
|
||
For more extended reading, check out check out [this article on the DMARC changes](http://www.mediapost.com/publications/article/277884/dmarc-changes-coming-soon-to-an-inbox-near-you.html?utm_source=newsletter&utm_medium=email&utm_content=headline&utm_campaign=93744), as well as our [DMARC Classroom article]({{root_url}}/Classroom/Basics/Email_Infrastructure/everything_about_dmarc.html). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.