--- lastModified: 2026-10-29 title: Send store events to Meta description: Connect your store to a Meta Dataset so Meta ads can measure and optimize for product views, carts, checkouts, and purchases. seo: description: "Connect a Runner store to a Meta Dataset through the Conversions API. Send product views, add to cart, checkout, and purchase events with consent, without custom code." --- Runner sends your store's shopping events to your Meta Dataset through Meta's Conversions API. Meta uses them to measure your Facebook and Instagram ads and to find more people who buy. You do not add code to your store, and the setup does not change your checkout. ## Entry path Open a store project → **Measure** → **Analytics** → **All reports**, then select **Tracking** in the **Setup** row at the bottom of the page. If your Analytics page does not show the **All reports** tab yet, the new Analytics has not reached your store. It is rolling out to all stores; contact support if you need it sooner. ## Before you start - You need a Meta business account with access to **Events Manager**. - You need permission to manage the store's Analytics settings in Runner. - Plan about 10 minutes. ## What Runner sends to Meta | Shopper action | Meta event | Value sent | | --- | --- | --- | | Opens a product page | `ViewContent` | Product price and store currency | | Adds a product to the cart | `AddToCart` | Item price times quantity, in the cart's currency | | Starts checkout | `InitiateCheckout` | Cart total in the cart's currency | | Places an order | `Purchase` | Order total in the store's currency, with the order ID | Each event also carries the page address, the shopper's IP address and browser, a hashed visitor ID, and Meta's ad-click ID when the visit came from a Meta ad. These help Meta match the event to an ad click. Events are sent from Runner's servers. Runner does not send the shopper's name, email, or postal address in these events. ## 1. Create a Dataset in Meta If you already have a Dataset for your website, skip to step 2. 1. Open [Meta Events Manager](https://business.facebook.com/events_manager2/overview). 2. Select **Connect data**, choose **Web**, and select **Next**. 3. Select **Create new dataset**, enter a name such as your store name, and select **Create**. 4. If Meta asks how to connect, choose **Conversions API**. You can skip Meta's event picker and code instructions. Runner already does that part. [![Meta's Connect a new data source dialog with Web selected.](https://ixft9x6szo.ufs.sh/f/Cc8uxBgAYTzgl0dyyAYeUkw7FfwK0GUS3UP4WuxSkfU8m50E)](https://ixft9x6szo.ufs.sh/f/Cc8uxBgAYTzgl0dyyAYeUkw7FfwK0GUS3UP4WuxSkfU8m50E) Choose **Web**, then **Next**. [![Meta's Create a new dataset dialog with the name field.](https://ixft9x6szo.ufs.sh/f/Cc8uxBgAYTzgA3CJirr8RzWZUm5ISnnFqcqRhlOqnS7MPlCF)](https://ixft9x6szo.ufs.sh/f/Cc8uxBgAYTzgA3CJirr8RzWZUm5ISnnFqcqRhlOqnS7MPlCF) Give the Dataset a name you will recognize. ## 2. Copy the Dataset ID In Events Manager, open **Datasets**. The Dataset ID is the number under the Dataset name. Copy it. [![A Dataset in Meta's list with its ID under the name.](https://ixft9x6szo.ufs.sh/f/Cc8uxBgAYTzgj5HmzVL63olM30ICAfDi5IRpMyzU1hHQSr5Y)](https://ixft9x6szo.ufs.sh/f/Cc8uxBgAYTzgj5HmzVL63olM30ICAfDi5IRpMyzU1hHQSr5Y) The ID in this example is from a test Dataset. Yours is a different number. ## 3. Generate an access token 1. Open your Dataset and select the **Settings** tab. 2. Scroll to **Conversions API**. 3. Under **Set up direct integration**, select **Generate access token**. 4. Copy the token. [![The Dataset Settings tab with the Conversions API section and the Generate access token button.](https://ixft9x6szo.ufs.sh/f/Cc8uxBgAYTzgj53NaBH63FdmJoI1sTh3EIkF6FO1hHQSr5Yw)](https://ixft9x6szo.ufs.sh/f/Cc8uxBgAYTzgj53NaBH63FdmJoI1sTh3EIkF6FO1hHQSr5Yw) **Generate access token** is at the bottom of the **Set up direct integration** section. Treat the token like a password. Paste it only into Runner, and do not send it by email or chat. ## 4. Open Tracking in Runner 1. In your store project, select **Measure** → **Analytics**. 2. Select the **All reports** tab. 3. Scroll to the **Setup** row at the bottom and select **Tracking**. [![The Runner sidebar with Analytics selected and the All reports tab at the top of the page.](https://ixft9x6szo.ufs.sh/f/Cc8uxBgAYTzgKMAZMxKlvyUE0XI1Zi1x6LvZ4haJMu8z0bFg)](https://ixft9x6szo.ufs.sh/f/Cc8uxBgAYTzgKMAZMxKlvyUE0XI1Zi1x6LvZ4haJMu8z0bFg) **Analytics** is in the **Measure** group. **All reports** is the third tab. [![The All reports page with the Setup row at the bottom, including Tracking.](https://ixft9x6szo.ufs.sh/f/Cc8uxBgAYTzgItdwwl2SQLF4UsRhj0QhGzLlsJsLqqyiuPB1)](https://ixft9x6szo.ufs.sh/f/Cc8uxBgAYTzgItdwwl2SQLF4UsRhj0QhGzLlsJsLqqyiuPB1) The **Setup** row is the last line on the page. ## 5. Turn on the consent banner In the **Consent mode** card, select **Consent banner**. The choice saves at once, and your store shows the banner from the next page load. You do not need to publish again. [![The Consent mode card with Consent banner selected.](https://ixft9x6szo.ufs.sh/f/Cc8uxBgAYTzgng0Ie79YEWuHbHOtg17aeD0ig76Jogcn1uzf)](https://ixft9x6szo.ufs.sh/f/Cc8uxBgAYTzgng0Ie79YEWuHbHOtg17aeD0ig76Jogcn1uzf) Runner sends events to ad platforms only from shoppers who select **Accept** on the banner. With **Implicit** mode, the **Ad platforms** card shows a warning and no events go to Meta. ## 6. Add your Meta Dataset 1. Scroll to **Ad platforms** and select **Meta**. 2. Paste the Dataset ID into **Destination / pixel ID**. 3. Paste the token into **Access token**. 4. Optionally, enter a **Label** that names the Dataset. 5. Keep **Enable this destination** on and select **Save destination**. [![The Meta row under Ad platforms with the Dataset ID, label, saved token, and Save destination button.](https://ixft9x6szo.ufs.sh/f/Cc8uxBgAYTzgsW9HnJuARqfXVaE9mpATnU9WU2rHVI3PoUvd)](https://ixft9x6szo.ufs.sh/f/Cc8uxBgAYTzgsW9HnJuARqfXVaE9mpATnU9WU2rHVI3PoUvd) Runner checks the token with Meta when you save. When the check passes, the Meta row shows **Configured** and your label. If it fails, generate a new token from the same Dataset and save again. ## 7. Check that it works 1. Open your store in a private browser window. 2. Select **Accept** on the consent banner. 3. Open a product and add it to the cart. 4. Return to **Tracking** and refresh the page. In the **Events** list, **View content** and **Add to cart** show a new fire, and the **Platforms** column shows **1 on**. 5. In Meta Events Manager, open your Dataset's **Overview**. The events appear within about 30 minutes, with **Server** as the connection method. [![The Events list on the Tracking page with 1 on in the Platforms column for the events sent to Meta.](https://ixft9x6szo.ufs.sh/f/Cc8uxBgAYTzgbRoTjjhGUwyJCgPpSLXzJC7vv27aOU9Nzycm)](https://ixft9x6szo.ufs.sh/f/Cc8uxBgAYTzgbRoTjjhGUwyJCgPpSLXzJC7vv27aOU9Nzycm) **1 on** means the event goes to one ad platform. **Begin checkout** and **Purchase** show **1 on** too, and fire when a shopper checks out and places an order. ## Troubleshooting | What you see | Meaning and next step | | --- | --- | | Meta's **Test Events** tab is empty | Expected. Runner sends events from its servers without a test code, so they show in **Overview** instead. | | The Meta Pixel Helper browser extension finds nothing | Expected. Runner does not add Meta's browser Pixel script to the store; events go through the Conversions API. | | **Overview** shows nothing after 30 minutes | Check that the event appears in the Runner **Events** list with **1 on**, that you selected **Accept** on the banner, and that you visited the published store, not the editor preview. | | **Save destination** fails | Meta did not accept the token for this Dataset. Generate the token from the same Dataset whose ID you pasted, then save again. | | The **Ad platforms** card warns that the banner is off | Select **Consent banner** in **Consent mode**. No events reach Meta until you do. | | Purchases show in another currency | Purchase values use the store's currency. Check the currency of the store's region. |