Integrate other first-party or third-party data

Import other service's data or in-house data to Optimize.

You can integrate a variety of external and internal data sources with Optimize — even if we don’t provide a dedicated setup guide. This includes company reveal tools (e.g., KickFire), CRMs (e.g., Zoho CRM), marketing automation platforms (e.g., Pardot), and first-party data (e.g., login cookies or browser variables). As long as the data is available in JavaScript when the Optimize snippet runs, you can use it to define audiences, target variations, or analyze performance by segment.

Integration options

Option 1 — Use the setAttributes() API

Your developers can use the setAttributes() API to pass custom data to Optimize. Once the attributes are sent, you can configure Optimize to use them for targeting and reporting.

• Review the setAttributes() API doc
• Learn how to add custom attributes to Optimize

Option 2 — We’ll help configure it

Review the sections below to understand what information we’ll need from you. Then, submit a support request to let us know which data source you want to connect.

Where is the data stored?

External services typically retrieve data from their databases and store it client-side for usage. For Optimize to access it, the data needs to be available via JavaScript.

Common storage methods include:

• LocalStorage (preferred)
• Global JavaScript variable

If your current setup isn’t accessible via JavaScript, we may ask you to restructure how the data is exposed.

What format are values returned in?

Let us know how your data is structured and what values it returns. Optimize needs this to identify and use the right values at the right time.

Example: A company reveal tool might return:

{
  "company": {
    "employee_range": "10,000+",
    "industry": "Pharmaceuticals",
    "revenue_range": "$5B+",
    "domain": "companywebsite.com",
    "name": "My Company Name"
  }
}

Please provide the following:

• The format your data is in
• Which values you want to use
• Whether the structure or values change depending on the page or use case
• Example data (if possible)
• Vendor documentation (if available)
• If in-house, we’ll work with you to define the values
• Fields to reference (e.g., employee_range, revenue_range)
• Clarify what those fields represent if it’s not obvious

How do you categorize visitors?

If you plan to group visitors based on this data, we’ll need to know your criteria.

Example: You segment company size into:

• Small Business: employee_range = 10–2,000
• Mid-Market: employee_range = 2,001–5,000
• Enterprise: employee_range = 5,001–10,000+

Let us know which fields to use and how to map returned values to your defined categories.

Do you have a method to test the data?

If you have a way to simulate different visitor groups — such as spoofing cookies or query parameters — please share your method. This helps us confirm that each variation displays correctly during setup and testing.

Plan for fallback behavior

If the custom data isn’t available or fails to load, make sure your variations still deliver value. You might want to create a default version of each variation to serve visitors who don’t match your defined segments.