ESP Information & Merge Tags

An Email Service Provider (ESP) is a platform that helps businesses send, manage, and track email campaigns. Each ESP has a different methodology for organizing your email campaigns, including how subscriber-specific information is stored and utilized. This information is sent back to RevContent to allow us to honor campaign targeting and IVT tools and best practices. 

ESP Integrations
RevContent is happy to share that we are fully integrated with the following ESPs, resulting in a quick and seamless integration. 

Beehiiv
Bigmailer.io
Campaigner
Clevertap
Constant Contact
Deployer
Earnware
Green Arrow
Inbox Genie
Iterable
MailChimp
Maildomo
MailerLite
Mailjet
Mailwizz
Ongage
PostUp
Robly
SalesForce
SailThru
Second Street
Tiny Email

Don’t see your ESP on this list? Have no fear - our team is happy to help you research and discover the appropriate merge tags that belong to your ESP, which we are able to manually insert into your ad codes. 

Merge Tags
As mentioned above, RevContent requires you to send us some subscriber-specific information from your ESP. ESPs do this using what’s called a merge tag, a placeholder in your email template that dynamically pulls in personalized information for each recipient. When the email is sent, the merge tag is replaced with real data - like the subscriber’s name, email address or a unique trackingID - and then sent back to RevContent, allowing our technology to determine unique vs. non-unique subscriber interactions. Every ESP has their own set of merge tags. 

In our ad codes, we’ve included some merge tag placeholders that indicate the type of data we want to receive:

{UNIQUEKEY} 
*Required*
A value that is unique to every subscriber AND send. This can be any combination of data points based on your ESPs capabilities.

{SENDID}
*Optional but preferred*
A value that is unique to every send - think of it similar to campaignID. 

{DATETIME}
*Optional but preferred*
The timestamp of every send. 

{EMAIL}, {MD5EMAIL}, {SHA1EMAIL}, {SHA256EMAIL}
*Required - See Note*
RevContent requires at least one version of the user’s email - plain text, MD5, SHA1 or SHA256 - to be included in the ad code and sent back to us. This is what allows us to serve ads affectively while also honoring the IVT tools and practices we have in place. 

Please note that privacy is at the forefront of what we do - there is no personally identifiable information visible to our team and is strictly used in our backend to honor campaign targeting. 

{ESP}
*Optional but preferred*
The name or shortened version of the name of the ESP you’re utilizing.