Informatica Amazon Ads Connector

In this article you will learn how to integrate Amazon Ads data to Informatica without coding in just a few clicks (live / bi-directional connection to Amazon Ads). Amazon Ads Connector can be used to get Amazon advertisements using Amazon Advertisements API, download various advertisement-related reports..

Using Amazon Ads Connector you will be able to connect, read, and write data from within Informatica. Follow the steps below to see how we would accomplish that.

Download  Help File  Buy 

NOTE: If you need to consume API which is not listed on connector library page then please refer to the below article links. It talks about how to read / write pretty much any API and not just Amazon Ads API. It explains various API tips / tricks using our other Universal Drivers not mentioned in this article (i.e. ZappySys JSON / XML and CSV Drivers).
How to read API data in Informatica (Call JSON / XML SOAP Service)
How to write data to API (POST) in Informatica (Call JSON / XML SOAP Service)

Read/Write Amazon Ads data in Informatica

Introduction

Informatica PowerCenter LogoJSON / REST API is becoming more and more popular each day as everyone embrace cloud-centric services. This article is primarily focused on Informatica users who want to access Amazon Ads data or may be other API Integration in Informatica. However many tips and techniques described in this article will help you to understand how to integrate XML SOAP / JSON / REST API in other ETL / Reporting apps such as Tableau, Power BI, SSRS, Talend, Excel and many more.

After going through this article you will learn how to Read Amazon Ads / JSON / REST API data in Informatica and understand the concept of JSON / REST API. We will go through many screenshots and step-by-step examples to demonstrate  JSON File or REST API integration in Informatica PowerCenter.

XML / JSON can come from a local file or REST API service (internal or public) so we will include both examples in this article (i.e. Read JSON files in Informatica,  Import REST API in Informatica). So let’s get started. Next article will focus on how to write data to API in Informatica (POST / PUT data)

Requirements

This article assumes that you have full filled following basic requirements.

  1. Download Install ZappySys ODBC PowerPack (API Driver for Amazon Ads included)
  2. Install Informatica PowerCenter Client Tools (e.g. Workflow and Mapping Designers)
  3. Access to a Relational database such as SQL Server (or use any of your choice e.g. Oracle, MySQL, DB2 ). If nothing available then you can use flat file target.

High level Steps for Import Amazon Ads data using Informatica (Read Amazon Ads API data)

Before we dive deep to learn how to load Amazon Ads data in Informatica (i.e. Amazon Ads to SQL Table), Here the summary of high-level steps you need to perform to import JSON Files or REST API in Informatica.

  1. Download and Install ZappySys API Driver (for connecting to Amazon Ads)
  2. Create ODBC DSN using ZappySys API driver and choose Amazon Ads Connector during Wizard
  3. Create Relational > ODBC Connection in Informatica Workflow designer (Point to DSN we created in the previous step)
  4. Import JSON Source Definition in the Informatica Mapping Designer > Sources Tab
  5. Import Target Table Definition in the Informatica Mapping Designer > Targets Tab
  6. Create source to target mapping in Mappings tab
  7. Save mapping (name m_API_to_SQL_Load )
  8. Create Session using the mapping we created in the previous step
  9. Save Workflow and execute to load Amazon Ads data into SQL Table. Verify your data and log.
    Loading JSON data to SQL Table in Informatica (Import REST API or JSON Files)

    Loading Amazon Ads data to SQL Table in Informatica (Import REST API or JSON Files)

Video Tutorial – Read any API / JSON data in Informatica (Load Amazon Ads to SQL Table)

Below video is not about Amazon Ads API but its showing API access in general (for any API). By watching following ~5 min video can learn steps listed in this article to load JSON API data into SQL Server Table using ZappySys JSON Driver. You can go though full article to learn many useful details not covered in this video.

Getting Started – Import Amazon Ads to SQL Server in Informatica

Now let’s get started. For example purpose, we will read data from Amazon Ads and load data into SQL Server Table using Informatica Workflow.

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

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

  1. Install ZappySys 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 System DSN for ZappySys API Driver
    You should create a System DSN (instead of a User DSN) if the client application is launched under a Windows System Account, e.g. as a Windows Service. If the client application is 32-bit (x86) running with a System DSN, use ODBC Data Sources (32-bit) instead of the 64-bit version.
  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.

    OAuth App must be created in Atlassian Developer Console. It is found at https://developer.atlassian.com/console/myapps/ [API Help..]

    Steps to get Amazon Ads Credentials : OAuth Authentication [OAuth]

    Firstly, login into Amazon Developer portal:

    1. Visit https://developer.amazon.com.
    2. Then click Sign in.
    3. If you don't have an account, press the button Create your Amazon Developer account.
    4. Once logged in, click on your profile icon on the right-top of the window.
    5. A menu appears, and then click 'Settings'.
    6. Then click Security Profiles.
    7. Proceed with creating a new Security Profile.
    8. Once you named it, click 'Save'.
    9. After that, click 'Web Settings' subtab.
    10. A window refreshes, click 'Show Secret' button and write down Client ID and Client Secret, you will need them later.
    11. Then press 'Edit' and add Allowed Return URLs. It can be your domain or you can use https://zappysys.com/oauth. Note it, you will need it in configuration.
    12. Close web browser.
    13. Now it's time to configure Amazon Ads API data source.
    14. Fill in all blank Required Parameters:
      1. ClientId
      2. ClientSecret
      3. ReturnUrl
    15. Click Generate Token to generate tokens.
    16. Now you can select the 'Profile' to work with.
    17. That's it!

    Fill in all required parameters and set optional parameters if needed:

    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 Fill in the parameter...
    RetryStatusCodeList Fill in the parameter...
    RetryCountMax Fill in the parameter...
    RetryMultiplyWaitTime Fill in the parameter...
    ODBC DSN Oauth Connection Configuration

  6. Once the data source has been configured, you can preview data. Select the Preview tab and use settings similar to the following to preview data:
    ODBC ZappySys Data Source Preview

  7. Click OK to finish creating the data source.

Create Connection in Informatica Workflow Designer

Once you create DSN using API Driver our next step is to define a connection for Amazon Ads source in Informatica PowerCenter Workflow designer.

  1. Open Workflow designer [W] icon
  2. Goto Connections > Relational
    Create new connection for JSON in Informatica

    Create a new connection for Amazon Ads in Informatica

  3. Click New and select ODBC
    Select ODBC connection type in Informatica (Using ZappySys JSON ODBC DSN)

    Select ODBC connection type in Informatica (Using ZappySys API ODBC DSN)

  4. Now on the ODBC connection setup enter connection name, some fake userid / password (this is a required field but its ignored by JSON Driver)
  5. In the Connection String field enter the exact same name of DSN (Open ODBC Data Sources UI to confirm)
    Configure Amazon Ads connection in Informatica for REST API – Using ZappySys API ODBC Driver

    Configure Amazon Ads connection in Informatica for REST API – Using ZappySys API Driver

  6. Click OK to close the connection properties.

That’s it. Now we ready to move to next step (define source and target in Mapping Designer).

Import Amazon Ads Source Definition in Informatica Mapping Designer

Now let’s look at steps to import Amazon Ads table definition.

  1. Open Informatica Mapping Designer (Click [D] icon)
  2. Click on Source Icon to switch to Sources designer
  3. From the top menu > Click on Sources > Import from Database
    Import JSON Source definition in Informatica Mapping Designer (JSON file or REST API)

    Import Amazon Ads Source definition in Informatica Mapping Designer (JSON file or REST API)

  4. Select ODBC data source from the dropdown (Find out DSN we created earlier to use as JSON Source)
  5. Click Connect button to get a list of tables. Any array node is listed as a table. Also, you will see array node with parent columns (e.g. value_with_parent). You may get some warning like below but they are harmless so just ignore by clicking OK.
    DLL name entry missing from C:\Informatica\PowerCenter8.6.1\client\bin\powrmart.ini Section = ODBCDLL Entry = ZappySys JSON Driver
    —————————————————-
    Using EXTODBC.DLL to support ZappySys JSON Driver. For native support of ZappySys JSON Driver make an entry in the .ini file.
    Select JSON Source Table in Informatica Mapping Designer (JSON file or REST API)

    Select Amazon Ads Source Table in Informatica Mapping Designer (JSON file or REST API)

  6. Select Table you wish to get (You can filter rows by custom SQL query. We will see later in this article how to do)
  7. Optionally once table structure is imported you can rename it
    Rename imported table definition in Informatica Source Designer

    Rename imported table definition in Informatica Source Designer

  8. That’s it, we are now ready to perform similar steps to import Target table structure in the next section.

Import SQL Server Target Definition in Informatica Mapping Designer

Now let’s look at steps to import Target table definition (very similar to the previous section, the only difference is this time we will select DSN which points to SQL Server or any other Target Server).

Now lets look at steps to import target table definition in Informatica mapping designer.

  1. In the Mapping Designer, Click on Target Icon to switch to Target designer
  2. From the top menu > Click on Targets > Import from Database
  3. Select DSN for your Target server (if DSN doesn’t exist then create one by opening ODBC Sources just like we created one for JSON API source (see the previous section about creating DSN).
    Import target Table Definition in informatica

    Import target Table Definition in informatica

  4. Enter your userid , password and Schema name and click Connect to see tables
  5. Select Table name to and click OK import definition.
    Import Target SQL Table Definition in Informatica - Select table from the list

    Import Target SQL Table Definition in Informatica – Select table from the list

Create Source to Target Mapping in Informatica (Import JSON to SQL Server)

Once you have imported source and target table definition, we can create mapping and transformation to load data from JSON to SQL Table.

  1. First open Mapping Designer (Click [D] icon)
  2. Drag JSON Source from sources folder
  3. Drag SQL Table from Targets folder
  4. Map desired columns from Source to target
    Define Source to Target mapping for JSON to SQL Table load in Informatica

    Define Source to Target mapping for Amazon Ads to SQL Table load in Informatica

  5. For certain columns you may have to do datatype conversion. For example to convert OrderDate form nstring to DataTime you have to use Expression Transform like below and map it to target. In below example, our JSON has date format (e.g. 2018-01-31 12:00:00 AM ). To import this to DateTime field in SQL server we need to convert it using TO_DATE function. Use double quotes around T to make this format working.
    TO_DATE(OrderDate,'YYYY-MM-DD H12:MI:SS AM')
    
     --For ISO use below way
                    TO_DATE(OrderDate,'YYYY-MM-DD"T"HH24:MI:SS')
    Informatica JSON to SQL Table Mapping - Datatype conversion (nstring to datetime)

    Informatica Amazon Ads to SQL Table Mapping – Datatype conversion (nstring to datetime)

  6. Once you done with mapping save your mapping and name it (i.e. m_Api_To_SQL)
  7. Now lets move to next section to create workflow.

Create Workflow and Session in Informatica

Now the final step is to create a new workflow. Perform following steps to create workflow which with a session task to import JSON data into SQL table.

  1. Open workflow designer by click [W] icon.
  2. Launch new workflow creation wizard by click Workflow top menuWizard
    name your workflow (e.g. wf_Api_Tp_Sql_Table_Import)

    Creating Informatica Workflow - Wizard UI (Import JSON data to SQL Table)

    Creating Informatica Workflow – Wizard UI (Import Amazon Ads data to SQL Table)

  3. Finish the wizard and double-click the Session to edit some default properties.
  4. First change Error settings so we fail session on error (By default its always green)
    Fail Informatica Session on error (JSON to SQL Load)

    Fail Informatica Session on error (Amazon Ads data to SQL Load)

  5. Select JSON connection for Source
    Select JSON Source Connection in Informatica - JSON File / REST API Load to SQL Table

    Select Amazon Ads Source Connection in Informatica – Load Amazon Ads data to SQL Table

  6. Change default Source query if needed. You can pass parameters to this query to make it dynamic.
    Modify JSON Source SQL query - Pass parameters, change URL, set filter etc

    Modify Amazon Ads Source SQL query – Pass parameters, change URL, set filter etc

  7. Select Target connection of SQL Target Table
    Select SQL Target Connection in Informatica - JSON File / REST API Load to SQL Table

    Select SQL Target Connection in Informatica – Load Amazon Ads data to SQL Table

  8. Save workflow
  9. That’s it. We ready to run our first workflow to load JSON data to SQL.

Execute Workflow and Validate Log in Informatica

Now once you are done with your workflow, execute it to see the log.

Loading JSON data to SQL Table in Informatica (Import REST API or JSON Files)

Loading Amazon Ads data to SQL Table in Informatica (Import REST API or JSON Files)

 

POST data to Amazon Ads in Informatica

There will be a time when you like to send Source data to REST API or SOAP Web Service. You can use below Query for example. For detailed explanation on how to POST data in Informatica check this article.

Video Tutorial – How to POST data to REST API in Informatica

Here is detailed step by step video on REST API POST in informatica PowerCenter

 

Keywords

how to import Amazon Ads in informatica | how to read Amazon Ads data in informatica powercenter | how to test json from informatica | how to use Amazon Ads data as source in informatica power center | how to connect Amazon Ads in informatica 10 | informatica how to import data from Amazon Ads | informatica jtx to import Amazon Ads (use of java transformation) | informatica plugin for restful api using json | informatica power center and Amazon Ads support | informatica read Amazon Ads | informatica rest api | informatica Amazon Ads connector | json parser import informatica

Create Custom Store Procedure in ZappySys Driver

You can create procedures to encapsulate custom logic and then only pass handful parameters rather than long SQL to execute your API call.

Steps to create Custom Store Procedure in ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here

  1. Go to Custom Objects Tab and Click on Add button and Select Add Procedure:
    ZappySys Driver - Add Store Procedure

  2. Enter the desired Procedure name and click on OK:
    ZappySys Driver - Add Store Procedure Name

  3. Select the created Store Procedure and write the your desired store procedure and Save it and it will create the custom store procedure in the ZappySys Driver:
    Here is an example stored procedure for ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here

    CREATE PROCEDURE [usp_get_orders]
        @fromdate = '<<yyyy-MM-dd,FUN_TODAY>>'
     AS
        SELECT * FROM Orders where OrderDate >= '<@fromdate>';
    

    ZappySys Driver - Create Custom Store Procedure

  4. That's it now go to Preview Tab and Execute your Store Procedure using Exec Command. In this example it will extract the orders from the date 1996-01-01:

    Exec usp_get_orders '1996-01-01';

    ZappySys Driver - Execute Custom Store Procedure

  5. Let's generate the SQL Server Query Code to make the API call using store procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
    As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.

    SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC usp_get_orders @fromdate=''1996-07-30''')

    ZappySys Driver - Generate SQL Server Query

  6. Now go to SQL served and execute that query and it will make the API call using store procedure and provide you the response.
    ZappySys Driver - Generate SQL Server Query

Create Custom Virtual Table in ZappySys Driver

ZappySys API Drivers support flexible Query language so you can override Default Properties you configured on Data Source such as URL, Body. This way you don't have to create multiple Data Sources if you like to read data from multiple EndPoints. However not every application support supplying custom SQL to driver so you can only select Table from list returned from driver.

If you're dealing with Microsoft Access and need to import data from an SQL query, it's important to note that Access doesn't allow direct import of SQL queries. Instead, you can create custom objects (Virtual Tables) to handle the import process.

Many applications like MS Access, Informatica Designer wont give you option to specify custom SQL when you import Objects. In such case Virtual Table is very useful. You can create many Virtual Tables on the same Data Source (e.g. If you have 50 URLs with slight variations you can create virtual tables with just URL as Parameter setting.

  1. Go to Custom Objects Tab and Click on Add button and Select Add Table:
    ZappySys Driver - Add Table

  2. Enter the desired Table name and click on OK:
    ZappySys Driver - Add Table Name

  3. And it will open the New Query Window Click on Cancel to close that window and go to Custom Objects Tab.

  4. Select the created table, Select Text Type AS SQL and write the your desired SQL Query and Save it and it will create the custom table in the ZappySys Driver:
    Here is an example SQL query for ZappySys Driver. You can insert Placeholders also. Read more about placeholders here

    SELECT
      "ShipCountry",
      "OrderID",
      "CustomerID",
      "EmployeeID",
      "OrderDate",
      "RequiredDate",
      "ShippedDate",
      "ShipVia",
      "Freight",
      "ShipName",
      "ShipAddress",
      "ShipCity",
      "ShipRegion",
      "ShipPostalCode"
    FROM "Orders"
    Where "ShipCountry"='USA'

    ZappySys Driver - Create Custom Table

  5. That's it now go to Preview Tab and Execute your custom virtual table query. In this example it will extract the orders for the USA Shipping Country only:

    SELECT * FROM "vt__usa_orders_only"

    ZappySys Driver - Execute Custom Virtual Table Query

  6. Let's generate the SQL Server Query Code to make the API call using store procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
    As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.

    SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC [usp_get_orders] ''1996-01-01''')

    ZappySys Driver - Generate SQL Server Query

  7. Now go to SQL served and execute that query and it will make the API call using store procedure and provide you the response.
    ZappySys Driver - Generate SQL Server Query

Conclusion

In this article we discussed how to connect to Amazon Ads in Informatica and integrate data without any coding. Click here to Download Amazon Ads Connector for Informatica and try yourself see how easy it is. If you still have any question(s) then ask here or simply click on live chat icon below and ask our expert (see bottom-right corner of this page).

Download Amazon Ads Connector for Informatica Documentation 

Actions supported by Amazon Ads Connector

Amazon Ads Connector support following actions for REST API integration. If some actions are not listed below then you can easily edit Connector file and enhance out of the box functionality.
 test_connection
Endpoint to test connection.    [Read more...]
 get_profiles
Gets your Amazon Ads profiles    [Read more...]
 Get Report
Downloads an Amazon Ads report.    [Read more...]
Parameter Description
Record Type
Option Value
campaigns campaigns
adGroups adGroups
keywords keywords
productAds productAds
asins asins
State Filter
Option Value
enabled enabled
paused paused
archived archived
Campaign Type
Option Value
sponsoredProducts sponsoredProducts
headlineSearch headlineSearch
Segment
Option Value
query query
placement placement
Report Date (yyyyMMdd) The date for which to retrieve the report in YYYYMMDD format. Supported functions now|today|yesterday|weekstart|weekend|monthstart|monthend|yearstart|yearend and supported intervals for add/subtract are ms|s|sec|min|h|hour|y|year|d|day|m|month|y|year. Example monthstart-3d (subtract 3days from month start)
Option Value
today today
yesterday yesterday
monthstart monthstart
monthend monthend
yearstart yearstart
yearend yearend
weekstart weekstart
weekend weekend
yearstart-1y yearstart-1y
yearend-1y yearend-1y
monthstart-1d monthstart-1d
monthend+1d monthend+1d
2022-01-31 2022-01-31
Metrics
Option Value
adGroupId adGroupId
adGroupName adGroupName
attributedConversions14d attributedConversions14d
attributedConversions14dSameSKU attributedConversions14dSameSKU
attributedConversions1d attributedConversions1d
attributedConversions1dSameSKU attributedConversions1dSameSKU
attributedConversions30d attributedConversions30d
attributedConversions30dSameSKU attributedConversions30dSameSKU
attributedConversions7d attributedConversions7d
attributedConversions7dSameSKU attributedConversions7dSameSKU
attributedKindleEditionNormalizedPagesRead14d attributedKindleEditionNormalizedPagesRead14d
attributedKindleEditionNormalizedPagesRoyalties14d attributedKindleEditionNormalizedPagesRoyalties14d
attributedSales14d attributedSales14d
attributedSales14dSameSKU attributedSales14dSameSKU
attributedSales1d attributedSales1d
attributedSales1dSameSKU attributedSales1dSameSKU
attributedSales30d attributedSales30d
attributedSales30dSameSKU attributedSales30dSameSKU
attributedSales7d attributedSales7d
attributedSales7dSameSKU attributedSales7dSameSKU
attributedUnitsOrdered14d attributedUnitsOrdered14d
attributedUnitsOrdered14dSameSKU attributedUnitsOrdered14dSameSKU
attributedUnitsOrdered1d attributedUnitsOrdered1d
attributedUnitsOrdered1dSameSKU attributedUnitsOrdered1dSameSKU
attributedUnitsOrdered30d attributedUnitsOrdered30d
attributedUnitsOrdered30dSameSKU attributedUnitsOrdered30dSameSKU
attributedUnitsOrdered7d attributedUnitsOrdered7d
attributedUnitsOrdered7dSameSKU attributedUnitsOrdered7dSameSKU
campaignBudget campaignBudget
campaignBudgetType campaignBudgetType
campaignId campaignId
campaignName campaignName
campaignStatus campaignStatus
clicks clicks
cost cost
currency currency
impressions impressions
keywordBid keywordBid
keywordId keywordId
keywordStatus keywordStatus
keywordText keywordText
matchType matchType
query query
 Get Beta Report
Generates and downloads an Amazon Ads report.    [Read more...]
Parameter Description
Report Name
Report Type
Option Value
Campaigns spCampaigns
Targeting spTargeting
Search Term spSearchTerm
Advertised Product spAdvertisedProduct
Purchased Product spPurchasedProduct
Time Unit
Option Value
Summary SUMMARY
Daily DAILY
Group By
Option Value
Campaign campaign
Ad Group adGroup
Campaign Placement campaignPlacement
Group By
Option Value
Targeting targeting
Group By
Option Value
Search Term searchTerm
Group By
Option Value
Advertiser advertiser
Group By
Option Value
ASIN asin
Purchased ASIN purchasedAsin
Report Start Date (yyyy-MM-dd) Maximum date range: 31 days The start date for the data to retrieve in YYYY-MM-DD format. Supported functions now|today|yesterday|weekstart|weekend|monthstart|monthend|yearstart|yearend and supported intervals for add/subtract are ms|s|sec|min|h|hour|y|year|d|day|m|month|y|year. Example monthstart-3d (subtract 3 days from month start)
Option Value
today today
yesterday yesterday
monthstart monthstart
monthend monthend
yearstart yearstart
yearend yearend
weekstart weekstart
weekend weekend
yearstart-1y yearstart-1y
yearend-1y yearend-1y
monthstart-1d monthstart-1d
monthend+1d monthend+1d
2022-01-31 2022-01-31
Report End Date (yyyy-MM-dd) Maximum date range: 31 days The end date for the data to retrieve in YYYY-MM-DD format. Supported functions now|today|yesterday|weekstart|weekend|monthstart|monthend|yearstart|yearend and supported intervals for add/subtract are ms|s|sec|min|h|hour|y|year|d|day|m|month|y|year. Example monthstart-3d (subtract 3 days from month start)
Option Value
today today
yesterday yesterday
monthstart monthstart
monthend monthend
yearstart yearstart
yearend yearend
weekstart weekstart
weekend weekend
yearstart-1y yearstart-1y
yearend-1y yearend-1y
monthstart-1d monthstart-1d
monthend+1d monthend+1d
2022-01-31 2022-01-31
Report Start Date (yyyy-MM-dd) Maximum date range: 731 days The start date for the data to retrieve in YYYY-MM-DD format. Supported functions now|today|yesterday|weekstart|weekend|monthstart|monthend|yearstart|yearend and supported intervals for add/subtract are ms|s|sec|min|h|hour|y|year|d|day|m|month|y|year. Example monthstart-3d (subtract 3 days from month start)
Option Value
today today
yesterday yesterday
monthstart monthstart
monthend monthend
yearstart yearstart
yearend yearend
weekstart weekstart
weekend weekend
yearstart-1y yearstart-1y
yearend-1y yearend-1y
monthstart-1d monthstart-1d
monthend+1d monthend+1d
2022-01-31 2022-01-31
Report End Date (yyyy-MM-dd) Maximum date range: 731 days The end date for the data to retrieve in YYYY-MM-DD format. Supported functions now|today|yesterday|weekstart|weekend|monthstart|monthend|yearstart|yearend and supported intervals for add/subtract are ms|s|sec|min|h|hour|y|year|d|day|m|month|y|year. Example monthstart-3d (subtract 3 days from month start)
Option Value
today today
yesterday yesterday
monthstart monthstart
monthend monthend
yearstart yearstart
yearend yearend
weekstart weekstart
weekend weekend
yearstart-1y yearstart-1y
yearend-1y yearend-1y
monthstart-1d monthstart-1d
monthend+1d monthend+1d
2022-01-31 2022-01-31
Metrics
Option Value
impressions impressions
clicks clicks
cost cost
purchases1d purchases1d
purchases7d purchases7d
purchases14d purchases14d
purchases30d purchases30d
purchasesSameSku1d purchasesSameSku1d
purchasesSameSku7d purchasesSameSku7d
purchasesSameSku14d purchasesSameSku14d
purchasesSameSku30d purchasesSameSku30d
unitsSoldClicks1d unitsSoldClicks1d
unitsSoldClicks7d unitsSoldClicks7d
unitsSoldClicks14d unitsSoldClicks14d
unitsSoldClicks30d unitsSoldClicks30d
sales1d sales1d
sales7d sales7d
sales14d sales14d
sales30d sales30d
attributedSalesSameSku1d attributedSalesSameSku1d
attributedSalesSameSku7d attributedSalesSameSku7d
attributedSalesSameSku14d attributedSalesSameSku14d
attributedSalesSameSku30d attributedSalesSameSku30d
unitsSoldSameSku1d unitsSoldSameSku1d
unitsSoldSameSku7d unitsSoldSameSku7d
unitsSoldSameSku14d unitsSoldSameSku14d
unitsSoldSameSku30d unitsSoldSameSku30d
kindleEditionNormalizedPagesRead14d kindleEditionNormalizedPagesRead14d
kindleEditionNormalizedPagesRoyalties14d kindleEditionNormalizedPagesRoyalties14d
date date
startDate startDate
endDate endDate
campaignBiddingStrategy campaignBiddingStrategy
costPerClick costPerClick
clickThroughRate clickThroughRate
spend spend
campaignName campaignName
campaignId campaignId
campaignStatus campaignStatus
campaignBudgetAmount campaignBudgetAmount
campaignBudgetType campaignBudgetType
campaignRuleBasedBudgetAmount campaignRuleBasedBudgetAmount
campaignApplicableBudgetRuleId campaignApplicableBudgetRuleId
campaignApplicableBudgetRuleName campaignApplicableBudgetRuleName
campaignBudgetCurrencyCode campaignBudgetCurrencyCode
topOfSearchImpressionShare topOfSearchImpressionShare
Metrics
Option Value
impressions impressions
clicks clicks
cost cost
purchases1d purchases1d
purchases7d purchases7d
purchases14d purchases14d
purchases30d purchases30d
purchasesSameSku1d purchasesSameSku1d
purchasesSameSku7d purchasesSameSku7d
purchasesSameSku14d purchasesSameSku14d
purchasesSameSku30d purchasesSameSku30d
unitsSoldClicks1d unitsSoldClicks1d
unitsSoldClicks7d unitsSoldClicks7d
unitsSoldClicks14d unitsSoldClicks14d
unitsSoldClicks30d unitsSoldClicks30d
sales1d sales1d
sales7d sales7d
sales14d sales14d
sales30d sales30d
attributedSalesSameSku1d attributedSalesSameSku1d
attributedSalesSameSku7d attributedSalesSameSku7d
attributedSalesSameSku14d attributedSalesSameSku14d
attributedSalesSameSku30d attributedSalesSameSku30d
unitsSoldSameSku1d unitsSoldSameSku1d
unitsSoldSameSku7d unitsSoldSameSku7d
unitsSoldSameSku14d unitsSoldSameSku14d
unitsSoldSameSku30d unitsSoldSameSku30d
kindleEditionNormalizedPagesRead14d kindleEditionNormalizedPagesRead14d
kindleEditionNormalizedPagesRoyalties14d kindleEditionNormalizedPagesRoyalties14d
date date
startDate startDate
endDate endDate
campaignBiddingStrategy campaignBiddingStrategy
costPerClick costPerClick
clickThroughRate clickThroughRate
spend spend
adGroupName adGroupName
adGroupId adGroupId
adStatus adStatus
Metrics
Option Value
impressions impressions
clicks clicks
cost cost
purchases1d purchases1d
purchases7d purchases7d
purchases14d purchases14d
purchases30d purchases30d
purchasesSameSku1d purchasesSameSku1d
purchasesSameSku7d purchasesSameSku7d
purchasesSameSku14d purchasesSameSku14d
purchasesSameSku30d purchasesSameSku30d
unitsSoldClicks1d unitsSoldClicks1d
unitsSoldClicks7d unitsSoldClicks7d
unitsSoldClicks14d unitsSoldClicks14d
unitsSoldClicks30d unitsSoldClicks30d
sales1d sales1d
sales7d sales7d
sales14d sales14d
sales30d sales30d
attributedSalesSameSku1d attributedSalesSameSku1d
attributedSalesSameSku7d attributedSalesSameSku7d
attributedSalesSameSku14d attributedSalesSameSku14d
attributedSalesSameSku30d attributedSalesSameSku30d
unitsSoldSameSku1d unitsSoldSameSku1d
unitsSoldSameSku7d unitsSoldSameSku7d
unitsSoldSameSku14d unitsSoldSameSku14d
unitsSoldSameSku30d unitsSoldSameSku30d
kindleEditionNormalizedPagesRead14d kindleEditionNormalizedPagesRead14d
kindleEditionNormalizedPagesRoyalties14d kindleEditionNormalizedPagesRoyalties14d
date date
startDate startDate
endDate endDate
campaignBiddingStrategy campaignBiddingStrategy
costPerClick costPerClick
clickThroughRate clickThroughRate
spend spend
placementClassification placementClassification
Metrics
Option Value
impressions impressions
clicks clicks
costPerClick costPerClick
clickThroughRate clickThroughRate
cost cost
purchases1d purchases1d
purchases7d purchases7d
purchases14d purchases14d
purchases30d purchases30d
purchasesSameSku1d purchasesSameSku1d
purchasesSameSku7d purchasesSameSku7d
purchasesSameSku14d purchasesSameSku14d
purchasesSameSku30d purchasesSameSku30d
unitsSoldClicks1d unitsSoldClicks1d
unitsSoldClicks7d unitsSoldClicks7d
unitsSoldClicks14d unitsSoldClicks14d
unitsSoldClicks30d unitsSoldClicks30d
sales1d sales1d
sales7d sales7d
sales14d sales14d
sales30d sales30d
attributedSalesSameSku1d attributedSalesSameSku1d
attributedSalesSameSku7d attributedSalesSameSku7d
attributedSalesSameSku14d attributedSalesSameSku14d
attributedSalesSameSku30d attributedSalesSameSku30d
unitsSoldSameSku1d unitsSoldSameSku1d
unitsSoldSameSku7d unitsSoldSameSku7d
unitsSoldSameSku14d unitsSoldSameSku14d
unitsSoldSameSku30d unitsSoldSameSku30d
kindleEditionNormalizedPagesRead14d kindleEditionNormalizedPagesRead14d
kindleEditionNormalizedPagesRoyalties14d kindleEditionNormalizedPagesRoyalties14d
salesOtherSku7d salesOtherSku7d
unitsSoldOtherSku7d unitsSoldOtherSku7d
acosClicks7d acosClicks7d
acosClicks14d acosClicks14d
roasClicks7d roasClicks7d
roasClicks14d roasClicks14d
keywordId keywordId
keyword keyword
campaignBudgetCurrencyCode campaignBudgetCurrencyCode
date date
startDate startDate
endDate endDate
portfolioId portfolioId
campaignName campaignName
campaignId campaignId
campaignBudgetType campaignBudgetType
campaignBudgetAmount campaignBudgetAmount
campaignStatus campaignStatus
keywordBid keywordBid
adGroupName adGroupName
adGroupId adGroupId
keywordType keywordType
matchType matchType
targeting targeting
topOfSearchImpressionShare topOfSearchImpressionShare
adKeywordStatus adKeywordStatus
Metrics
Option Value
impressions impressions
clicks clicks
costPerClick costPerClick
clickThroughRate clickThroughRate
cost cost
purchases1d purchases1d
purchases7d purchases7d
purchases14d purchases14d
purchases30d purchases30d
purchasesSameSku1d purchasesSameSku1d
purchasesSameSku7d purchasesSameSku7d
purchasesSameSku14d purchasesSameSku14d
purchasesSameSku30d purchasesSameSku30d
unitsSoldClicks1d unitsSoldClicks1d
unitsSoldClicks7d unitsSoldClicks7d
unitsSoldClicks14d unitsSoldClicks14d
unitsSoldClicks30d unitsSoldClicks30d
sales1d sales1d
sales7d sales7d
sales14d sales14d
sales30d sales30d
attributedSalesSameSku1d attributedSalesSameSku1d
attributedSalesSameSku7d attributedSalesSameSku7d
attributedSalesSameSku14d attributedSalesSameSku14d
attributedSalesSameSku30d attributedSalesSameSku30d
unitsSoldSameSku1d unitsSoldSameSku1d
unitsSoldSameSku7d unitsSoldSameSku7d
unitsSoldSameSku14d unitsSoldSameSku14d
unitsSoldSameSku30d unitsSoldSameSku30d
kindleEditionNormalizedPagesRead14d kindleEditionNormalizedPagesRead14d
kindleEditionNormalizedPagesRoyalties14d kindleEditionNormalizedPagesRoyalties14d
salesOtherSku7d salesOtherSku7d
unitsSoldOtherSku7d unitsSoldOtherSku7d
acosClicks7d acosClicks7d
acosClicks14d acosClicks14d
roasClicks7d roasClicks7d
roasClicks14d roasClicks14d
keywordId keywordId
keyword keyword
campaignBudgetCurrencyCode campaignBudgetCurrencyCode
date date
startDate startDate
endDate endDate
portfolioId portfolioId
searchTerm searchTerm
campaignName campaignName
campaignId campaignId
campaignBudgetType campaignBudgetType
campaignBudgetAmount campaignBudgetAmount
campaignStatus campaignStatus
keywordBid keywordBid
adGroupName adGroupName
adGroupId adGroupId
keywordType keywordType
matchType matchType
targeting targeting
adKeywordStatus adKeywordStatus
Metrics
Option Value
date date
startDate startDate
endDate endDate
campaignName campaignName
campaignId campaignId
adGroupName adGroupName
adGroupId adGroupId
adId adId
portfolioId portfolioId
impressions impressions
clicks clicks
costPerClick costPerClick
clickThroughRate clickThroughRate
cost cost
spend spend
campaignBudgetCurrencyCode campaignBudgetCurrencyCode
campaignBudgetAmount campaignBudgetAmount
campaignBudgetType campaignBudgetType
campaignStatus campaignStatus
advertisedAsin advertisedAsin
advertisedSku advertisedSku
purchases1d purchases1d
purchases7d purchases7d
purchases14d purchases14d
purchases30d purchases30d
purchasesSameSku1d purchasesSameSku1d
purchasesSameSku7d purchasesSameSku7d
purchasesSameSku14d purchasesSameSku14d
purchasesSameSku30d purchasesSameSku30d
unitsSoldClicks1d unitsSoldClicks1d
unitsSoldClicks7d unitsSoldClicks7d
unitsSoldClicks14d unitsSoldClicks14d
unitsSoldClicks30d unitsSoldClicks30d
sales1d sales1d
sales7d sales7d
sales14d sales14d
sales30d sales30d
attributedSalesSameSku1d attributedSalesSameSku1d
attributedSalesSameSku7d attributedSalesSameSku7d
attributedSalesSameSku14d attributedSalesSameSku14d
attributedSalesSameSku30d attributedSalesSameSku30d
salesOtherSku7d salesOtherSku7d
unitsSoldSameSku1d unitsSoldSameSku1d
unitsSoldSameSku7d unitsSoldSameSku7d
unitsSoldSameSku14d unitsSoldSameSku14d
unitsSoldSameSku30d unitsSoldSameSku30d
unitsSoldOtherSku7d unitsSoldOtherSku7d
kindleEditionNormalizedPagesRead14d kindleEditionNormalizedPagesRead14d
kindleEditionNormalizedPagesRoyalties14d kindleEditionNormalizedPagesRoyalties14d
acosClicks7d acosClicks7d
acosClicks14d acosClicks14d
roasClicks7d roasClicks7d
roasClicks14d roasClicks14d
 Generic Request
This is generic endpoint. Use this endpoint when some actions are not implemented by connector. Just enter partial URL (Required), Body, Method, Header etc. Most parameters are optional except URL.    [Read more...]
Parameter Description
Url API URL goes here. You can enter full URL or Partial URL relative to Base URL. If it is full URL then domain name must be part of ServiceURL or part of TrustedDomains
Body Request Body content goes here
IsMultiPart Check this option if you want to upload file(s) (i.e. POST RAW file data) or send data using Multi-Part encoding method (i.e. Content-Type: multipart/form-data). Multi-Part request allows you to mix key/value and upload files in same request. On the other hand raw upload allows only single file upload (without any key/value) ==== Raw Upload (Content-Type: application/octet-stream) ===== To upload single file in raw mode check this option and specify full file path starting with @ sign in the Body (e.g. @c:\data\myfile.zip ) ==== Form-Data / Multipart Upload (Content-Type: multipart/form-data) ===== To treat your Request data as multi part fields you must specify key/value pairs separated by new lines into RequestData field (i.e. Body). Each key value pair is entered on new-line and key/value are separated using equal sign (=). Preceding and trailing spaces are ignored also blank lines are ignored. If field value has some any special character(s) then use escape sequence (e.g. For NewLine: \r\n, For Tab: \t, For at (@): \@). When value of any field starts with at sign (@) its automatically treated as File you want to upload. By default file content type is determined based on extension however you can supply content type manually for any field using this way [ YourFileFieldName.Content-Type=some-content-type ]. By default File Upload Field always includes Content-Type in the request (non file fields do not have content-type by default unless you supply manually). For some reason if you dont want to use Content-Type header in your request then supply blank Content-Type to exclude this header altogather [e.g. SomeFieldName.Content-Type= ]. In below example we have supplied Content-Type for file2 and SomeField1, all other fields are using default content-type. See below Example of uploading multiple files along with additional fields. If some API requires you to pass Content-Type: multipart/form-data rather than multipart/form-data then manually set Request Header =&gt; Content-Type: multipart/mixed (it must starts with multipart/ else will be ignored). file1=@c:\data\Myfile1.txt file2=@c:\data\Myfile2.json file2.Content-Type=application/json SomeField1=aaaaaaa SomeField1.Content-Type=text/plain SomeField2=12345 SomeFieldWithNewLineAndTab=This is line1\r\nThis is line2\r\nThis is \ttab \ttab \ttab SomeFieldStartingWithAtSign=\@MyTwitterHandle
Filter Enter filter to extract array from response. Example: $.rows[*] --OR-- $.customers[*].orders[*]. Check your response document and find out hierarchy you like to extract
Headers Headers for Request. To enter multiple headers use double pipe or new line after each {header-name}:{value} pair

Amazon Ads Connector Examples for Informatica Connection

This page offers a collection of SQL examples designed for seamless integration with the ZappySys API ODBC Driver under ODBC Data Source (36/64) or ZappySys Data Gateway, enhancing your ability to connect and interact with Prebuilt Connectors effectively.

There are no examples


Other App Integration scenarios for Amazon Ads

Other Connectors for Informatica


Download Amazon Ads Connector for Informatica Documentation 

  • How to connect Amazon Ads in Informatica?

  • How to get Amazon Ads data in Informatica?

  • How to read Amazon Ads data in Informatica?

  • How to load Amazon Ads data in Informatica?

  • How to import Amazon Ads data in Informatica?

  • How to pull Amazon Ads data in Informatica?

  • How to push data to Amazon Ads in Informatica?

  • How to write data to Amazon Ads in Informatica?

  • How to POST data to Amazon Ads in Informatica?

  • Call Amazon Ads API in Informatica

  • Consume Amazon Ads API in Informatica

  • Amazon Ads Informatica Automate

  • Amazon Ads Informatica Integration

  • Integration Amazon Ads in Informatica

  • Consume real-time Amazon Ads data in Informatica

  • Consume realtime Amazon Ads API data in Informatica

  • Amazon Ads ODBC Driver | ODBC Driver for Amazon Ads | ODBC Amazon Ads Driver | SSIS Amazon Ads Source | SSIS Amazon Ads Destination

  • Connect Amazon Ads in Informatica

  • Load Amazon Ads in Informatica

  • Load Amazon Ads data in Informatica

  • Read Amazon Ads data in Informatica

  • Amazon Ads API Call in Informatica