Freshpaint Help Center
What is Freshpaint?
Web Quickstart Guide
React Native Quickstart Guide
iOS Quickstart Guide
Android Quickstart Guide
Building Out Your Account
Overview of Features
Event Schema Dashboard
Projects & Environments
Frequently Asked Questions
How Do I Switchover From Segment?
Where do I find my Environment ID?
Is Freshpaint GDPR & CCPA Compliant?
Can I use transformations to anonymize data for client-side destinations?
How do I QA or debug my data?
Why Do My Numbers Differ Across Different Tools?
Billing: How Does Freshpaint Determine MTUs?
Can I Use Freshpaint on Multiple Sites?
How Can I Export Data From Freshpaint?
How Does Freshpaint Identify Users?
How Many Events Should I Create?
What Should I Name My Events?
How do I track scroll depth?
What Data Does Freshpaint Collect?
Does Freshpaint's Autotrack slow my site down?
Running Freshpaint with a Proxy
Should my Environment ID be treated as a sensitive key?
How Does Freshpaint Determine Session Count?
What is the difference between client-side and server-side connection mode?
Freshpaint Web SDK Reference
Freshpaint React Native SDK Reference
Freshpaint iOS SDK Reference
Freshpaint Android SDK Reference
The Mailchimp source allows you to send email events to Freshpaint, and send those events to your destinations.
to track email deliveries, opens, and more. You'll need to set up this webhook in Mailchimp with the following steps:
Add a Webhook
at the top of the page
Choose the events you want to listen for in the “Trigger on Events” section.
In the “Post To URL” field, input the url you can find on
page. It will follow the format
Freshpaint supports tracking the following events for the Mailchimp source:
The following properties are attached (when available) to the properties:
The "Email: send"
The recipient's email
The mailchimp internal id of the message
The sender's email
The state of the message (sent, rejected, spam, unsub, bounced, or soft-bounced)
The subaccount from which the message originated; if no subaccount was used, the value will be null
The subject line of the message
The URL clicked (if the event is a click event)
For bounced and soft-bounced messages, provides the specific SMTP response code and bounce description, if any, received from the remote server
For bounced and soft-bounced messages, a short description of the bounce reason, such as bad_mailbox or invalid_domain
The slug of the template used, if any. If no template was used, the value will be null
An array of the metadata key–value pairs that were applied to the message, if any
A list of tags attached to the message
A list of click objects (see below)
A list of open objects (see below)
Opens & Clicks:
For open and click events only, a parsed version of the user agent detected for the event. The following properties will be attached if a UA was captured:
Whether the user agent is a mobile agent
The operating system company
URL of the operating system company
The operating system family (i.e., Linux, Mac, or Windows)
URL for an icon for the operating system
The name of the operating system used for the event
URL for the operating system
The type of user agent (e.g., "browser", "email client", "robot"); these may be updated, so string values may be added
Company for the user agent (specifically the browser or email client)
URL for the user agent company
Family for the user agent (e.g., Firefox, Chrome, Safari)
URL for an icon for the user agent
Name of the user agent
URL for the user agent
Version of the user agent
For open and click events only, a parsed location based on the IP may be detected for the event. The following properties will be attached if a location was captured:
The abbreviated country name
The full country name
The latitude of the user
The longitude of the user
The timestamp of the click
The url that was clicked
The timestamp the email was opened
The IP address where the open occurred
The approximate geolocation of the IP where the open occurred
Opens & Clicks: