Meta

Connecting Meta lets Flowfy send every purchase, add-to-cart and page view from your store straight to Meta's servers. Meta then knows which of your ads produced which sale, even when the shopper's browser blocked the pixel.

Watch the Meta setup walkthrough

Before you start

• Access to your business's Meta Business Suite
• Developer privileges on that business. Without them Meta hides the link that creates the token, so ask whoever administers the business to grant them, or to generate the token for you.
• A Flowfy source already connected. If you have not done that, start with Getting started.

You will end up with two values: a Dataset ID and a Business Access Token.

Part 1 · Get your credentials from Meta

1. Open Events Manager and pick your data source

Go to Events Manager and select the data source for your store. If you already run a Meta pixel on your website, choose that same one — browser events and server events belong on a single data source, or Meta will count the same sale twice.

2. Open the Settings tab

With the data source selected, open Settings from the tab bar. Both values you need live on this one page.

3. Copy the Dataset ID

Under Details, copy Dataset ID. It is a 15 to 16 digit number.

Meta's developer documentation still calls this same number a Pixel ID. It is one value with two names — paste it into Flowfy's Dataset ID field.

4. Generate the access token

Scroll to the Conversions API section and find Set up direct integration. Leave Set up with Dataset Quality API selected — it is Meta's recommended option and it also authorises tokens you generated earlier. Then click Generate access token and copy the token that appears.

Ignore Set up using a cloud-based connection above it. Conversions API Gateway and Signals Gateway are alternatives to Flowfy, not steps in this setup.

Part 2 · Create the destination in Flowfy

1. Start a new destination

In Flowfy, open Destinations and click Create destination.

2. Choose Meta

3. Connect your store

Tick the source whose events should flow to Meta, then continue.

4. Name it and paste both values

Give the destination a name you will recognise later, put the number from step 3 into Dataset ID, and the token from step 4 into Business Access Token. Then click Create.

Part 3 · Check that it's working

Place a test order in your store, then look in two places.

In Flowfy, open the destination and watch Live events. Your order should appear within a few seconds.

In Meta, open Events Manager and check the Overview tab for the same data source. Server events are labelled as coming from the Conversions API. Meta can take up to 20 minutes to display them, so an empty Overview right after a test order is normal — Flowfy's live events view is the faster signal.

If something goes wrong

Nothing arrives in Flowfy's live events. The problem is between your store and Flowfy, not between Flowfy and Meta. Check that your source is connected and active.

Flowfy shows events, Meta shows none after half an hour. The Dataset ID probably belongs to a different data source than the one you are looking at in Events Manager. Re-copy it from the data source you expect the events on.

Meta rejects the token. A token generated from a personal account rather than the business will not work. Generate it again from Events Manager with the correct business selected.

The Generate access token link is missing. You need developer privileges on the business. See the note in Part 1.

Meta counts every sale twice. Your browser pixel and Flowfy are sending to different data sources. Both must point at the same Dataset ID for Meta to recognise the two reports as one sale.