Using Components: Bing Ads Source

Use the Bing Ads source component to define the Bing Ads reporting source, and which fields will be used in the package.
Source components are always the first components in a package.

To define the Bing Ads source:

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

source settings

Define the source settings parameters:
  • connection - either click the dropdown arrow and select an existing Bing connection, or click create new to create a new connection (see Defining connections).
  • version - Xplenty will use the selected API version when running the job. Microsoft releases a new API version every few months and sunsets older versions of the API. You should check and update the API versions periodically.
  • accounts and campaigns - Select accounts (i.e. all campaigns in the account) or specific campaigns to report on.
  • report type - select the Bing report type. 
  • columns - Select dimensions and metrics from the dropdown list of columns. Make sure to select the required columns according to Bing Ads documentation (Click the report type, then click columns data type and see "Required columns").
  • unit of time - Select date/time granularity.
  • time period field name(s) - depending on the unit of time selected, time period fields will be added and you can change the field names. 
  • date range - Select a predefined date range or enter a custom date range. You can also use variables as values for the custom date range in the format yyyyMMdd.

report fields mapping

After defining the dimension and metrics source settings, the field names and data types will be populated. 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.

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
  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 components: Snowflake Destination (beta)
  40. Using and setting variables in your packages
  41. System and pre-defined variables
  42. Validating a package
  43. Using pattern-matching in source component paths
  44. Using ISO 8601 string functions
  45. Using Expressions in Xplenty
  46. Xplenty Functions

Feedback and Knowledge Base