Klaviyo

Klaviyo is an ecommerce marketing automation platform that helps deliver more personalized experiences across marketing channels like email, SMS, in-app notifications, and web. It helps businesses grow with real-time data learnings for marketing campaigns through email and SMS marketing campaign automation.

In order to integrate Klaviyo with Relyance AI you will need an API Key.

In Klaviyo:

1. Login to your Klaviyo account.
2. Click on your profile menu in the bottom left-hand corner and select Settings.
3. Click on the API Keys tab.
4. Click the Create Private API Key button.
5. This will open up a dialog. Set the following settings: Private API Key Name: Provide a meaningful name (e.g. Relyance Scan) Select Access Level:
   1. For a regular property scan, select Read-Only Key.
   2. For DSRs, select the Custom Key option, set Read Access for all API Scopes and set the profile and data-privacy scopes to Full Access.
6. Click Create.
7. This will create a new API Key. Copy the Private API Key to be used in Relyance.

In the Relyance AI application:

1. Login to your Relyance AI account.
2. Navigate to the Settings (bottom-left corner).
3. Select Integrations.
4. Search and locate the Klaviyo integration card and click on it.
5. Click on the Add Connection button on the top right.
6. Provide a meaningful name for the integration and click on the Add button.
7. In the Overview section, select the integration features you wish to enable for the integration, review the Scope and Permission, and Endpoint details and click on Continue. For more details, see Integration Features.
8. In the Connection section, provide the appropriate values and click on Continue,
   • Connection Name: This property allows you to update the integration specified in Step 6. If you have multiple integrations for the same vendor, you may want to assign distinct names to each. This helps streamline filtering by Discovery Source across the Inventory, Visual Maps, Assets, and Data Flow Analysis pages.
   • Rescan Frequency: This property allows you to configure how often Relyance executes scans against this Vendor connection.
   • Business Atlas Associations (required): the business entities or products that newly discovered third parties, services and assets from this integration are attributed to. Choose at least one from the Select Associations dropdown — the wizard will not advance past this step without one. For more details, see Business Atlas.
9. In the Authentication section, provide the following information retrieved from the In Klaviyo section and click on Authenticate.
   • API Key
10. Review the configuration summary from the Completion section and click on Finish.
11. Confirm the integration Status reflects Connected.

If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

1. A feature you enabled returns nothing. Some scopes belong to a feature rather than to the connection: Data subject requests needs Full Access Key. Turning the feature on after the connection exists does not widen the grant it already holds, so re-authenticate the connection.
2. A credential rotated at the vendor is not picked up here. API Key is stored when you save the connection, so regenerating the value at the vendor breaks the next scan until it is re-pasted here. Recording the expiry on the connection means Relyance warns you before it lapses.

Manage this integration with Terraform

Connections for this integration can be managed as code with the Relyance Terraform provider. Non-secret fields go in auth.params; secret fields go in auth.secrets_wo, which is write-only — never stored in Terraform state. Rotate secrets by bumping auth.secrets_wo_version.

resource "relyance_integration_connection" "klaviyo" {
  vendor = "klaviyo"
  name   = "<your connection name>"

  auth = {
    method = "api-key"
    params = {
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      api_key = var.klaviyo_api_key
    }
    secrets_wo_version = 1
  }

  scans = { "property-inspection" = { enabled = true } }
}