Amazon Ads Connector for Azure Data Factory (Pipeline)

Amazon Ads Connector can be used to get Amazon advertisements using Amazon Advertisements API, download various advertisement-related reports.

In this article you will learn how to quickly and efficiently integrate Amazon Ads data in Azure Data Factory (Pipeline) without coding. We will use high-performance Amazon Ads Connector to easily connect to Amazon Ads and then access the data inside Azure Data Factory (Pipeline).

Let's follow the steps below to see how we can accomplish that!

Download Documentation

Create ODBC Data Source (DSN) based on ZappySys API Driver

Step-by-step instructions

To get data from Amazon Ads using Azure Data Factory (Pipeline) we first need to create a DSN (Data Source) which will access data from Amazon Ads. We will later be able to read data using Azure Data Factory (Pipeline). Perform these steps:

  1. Download and install ODBC PowerPack.

  2. Open ODBC Data Sources (x64):

    Open ODBC Data Source
  3. Create a User data source (User DSN) based on ZappySys API Driver:

    ZappySys API Driver
    Create new User DSN for ZappySys API Driver
    • Create and use User DSN if the client application is run under a User Account. This is an ideal option in design-time, when developing a solution, e.g. in Visual Studio 2019. Use it for both type of applications - 64-bit and 32-bit.
    • Create and use System DSN if the client application is launched under a System Account, e.g. as a Windows Service. Usually, this is an ideal option to use in a production environment. Use ODBC Data Source Administrator (32-bit), instead of 64-bit version, if Windows Service is a 32-bit application.
    Azure Data Factory (Pipeline) uses a Service Account, when a solution is deployed to production environment, therefore for production environment you have to create and use a System DSN.
  4. When the Configuration window appears give your data source a name if you haven't done that already, then select "Amazon Ads" from the list of Popular Connectors. If "Amazon Ads" is not present in the list, then click "Search Online" and download it. Then set the path to the location where you downloaded it. Finally, click Continue >> to proceed with configuring the DSN:

    AmazonAdsDSN
    Amazon Ads
    ODBC DSN Template Selection
  5. Now it's time to configure the Connection Manager. Select Authentication Type, e.g. Token Authentication. Then select API Base URL (in most cases, the default one is the right one). More info is available in the Authentication section.

    Amazon Ads authentication

    Amazon OAuth Security Profile has be created in Amazon Developer portal. [API reference]

    1. Firstly, login into Amazon Developer portal in https://developer.amazon.com.
    2. Then click Sign in.
    3. If you don't have an account, press Create your Amazon Developer account button to create one.
    4. Once logged in, click on your profile icon on the right-top of the window and hit Settings: Amazon developer profile settings
    5. Then click Security Profiles and proceed with creating a new Security Profile:
    6. Create Amazon developer security profile
    7. After that, click Web Settings subtab, then hit Show Secret button to reveal the Client Secret (you will need it later), and click Edit to add a Redirect URL:
    8. Reveal client secret in Amazon developer security profile
    9. Continue by setting Allowed Return URLs (you can have your own or use https://zappysys.com/oauth): Set return URLs in Amazon developer security profile
    10. Done! Now you can use Client ID, Client Secret, and Redirect URL when configuring OAuth Authentication parameters: Use client ID and client secret to connect to REST API Amazon services
    API Connection Manager configuration

    Just perform these simple steps to finish authentication configuration:

    1. Set Authentication Type to OAuth Authentication [OAuth]
    2. Optional step. Modify API Base URL if needed (in most cases default will work).
    3. Fill in all the required parameters and set optional parameters if needed.
    4. Press Generate Token button to generate the tokens.
    5. Finally, hit OK button:
    AmazonAdsDSN
    Amazon Ads
    OAuth Authentication [OAuth]
    https://advertising-api.amazon.com/v2
    Required Parameters
    ClientId Fill-in the parameter...
    ClientSecret Fill-in the parameter...
    AuthorizationUrl Fill-in the parameter...
    ReturnUrl Fill-in the parameter...
    Scope Fill-in the parameter...
    Profile (click 'Generate Token' before this) Fill-in the parameter...
    Optional Parameters
    RetryMode RetryWhenStatusCodeMatch
    RetryStatusCodeList 429
    RetryCountMax 5
    RetryMultiplyWaitTime True
    ODBC DSN OAuth Connection Configuration

  6. Once the data source connection has been configured, it's time to configure the SQL query. Select the Preview tab and then click Query Builder button to configure the SQL query:

    ZappySys API Driver - Amazon Ads
    Amazon Ads Connector can be used to get Amazon advertisements using Amazon Advertisements API, download various advertisement-related reports.
    AmazonAdsDSN
    Open Query Builder in API ODBC Driver to read and write data to REST API
  7. Start by selecting the Table or Endpoint you are interested in and then configure the parameters. This will generate a query that we will use in Azure Data Factory (Pipeline) to retrieve data from Amazon Ads. Hit OK button to use this query in the next step.

    SELECT * FROM Orders
    Configure table/endpoint parameters in ODBC data source based on API Driver
    Some parameters configured in this window will be passed to the Amazon Ads API, e.g. filtering parameters. It means that filtering will be done on the server side (instead of the client side), enabling you to get only the meaningful data much faster.
  8. Now hit Preview Data button to preview the data using the generated SQL query. If you are satisfied with the result, use this query in Azure Data Factory (Pipeline):

    ZappySys API Driver - Amazon Ads
    Amazon Ads Connector can be used to get Amazon advertisements using Amazon Advertisements API, download various advertisement-related reports.
    AmazonAdsDSN
    SELECT * FROM Orders
    API ODBC Driver-based data source data preview
    You can also access data quickly from the tables dropdown by selecting <Select table>.
    A WHERE clause, LIMIT keyword will be performed on the client side, meaning that the whole result set will be retrieved from the Amazon Ads API first, and only then the filtering will be applied to the data. If possible, it is recommended to use parameters in Query Builder to filter the data on the server side (in Amazon Ads servers).
  9. Click OK to finish creating the data source.

Video Tutorial

Read data in Azure Data Factory (ADF) from ODBC datasource (Amazon Ads)

  1. Sign in to Azure Portal

    • Open your browser and go to: https://portal.azure.com

    • Enter your Azure credentials and complete MFA if required.

    • After login, go to Data factories.

    Azure Portal
  2. Under Azure Data Factory Resource - Create or select the Data Factory you want to work with.

    Select the Data Factory
  3. Inside the Data Factory resource page, click Launch studio.

    Launch Azure Data Factory Studio
  4. Create a New Integration Runtime (Self-Hosted):

    • In Azure Data Factory Studio, go to the Manage section (left menu).

    • Under Connections, select Integration runtimes.

    • Click + New to create a new integration runtime.

    Create new Self-Hosted integration runtime
  5. Select Azure, Self-Hosted option:

    Create new Self-Hosted integration runtime
  6. Select Self-Hosted option:

    Create new Self-Hosted integration runtime
  7. Set a name, we will use OnPremisesRuntime:

    Set a name for IR
  8. Download and install Microsoft Integration Runtime.

    Download and install Microsoft Integration Runtime
  9. Launch Integration Runtime and copy/paste Authentication Key from Integration Runtime configuration in Azure Portal:

    Copy/paste Authentication Key
  10. After finishing registering the Integration Runtime node, you should see a similar view:

    Check Integration Runtime node status
  11. Go back to Azure Portal and finish adding new Integration Runtime. You should see it was successfully added:

    Integration Runtime status
  12. Create a New Linked service:

    • In the Manage section (left menu).

    • Under Connections, select Linked services.

    • Click + New to create a new Linked service based on ODBC.

    Add new Linked service
  13. Select ODBC service:

    Add new ODBC service
  14. Configure new ODBC service. Use the same DSN name we used in the previous step and copy it to Connection string box:

    AmazonAdsDSN
    DSN=AmazonAdsDSN
    Configure new ODBC service
  15. For created ODBC service create ODBC-based dataset:

    Add new ODBC dataset
  16. Go to your pipeline and add Copy data connector into the flow. In Source section use OdbcDataset we created as a source dataset:

    Set source in Copy data
  17. Then go to Sink section and select a destination/sink dataset. In this example we use precreated AzureBlobStorageDataset which saves data into an Azure Blob:

    Set sink in Copy data
  18. Finally, run the pipeline and see data being transferred from OdbcDataset to your destination dataset:

    Run the flow

Executing SQL queries using Lookup activity

If you need to execute commands in Amazon Ads instead of retrieving data, use the Lookup activity for that purpose. Use this approach when you want data to be changed on the Amazon Ads side, but you don't need the data on your side (a "fire-and-forget" scenario).

Perform these simple steps to accomplish that:

  1. Go to your pipeline in Azure Data Factory

  2. Find Lookup activity in the Activities pane

  3. Then drag-and-drop the Lookup activity onto your pipeline canvas

  4. Click Settings tab

  5. Select OdbcDataset in the Source dataset field

  6. Finally, enter your SQL query in the Query text box:

SELECT * FROM get_report WITH ( "RecordType" = 'keywords', "ReportDate" = 'today', "Metrics" = 'abcd-1234-metrics' )
Configuring Lookup activity in ADF pipeline to perform a command in Amazon Ads

Centralized data access via Data Gateway

In some situations, you may need to provide Amazon Ads data access to multiple users or services. Configuring the data source on a Data Gateway creates a single, centralized connection point for this purpose.

This configuration provides two primary advantages:

  • Centralized data access
    The data source is configured once on the gateway, eliminating the need to set it up individually on each user's machine or application. This significantly simplifies the management process.
  • Centralized access control
    Since all connections route through the gateway, access can be governed or revoked from a single location for all users.
Data Gateway
Local ODBC
data source
Simple configuration
Installation Single machine Per machine
Connectivity Local and remote Local only
Connections limit Limited by License Unlimited
Central data access
Central access control
More flexible cost

If you need any of these requirements, you will have to create a data source in Data Gateway to connect to Amazon Ads, and to create an ODBC data source to connect to Data Gateway in Azure Data Factory (Pipeline).

Let's not wait and get going!

Creating Amazon Ads data source in Gateway

In this section we will create a data source for Amazon Ads in Data Gateway. Let's follow these steps to accomplish that:

  1. Search for gateway in Windows Start Menu and open ZappySys Data Gateway Configuration:

    Opening Data Gateway
  2. Go to Users tab and follow these steps to add a Data Gateway user:

    • Click Add button
    • In Login field enter username, e.g., john
    • Then enter a Password
    • Check Is Administrator checkbox
    • Click OK to save
    Data Gateway - Adding User
  3. Now we are ready to add a data source:

    • Click Add button
    • Give Datasource a name (have it handy for later)
    • Then select Native - ZappySys API Driver
    • Finally, click OK
    AmazonAdsDSN
    ZappySys API Driver
    Data Gateway - Adding data source
  4. When the ZappySys API Driver configuration window opens, configure the Data Source the same way you configured it in ODBC Data Sources (64-bit), in the beginning of this article.

  5. Very important step. Now, after creating or modifying the data source make sure you:

    • Click the Save button to persist your changes.
    • Hit Yes, once asked if you want to restart the Data Gateway service.

    This will ensure all changes are properly applied:

    ZappySys Data Gateway - Save Changes
    Skipping this step may result in the new settings not taking effect and, therefore you will not be able to connect to the data source.

Creating ODBC data source for Data Gateway

In this part we will create ODBC data source to connect to Data Gateway from Azure Data Factory (Pipeline). To achieve that, let's perform these steps:

  1. Open ODBC Data Sources (x64):

    Open ODBC Data Source
  2. Create a User data source (User DSN) based on ODBC Driver 17 for SQL Server:

    ODBC Driver 17 for SQL Server
    Create new User DSN for ODBC Driver 17 for SQL Server
    If you don't see ODBC Driver 17 for SQL Server driver in the list, choose a similar version driver.
  3. Then set a Name of the data source (e.g. Gateway) and the address of the Data Gateway:

    GatewayDSN
    localhost,5000
    ODBC driver for SQL Server - Setting hostname and port
    Make sure you separate the hostname and port with a comma, e.g. localhost,5000.
  4. Proceed with authentication part:

    • Select SQL Server authentication
    • In Login ID field enter the user name you used in Data Gateway, e.g., john
    • Set Password to the one you configured in Data Gateway
    ODBC driver for SQL Server - Selecting SQL Authentication
  5. Then set the default database property to AmazonAdsDSN (the one we used in Data Gateway):

    AmazonAdsDSN
    ODBC driver for SQL Server - Selecting database
  6. Continue by checking Trust server certificate option:

    ODBC driver for SQL Server - Trusting certificate
  7. Once you do that, test the connection:

    ODBC driver for SQL Server - Testing connection
  8. If connection is successful, everything is good:

    ODBC driver for SQL Server - Testing connection succeeded
  9. Done!

We are ready to move to the final step. Let's do it!

Accessing data in Azure Data Factory (Pipeline) via Data Gateway

Finally, we are ready to read data from Amazon Ads in Azure Data Factory (Pipeline) via Data Gateway. Follow these final steps:

  1. Go back to Azure Data Factory (Pipeline).

  2. Create a New Linked service:

    • In the Manage section (left menu).

    • Under Connections, select Linked services.

    • Click + New to create a new Linked service based on ODBC.

    Add new Linked service
  3. Select ODBC service:

    Add new ODBC service
  4. Configure new ODBC service. Use the same DSN name we used in the previous step and copy it to Connection string box:

    GatewayDSN
    DSN=GatewayDSN
    Configure new ODBC service
  5. Read the data the same way we discussed at the beginning of this article.

  6. That's it!

Now you can connect to Amazon Ads data in Azure Data Factory (Pipeline) via the Data Gateway.

If you are asked for authentication details, use Database authentication or SQL Authentication option and enter credentials you used when configuring Data Gateway, e.g. john and your password.

Actions supported by Amazon Ads Connector

Learn how to perform common Amazon Ads actions directly in Azure Data Factory (Pipeline) with these how-to guides:

Conclusion

In this article we showed you how to connect to Amazon Ads in Azure Data Factory (Pipeline) and integrate data without any coding, saving you time and effort.

We encourage you to download Amazon Ads Connector for Azure Data Factory (Pipeline) and see how easy it is to use it for yourself or your team.

If you have any questions, feel free to contact ZappySys support team. You can also open a live chat immediately by clicking on the chat icon below.

Download Amazon Ads Connector for Azure Data Factory (Pipeline) Documentation

More integrations

Other connectors for Azure Data Factory (Pipeline)

All
Big Data & NoSQL
Database
CRM & ERP
Marketing
Collaboration
Cloud Storage
Reporting
Commerce
API & Files

Other application integration scenarios for Amazon Ads

All
Data Integration
Database
BI & Reporting
Productivity
Programming Languages
Automation & Scripting
ODBC applications