- Patryk Marek
- News
- 0 likes
- 777 views
- 0 comments
If events from PrestaShop do not match products in the Meta catalog, compare the full offer identifier with the value sent in content_ids. The prefix, separator, and combination number all matter. For the integration, the identifiers 812, ps_812-41, and ps_812_41 mean different strings, even though a person may associate them with the same product card.

This guide helps verify the cooperation between the product feed and the Pixel. The example of product 812 is for demonstration purposes. A separate section describes our own test on PrestaDev.pl; both examples do not contain customer data. They are not a screenshot from an advertising account or confirmation of campaign results.
The catalog, Pixel, and Conversions API perform different tasks
The catalog contains offers: identifiers, names, images, prices, and availability. The feed is one of the ways to deliver this data. The Pixel sends events from the browser, such as a product view or add to cart. The Conversions API allows events to be sent from the server side.
A correctly fetched catalog does not prove that events refer to the correct offers. Likewise, the presence of a purchase event does not prove that every product from that purchase has a match in the catalog. First determine which part of the connection you are diagnosing.
Also check whether you are viewing the correct catalog and the correct event source. With several stores, an old Pixel, or a test feed, you may be comparing technically correct data coming from different configurations.
Example: one product, two combinations
Let us assume a product with ID 812 and combinations 41 and 42. The feed exports variants as separate offers with the ps_ prefix and a hyphen. For the first combination, the identifier is therefore ps_812-41.
| Place | Combination 41 | Combination 42 | What you compare |
|---|---|---|---|
| PrestaShop | Product 812, combination 41. | Product 812, combination 42. | The identity of the product and the selected variant. |
Feed: g:id | ps_812-41 | ps_812-42 | The identifier of a specific offer in the catalog. |
Event: content_ids | ["ps_812-41"] | ["ps_812-42"] | Whether it points to the offer corresponding to the user's action. |
| Group in the sample feed | 812 | 812 | The shared variant group; it does not automatically replace the offer ID. |
The simplest check is to copy the value from the processed offer and the event into two rows. Compare them character by character. Do not remove the “unnecessary” prefix until you determine what the other integrations refer to.
What was checked in the PrestaDev modules?
In the code of Facebook Pixel Pro 1.4.5, there is a choice of how to build the ID and an optional prefix. One path creates a product ID combined with the combination ID using a hyphen, another uses an underscore. There are also modes based on other fields. This is a configuration that must be compared with the actual export, not selected solely by name.
The checked code of Meta feed 2.9.2 saves g:id during combination export in the form prefix + product ID + hyphen + combination ID. For this setting, the variant ps_812_41 sent by the Pixel will not be identical to ps_812-41 in the feed. In this path, the feed saves the shared g:item_group_id as the product ID without a prefix.
This confirms the way data is built in the listed code versions, not proof of matching on a specific Meta account. After changing settings, you still need to check the generated file, the catalog import, and the actual event.
Own test: ID in the feed and ViewContent on two product pages
Test from 27 September 2026, PrestaDev.pl. The public Meta feed contained 107 offers with base product identifiers. For two product pages, we compared the ID, the price after applying the promotion (sale_price), and the currency from the file with the data prepared by the Pixel script when the page was opened. The amounts below describe the moment of the test, not the current price list.
| Product | ID in the feed and local ViewContent | Value / currency |
|---|---|---|
| Facebook Pixel Pro | 131 | 70,00 PLN |
| Omnibus | 310 | 139,30 PLN |
We performed the test in two separate guest sessions in Chromium. Instead of the Meta library, we used a local receiver for fbq calls; requests to external domains were blocked. At the checkpoint before marketing consent, the receiver did not record ViewContent. After accepting consent and reloading each page, it received one ViewContent with the above data and content_type: "product". This is a check of the data prepared in the browser, without sending those fbq calls from the browser to Meta.
Important limitation: we did not switch to the license renewal option. This option was disabled for guests and required logging in with the appropriate permission. Reading the variant data showed the same base ID with a different amount. Therefore, a matching ID alone does not prove that the catalog distinguishes between the full license and the renewal; you still need to determine the intended offer model.
The full variant scenario remained uncaptured. The test did not include add to cart, purchase, deduplication, CAPI, or Meta’s acceptance of events or the catalog. The result applies to this store configuration; it does not confirm operation in all PrestaShop versions and themes. In this test, the exact environment version numbers were not recorded. In your own capture, record the store, theme, browser, and both module versions, then compare the imported offer and the event in Meta tools.
content_ids and content_type must be consistent
content_ids contains identifiers related to the event. content_type defines how the reference to products or their groups should be interpreted. You should not change product to product_group just to make the message disappear: this changes the meaning of the identifiers the event refers to.
In the demonstration example of product 812, we select a specific variant offer and content_type: "product". A simplified data set for viewing a variant looks like this:
{
"content_ids": ["ps_812-41"],
"content_type": "product",
"value": 129.00,
"currency": "PLN"
}
This is a fragment of sample event data, not complete implementation code or an API request. The field types of content_ids, content_type, value, and currency can be checked in the official Meta SDK — CustomData. When diagnosing a specific account, also check the current messages in Events Manager.
After changing the variant, perform a new test
A correct ID on the first page load is not enough. The theme may change the variant without reloading the document. The event integration should use data corresponding to the current action, instead of remaining on the default combination.
- Select a product with at least two combinations present in the feed.
- Save their full identifiers from the file and from the catalog after import.
- Open the product in a controlled test session, with the correct consent settings.
- Check the event data for the first variant.
- Change the combination and add the selected variant to the cart.
- Compare the event ID, quantity, value, and currency with the current cart.
- Check whether the same action is also being sent by a second Pixel installation, for example through another module or tag manager.
Do not interpret the absence of an event as a catalog error before checking consent, script blocking, and the event source configuration. Sending data through the server also requires proper privacy configuration; CAPI should not be treated as a way to bypass the user's decision.
Value and currency are a separate check
An identical ID does not confirm the correct amount. For a product event, check the price of the selected combination, and for a purchase, the agreed definition of the value of the entire order. Do not compare a single item with the cart total or a net amount with a gross amount without determining how the implementation works.
The currency must match the sent value. In a multi-currency store, perform a separate test after changing it. If the data comes from an order, compare it with the saved order, not with the current catalog price read later.
Product matching vs purchase deduplication
Deduplication recognizes two copies of the same event sent from the browser and the server. It is not used to merge product variants. The official Meta SDK states that for corresponding events, the browser eventID should match the server event_id, and the event name is also used in the process. Source: Meta — Event description and setEventId.
| Identifier | Demonstration example | What it should identify |
|---|---|---|
content_ids | ["ps_812-41"] | The product or variant related to the action. |
eventID / event_id | purchase_demo_1001 | One specific purchase event sent through two channels. |
A fixed event_id equal to the product ID would be an inappropriate idea for different purchases of that product. On the other hand, matching event identifiers will not fix incorrect content_ids. Check these two things separately. If you are also analyzing GA4, use the existing guide on purchase measurement.
Where to start improving the integration?
Select one product and keep three pieces of data: the ID in the store, the ID imported into the catalog, and the ID from the event. Determine the format, change the correct setting, refresh the required source, and repeat the test. Do not change the prefix, separator, variant export method, and several Pixel installations at the same time — this will make it harder to determine which correction solved the problem.
Check the consistency of the ID format in both integrations: Facebook Pixel Pro and XML product feed for Meta. Their configuration should result from the same catalog model. Correct matching is an element of data quality, not a guarantee of advertising profitability.
Substantive verification: 13 September 2026. Checked: Facebook Pixel Pro 1.4.5 code, Meta feed 2.9.2, and public definitions in the official Meta SDK. No publication or test purchase was performed on a client advertising account.
Check CAPI conditions before analyzing a missing purchase
In the checked code of Facebook Pixel Pro 1.4.6, the CAPI path requires the function to be enabled, a valid Pixel ID, Access Token, and the correct order status. It also verifies an active PD Cookie Pro in the order store and the current consent record linked to the cart. A correct product identifier alone does not meet these conditions.
Start by comparing the configuration of the Pixel offer with the version in use. Then check consent, the conditions for triggering the send, and Meta’s response for the controlled event. The absence of CAPI does not automatically mean a catalog mapping error; this is a separate control point.
Comments (0)