Connect Meta Conversions API

Before you start

Once connected, LatchPay's server tells Meta about every checkout, payment attempt and purchase, next to the Meta pixel in the buyer's browser. Meta counts each one once. This helps Meta see purchases the browser missed, for example because of an ad blocker. Server-side tracking explains what is sent.

• You need full control of the pixel in your Meta business. Ask the owner of the business if you are not sure.
• In LatchPay, open Settings → Tracking for the right store: ids and tokens are saved per store.
• It takes about five minutes. Keep LatchPay and Meta open in two browser tabs.

Connect Meta, step by step

1. 1

   Open Events Manager

   Open Meta Events Manager and log in with the Facebook account you use for your ads. Open Events Manager

2. 2

   Choose your pixel

   In the list of Data sources on the left, click the pixel your Shopify store uses. Meta also calls a pixel a dataset.

3. 3

   Copy the pixel ID

   Copy the ID shown under the pixel’s name (on the Settings tab Meta may call it Dataset ID). It is a number of 15 or 16 digits.

4. 4

   Paste the pixel ID

   Paste it into Pixel ID on the Meta card in LatchPay.

5. 5

   Create an access token

   Back on the Settings tab in Meta, scroll down to Conversions API and, under Set up manually, click Generate access token. An access token is a long code that works like a password: it lets LatchPay send your checkout events to this pixel.

6. 6

   Copy the token

   Copy the token Meta shows in the pop-up.

7. 7

   Paste the token

   Paste it into Conversions API access token on the Meta card.

8. 8

   Only if another app sends purchases

   Skip this unless an app such as WeTracked or TrackBee sends your purchases to Meta. Then turn on Another app already sends purchases to Meta, so no order counts twice (TrackBee: see Do you use WeTracked or TrackBee? first).

9. 9

   Save

   Click Save. The card now says Pixel + server.

LatchPay stores the token encrypted and only ever shows its last four characters. To replace it, paste a new one and click Save.

Send a test event

1. 1

   Open Test events

   In Events Manager, open the Test events tab of the same pixel.

2. 2

   Copy the test code

   Copy the test code for server events. It looks like TEST12345.

3. 3

   Send the test event

   Paste it into Test event code on the Meta card and click Send test event.

What you should see: Within a minute an event named LatchPayTest shows up in the Test events tab. It is not a purchase, so it never changes your results.

After your next order

• In Events Manager, your pixel's Overview tab lists InitiateCheckout, AddPaymentInfo and Purchase, received from both "Browser" and "Server", each counted once.
• The Meta card on Tracking shows when LatchPay last sent an event, and Failed · 7 days stays at 0.
• If another app, such as WeTracked or TrackBee, also sends your orders to this pixel, read Using WeTracked or TrackBee with LatchPay first.

If something is wrong

If it does not work: The token was made on another pixel: create it on the Settings tab of the pixel whose ID you pasted. Or you do not see Generate access token: you need full control of the pixel in your Meta business, so ask its admin.

• The Meta token was refused. The token was deleted, or the person who made it lost access. Create a new one (the step “Create an access token” above) and paste it; waiting events are sent within minutes.
• This token cannot send events to this pixel. The token belongs to another pixel. Create it on the Settings tab of the pixel whose ID you pasted.
• Traffic permissions. If your pixel only accepts events from a list of websites (Events Manager → your pixel → Settings → Traffic permissions), add the checkout's address: checkout.latchpay.io, or your own checkout domain when you set one up.
• Remove on the card deletes the token: server events stop and the browser pixel keeps running.