Using components: Google AdWords Source

Use the Google AdWords source component to define which Google AdWords report to execute, and which fields will be used in the package.
Source components are always the first components in a package.

Note: Ad blockers may block html and javascript elements that mention AdWords. We recommend that you disable your ad blocker or make an exception for Xplenty.

To define the Google AdWords source:

  1. Add a Google AdWords source component to begin your dataflow.
  2. Open the component and name it.

source settings

Define the source settings parameters:
  • adwords connection - either click the dropdown arrow and select an existing connection, or click create new to create a new connection (see Defining connections).
  • api version - Xplenty will use the selected API version when running the job. Google releases a new API version every few months and sunsets older versions of the API. You should check and update the API versions periodically.
  • customer ids - A comma separated list of AdWords customer account ids, that appear in the top right corner of your AdWorks page or are managed by AdWords Manager (MCC). If you provide an MCC account's customer id, the report will be executed for all the AdWord accounts it has access to. Customer ids appear in the format nnn-nnn-nnnn (e.g. 123-456-7890)
  • customer id field name - Modify the name that will appear as the field for customer IDs.
  • report type - Select a report type from the dropdown list of reports. See this article to map reports to Google AdWords UI.
  • report fieldsSelect the report fields from the dropdown list of fields. They will be added to the fields list on the right where you can change the fields' aliases.
  • date range - Select a date range from the dropdown list of ranges. If you select custom, you will be prompted to enter the Start date and End date. Click on each date and select the date from the calendar. You can also use variables as values for the custom date range in the format yyyyMMdd.

Then click the Test Connection button to help check that the connection is good and that the customer ids exist.

report fields mapping

Use the report fields drop down to select fields. You can make these modifications to the list of fields:

  • Define how you will refer to these fields (alias) in the other components of your package. If you use illegal characters, we'll let you know before you close the dialog.
  • Remove report fields from the list.

Note: The Notes of some report fields under AdWords report descriptions state that the field is not compatible with other available fields. If you are including one of those fields, remove other report fields which are listed as not compatible with that field.

Note: Starting with API v201603, null values for string fields will be returned as two dashes (--).

Creating packages

  1. Creating a new package
  2. Create a package from a template
  3. Working in the package designer
  4. Using Components: Facebook Ads Insights Source (Beta)
  5. Using components: File Storage Source
  6. Using components: Database Source
  7. Using components: Google AdWords Source
  8. Using components: NetSuite Source
  9. Using Components: Google Analytics Source
  10. Using Components: Google BigQuery Source
  11. Using components: Google Cloud Spanner Source
  12. Using Components: Bing Ads Source
  13. Using components: MongoDB Source
  14. Using components: Amazon Redshift Source
  15. Using Components: Rest API Source
  16. Using Components: Salesforce Source
  17. Using components: Select
  18. Using components: Sort
  19. Using components: Rank
  20. Using components: Limit
  21. Using components: Sample
  22. Using components: Join
  23. Using components: Cross Join
  24. Using components: Clone
  25. Using components: Cube and Rollup
  26. Using components: Union
  27. Using components: Filter
  28. Using Components: Window
  29. Using components: Assert
  30. Using components: Aggregate
  31. Using components: Distinct
  32. Using components: File Storage Destination
  33. Using components: Amazon Redshift Destination
  34. Using Components: Salesforce Destination (Beta)
  35. Using components: Google BigQuery Destination
  36. Using components: Google Cloud Spanner Destination
  37. Using components: Database Destination
  38. Using components: MongoDB Destination
  39. Using and setting variables in your packages
  40. Validating a package
  41. Using pattern-matching in source component paths
  42. Using ISO 8601 string functions
  43. Using Expressions in Xplenty
  44. Xplenty Functions

Feedback and Knowledge Base