Connect Snap Pixel and Conversions API

Before you start

With a Pixel ID, the checkout loads the Snap Pixel in the buyer's browser and reports START_CHECKOUT, ADD_BILLING and, on the thank-you page, PURCHASE. With a Conversions API token as well, LatchPay's server reports the same three events, and Snapchat keeps one of each. Server-side tracking explains what is sent.

• You need to be an Organization Admin of the Snapchat business. A token only works for pixels of that organisation.
• In LatchPay, open Settings → Tracking for the right store: ids and tokens are saved per store.

Connect Snapchat, step by step

1. 1

   Open Snapchat Ads Manager

   Open Snapchat Ads Manager and log in. Open Snapchat Ads Manager

2. 2

   Open Business Details

   Click the menu in the top corner and choose Business Details.

3. 3

   Create an access token

   Under OAuth Apps, find Conversions API Tokens and click Generate Token. An access token is a long code that works like a password: it lets LatchPay send your checkout events to your Snap Pixel. Only an Organization Admin sees this.

4. 4

   Paste the token

   Copy the token and paste it into Conversions API token on the Snapchat card in LatchPay.

5. 5

   Open Events Manager

   Back in Snapchat, click the menu in the top corner and choose Events Manager.

6. 6

   Copy the pixel ID

   Click your Snap Pixel and copy its pixel ID: a long code of letters, digits and dashes, like 1a2b3c4d-5e6f-….

7. 7

   Paste the pixel ID

   Paste it into Pixel ID on the Snapchat card.

8. 8

   Save

   Click Save. The card now says Pixel + server.

LatchPay stores the token encrypted and only ever shows its last four characters.

Send a test event

1. 1

   Send the test event

   Click Send test event on the Snapchat card.

What you should see: Under the button, LatchPay says the event format is valid. Snapchat only checks this test and records nothing; after your next real checkout, Events Manager shows the events.

LatchPay sends a PURCHASE-shaped event to Snapchat's checking address: Snapchat checks the pixel and the event, and records nothing.

If it does not work: The token was made in another Snapchat organisation than the pixel: create it in the organisation that owns the pixel. Or the pixel ID has a typo: copy it again from Events Manager.

After your next order

• Events Manager shows PURCHASE, START_CHECKOUT and ADD_BILLING from both the pixel and the Conversions API, each counted once.
• The Snapchat card on Tracking shows when LatchPay last sent an event, and Failed · 7 days stays at 0.

Good to know

• The purchase is matched on the event id and also on the payment id, so it is counted once even when one of the two arrives much later.
• The Snapchat token was refused: create a new token and paste it; waiting events are sent within minutes. This token cannot send events to this pixel: the pixel belongs to another organisation.
• Remove on the card deletes the token: server events stop and the pixel keeps running.