CRM Integrations

Key Capabilities

The integration supports three things:

• Targeting and 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 through Subscription and Offer+ campaigns 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

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

Kodo 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

To send leads to Beehiiv, we need:

• The publication ID
• A secure API key

Braze

To send leads to Braze, we need:

• The Braze host
• A secure API key

Customer.io

To send leads to Customer.io, we need:

• The Site ID
• A secure API key

Emarsys

To send leads to Emarsys, we need:

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

HubSpot

To send leads to HubSpot, we need:

• A secure API key

Iterable

To send leads to Iterable, we need:

• A secure API key: a server-side Iterable API key, sent in the Api-Key header
• A list ID: the numeric ID of the target Iterable list to subscribe contacts to

Klaviyo

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

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

To send leads to Marigold Sailthru, we need:

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

Salesforce

To send leads to Salesforce, we need:

• A client ID: an Installed Packages client ID
• A secure client secret: an Installed Packages client secret
• An account ID: the Salesforce Marketing Cloud tenant/account ID
• A subdomain: the auth/REST host prefix (region-specific)
• An external key: the target Data Extension's external key