most of streams in Facebook marketing not working good | update Facebook marketing API field to be appropriate with API 19

[eslamaboushashaa]

Note from @aaronsteers (maintainer):

Duplicate of:

• [source-facebook-marketing] fields are not valid for fields param after V19.0 airbyte#35334

Pull request pending:

• 🚨🚨 Source Facebook Marketing: update API to v19.0 airbyte#35746

---

Original issue description:

I received an error message as some fields that I was trying to access do not exist in the Facebook API V-19.
I got these fields

• age_targeting
• gender_targeting
• labels, location
• estimated_ad_recall_rate_lower_bound
• estimated_ad_recall_rate_upper_bound
• estimated_ad_recallers_lower_bound
• estimated_ad_recallers_upper_bound

Full error
Error: 100, (#100) age_targeting, gender_targeting, labels, location, estimated_ad_recall_rate_lower_bound, estimated_ad_recall_rate_upper_bound, estimated_ad_recallers_lower_bound, estimated_ad_recallers_upper_bound are not valid for fields param after V19.0.

[aaronsteers]

@eslamaboushashaa - Thanks very much for reporting this issue. As a first step, we will see if I can reproduce this error.

Do you have a PyAirbyte code sample that can share with us? It is helpful if you include the "config" entry - removing or redacting any secrets, of course.

Also - were you able to find any workaround as of yet, or is this a blocker for you?

Thanks again!

---

Update:

Attaching here a notice of these fields deprecated as of Marketing API v0.19.0, dated Jan 23, 2024.

[aaronsteers]

@eslamaboushashaa - It looks like we have an issue open for this:

• [source-facebook-marketing] fields are not valid for fields param after V19.0 airbyte#35334

cc @marcosmarxm

[aaronsteers]

I found an open PR here:

• 🚨🚨 Source Facebook Marketing: update API to v19.0 airbyte#35746

Was approved yestersday, expected to merge and release soon.

[aaronsteers]

Closing (dedupe), in favor of:

• [source-facebook-marketing] fields are not valid for fields param after V19.0 airbyte#35334

as primary.

Please upvote that issue to get updates, and/or re-open if this is still needed to be separately tracked.

Thanks again for logging. Hopefully will close out with successful resolution very soon.