From b5c9d2c8b72de472c3d7186267cca68469a0a129 Mon Sep 17 00:00:00 2001 From: Leor Manelis Date: Wed, 14 Jan 2015 14:07:29 -0700 Subject: [PATCH 01/30] Create Confirmed_Opt_In docathon #256 --- source/Glossary/ Confirmed_Opt_In | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 source/Glossary/ Confirmed_Opt_In diff --git a/source/Glossary/ Confirmed_Opt_In b/source/Glossary/ Confirmed_Opt_In new file mode 100644 index 0000000000..ced6242a3b --- /dev/null +++ b/source/Glossary/ Confirmed_Opt_In @@ -0,0 +1,7 @@ +Opt-in email is a term used when someone is given the option to receive "bulk" email, that is, email that is sent to many people at the same time. Typically, this is some sort of mailing list, newsletter, or advertising. Without obtaining permission before sending email, the email is unsolicited bulk email, better known as spam. + +Making sure your users have the opportunity to give their preference can help you increase your sender reputation and stay out of the spam box. + +The term Opt-out refers to several methods by which individuals can avoid receiving unsolicited product or service information. This ability is usually associated with direct marketing campaigns such as telemarketing, e-mail marketing, or direct mail. + +What is Confirmed Opt-In? The Confirmed Opt-In sending practice requires you to send confirmation emails to every registrant asking them to click to confirm their interest in receiving your emails. Conversely, a Single Opt-In is if you accept email addresses at the time of registration and then begin emailing them normally. From 2da20897bd3e7c64b9cdb6ef97437c6a6857983e Mon Sep 17 00:00:00 2001 From: Leor Manelis Date: Wed, 14 Jan 2015 14:32:55 -0700 Subject: [PATCH 02/30] Create Autoresponder docathon#219 --- source/Glossary/Autoresponder | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 source/Glossary/Autoresponder diff --git a/source/Glossary/Autoresponder b/source/Glossary/Autoresponder new file mode 100644 index 0000000000..596d9889df --- /dev/null +++ b/source/Glossary/Autoresponder @@ -0,0 +1,11 @@ +An autoresponder is a computer program that automatically answers e-mail sent to it. They can be very simple or quite complex. The first autoresponders were created within mail transfer agents that found they could not deliver an e-mail to a given address. These create bounce messages such as "your e-mail could not be delivered because..." type responses. Today's autoresponders need to be careful to not generate e-mail backscatter, which can result in the auto-responses being considered E-mail spam. + +Autoresponders are often used as e-mail marketing tools, to immediately provide information to their prospective customers and then follow-up with them at preset time intervals. Such follow-up autoresponders can be divided into two categories: + +Outsourced ASP model — these autoresponders operate on the provider's infrastructure and are usually configurable via a web-based control panel. The customer pays a monthly usage fee. This is easiest to implement for the end-user. + +Server-side — enables users to install the autoresponder system on their own server. This requires technical skills. + +Autoresponders are also incorporated into electronic mailing list software, to confirm subscriptions, unsubscriptions, posts, and other list activities. + +Read more here From d596326f8e21db8f9e8397e0c6284650ca2474f8 Mon Sep 17 00:00:00 2001 From: Leor Manelis Date: Wed, 14 Jan 2015 14:49:30 -0700 Subject: [PATCH 03/30] Create Bayesian Filter docathon #220 --- source/Glossary/Bayesian Filter | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 source/Glossary/Bayesian Filter diff --git a/source/Glossary/Bayesian Filter b/source/Glossary/Bayesian Filter new file mode 100644 index 0000000000..3896cfb580 --- /dev/null +++ b/source/Glossary/Bayesian Filter @@ -0,0 +1,7 @@ +Naive Bayes classifiers are a popular statistical technique of e-mail filtering. They typically use bag of words features to identify spam e-mail, an approach commonly used in text classification. + +Naive Bayes classifiers work by correlating the use of tokens (typically words, or sometimes other things), with spam and non-spam e-mails and then using Bayesian inference to calculate a probability that an email is or is not spam. + +Naive Bayes spam filtering is a baseline technique for dealing with spam that can tailor itself to the email needs of individual users and give low false positive spam detection rates that are generally acceptable to users. It is one of the oldest ways of doing spam filtering, with roots in the 1990s. + +Learn more here From 3bbfed4372c9f013b186538c26004829484e4b51 Mon Sep 17 00:00:00 2001 From: Leor Manelis Date: Mon, 19 Jan 2015 11:38:27 -0700 Subject: [PATCH 04/30] Create Drip Campaign #240 I didn't add the link you mentioned because currently drip campaigns are not available and that could be confusing for users --- source/Glossary/Drip Campaign | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 source/Glossary/Drip Campaign diff --git a/source/Glossary/Drip Campaign b/source/Glossary/Drip Campaign new file mode 100644 index 0000000000..353c2d28d4 --- /dev/null +++ b/source/Glossary/Drip Campaign @@ -0,0 +1,3 @@ +Drip Campaign - is a communication strategy that sends, or "drips," a pre-written set of messages to customers or prospects over time. These messages often take the form of email marketing, although other media can also be used. Drip marketing is distinct from other database marketing in two ways: (1) the timing of the messages follow a pre-determined course; (2) the messages are dripped in a series applicable to a specific behavior or status of the recipient. It is also typically automated. + +This feature is not yet available. From 2484256c87a1284b44354ed1bce58d27b228a7a7 Mon Sep 17 00:00:00 2001 From: VictorAcatrinei Date: Mon, 9 Nov 2015 12:37:55 +0200 Subject: [PATCH 05/30] Update mail.md The URL from the Spam Checker app is mandatory now. It isn't optional like the current page says. --- source/User_Guide/Settings/mail.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/User_Guide/Settings/mail.md b/source/User_Guide/Settings/mail.md index 5c3c7e19e5..f033f89b50 100644 --- a/source/User_Guide/Settings/mail.md +++ b/source/User_Guide/Settings/mail.md @@ -174,7 +174,7 @@ The Spam Checker setting, is useful when your web application allows your end us The default threshold is 5.0 and can range between 1 and 10. The lower the number, the more strict the filtering. For example, a value of 2 will drop all but the most flawless emails, whereas 9 will only drop the spammiest of spam emails. {% endwarning %} -We use [SpamAssassin](http://spamassassin.apache.org/full/3.4.x/doc/Mail_SpamAssassin_Conf.html#scoring_options) to process the spam checks for this filter. The default threshold is 5.0, but you can set this to any value between 1 and 10. If you provide a URL, we will post the message to that URL, but this field is optional. If a message is flagged as spam using this filter, it will automatically be dropped by our system and will not be delivered to the recipient. +We use [SpamAssassin](http://spamassassin.apache.org/full/3.4.x/doc/Mail_SpamAssassin_Conf.html#scoring_options) to process the spam checks for this filter. The default threshold is 5.0, but you can set this to any value between 1 and 10. You must provide an URL, so we will post the message to that URL. If a message is flagged as spam using this filter, it will automatically be dropped by our system and will not be delivered to the recipient. {% anchor h3 %} Settings From 4c736455e132c91d6eae519324669bf80f83c8b7 Mon Sep 17 00:00:00 2001 From: Eric Schallock Date: Mon, 9 Nov 2015 09:23:24 -0700 Subject: [PATCH 06/30] Edited drip_campaign glossary entry --- source/Glossary/drip_campaign | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 source/Glossary/drip_campaign diff --git a/source/Glossary/drip_campaign b/source/Glossary/drip_campaign new file mode 100644 index 0000000000..f982612aa6 --- /dev/null +++ b/source/Glossary/drip_campaign @@ -0,0 +1,28 @@ +--- +layout: page +weight: 0 +title: Drip Campaign +navigation: + show: true +seo: + title: Drip Campaign + override: true + description: Drip Campaigns are a type of automated email marketing strategy. +--- + +A drip campaign is a type of automated [email marketing strategy]({{root_url}}/Glossary/email_marketing.html) that involves sending a recipient +a series of pre-written messages according to a predetermined schedule. This schedule is often +initiated by certain events in the recipient’s lifecycle as a customer, such as registering for +a service or purchasing a product. Drip campaigns revolve around the idea of slowly “dripping” +specific emails to a recipient in an effort to generate or increase customer engagement over a finite +period of time. + +Drip campaigns help you to send relevant and well timed emails that your customers are likely interested in +seeing. Striving to send emails that are relevant to your recipients can help to improve your [sender +reputation]({{root_url}}/Glossary/sender_reputation.html), cultivate customer satisfaction, and increase customer retention. + +{% info %} +It is important to avoid initiating a series of messages that your customer doesn’t want to receive. Make sure +that you give your recipient the option of opting out of the drip campaign by including an [unsubscribe link]({{root_url}}/User_Guide/Suppressions/group_unsubscribes.html) in +every email you send. +{% endinfo %} From 65313cd5352e420fab3b3fd18442283f33a6ba70 Mon Sep 17 00:00:00 2001 From: Eric Schallock Date: Mon, 9 Nov 2015 10:03:05 -0700 Subject: [PATCH 07/30] renamed drip_campaign to drip_campaign.md --- source/Glossary/{drip_campaign => drip_campaign.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename source/Glossary/{drip_campaign => drip_campaign.md} (100%) diff --git a/source/Glossary/drip_campaign b/source/Glossary/drip_campaign.md similarity index 100% rename from source/Glossary/drip_campaign rename to source/Glossary/drip_campaign.md From 5c18918104b5cce469e0625d9f265db881979db4 Mon Sep 17 00:00:00 2001 From: Matt Bernier Date: Mon, 9 Nov 2015 10:19:35 -0700 Subject: [PATCH 08/30] Update scheduling_parameters.md --- source/API_Reference/SMTP_API/scheduling_parameters.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/API_Reference/SMTP_API/scheduling_parameters.md b/source/API_Reference/SMTP_API/scheduling_parameters.md index 5d1fa4b5da..6e46a573d5 100644 --- a/source/API_Reference/SMTP_API/scheduling_parameters.md +++ b/source/API_Reference/SMTP_API/scheduling_parameters.md @@ -19,7 +19,7 @@ performance. This functionality: * Is available for free to all SendGrid customers. {% info %} -Once you send SendGrid a request with a scheduling parameter, that email request cannot be cancelled and we currently only accept time stamps no greater than 72 hours in advance. +Scheduled sends can be cancelled, if you include a batch ID with your send. For more information, check out [Cancel Scheduled Sends]({{root_url}}/API_Reference/Web_API_v3/cancel_schedule_send.html)! {% endinfo %} {% warning %} From 8e0f7913524902f10a7412386cf07e75c51b2b4b Mon Sep 17 00:00:00 2001 From: Nando Sousa Date: Mon, 9 Nov 2015 16:59:25 -0200 Subject: [PATCH 09/30] Removes duplicated fields in Get example --- source/API_Reference/Web_API_v3/IP_Management/ip_addresses.md | 1 - 1 file changed, 1 deletion(-) diff --git a/source/API_Reference/Web_API_v3/IP_Management/ip_addresses.md b/source/API_Reference/Web_API_v3/IP_Management/ip_addresses.md index 9970472772..1f5eb1a50c 100644 --- a/source/API_Reference/Web_API_v3/IP_Management/ip_addresses.md +++ b/source/API_Reference/Web_API_v3/IP_Management/ip_addresses.md @@ -50,7 +50,6 @@ HTTP/1.1 200 OK [ { "ip":"000.00.00.0", - "pools":["new_test5"], "warmup":true, "start_date":1409616000, "subusers": ["username1", "username2"], From acf0aca01bbff66684c1fe52d55cf560d142407f Mon Sep 17 00:00:00 2001 From: Eric Schallock Date: Mon, 9 Nov 2015 12:03:39 -0700 Subject: [PATCH 10/30] Edited Autoresponder Glossary entry --- source/Glossary/Autoresponder | 11 ----------- source/Glossary/autoresponder.md | 23 +++++++++++++++++++++++ 2 files changed, 23 insertions(+), 11 deletions(-) delete mode 100644 source/Glossary/Autoresponder create mode 100644 source/Glossary/autoresponder.md diff --git a/source/Glossary/Autoresponder b/source/Glossary/Autoresponder deleted file mode 100644 index 596d9889df..0000000000 --- a/source/Glossary/Autoresponder +++ /dev/null @@ -1,11 +0,0 @@ -An autoresponder is a computer program that automatically answers e-mail sent to it. They can be very simple or quite complex. The first autoresponders were created within mail transfer agents that found they could not deliver an e-mail to a given address. These create bounce messages such as "your e-mail could not be delivered because..." type responses. Today's autoresponders need to be careful to not generate e-mail backscatter, which can result in the auto-responses being considered E-mail spam. - -Autoresponders are often used as e-mail marketing tools, to immediately provide information to their prospective customers and then follow-up with them at preset time intervals. Such follow-up autoresponders can be divided into two categories: - -Outsourced ASP model — these autoresponders operate on the provider's infrastructure and are usually configurable via a web-based control panel. The customer pays a monthly usage fee. This is easiest to implement for the end-user. - -Server-side — enables users to install the autoresponder system on their own server. This requires technical skills. - -Autoresponders are also incorporated into electronic mailing list software, to confirm subscriptions, unsubscriptions, posts, and other list activities. - -Read more here diff --git a/source/Glossary/autoresponder.md b/source/Glossary/autoresponder.md new file mode 100644 index 0000000000..15c0896573 --- /dev/null +++ b/source/Glossary/autoresponder.md @@ -0,0 +1,23 @@ +--- +seo: + title: Autoresponder + description: Autoresponders generate email responses to actions and events. + keywords: automated email +title: Autoresponder +weight: 0 +layout: page +navigation: + show: true +--- + +An autoresponder is a computer program that generates a response to an email, request, or action. Autoresponders were initially used to notify a sender of an undeliverable email, but now they are often used in email marketing. Autoresponders can give you the ability to send a customer a pre-written email when a specified event takes place, such as a customer creating an account or purchasing a product. + +- Autoresponders can be outsourced to an **Application Service Provider** that provides the infrastructure and support for the autoresponder. + +- Autoresponders can also be **installed server-side**, giving you complete control while requiring you to provide the infrastructure and technical skill to maintain the autoresponder. + +{% info %} +You can set up an autoresponder with SendGrid, by utilizing the [Inbound Parse Webhook]({{root_url}}/API_Reference/Webhooks/parse.html) and the [Mail Send endpoint]({{root_url}}/API_Reference/Web_API/mail.html). +{% endinfo %} + +More information about autoresponders can be found [here](https://en.wikipedia.org/wiki/Autoresponder). From 51c096387c1dfbed096ff993d60f5306ec205a6f Mon Sep 17 00:00:00 2001 From: Eric Schallock Date: Mon, 9 Nov 2015 12:57:59 -0700 Subject: [PATCH 11/30] copy edits and renamed CAN-SPAM to can_spam.md --- source/Glossary/{CAN-SPAM => can_spam.md} | 4 ++++ 1 file changed, 4 insertions(+) rename source/Glossary/{CAN-SPAM => can_spam.md} (75%) diff --git a/source/Glossary/CAN-SPAM b/source/Glossary/can_spam.md similarity index 75% rename from source/Glossary/CAN-SPAM rename to source/Glossary/can_spam.md index 6fd0de4735..ad07368328 100644 --- a/source/Glossary/CAN-SPAM +++ b/source/Glossary/can_spam.md @@ -19,6 +19,10 @@ The [CAN-SPAM Act of 2003](https://www.ftc.gov/tips-advice/business-center/guida This is by no means a complete description of CAN-SPAM, please visit the [CAN-SPAM Act Compliance Guide](https://www.ftc.gov/tips-advice/business-center/guidance/can-spam-act-compliance-guide-business) for more information. +{% info %} +The guidelines laid out in CAN-SPAM represent the “bare-minimum” regarding sending practices. Following these guidelines does not guarantee delivery to your recipients’ inboxes: CAN-SPAM leaves a considerable amount of room for improvement. Please visit [SendGrid Deliverability Tips and Tricks]({{root_url}}/Classroom/Deliver/index.html) for a more detailed discussion of how you can improve your sending practices. +{% endinfo %} + {% warning %} CAN-SPAM is not limited to bulk email. Any commercial email communication, including business-to-business and business-to-customer email, is covered by the CAN-SPAM Act. {% endwarning %} From f2585156b58780650f7a2ff49a2654a6055c84d7 Mon Sep 17 00:00:00 2001 From: Eric Schallock Date: Mon, 9 Nov 2015 14:20:55 -0700 Subject: [PATCH 12/30] Copy edited and renamed Bayesian Filtering Glossary entry --- source/Glossary/Bayesian Filter | 7 ------- source/Glossary/bayesian_filter.md | 23 +++++++++++++++++++++++ 2 files changed, 23 insertions(+), 7 deletions(-) delete mode 100644 source/Glossary/Bayesian Filter create mode 100644 source/Glossary/bayesian_filter.md diff --git a/source/Glossary/Bayesian Filter b/source/Glossary/Bayesian Filter deleted file mode 100644 index 3896cfb580..0000000000 --- a/source/Glossary/Bayesian Filter +++ /dev/null @@ -1,7 +0,0 @@ -Naive Bayes classifiers are a popular statistical technique of e-mail filtering. They typically use bag of words features to identify spam e-mail, an approach commonly used in text classification. - -Naive Bayes classifiers work by correlating the use of tokens (typically words, or sometimes other things), with spam and non-spam e-mails and then using Bayesian inference to calculate a probability that an email is or is not spam. - -Naive Bayes spam filtering is a baseline technique for dealing with spam that can tailor itself to the email needs of individual users and give low false positive spam detection rates that are generally acceptable to users. It is one of the oldest ways of doing spam filtering, with roots in the 1990s. - -Learn more here diff --git a/source/Glossary/bayesian_filter.md b/source/Glossary/bayesian_filter.md new file mode 100644 index 0000000000..d87e4d9c28 --- /dev/null +++ b/source/Glossary/bayesian_filter.md @@ -0,0 +1,23 @@ +--- +seo: + title: Bayesian Filter + description: Bayesian Filtering is a technique for detecting spam. + keywords: Bayesian Filter, spam +title: Bayesian Filter +weight: 0 +layout: page +navigation: + show: true +--- + +This is a statistical method for determining the probability that an email is spam by looking for the use of words or phrases commonly associated with spam email. + +A Bayesian filter detects spam by comparing the words or phrases within the questionable email to a set of known words or phrases associated with spam. Bayesian filtering has a very low rate of false positives and is a tried and true method for filtering spam. + +More information about Bayesian filtering can be found [here](https://en.wikipedia.org/wiki/Naive_Bayes_spam_filtering). + +Related Articles: +- [Spam]({{root_url}}/Glossary/spam.html) +- [Spam Filter]({{root_url}}/Glossary/spam_filter.html) +- [Spam Reports]({{root_url}}/Glossary/spam_reports.html) +- [Spam Trap]({{root_url}}/Glossary/spam_traps.html) From 9fc024fefdab64b8db535491328d70db9928f823 Mon Sep 17 00:00:00 2001 From: Eric Schallock Date: Mon, 9 Nov 2015 15:01:22 -0700 Subject: [PATCH 13/30] fixed bulleted list --- source/Glossary/bayesian_filter.md | 1 + 1 file changed, 1 insertion(+) diff --git a/source/Glossary/bayesian_filter.md b/source/Glossary/bayesian_filter.md index d87e4d9c28..d10a8ee4da 100644 --- a/source/Glossary/bayesian_filter.md +++ b/source/Glossary/bayesian_filter.md @@ -17,6 +17,7 @@ A Bayesian filter detects spam by comparing the words or phrases within the ques More information about Bayesian filtering can be found [here](https://en.wikipedia.org/wiki/Naive_Bayes_spam_filtering). Related Articles: + - [Spam]({{root_url}}/Glossary/spam.html) - [Spam Filter]({{root_url}}/Glossary/spam_filter.html) - [Spam Reports]({{root_url}}/Glossary/spam_reports.html) From e6a5de5006dee6ef03334e8a0c077852a37605b5 Mon Sep 17 00:00:00 2001 From: Eric Schallock Date: Mon, 9 Nov 2015 15:02:11 -0700 Subject: [PATCH 14/30] fixed bulleted list --- source/Glossary/can_spam.md | 1 + 1 file changed, 1 insertion(+) diff --git a/source/Glossary/can_spam.md b/source/Glossary/can_spam.md index ad07368328..bd4c6fd684 100644 --- a/source/Glossary/can_spam.md +++ b/source/Glossary/can_spam.md @@ -28,4 +28,5 @@ CAN-SPAM is not limited to bulk email. Any commercial email communication, inclu {% endwarning %} Related Articles: + - [SendGrid Deliverability Tips and Tricks]({{root_url}}/Classroom/Deliver/index.html) From 261fbd6e8e7e0c6ed9bed47f525e7e5a33157377 Mon Sep 17 00:00:00 2001 From: Eric Schallock Date: Mon, 9 Nov 2015 15:35:19 -0700 Subject: [PATCH 15/30] Edited Opt-In Email Glossary entry --- source/Glossary/ Confirmed_Opt_In | 7 ------- source/Glossary/opt_in_email.md | 29 +++++++++++++++++++++++++++++ 2 files changed, 29 insertions(+), 7 deletions(-) delete mode 100644 source/Glossary/ Confirmed_Opt_In create mode 100644 source/Glossary/opt_in_email.md diff --git a/source/Glossary/ Confirmed_Opt_In b/source/Glossary/ Confirmed_Opt_In deleted file mode 100644 index ced6242a3b..0000000000 --- a/source/Glossary/ Confirmed_Opt_In +++ /dev/null @@ -1,7 +0,0 @@ -Opt-in email is a term used when someone is given the option to receive "bulk" email, that is, email that is sent to many people at the same time. Typically, this is some sort of mailing list, newsletter, or advertising. Without obtaining permission before sending email, the email is unsolicited bulk email, better known as spam. - -Making sure your users have the opportunity to give their preference can help you increase your sender reputation and stay out of the spam box. - -The term Opt-out refers to several methods by which individuals can avoid receiving unsolicited product or service information. This ability is usually associated with direct marketing campaigns such as telemarketing, e-mail marketing, or direct mail. - -What is Confirmed Opt-In? The Confirmed Opt-In sending practice requires you to send confirmation emails to every registrant asking them to click to confirm their interest in receiving your emails. Conversely, a Single Opt-In is if you accept email addresses at the time of registration and then begin emailing them normally. diff --git a/source/Glossary/opt_in_email.md b/source/Glossary/opt_in_email.md new file mode 100644 index 0000000000..1d8aeb770a --- /dev/null +++ b/source/Glossary/opt_in_email.md @@ -0,0 +1,29 @@ +--- +seo: + title: Opt-In Email + description: Obtaining permission to send recipients email. + keywords: opt-in, opt-out, bulk email, CAN-SPAM +title: Opt-In Email +weight: 0 +layout: page +navigation: + show: true +--- + +**Opt-in email** refers to bulk email, such as a newsletter or advertisement, that is sent out to a mailing list where every member of that list has actively given you permission to send them email. Without obtaining this permission, your email is likely unwanted or unsolicited, and is liable to be marked as [spam]({{root_url}}/Glossary/spam.html) by the recipient or be “bulked” by the receiving mailbox provider (i.e. delivered directly to the spam folder). + +There are several variations of opt-in email: + +- **Single Opt-in** refers to the practice of requesting your recipient’s permission to send them email during, and only during, registration. + +- **Double Opt-in** refers to the practice of requesting your recipient's permission to send them email twice. For example, you could ask them if they want to receive your email at registration, and then send another email asking them to confirm their permission again. + +- **Confirmed Opt-in** refers to the practice of sending confirmation emails to your recipients asking them to confirm their continued interest in receiving your future emails. + +Giving your recipients the option to opt-in to receive your email will help to improve your [sender reputation]({{root_url}}Glossary/sender_reputation.html) and will prevent your emails from ending up in your recipients’ [spam folders]({{root_url}}/Glossary/bulk_mail_folder.html). + +Regardless of your method of obtaining a recipient's permission, it is important to give them the option of **opting-out** of receiving your future emails by including an [unsubscribe link]({{root_url}}/User_Guide/Suppressions/index.html). + +{% info %} +[CAN-SPAM]({{root_url}}/Glossary/can_spam.html) requires an opt-out option in all commercial emails, but it’s good practice to provide it in any email to your recipients. CAN-SPAM requires all senders to immediately honor an opt-out request submitted by a recipient. +{% endinfo %} From 569eded1e60fadd3ee0e5b86b3dc327b7213a9c0 Mon Sep 17 00:00:00 2001 From: Marius Rusu Date: Tue, 10 Nov 2015 09:24:13 +0000 Subject: [PATCH 16/30] Update doc for reseller customer management --- .../Web_API/Reseller_API/customer_management.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/source/API_Reference/Web_API/Reseller_API/customer_management.md b/source/API_Reference/Web_API/Reseller_API/customer_management.md index 5132e759fa..0a3b946944 100644 --- a/source/API_Reference/Web_API/Reseller_API/customer_management.md +++ b/source/API_Reference/Web_API/Reseller_API/customer_management.md @@ -95,6 +95,8 @@ Obtain a complete list of all customers. {% parameter 'phone' 'No' 'Search filter, phone number of customer' %} {% parameter 'website' 'No' 'Search filter, website of customer' %} {% parameter 'method' 'Yes' 'Must be set to *profile*' %} + {% parameter 'limit' 'No' 'Optional field to limit the number of results returned.' %} + {% parameter 'offset' 'No' 'Optional beginning point in the list to retrieve from.' %} {% endparameters %} @@ -102,6 +104,7 @@ Obtain a complete list of all customers. {% response json %} [ { + "id": "123", "username": "username", "email": "example1@example.com", "active": "true", @@ -116,6 +119,7 @@ Obtain a complete list of all customers. "website": "example.com" }, { + "id": "124", "username": "username", "email": "example2@example.com", "active": "false", @@ -134,14 +138,13 @@ Obtain a complete list of all customers. {% response xml %} + 123 user1 example1@example.com true john doe -
-555 any street -
+
555 any street
any city CA 91234 @@ -150,14 +153,13 @@ Obtain a complete list of all customers. example.com + 124 user2 example2@example.com false jane doe -
-555 any street -
+
555 any street
any city CA 91234 From cf627ded4268789b988db481d04f6f43a6b488bd Mon Sep 17 00:00:00 2001 From: Marius Rusu Date: Tue, 10 Nov 2015 11:36:11 +0000 Subject: [PATCH 17/30] fix /Glossary/sender_reputation.html link --- source/Glossary/opt_in_email.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/Glossary/opt_in_email.md b/source/Glossary/opt_in_email.md index 1d8aeb770a..a0bff4d5a8 100644 --- a/source/Glossary/opt_in_email.md +++ b/source/Glossary/opt_in_email.md @@ -20,7 +20,7 @@ There are several variations of opt-in email: - **Confirmed Opt-in** refers to the practice of sending confirmation emails to your recipients asking them to confirm their continued interest in receiving your future emails. -Giving your recipients the option to opt-in to receive your email will help to improve your [sender reputation]({{root_url}}Glossary/sender_reputation.html) and will prevent your emails from ending up in your recipients’ [spam folders]({{root_url}}/Glossary/bulk_mail_folder.html). +Giving your recipients the option to opt-in to receive your email will help to improve your [sender reputation]({{root_url}}/Glossary/sender_reputation.html) and will prevent your emails from ending up in your recipients’ [spam folders]({{root_url}}/Glossary/bulk_mail_folder.html). Regardless of your method of obtaining a recipient's permission, it is important to give them the option of **opting-out** of receiving your future emails by including an [unsubscribe link]({{root_url}}/User_Guide/Suppressions/index.html). From 39413e454ad650e9c1395a6110e92c925a233578 Mon Sep 17 00:00:00 2001 From: adulion Date: Tue, 10 Nov 2015 15:40:47 +0000 Subject: [PATCH 18/30] Update to laravel docs Adding example code for integration to sendgrid categories and custom variables for sendgrid notification tracking --- source/Integrate/Frameworks/laravel.md | 42 ++++++++++++++++++++++++++ 1 file changed, 42 insertions(+) diff --git a/source/Integrate/Frameworks/laravel.md b/source/Integrate/Frameworks/laravel.md index fd6c7a82a6..0bd2626861 100644 --- a/source/Integrate/Frameworks/laravel.md +++ b/source/Integrate/Frameworks/laravel.md @@ -41,3 +41,45 @@ Mail::send('emails.demo', $data, function($message) ?> {% endcodeblock %} + +## Adding a category or custom field + +Categories in sendgrid allow you to split your statistics into categories. An example would be if you have a white labeled service you can split your statistics by the user login. + +Another useful feature of sendgrid is the notifications. If you want to complete the feedback loop for your product you can pass identifiers as a header which relate to a record in your database which you can then parse the notifications against that record to track deliveries/opens/clicks/bounces. + + +{% codeblock lang:php %} +asString($data); + + $message->getSwiftMessage()->getHeaders()->addTextHeader('X-SMTPAPI', $header); + + $message->to('jane@example.com', 'Jane Doe')->subject('This is a demo!'); + }); + + private function asJSON($data) // set as private with the expectation of being a class method + { + $json = json_encode($data); + + $json = preg_replace('/(["\]}])([,:])(["\[{])/', '$1$2 $3', $json); + + return $json; + } + + private function asString($data) // set as private with the expectation of being a class method + { + $json = $this->asJSON($data); + $str = wordwrap($json, 76, "\n "); + + return $str; + } +?> +{% endcodeblock %} + From 667187d7d83c616fd706323b499734112fcfd2b0 Mon Sep 17 00:00:00 2001 From: Eric Schallock Date: Tue, 10 Nov 2015 08:42:37 -0700 Subject: [PATCH 19/30] fixed broken link --- source/Glossary/opt_in_email.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/Glossary/opt_in_email.md b/source/Glossary/opt_in_email.md index 1d8aeb770a..a0bff4d5a8 100644 --- a/source/Glossary/opt_in_email.md +++ b/source/Glossary/opt_in_email.md @@ -20,7 +20,7 @@ There are several variations of opt-in email: - **Confirmed Opt-in** refers to the practice of sending confirmation emails to your recipients asking them to confirm their continued interest in receiving your future emails. -Giving your recipients the option to opt-in to receive your email will help to improve your [sender reputation]({{root_url}}Glossary/sender_reputation.html) and will prevent your emails from ending up in your recipients’ [spam folders]({{root_url}}/Glossary/bulk_mail_folder.html). +Giving your recipients the option to opt-in to receive your email will help to improve your [sender reputation]({{root_url}}/Glossary/sender_reputation.html) and will prevent your emails from ending up in your recipients’ [spam folders]({{root_url}}/Glossary/bulk_mail_folder.html). Regardless of your method of obtaining a recipient's permission, it is important to give them the option of **opting-out** of receiving your future emails by including an [unsubscribe link]({{root_url}}/User_Guide/Suppressions/index.html). From 651cb14c2f5bdbf74f35cb944a9a805f51226d98 Mon Sep 17 00:00:00 2001 From: Matt Bernier Date: Tue, 10 Nov 2015 12:27:20 -0700 Subject: [PATCH 20/30] New video! --- source/User_Guide/dashboard.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/User_Guide/dashboard.md b/source/User_Guide/dashboard.md index 71959f2cdb..22513e47c8 100644 --- a/source/User_Guide/dashboard.md +++ b/source/User_Guide/dashboard.md @@ -10,6 +10,8 @@ navigation: show: true --- + + The SendGrid dashboard is designed to give you an at-a-glance view of your current email activity. You can view the stats about all of the emails you have sent through your SendGrid account. {% anchor h2 %} From 51b6e7d84a1a127b625938342962cb6ad1aacdaa Mon Sep 17 00:00:00 2001 From: Eric Schallock Date: Tue, 10 Nov 2015 14:50:09 -0700 Subject: [PATCH 21/30] Created glossary entry for Automated Email --- source/Glossary/automated_email.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 source/Glossary/automated_email.md diff --git a/source/Glossary/automated_email.md b/source/Glossary/automated_email.md new file mode 100644 index 0000000000..e069491af3 --- /dev/null +++ b/source/Glossary/automated_email.md @@ -0,0 +1,22 @@ +--- +layout: page +weight: 0 +title: Automated Email +navigation: + show: true +seo: + title: Automated Email + override: true + description: Automated Email allows you to dynamically send relevant content to individual recipients. + keywords: triggered email, automated email, Threads, behavior-driven email +--- + +Automated email, also known as [triggered email]({{root_url}}/Glossary/triggered_email.html) or behavior-driven email, refers to any email that is programed to be delivered as a response to a specified [event]({{root_url}}/Glossary/triggering_event.html) or action. While traditional [marketing email]({{root_url}}/Glossary/Email_Types/index.html) involves sending a general promotional message to a large list of recipients, automated email allows you to dynamically send targeted, promotional content that is uniquely relevant to an individual recipient. + +Examples of automated email include a welcome series [drip campaign]({{root_url}}/Glossary/drip_campaign.html) that is initiated by a new user sign-up or targeted advertisements based on an individual user’s purchase history. + +The ability to send very relevant, timely emails directed to individual recipients makes automated email a uniquely powerful tool for building and nurturing customer relationships, enhancing the image of your brand, and increasing customer engagement. + +{% info %} +[Threads](http://threads.io/) is SendGrid’s behavior-driven, automated email solution that allows you to dynamically send email based on user engagement. Visit the [Threads Support Page](https://support.threads.io/hc/en-us) to learn more about how you can integrate Threads with your SendGrid account. +{% endinfo %} From 25044e3e9b74bb0bbf97809a7d9f159fc03836d0 Mon Sep 17 00:00:00 2001 From: Eric Schallock Date: Tue, 10 Nov 2015 15:05:14 -0700 Subject: [PATCH 22/30] Created glossary entry for Triggered Email --- source/Glossary/triggered_email.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 source/Glossary/triggered_email.md diff --git a/source/Glossary/triggered_email.md b/source/Glossary/triggered_email.md new file mode 100644 index 0000000000..4c23cde877 --- /dev/null +++ b/source/Glossary/triggered_email.md @@ -0,0 +1,19 @@ +--- +seo: + title: Triggered Email + description: Triggered emails are emails that are triggered by specific events or actions. + keywords: automated email, triggered email, Threads, triggering event, event +title: Triggered Email +weight: 0 +layout: page +navigation: + show: true +--- + +Triggered email is a form of [automated email]({{root_url}}/Glossary/automated_email.html) that is sent only when a specific [triggering event]({{root_url}}/Glossary/triggering_event.html) occurs or a specific user takes a certain action that prompts the delivery of the email. Triggered emails must be set up in advance: you have to specify which event will trigger the delivery of the email. + +In the case of SendGrid’s automated and behavior driven email platform, [Threads](http://threads.io/), this is accomplished by tracking individual users and the actions that they may take when interacting with your application or website. + +{% info %} +Please visit the [Threads Support Page](https://support.threads.io/hc/en-us) for more information about how you can send triggered email through your SendGrid account. +{% endinfo %} From a50512cc195ab9aac529df8dc3feee3625df7057 Mon Sep 17 00:00:00 2001 From: Eric Schallock Date: Tue, 10 Nov 2015 15:13:14 -0700 Subject: [PATCH 23/30] Created glossary entry for Triggering Events --- source/Glossary/triggering_events.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 source/Glossary/triggering_events.md diff --git a/source/Glossary/triggering_events.md b/source/Glossary/triggering_events.md new file mode 100644 index 0000000000..8cac14074c --- /dev/null +++ b/source/Glossary/triggering_events.md @@ -0,0 +1,21 @@ +--- +seo: + title: Triggering Events + description: Triggering events are the events or actions which prompt the delivery of an automated email. + keywords: automated email, triggered email, Threads, triggering event, event +title: Triggering Events +weight: 0 +layout: page +navigation: + show: true +--- + +Not to be confused with the post-send email events like [clicks]({{root_url}}/Glossary/clicks.html), [drops]({{root_url}}/Glossary/drops.html), or [bounces]({{root_url}}/Glossary/bounces.html) that SendGrid tracks: in terms of [automated email]({{root_url}}/Glossary/automated_email.html), **triggering events** are events that you specify based on the ways that your users interact with your website or application. These events can be tracked and used to prompt a [triggered action]({{root_url}}/Glossary/triggered_action.html), such as the delivery of an email. + +Viewing a webpage, using a feature, clicking a button, or buying a product are all examples of events that can be used to determine when an email should be sent and what the content of that email should be. + +Events that are tracked through [Threads](http://threads.io/) may also have properties that can tell you more about what happened: the address of the webpage that your user visited, the exact button that they clicked, or the SKU (stock keeping unit) of the product they purchased. + +{% info %} +More information about how events can be tracked in [Threads](http://threads.io/) can be found [here](https://support.threads.io/hc/en-us). +{% endinfo %} From 34e3844cf7d022c07589eab060254758f803173a Mon Sep 17 00:00:00 2001 From: Eric Schallock Date: Tue, 10 Nov 2015 15:19:31 -0700 Subject: [PATCH 24/30] Created glossary entry for Triggered Actions --- source/Glossary/triggered_actions.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 source/Glossary/triggered_actions.md diff --git a/source/Glossary/triggered_actions.md b/source/Glossary/triggered_actions.md new file mode 100644 index 0000000000..ede433acf9 --- /dev/null +++ b/source/Glossary/triggered_actions.md @@ -0,0 +1,19 @@ +--- +seo: + title: Triggered Actions + description: Triggered Actions are initiated by a triggering event. + keywords: automated email, triggered actions, triggering events, Threads +title: Triggered Actions +weight: 0 +layout: page +navigation: + show: true +--- + +Triggered actions are automatically completed when a specific [triggering event]({{root_url}}/Glossary/triggering_events.html) that you are tracking takes place. These actions must be defined in advance, and they must be associated with a predetermined user and event. + +SendGrid’s automated email platform, [Threads](http://threads.io/), makes it possible for you to take several different actions depending on the ways in which a specified user interacts with your website or application. An example of a triggered action might be a purchase confirmation or receipt. + +{% info %} +To learn more about the different actions that Threads makes possible, please visit our [Threads FAQ](https://support.threads.io/hc/en-us/articles/206049497-What-types-of-Workflow-Actions-are-supported-). +{% endinfo %} From 24abf523efa21a1d0b04d80a4595fa4c3c04f716 Mon Sep 17 00:00:00 2001 From: Eric Schallock Date: Tue, 10 Nov 2015 15:21:49 -0700 Subject: [PATCH 25/30] Update triggered_email.md --- source/Glossary/triggered_email.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/Glossary/triggered_email.md b/source/Glossary/triggered_email.md index 4c23cde877..57fea94646 100644 --- a/source/Glossary/triggered_email.md +++ b/source/Glossary/triggered_email.md @@ -10,7 +10,7 @@ navigation: show: true --- -Triggered email is a form of [automated email]({{root_url}}/Glossary/automated_email.html) that is sent only when a specific [triggering event]({{root_url}}/Glossary/triggering_event.html) occurs or a specific user takes a certain action that prompts the delivery of the email. Triggered emails must be set up in advance: you have to specify which event will trigger the delivery of the email. +Triggered email is a form of [automated email]({{root_url}}/Glossary/automated_email.html) that is sent only when a specific [triggering event]({{root_url}}/Glossary/triggering_events.html) occurs or a specific user takes a certain action that prompts the delivery of the email. Triggered emails must be set up in advance: you have to specify which event will trigger the delivery of the email. In the case of SendGrid’s automated and behavior driven email platform, [Threads](http://threads.io/), this is accomplished by tracking individual users and the actions that they may take when interacting with your application or website. From 7e2018d60db1731d03ef297bb78e72632ab7a354 Mon Sep 17 00:00:00 2001 From: Eric Schallock Date: Tue, 10 Nov 2015 15:23:06 -0700 Subject: [PATCH 26/30] Update automated_email.md --- source/Glossary/automated_email.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/Glossary/automated_email.md b/source/Glossary/automated_email.md index e069491af3..508349801a 100644 --- a/source/Glossary/automated_email.md +++ b/source/Glossary/automated_email.md @@ -11,7 +11,7 @@ seo: keywords: triggered email, automated email, Threads, behavior-driven email --- -Automated email, also known as [triggered email]({{root_url}}/Glossary/triggered_email.html) or behavior-driven email, refers to any email that is programed to be delivered as a response to a specified [event]({{root_url}}/Glossary/triggering_event.html) or action. While traditional [marketing email]({{root_url}}/Glossary/Email_Types/index.html) involves sending a general promotional message to a large list of recipients, automated email allows you to dynamically send targeted, promotional content that is uniquely relevant to an individual recipient. +Automated email, also known as [triggered email]({{root_url}}/Glossary/triggered_email.html) or behavior-driven email, refers to any email that is programed to be delivered as a response to a specified [event]({{root_url}}/Glossary/triggering_events.html) or action. While traditional [marketing email]({{root_url}}/Glossary/Email_Types/index.html) involves sending a general promotional message to a large list of recipients, automated email allows you to dynamically send targeted, promotional content that is uniquely relevant to an individual recipient. Examples of automated email include a welcome series [drip campaign]({{root_url}}/Glossary/drip_campaign.html) that is initiated by a new user sign-up or targeted advertisements based on an individual user’s purchase history. From 72e3e83f0223887cfe1889f2482a7b9c78d68da5 Mon Sep 17 00:00:00 2001 From: Eric Schallock Date: Tue, 10 Nov 2015 15:28:37 -0700 Subject: [PATCH 27/30] Update triggering_events.md --- source/Glossary/triggering_events.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/Glossary/triggering_events.md b/source/Glossary/triggering_events.md index 8cac14074c..4b09f3c8c5 100644 --- a/source/Glossary/triggering_events.md +++ b/source/Glossary/triggering_events.md @@ -10,7 +10,7 @@ navigation: show: true --- -Not to be confused with the post-send email events like [clicks]({{root_url}}/Glossary/clicks.html), [drops]({{root_url}}/Glossary/drops.html), or [bounces]({{root_url}}/Glossary/bounces.html) that SendGrid tracks: in terms of [automated email]({{root_url}}/Glossary/automated_email.html), **triggering events** are events that you specify based on the ways that your users interact with your website or application. These events can be tracked and used to prompt a [triggered action]({{root_url}}/Glossary/triggered_action.html), such as the delivery of an email. +Not to be confused with the post-send email events like [clicks]({{root_url}}/Glossary/clicks.html), [drops]({{root_url}}/Glossary/drops.html), or [bounces]({{root_url}}/Glossary/bounces.html) that SendGrid tracks: in terms of [automated email]({{root_url}}/Glossary/automated_email.html), **triggering events** are events that you specify based on the ways that your users interact with your website or application. These events can be tracked and used to prompt a [triggered action]({{root_url}}/Glossary/triggered_actions.html), such as the delivery of an email. Viewing a webpage, using a feature, clicking a button, or buying a product are all examples of events that can be used to determine when an email should be sent and what the content of that email should be. From d09221a3d1f6fd452a3a5f6647d4fbc8faf3ac27 Mon Sep 17 00:00:00 2001 From: mbernier Date: Tue, 10 Nov 2015 16:16:57 -0700 Subject: [PATCH 28/30] forcing a change --- source/Glossary/triggered_email.md | 1 + 1 file changed, 1 insertion(+) diff --git a/source/Glossary/triggered_email.md b/source/Glossary/triggered_email.md index 57fea94646..8302ac0c42 100644 --- a/source/Glossary/triggered_email.md +++ b/source/Glossary/triggered_email.md @@ -14,6 +14,7 @@ Triggered email is a form of [automated email]({{root_url}}/Glossary/automated_e In the case of SendGrid’s automated and behavior driven email platform, [Threads](http://threads.io/), this is accomplished by tracking individual users and the actions that they may take when interacting with your application or website. + {% info %} Please visit the [Threads Support Page](https://support.threads.io/hc/en-us) for more information about how you can send triggered email through your SendGrid account. {% endinfo %} From 6aa1f0a0fcde19a02f366aa9a365c0df871e0932 Mon Sep 17 00:00:00 2001 From: Eric Schallock Date: Tue, 10 Nov 2015 16:44:59 -0700 Subject: [PATCH 29/30] Edited as per Molly's suggestions --- source/Glossary/automated_email.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/source/Glossary/automated_email.md b/source/Glossary/automated_email.md index 508349801a..e2fcb7eb57 100644 --- a/source/Glossary/automated_email.md +++ b/source/Glossary/automated_email.md @@ -11,12 +11,14 @@ seo: keywords: triggered email, automated email, Threads, behavior-driven email --- -Automated email, also known as [triggered email]({{root_url}}/Glossary/triggered_email.html) or behavior-driven email, refers to any email that is programed to be delivered as a response to a specified [event]({{root_url}}/Glossary/triggering_events.html) or action. While traditional [marketing email]({{root_url}}/Glossary/Email_Types/index.html) involves sending a general promotional message to a large list of recipients, automated email allows you to dynamically send targeted, promotional content that is uniquely relevant to an individual recipient. +Automated email, also known as [triggered email]({{root_url}}/Glossary/triggered_email.html) or behavior-driven email, is sent when a specific [triggering event]({{root_url}}/Glossary/triggering_events.html) occurs or a specific user takes an action that prompts the delivery of the email. While traditional [marketing email]({{root_url}}/Glossary/Email_Types/index.html) involves sender-initiated promotional messages sent to a list of recipients, automated email is initiated by user behavior, allowing you to dynamically send targeted, real-time promotional content that is uniquely relevant to an individual recipient. -Examples of automated email include a welcome series [drip campaign]({{root_url}}/Glossary/drip_campaign.html) that is initiated by a new user sign-up or targeted advertisements based on an individual user’s purchase history. +Examples of automated email include a welcome series [drip campaign]({{root_url}}/Glossary/drip_campaign.html) that is initiated by a new user sign-up or a win-back campaign to re-engage a lapsed user. The ability to send very relevant, timely emails directed to individual recipients makes automated email a uniquely powerful tool for building and nurturing customer relationships, enhancing the image of your brand, and increasing customer engagement. +You can use SendGrid’s automated, behavior driven email platform, [Threads](http://threads.io/), to track individual users and the actions that they take when interacting with your application or website. This information can then be used to dynamically create and send automated email. + {% info %} -[Threads](http://threads.io/) is SendGrid’s behavior-driven, automated email solution that allows you to dynamically send email based on user engagement. Visit the [Threads Support Page](https://support.threads.io/hc/en-us) to learn more about how you can integrate Threads with your SendGrid account. +Visit the [Threads Support Page](https://support.threads.io/hc/en-us) to learn more about how you can integrate Threads with your SendGrid account. {% endinfo %} From dfe198cb69b488a23f4739709d6e874ead8f479f Mon Sep 17 00:00:00 2001 From: Eric Schallock Date: Tue, 10 Nov 2015 16:49:57 -0700 Subject: [PATCH 30/30] Removed content and linked to Automated Email page --- source/Glossary/triggered_email.md | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/source/Glossary/triggered_email.md b/source/Glossary/triggered_email.md index 8302ac0c42..889e5ef445 100644 --- a/source/Glossary/triggered_email.md +++ b/source/Glossary/triggered_email.md @@ -1,7 +1,7 @@ --- seo: title: Triggered Email - description: Triggered emails are emails that are triggered by specific events or actions. + description: Triggered emails are another name for automated emails that are triggered by specific events or actions. keywords: automated email, triggered email, Threads, triggering event, event title: Triggered Email weight: 0 @@ -10,11 +10,6 @@ navigation: show: true --- -Triggered email is a form of [automated email]({{root_url}}/Glossary/automated_email.html) that is sent only when a specific [triggering event]({{root_url}}/Glossary/triggering_events.html) occurs or a specific user takes a certain action that prompts the delivery of the email. Triggered emails must be set up in advance: you have to specify which event will trigger the delivery of the email. - -In the case of SendGrid’s automated and behavior driven email platform, [Threads](http://threads.io/), this is accomplished by tracking individual users and the actions that they may take when interacting with your application or website. - - {% info %} -Please visit the [Threads Support Page](https://support.threads.io/hc/en-us) for more information about how you can send triggered email through your SendGrid account. +Triggered email is another term for [automated email]({{root_url}}/Glossary/automated_email.html). {% endinfo %}