BaseLinker purchases to Meta, and products into a fixed feed
BaseLinker gathers orders from many places and often generates feeds, but along the way you cannot see what Meta and Google did with them. Basketly reads orders and products from BaseLinker through an API token. It sends Meta only the purchases from the sources you tick, and shows the products with a diagnosis.
The demo has sample data; the login comes to your e-mail.
Why BaseLinker needs separate attention
BaseLinker takes orders from the shop and from marketplaces. If you send Meta everything, you get purchases no ad could have caused. If you run a feed out of BaseLinker, you do not see along the way which products Google and Meta found faulty. Basketly separates the one from the other and shows both.
What Basketly does on BaseLinker
You give the shop address (the page purchases are reported under) and the account’s API token. The app does the rest.
- Saving the token checks it with an order sources call, and the connection dialog then lists the order statuses, order sources and product catalogues of your account.
- Orders confirmed in the last 7 days are read again every 15 minutes. An order where nothing changed (status, payment, total, items) is not saved again.
- A purchase from a ticked source becomes an event: value, currency, products from the lines (by the chosen field: product id, SKU or EAN), e-mail and phone (hashed before sending).
- Every purchase is saved first and then sent with retries. When Meta has an outage, the purchase waits instead of getting lost.
- Products from the chosen catalogue (name and description in the catalogue language, manufacturer, category, price of the default price group, stock over warehouses, first photo) land on the Products screen with a diagnosis for Google Merchant Center and the Meta catalogue.
- BaseLinker does not know the product page address, so products have no link, and the diagnosis says so plainly.
Connect BaseLinker in 4 steps
It takes a few minutes. You need no developer and no server access.
Copy the API token from BaseLinker
In BaseLinker open Moje konto → API and copy the token. It is not shown again in Basketly.
Connect the account in the app
In Basketly open Integrations, choose the BaseLinker tile and enter a name, the shop address and the token. In the connection dialog tick the bought statuses, the order sources that should go to Meta, the product catalogue and the id field, and confirm the legal basis.
Connect Meta
Sign in with your Meta account, choose the dataset (Pixel) and keep the purchase flow from the shop to Meta. The getting-started checklist in the app shows what is still missing.
Check the first purchase
Click “Fetch now”, send a Test event with the code from Events Manager and, after the first orders, open the purchase balance.
Order sources and cash on delivery
An order is bought when its “payment done” amount covers the total, or when it has a status you tick (for example for cash on delivery). An order is cancelled when its status contains “anulow” or “cancel”. Only bought orders from the ticked sources go to Meta. Keep Meta’s limit in mind: a purchase older than 7 days is not accepted.
Products and a feed with fixes
BaseLinker products appear in Products with their diagnosis, and in Feeds you can pick the BaseLinker shop as the input. From there the fixes, rules and Google categories work as for any feed, and you get the result at your own secret address to paste into Merchant Center or the Meta catalogue.
How to check that it works
- Test event: one click sends the newest shop purchase with the test code from Events Manager, and you see it under Test Events.
- Purchase balance: shop orders next to purchases Meta accepted, day by day, with the most common error reasons.
- Self-check: compares the dataset’s statistics in Meta with what was actually sent, and says what to fix.
- Orders: each order shows whether its purchase was accepted, failed or is waiting.
What it does not do
- It does not fix or replace the Pixel in the browser: events such as product views or add to cart stay on the shop side. It is a second, independent path for purchases.
- An order read from the API carries no browser data. Without the Basketly script in the shop and the buyer’s consent Meta gets no ad click id, so matching the purchase to an ad can be weaker.
- Reading every 15 minutes means a delay, and orders older than 7 days are not sent to Meta.
- BaseLinker does not know the product link, so its products have no page address. A feed made only from them is not complete until the link comes from another source.
- BaseLinker allows 100 requests a minute per token. Basketly keeps under 90, so a big catalogue takes longer to load.
Not until you tick that order source. By default only sources that are shops go. All orders are still visible in Orders and Clients.
No. You need an API token. Basketly reads the orders by itself every 15 minutes.
Yes, when you tick the status that counts as bought. The purchase goes after such a change, as long as the order is not older than 7 days.
Yes, pick the BaseLinker shop as the feed input. The products have no page link, though, so for a complete feed you need it from another source, for example the shop.
The free plan covers up to 100 orders a month, with no card and no time limit. The limit counts orders, not sends to platforms. Other plans are on the pricing page.
See also
- Meta Conversions APIPaid shop orders sent to Meta from the server, through a queue that does not drop purchases, with a result for every delivery.Read
- Product feedsYour shop’s feed fixed automatically and by your rules, every product diagnosed against Google Merchant Center and Meta catalogue requirements, served at its own address.Read
- Google Merchant CenterA feed from a shop, address or file, repaired and ready to paste into Merchant Center.Read
- Conversions API (CAPI)Sending events, such as purchases, to Meta from the shop’s server instead of the buyer’s browser.Read
- Shop integrations: where to start so orders, ads and the catalogue work togetherWhat to connect first in a Shoper shop: the Shoper API, Meta login and receiver, the purchase flow, the consent script, feeds, then other platforms. States and limits.Read
- Product data guidelines of Google, Meta, TikTok and Pinterest: rules with sources and AI titlesProduct data rules of Google Merchant Center, the Meta catalogue, TikTok and Pinterest: how to see which ones your products break and how title suggestions work.Read
Get started in under 5 minutes
Connect your shop and Meta and see how many purchases really arrive.
- Free up to 100 orders a month
- No developer needed
- Purchase balance and self-check