Getting started with Devart ODBC Driver for ActiveCampaign

To connect ODBC-compatible applications to ActiveCampaign, you need an ODBC Driver and an ActiveCampaign account.

Devart ODBC Driver for ActiveCampaign enables high-performance access to ActiveCampaign data from Windows-based applications and tools. The Driver connects BI and reporting platforms, IDEs, spreadsheets, programming environments, and other ODBC-compatible applications to ActiveCampaign, allowing you to access and manage data stored in ActiveCampaign using standard SQL.

The Driver communicates with ActiveCampaign over a secure HTTPS connection and can also connect through a proxy server.

This guide shows you how to install and activate the Driver, configure an ODBC data source (DSN), connect to ActiveCampaign using a DSN or connection string, and troubleshoot common connection issues.

Quick start: Connect to ActiveCampaign with ODBC

To connect to ActiveCampaign using the Devart ODBC Driver:

  1. Download and install the Driver.
  2. Activate the Driver using your activation key, or continue with the 30-day trial.
  3. Create an ODBC data source (DSN) and select Devart ODBC Driver for ActiveCampaign.
  4. Configure the connection by providing your ActiveCampaign user account name and API key associated with your account.
  5. Use the DSN in your ODBC-compatible application to access ActiveCampaign and work with its data.

The following sections provide detailed instructions for installing and configuring the ODBC Driver.

Prerequisites

Before you begin, make sure your environment meets the following requirements:

  • Operating system: Windows Vista or later (32-bit or 64-bit), including Windows Terminal Server.
  • Connection details: A valid ActiveCampaign account and API key.
  • Activation key: For a purchased version of the Driver or a full-featured 30-day trial, use the activation key you received in the registration email or through the Customer Portal.
  • Administrator rights: Required to install the Driver.

For a complete list of third-party tools supported by ActiveCampaign, see the ODBC Driver for ActiveCampaign compatibility page.

Install the Driver

Installing the Devart ODBC Driver for ActiveCampaign is straightforward. All you need to do is download the package and follow the installation instructions.

Note
The installer for Devart ODBC Driver for ActiveCampaign is available in two formats: .exe and .msi.

Use the .exe installer for manual installation on individual computers. Use the .msi installer for enterprise deployments and automated installation. You can deploy the .msi package to domain computers through Group Policy and activate the Driver without user interaction. For more information, see Remote installation using Group Policy.

1. Download the ODBC Driver for ActiveCampaign from the Devart website, open it, and click Next.

Install the ODBC Driver for ActiveCampaign

2. Read the License Agreement, select I accept the agreement, and click Next.

Accept the license agreement for the ODBC Driver for ActiveCampaign

3. On the Select Destination Location page, keep the default folder or click Browse to choose another one, and click Next.

Select the destination folder for the Driver installation

4. On the Select Components page, select the components to install, then click Next.

Note
Install the Driver version that matches your application bitness, not your operating system bitness. For example, a 32-bit application, such as 32-bit Microsoft Office, requires Driver for Win32 even on 64-bit Windows.
Choose the ODBC Driver for ActiveCampaign version

5. On the Select Start Menu Folder page, specify the folder for the Driver shortcuts. To skip creating a Start Menu folder, select Don't create a Start Menu folder. Click Next, then click Install.

Select the Start menu folder

6. On the License Information page, select Input activation key and enter your key. You can find it in the registration email or your Customer Portal. To open the Customer Portal, click Get Activation Key.

If the activation key is saved on your computer, click Load Activation Key and select the corresponding file.

To evaluate the Driver without a purchased key, select Trial evaluation.

Activate the ODBC Driver for ActiveCampaign

7. Click Next, then click Finish to complete the installation.

Tip
The ODBC Driver for ActiveCampaign can also be installed using silent installation.

Configure an ODBC data source

In this guide, you create a Data Source Name (DSN) for the ODBC connection and verify the connection details. A DSN stores the connection details, such as the ActiveCampaign account and API key that applications use to connect to ActiveCampaign. Applications can also connect without a DSN by passing the same parameters in a connection string.

1. In Windows Search, enter ODBC Data Sources, and open the ODBC Data Source Administrator that matches the bitness of your application.

2. Select the User DSN, System DSN, or File DSN tab, and click Add:

  • User DSN — Available only to the user who creates it.
  • System DSN — Available to all users on the computer.
  • File DSN — Stores connection settings in a file that can be shared between computers where the required ODBC driver is installed.
Note
Most applications support all DSN types. However, some applications require a specific DSN type.

3. In the Create New Data Source dialog, select Devart ODBC Driver for ActiveCampaign, and click Finish.

Create a new data source for the ODBC Driver for ActiveCampaign

4. In the Devart ODBC Driver for ActiveCampaign Configuration dialog, enter a Data Source Name and an optional Description.

5. In the Account field, enter your ActiveCampaign account name. In the API Key field, enter the ActiveCampaign API key that you can find in your account settings. Optionally, click Save API Key to enable future connections with the same credentials.

Configure DSN for the connection to ActiveCampaign

6. Optional: Click Test Connection to verify the connection settings.

Test the ODBC connection to ActiveCampaign

7. Click OK to save the DSN settings.

To fine-tune metadata, timeout, and compatibility behavior, use the Advanced Settings tab of the same dialog.

Connect to ActiveCampaign using a connection string

In addition to using a DSN, you can connect to ActiveCampaign by specifying the connection parameters directly in an ODBC connection string. This type of connection is known as a DSN-less connection.

The following table summarizes when to use each connection method:

Connection method How it works Best for
DSN Stores the connection settings in a configured ODBC data source. Applications connect by specifying the DSN name. Desktop applications, BI and reporting tools, and reusable connections configured on a client computer
DSN-less Specifies the Driver and connection parameters directly in a connection string. No DSN needs to be created beforehand. Applications, scripts, and automated deployments where connection settings are managed programmatically

To create a DSN-less connection, configure the connection string as follows.

DRIVER={Devart ODBC Driver for ActiveCampaign};Account=your_account;API Key=your_apikey

You can also specify advanced connection parameters to configure ODBC behavior, string types, proxy configuration, and other Driver settings.

For the complete list of supported options, see ActiveCampaign ODBC connection string parameters.

Troubleshoot common issues

If you cannot connect to ActiveCampaign through the Devart ODBC Driver, use the following solutions to resolve common connection issues.

"Product is not activated or has been deactivated" error

This error occurs when the Driver has not been activated or its activation is no longer valid.

Open the DSN configuration dialog, go to the License tab, click Input Activation Key, and enter your activation key. After activation, test the connection again.

ODBC data source not found or Driver not available

If your application cannot find the DSN or the Devart ODBC Driver for ActiveCampaign, check the application and Driver bitness.

A 32-bit application cannot use a DSN created in the 64-bit ODBC Data Source Administrator, and a 64-bit application cannot use a DSN created in the 32-bit administrator.

Make sure that:

  • The DSN is created in the ODBC administrator that matches your application's bitness.
  • The corresponding 32-bit or 64-bit version of the Driver is installed.
  • The application is configured to use the correct DSN.

Cannot connect to ActiveCampaign

If the Driver cannot reach ActiveCampaign, check the following:

  • Verify that the ActiveCampaign API key is correct. Copy the API key from your account settings and reenter it in the ODBC Driver configuration.
  • Check that the API key has not been reset. Reenter the API key to make sure you are using the active one.
  • If a connection attempt returns a "Too many requests" error, try reconnecting. ActiveCampaign limits API traffic to 5 requests per second per account.

ActiveCampaign connection times out

If the server is available but the connection takes too long to establish, increase Connection Timeout on the Advanced Settings tab. The default connection timeout is 60 seconds.

Additional resources

After you install and configure Devart ODBC Driver for ActiveCampaign, use the following resources to continue setting up and working with your connections:

ODBC Drivers

Reliable and easy-to-use ODBC connectors for popular data sources. Compatible with multiple third-party tools.

Buy now Download