Substitution tags allow you to generate dynamic content for each recipient on your list. When you send to a list of recipients over SMTP API, you can specify substitution tags specific to each recipient. For example, a first name that will then be inserted into an opening greeting like the following, where each recipient sees -firstName- replaced with their first name.
_10"Dear -firstName-"
These tags can also be used in more complex scenarios. For example, you could use a -customerID- to build a custom URL that is specific to that user.
_10<a href="http://example.com/customerOffer?id=-customerID-">Claim your offer!</a>
Substitution tags will work in the Subject line, body of the email and in Unique Arguments.
Unique Arguments will be stored as a "Not PII" field and may be used for counting or other operations as SendGrid runs its systems. These fields generally cannot be redacted or removed. You should take care not to place PII in this field. SendGrid does not treat this data as PII, and its value may be visible to SendGrid employees, stored long-term, and may continue to be stored after you've left SendGrid's platform.
Substitutions are limited to 50,000 bytes per personalization block.
When passing substitutions please make sure to only use strings as shown in our examples. Any other type could result in unintended behavior.
How you format your substitution tags may depend on the library you use to create your SMTP connection, the language you are writing your code in, or any intermediate mail servers that your servers will send mail through. In some cases -subVal- may be the best choice while in other %subVal% or #subVal# may make more sense. It is best to avoid characters that have special meaning in HTML, such as <, >, and &. These might end up encoded and will not be properly substituted.
You can have up to 4 nested substitutions.
Do not use spaces inside your substitution tags, for example: %first name%
Do not nest substitution tags in substitutions as they will fail and your substitution will not take place.
Email HTML content:
_14<html>_14 <head></head>_14 <body>_14 <p>_14 Hello -name-,<br />_14 Thank you for your interest in our products. I have set up an appointment_14 to call you at -time- EST to discuss your needs in more detail. If you_14 would like to reschedule this call, please visit the following link: `<a_14 href="http://example.com/reschedule?id=-customerID-"_14 >reschedule</a_14 >` Regards, -salesContact- -contactPhoneNumber-<br />_14 </p>_14 </body>_14</html>
An accompanying SMTP API JSON header might look something like this:
_10{_10 "to": ["example@example.com", "example@example.com"],_10 "sub": {_10 "-name-": ["John", "Jane"],_10 "-customerID-": ["1234", "5678"],_10 "-salesContact-": ["Jared", "Ben"],_10 "-contactPhoneNumber-": ["555.555.5555", "777.777.7777"],_10 "-time-": ["3:00pm", "5:15pm"]_10 }_10}
The resulting email for John would look like this:
_13<html>_13 <head></head>_13 <body>_13 <p>_13 Hello John,<br />_13 Thank you for your interest in our products. I have set up an appointment_13 to call you at 3:00 pm EST to discuss your needs in more detail. If you_13 would like to reschedule this call, please visit the following link:_13 <a href="http://example.com/reschedule?id=1234">reschedule</a>_13 Regards, Jared 555.555.5555_13 </p>_13 </body>_13</html>
In contrast, the resulting email for Jane will look like the following, with her specific values replaced in for each tag:
_13<html>_13 <head></head>_13 <body>_13 <p>_13 Hello Jane,<br />_13 Thank you for your interest in our products. I have set up an appointment_13 to call you at 5:15pm EST to discuss your needs in more detail. If you_13 would like to reschedule this call please visit the following link:_13 <a href="http://example.com/reschedule?id=5678">reschedule</a>_13 Regards, Ben 777.777.7777_13 </p>_13 </body>_13</html>