CRM integrations

Key Capabilities Our integration architecture supports three primary strategic functions:

• Targeting & Suppression: When a publisher provides email data, we cross-reference your existing database to ensure your ads are prioritized for new users, optimizing your acquisition spend and preventing redundant reach.
• Automated Lead Injection: Emails captured via Thanks Subscribe or Offers Plus are pushed directly into your CRM in real-time. This allows you to immediately trigger welcome campaigns or add new leads to specific mailing lists without manual data exports.
• 7-Day Conversion Verification: To ensure lead quality, we verify subscription status at the time of initial engagement and again 7 days later. This ensures you only pay for persistent, high-value leads that remain in your ecosystem.

Integrations

Custom CRM

Thanks can support any custom or internal CRM that has an available endpoint to which we can send leads. For custom integrations Thanks expects to receive a credential that authenticates and authorises Thanks to push leads into the CRM. Thanks only supports sending leads via POST or PUT requests at this time to ensure that customer data is encrypted using TLS (i.e. Thanks does not support sending leads via query parameters in a GET request for example).

Thanks cannot guarantee that all proposed functionality will work for a custom CRM, e.g. the 7 day conversion verification can only work if the custom CRM supports it.

Beehiiv

For Thanks to send leads to Beehiiv, we need:

• The publication ID
• A secure API key 🔒

Braze

For Thanks to send leads to Braze, we need:

• The Braze host
• A secure API key 🔒

Customer.io

For Thanks to send leads to customer.io, we need:

• The Site ID
• A secure API key 🔒

Emarsys

For Thanks to send leads to emarsys, we need:

• A username
• A secure password 🔒
• The list of field indexes that Thanks will send data to, usually "3" is the primary key and email. Further emarsys fields can be found here

Hubspot

For Thanks to send leads to Hubspot, we need:

• A secure API key🔒

Klaviyo

For Thanks to send leads to Klaviyo, we need:

• The list to send users to
• A secure private key🔒
  • Full access to
    • Profiles
    • Subscriptions
    • Lists
    • Events
  • Read only access to
    • Segments
    • Metrics

Mailchimp

For Thanks to send leads to Mailchimp, we need:

• The Mailchimp server value. Check here for instructions on how to find the server.
• A secure API key🔒

Marigold Sailthru

For Thanks to send leads to Sailthru, we need:

• The mailing list ID
• A secure API key🔒
• A secure API secret🔒

Salesforce

For Thanks to send leads to Salesforce, we need:

• A subdomain
• An external key
• A client ID
• A secure client secret 🔒