Connect Meta Pixel and the Conversions API
Put your Facebook and Instagram pixel on the store and send purchases from the server: Pixel ID, access token, test event code, checking in Events Manager.
What it is#
The Meta Pixel tells Facebook and Instagram what visitors do on your store, so your ads can find buyers and you can measure sales. The Conversions API sends purchases from Jukto's server too, which survives ad blockers and closed tabs.
What you need#
- A Meta pixel in your Meta Events Manager. If you have none, create one there.
- The Pixel ID (numbers only).
- Optional: a Conversions API token for server purchases, and a Test event code while you check.
Where to find your keys#
- 1
Open your pixel
Open Meta Events Manager, then Data sources, and select your pixel.
- 2
Copy the Pixel ID
Copy the Pixel ID (numbers only). You paste it into the Pixel ID field in Jukto.
- 3
Optional: make the server token
For server events open the pixel Settings, find Conversions API and press Generate access token. Copy it into Conversions API token.
- 4
Optional: the test code
To check the setup, open the Test events tab and copy the test code into Test event code. Clear it when you finish.
What Jukto does#
- The Pixel ID is a setting, and the pixel is placed on every page of your live store. Only a well-formed ID (6 to 20 digits) is ever placed on a page.
- The Conversions API token is stored encrypted and used only on the server, to send purchases.
- Test connection checks the ID format. With a token it also reads your pixel from Meta, and with a test event code it sends a test Purchase.
| Event | When it is sent |
|---|---|
| PageView | on every page |
| ViewContent | on a product page |
| AddToCart | when a line is added to the cart (quantity steps too) |
| InitiateCheckout | when the checkout opens with lines |
| AddPaymentInfo | when the order is sent |
| Purchase | on the thank-you page, and again from the server when the order is confirmed; one copy is kept |
For server purchases Jukto sends the order total, items, hashed email and phone, and the visitor details described in Marketing and ads. A purchase is sent once per order, whatever the number of retries.
Test and turn on#
- 1
Open the provider page
Go to Tools, open Integrations, choose Marketing & ads, then Meta Pixel and press Set up (it says Manage once you have started).
- 2
Fill in the fields and save
Paste each value into the field with the same name, then press Save. A secret value is stored encrypted, and afterwards only its last four characters are shown.
- 3
Test the connection
Press Test connection. Jukto asks Meta Pixel whether the saved values work and shows whether it worked and, if not, what Meta Pixel answered. The test uses the saved values, so save first.
- 4
Send a test event
With a Test event code saved, press Send test event. Jukto sends a test Purchase that shows up in Events Manager under Test events. It is not counted as a sale.
- 5
Turn on
Press Turn on. Until then your website does not use it. Turn off stops it again and your saved values stay.
- 6
Look at your live store
Open your live website (not the editor preview) and browse. In Events Manager watch Test events for PageView, ViewContent and AddToCart.
- 7
Clear the test event code
When you are happy, delete the Test event code and press Save.
Common errors#
| What you see | What to do |
|---|---|
| the Pixel ID is numbers only (6 to 20 digits) | You pasted something other than the ID. Copy the Pixel ID again from Events Manager. |
| pixel read failed: check the Pixel ID and the token | The token does not belong to this pixel, or it was removed. Generate a new token for the same pixel. |
| test event refused | Meta refused the test Purchase. Check the Test event code against the Test events tab and the token. |
| pixel id format OK; without a Conversions API token the browser pixel is used alone | This is fine: it only says no server events will be sent. Add the token if you want them. |
| Events Manager shows nothing | Check that the integration is turned on, that you browse the live store and not the preview, and that the Pixel ID is the one in Events Manager. Visitors with an ad blocker send no browser events. |

Comments (0)
Anyone can comment. Please do not post phone numbers, passwords or customer details.