Connect to LinkedIn Ads from Asprova with CData ODBC Driver for LinkedIn Ads



This article shows how to connect faster to LinkedIn Ads data from Asprova.

The CData ODBC driver for LinkedIn Ads enables you to access LinkedIn Ads data from Asprova. In this article, you will import LinkedIn Ads data into item data in Asprova as an example.

Asprova setting

  1. Click File -> Data I/O Settings.

  2. Double click the header of Item and open the Edit I/O dialog.

  3. Select "No" from the RDB transaction combo box and close the dialog.

Data driver setting

  1. Select "OLE DB" from combo box in "Data source" column.

  2. Click button in Folder/database column and open the Data Link Property dialog. Select "Microsoft OLE DB Provider for ODBC Drivers" from the list of data provider.

  3. Select the Connection tab. Check "Use data source name" and select "CData LinkedIn Ads Source" from DSN combo box.

  4. Click the Test Connection button and make sure you see the message "Connection successful".

Schema setting

  1. Click the button in "External table name" column and open the Table List dialog. Make sure tables in LinkedIn Ads are listed in the dialog.

  2. Click the button in "Field mapping" column and open the Item-Field Mapping dialog.

  3. Open the context menu in the space between tables and click Delete All. Link corresponding fields by dragging mouse.

  4. Click File > Import and data will be imported into Asprova.

Check data

Click Table View > Item. Be sure you can see the item data stored in LinkedIn Ads.

Ready to get started?

Download a free trial of the LinkedIn Ads ODBC Driver to get started:

 Download Now

Learn more:

LinkedIn Ads Icon LinkedIn Ads ODBC Driver

The LinkedIn Ads ODBC Driver is a powerful tool that allows you to connect with live data from LinkedIn Ads, directly from any applications that support ODBC connectivity.

Access LinkedIn Ads data like you would a database - read, write, and update LinkedIn Ads Analytics, Campaings, Conversion, Forms, etc. through a standard ODBC Driver interface.