Full Changelog: https://github.com/facebook/facebook-python-business-sdk/compare/19.0.3...20.0.0

Full Changelog: https://github.com/facebook/facebook-python-business-sdk/compare/19.0.1...19.0.2

Hello again! Apologies for the delay in rolling out this minor version update. Your patience is to be rewarded! We're offering much more than you might expect from a typical minor version bump.

Full Changelog: https://github.com/facebook/facebook-python-business-sdk/compare/19.0.0...19.0.1

Happy New Year! As of January 23, 2024, we are thrilled to announce the release of Meta Business SDK v19.0, which now supports [Graph API v19.0 and Marketing API v19.0]. Due to the code freeze in December, we bypassed the minor version increments for v18.0. However, during this period, our developers remained actively engaged in our community, submitting issues and pull requests. While we updated the [Changelog] to include all API interface changes, you can access comprehensive code modifications in our repositories.

Full Changelog: https://github.com/facebook/facebook-python-business-sdk/compare/18.0.5...19.0.0

18.0.4..18.0.5

18.0.3..18.0.4

18.0.2..18.0.3

18.0.1..18.0.2

🐛 Bug Fix 🔨 Address Python Single Quote Escape Issue https://github.com/facebook/facebook-python-business-sdk/commit/22d7355fbe25b390ca4936684140b124ddb024a9

18.0.0..18.0.1

Introducing Meta Business SDK v18.0 for Python

Time flies. Today, (September 15, 2023) we’re announcing the release of Meta Business SDK v18.0 to support the [Graph API v18.0 and Marketing API v18.0]. It represents a major update which addresses numerous longstanding issues and expands support to additional features, nodes, and types. While you can find a comprehensive list of changes in our [Chagnelog], here are also following notable SDK-only updates that we believe are relevant to our developer community.

• AdAssetFeedSpecAssetCustomizationRule and AdAssetMessageExtensions Support: Developer is able to Get a list of structuralized AdAssetFeedSpecAssetCustomizationRule and AdAssetMessageExtensions objects from AdAssetFeedSpec node.

• AdsHistogramStats Support: Developer is able to Get a list of structuralized AdsHistogramStats objects from multiple video play related metrics.

• BusinessImage, BusinessVideo, BusinessCreativeFolder Support: Developer is able to Post and Get these types of objects via Business node.

• Four Instagram Nodes Support: InstagramCarousel, InstagramComment, InstagramMedia, and InstagramUser are now available for developers to work on, including all POST and GET APIs.

• Multiple LeadGen Form Objects Support: Developer is able to work on multiple LeadGen Form related objects, including LeadGenContextCard, LeadGenCustomDisclaimer, LeadGenThankYouPage.

A full API spec change could be viewed here.

• Various bug fixes

See https://developers.facebook.com/docs/business-sdk/ for more details

In this release we named facebook python ads sdk to facebook python business sdk.
See https://developers.facebook.com/docs/business-sdk/ for more details

Changelog: https://developers.facebook.com/ads/blog/post/2017/07/18/marketing-api-2.10/

Changes in v2.8

New Features

• Instant Articles is now a separate ads placement, so that advertisers can enable or disable showing ads in Instant Articles. This new placement options is under /ACCOUNT_ID/adsets and /AD_SET_ID. See Targeting Specs. If you use this placement you must also select feed as a position and for device_platforms select mobile since Instant Articles is for mobile only.
• Facebook Offers is redesigned and is easier for people to save and redeem your offer from any device. If they don't use your offer, they'll get notifications about it before it expires. To use the API to create offers:
• Use /nativeoffers as an endpoint. The endpoint /offers is associated with the old product and has been deprecated.
• Use offer_id in the promoted_object for an ad set.
• To learn more see Offer Ads and Page Native Offers.

Breaking Changes

** Please Review These Changes

Ads Management

• As of 2.8, Website Custom Audiences now only allow at most 200 comparisons in the rule. The number of comparisons are the number of comparison operators in the rule.
• The place_page_set_id field under Ad creative is now optional for versions v2.7 and v2.6
  and has been deprecated in v2.8. See Ad Creative.
• offer_data under link_data for an ad object has been deprecated.
• The ad account group endpoints AdAccountGroup have been deprecated. To manage Ad Accounts, you should use Business Manager or Business Manager API with business_management extended permission.
• The edge AD_ACCOUNT/audiences has been deprecated.
• The ad_object_by_url field for /search in Ad Targeting Search has been deprecated.
• The fields actor_id, actor_image_hash, actor_image_url, and actor_name have been deprecated from ad creative GET.

Ads Insights

• We deprecated the redundant fields and parameters in /insights endpoint.
  In earlier releases it supported the params: fields,summary, default_summary, filtering and sort. However/insights should always exactly return what you queried in the POST requests.
• In earlier releases we will display all valid fields for /insights if you provided an invalid field as a parameter. We now send an the error message which points to a list of valid fields.
• In the past we inconsistently returned /insights fields in a variety of types: some fields were string such as impressions, some were numericstring, and some were float. We now return all numeric fields, including float as numericstring. All floating point numbers will maintain six precision points.
• The insights metric post_like in the actions field is now named post_reaction, see Ads Action Stats. This is more consistent with naming in user interfaces.

Business Manager

The owner_business field has been deprecated and no longer exists for objects connected to a business, including Ad accounts, Ad Campaign, Product Catalog, and Instagram User.

This is a new major release, which diverges in behavior from the previous one.
Please review these changes:

• New Daily Budget Limits: We changed the logic around ads delivery which impacts the interpretation of the daily ad budget limits. Starting from v2.7, you may be charged up to 125% of your daily budget. For example, if your daily budget is $10, you may be charged up to $12.50. However, your weekly spend will NOT exceed 7 times the daily amount, or $70 in this example. We will prorate this for partial weeks. More details Ad Set Budget.
• Lifetime Budgets and New Daily Budgets: Also, starting with v2.7, you can no longer edit ad sets created with the new daily budget controls to use lifetime budgets. Similarly you can no longer edit lifetime budgets to use the new daily budget controls.
• Ad Placements Update: We have improvements to our design of placement, so that advertisers can more easily identify and select placement options that will serve them best. Instead of having platform as the only dimension, advertisers can select placements across different dimensions, such as device type including desktop or mobile, publisher such as facebook, instagram, or audience_network, and placements of each publisher. Only Facebook has multiple placements currently. The field page_types will still be included in read results, but cannot be used to create or update placements in v2.7. More details in Targeting Spec.
• Insights Placement Updates: As a related change, on the /insights endpoints, we’ll introduce two new breakdowns options: publisher_platform and platform_position. Along with the existing impression_device breakdown, you can get performance metrics with these placement dimensions. See Insights Breakdowns for more details.
• Ad Creative Update: With 2.7 object_story_id will be null for an ad creative created with an object_story_spec. The effective_object_story_id will always be the object_story_id regardless of object_story_spec. More details in Ad Creative.
• Insights Integer Field: For Insights API, integer values were too big and overflowed with int32. We changed all int32 field values into numeric strings to keep consistent with other Marketing API fields with currency values. For v2.7 onward, numeric values in int32 will be quoted in responses. For v2.5 for backwards compatibility, numeric values in int32 will be shown as a number. More details in Ads Insights.

1. Allowing version to be passed in api call
2. Fixes to objects for batch call

1. Setup.py is the file which installs facebookads packages. Adding adobjects.helpers module to this.
2. Abstract crud updated for api instance to flow

1. Setup.py is the file which installs facebookads packages. Adding adobjects module to this.
2. api.py method open_files updated to be compatible with PY 2.6

1. The new SDK is an improved SDK version, autogenerated using our Marketing API. Hence there is greater coverage to features provided by our API.
2. The adobjects folder contains separate classes for every ad object and possible CRUD operation on these objects can be based on the presence/absence of api_create, api_get, api_update and api_delete methods.
3. This SDK also contains all the breaking changes for v2.6 API version and is compatible with the manual (legacy) SDK. The legacy branch contains the v2.6 version of the manual SDK. We will continue to maintain it till v2.7 is released.
4. The objects.py file is maintained only for compatibility to existing code, it is advisable to start using the individual files under the adobjects folder directly.

1. status is not a valid field under ad objects. It needs to be passed as a parameter during create/update calls
2. Fixing duplicaiton of Aggregation fields on AdsPixel class
3. Adding back the AdGroupPreview equivalent class and reaming AdPreview to GeneratePreview