Using Promo Feeds, you can add offer information to your product catalog to enable merchandising
your offers on Facebook and Instagram. For sellers with Facebook or Instagram checkout enabled,
buyers will be able to redeem your offers directly within the Facebook family of apps.
Glossary
Product Sets
A product set is a group of related items within a product catalog.
Offer Target Items
These are the products for which an offer is valid.
Offer Prerequisites
These are the prerequisites that need to be met for the offer to apply. For example, you can determine that the offer is only valid when people buy at least a specific number of products or reach at least a specific subtotal quantity or value of those products. Currently, the prerequisite products are derived from the target products. For example, an offer of 20% off all shoes means the minimum subtotal/quantity requirements must be met with shoes in the cart.
Offer Application Type
The Offer's application type specifies how an offer is applied at checkout either on your own website or within Facebook checkout. For instance, application type can be used to determine whether an offer is automatically applied at checkout or requires a coupon code to be redeemed. The application type also informs an offer's combination behavior with other offers.
Meta (Facebook) Promotions Feed Setup
- Create product sets in your Facebook catalog.
- Configure Mapping: Set the following fields when configuring offer types.
a) offer_id: This is the retailer's ID for the offer item. Required field.
b) title: A title for the offer item.
c) application_type: Determines how and when an offer is applied. Available options are:
- SALE: Items are directly marked down, reflected as strikethrough pricing for buyers. These offers require no prerequisites from the buyer and are not affected by other items at checkout. The sale producing the lowest price of an item is always chosen, as sales are never combined. Sales can be combined with other offer types but are always applied first. If a product already has the sale_price field set then the final price is computed using sale_price as the base price.
- AUTOMATIC_AT_CHECKOUT: The offer is automatically applied at checkout when the buyer meets the necessary redemption criteria. This offer has some configuration which prevents it from qualifying as a sale. It can only be combined with sale offers and currently only 1 such offer may be active at a time.
- BUYER_APPLIED: This offer is applied at checkout based on an action taken by the buyer, such as entering a promo code. These offers cannot currently be combined with each other or offers applied automatically at checkout. Requires one of [public_coupon_code, coupon_codes] to be provided.
d) coupon_codes: List of case-insensitive coupon codes that customers use at checkout to redeem the offer. Maximum of 100 coupon codes allowed. For example: ["10OFF", "HOLIDAY_SALE"]. Coupon codes may only be specified when the application_type is BUYER_APPLIED.
e) start_date_time: When the offer starts. This is an Unix timestamp. Required field.
f) end_date_time: When the offer ends. This is an Unix timestamp. If left empty or null, the offer has no end date.
g) target_filter: Filter rule to identify products that the offer can be applied to. Uses the same filter rule logic used for adding products to a product set. If this field is set, target_selection must be SPECIFIC_PRODUCTS and both target_filter and target_product_set_ids must be null.
h) target_granularity: The granularity at which the offer's discount is applied.
Available options are:
- ITEM_LEVEL: represents a discount applied to each of the target items in the cart.
- ORDER_LEVEL: represents a discount applied across all of the target items in the cart. For example, if you have a "$30 off shoes" offer with 3 pairs of shoes in the cart, ITEM_LEVEL will apply $30 off each pair of shoes ($90 value), while ORDER_LEVEL will apply $30 off the sum of all 3 pairs of shoes (max $30 value).
Note that offers with ORDER_LEVEL granularity may result in discount allocations at purchase that do not divide evenly across items in an order. Handling these uneven discount allocations may result in added complexity at fulfillment time or in case of refunds. For this reason, currently sellers using Facebook or Instagram checkout can only create ORDER_LEVEL offers if they manage their orders solely via Commerce Manager. Required field.
i) target_selection: This field is used to differentiate between offers which apply to an entire product catalog and offers restricted to a specific subset of items within a catalog.
Available options are:
- ALL_CATALOG_PRODUCTS: offer can be applied to any product in the catalog.
- SPECIFIC_PRODUCTS: offer can only be applied to the target products specified by target_filter, target_product_set_ids, or target_product_set_retailer_ids.
Required field.
j) value_type: The type of discount provided by the offer.
Available options are:
- FIXED_AMOUNT: applies a discount with the value taken from fixed_amount_off.
- PERCENTAGE: applies a percentage discount with the value taken from percent_off.
Required field.
k) target_product_set_ids: If target_selection is SPECIFIC_PRODUCTS, one of the following is required: target_filter, target_product_set_ids, or target_product_set_retailer_ids.
Facebook IDs for product sets containing items that the offer can be applied to. The offer will apply to the union of all products yielded by evaluating the specified product sets.
This field should only be set if target_selection is set to SPECIFIC_PRODUCTS.
If this field is set, target_selection must be SPECIFIC_PRODUCTS and both target_filter and target_product_set_retailer_ids must be null.
You can also use rules to set values for the promo fields.
Sample Feed File: This is a sample of the promo file generated by the feed.
When it comes to setting up a feed we suggest the following help articles that may assist you further in combination with this article on setting this up.
All-in-One feed setup Overview
If you have any additional questions regarding our Meta Promotions feed you can contact support for further assistance via support ticket or chat.
Related to
Comments
0 comments
Please sign in to leave a comment.