Using Components: Facebook Ads Insights Source (Beta)

Use the Facebook Ads Insights source component to define Facebook Ads Insights reports to use as a source in a data flow package.

To define the Facebook Ads Insights source:

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

source settings

Define the source settings parameters.
  • facebook 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. Facebook releases a new Facebook Marketing API version every few months and sunsets older versions of the API. You should check and update the API versions periodically.
  • accounts - Select the ad accounts to run the reports on. By default, the report will be executed in all ad accounts.
  • dimensions (optional) - Select dimensions from the dropdown list of dimensions.
  • fields - Select fields for the source to return from the report. The fields include dimensions, metrics and breakdowns. Action metrics are available in all attribution windows and include custom events as well.
  • level - Select the report level (ad by default).
  • date range - select a preset date range or custom date range. Using the custom date range, you may either use constant dates or variables whose values are in the format yyyy-MM-dd.
  • action report time - determines the report time of action stats (by impression by default). See Facebook Marketing APIs documentation for more details.
  • time breakdown - use to break the results by period. The default, "All days" means that one result will be returned for the entire period. Add the fields date_start and date_stop to get the period per record in the result.

Then click the Show Data Preview button to verify your report. Note that you if you report requires too much data, preview may fail, but the job will still succeed.

report field mapping

After selecting the fields to use in the report, you can change the alias to use as a field in the data-flow.

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