Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: Fivetran Cost Per Result field in insights reports

Planned
Ariel David Jančar User

We're inquiring about the feasibility to ingest the objective_results, objective_result_rate and cost_per_result fields from the Facebook's Insights API, in all default and custom reports for the Facebook Ads connector.

Ingesting this field is imperative for us, as we're trying to move to a more general method of modeling ad performance, which is governed by the ad set's selected objective. These fields allow for modeling ad performance in a uniform manner, and act as a source of truth for our goals.

Documentation link (Facebook): https://developers.facebook.com/docs/marketing-api/reference/ad-account/insights/

Please sign in to leave a comment.

Comments

7 comments

Date Votes
  • Official comment
    Lucas Alexander Fivetranner
    • Edited

    Hi Vid, 

    Thanks for following up on this and for the reminder – we added support for these three fields in December 2025. I forgot to update this post, but we included an announcement in our December release notes: https://fivetran.com/docs/connectors/applications/facebook-ads/changelog#december2025. 

    • We now support the following fields in our custom report tables:

      • objective_results
      • objective_result_rate
      • cost_per_result

    • When the objective_results field is selected in a custom report, it is represented in the schema as a child table with the suffix _objective_results (for example, your_report_name_objective_results). This child table contains the following columns:

      Primary Key Columns:

      • _fivetran_id - Unique identifier of the parent record
      • date - Date of the report aggregation (for aggregations Day, Lifetime)
      • week - Week of the report aggregation (for aggregation Week)
      • month - Month of the report aggregation (for aggregation Month)
      • indicator - Type of objective result (for example, link_click, post_engagement, lead)
      • attribution_window - Attribution window for the result (for example, 1d_click, 7d_click, 28d_click)
      • Level ID column - The ID of the level being reported on (the column name depends on the report level: ad_id, adset_id, campaign_id, or account_id)

      Data Columns:

      • value - Numeric value of the objective result

    I marked this feature request as completed. Let me know if you have any questions!

    Cheers,
    Luke

  • Lucas Alexander Fivetranner
    • Edited

    Hi Ariel,

    Luke from the Product team here. Thanks for submitting this feature request!

    I've added this to the backlog. I'm unsure why we don't already support these fields, but I'll check with the team. 

    We would start by supporting these fields for custom reports. We would only add these to prebuilt reports if there is significant customer demand for them to be added there. Prebuilt reports are shared by all customers. We are very selective about which fields we add to those tables because it impacts everyone. However, supporting these fields in custom reports for anyone to use makes sense.

    Cheers,
    Luke

  • Ariel David Jančar User
    • Edited

    Hi Lucas,

    We appreciate the response, and are awaiting its implementation. It is understandable that it may be just a bit too soon, but should you already know of any ETAs (or once you will) they would be appreciated even further!

    Otherwise, we will just keep track of the status of this ticket.

    Thanks for the quick feedback, as well as the immediate action by moving the request into the backlog.

     

    Best regards,

    Ariel

  • Ariel David Jančar User
    • Edited

    Hi,

    We are just pinging for any status updates regarding this field (Cost per result).

    We would also want to emphasize that there is a related metric here - Result rate.

    Was there any progress done on this part, or should anyone looking to rely on this metric look for other solutions? Do you have any ETAs for this feature otherwise?

    Thanks!

    Ariel David Jančar

  • Vid Stropnik User

    Hi @Lucas Alexander,

    Is there any news regarding an ETA for these fields in custom connectors? Using these fields (instead of manually mapping to individual actions currently available in the custom reports) is of really high value for our team. We would love to plan accordingly. 

     

    Best,

    Vid Stropnik

  • Lucas Alexander Fivetranner
    • Edited

    Hi all,

    Sorry for the delay on this. I understand it's important to your business.

    We have this assigned to the current quarter and hope to start work on it soon. I'll let you know once it is assigned to a sprint and development has started.

    Best, 
    Luke

  • Vid Stropnik User

    Hi Luke,

    Any news regarding this issue, as we've rolled over into the next quarter?

    This remains a very relevant and valuable feature for our business.

     

    Regards,

    Vid S