Track Your Meta Ad Conversions on Curios: Setting Up Meta Pixel and the Conversions API

If you run Facebook or Instagram ads that send people to your Curios products, you want to know which ads actually produce sales, not just clicks. Connecting your Meta Pixel to Creator Studio does exactly that: Curios places your pixel on your marketplace pages, and, with the Conversions API (CAPI) connected, reports every sale to Meta directly from our servers. Meta can then attribute purchases back to your campaigns, optimize delivery toward buyers, and let you build retargeting and lookalike audiences from real Curios traffic.

This tutorial walks through both steps. The Pixel takes about two minutes. The Conversions API takes a few more but is where most of the value is.

Why connect both the Pixel and the Conversions API?

• The Pixel fires from the buyer's browser. It's the standard way to track page views and purchases, but it gets blocked by ad blockers, iOS privacy settings, and cookie restrictions. Meta itself estimates a meaningful share of conversions go unreported through the pixel alone.
• The Conversions API sends the same events from Curios' servers to Meta, so a sale is reported whether or not the buyer's browser allowed tracking. Meta deduplicates events it receives both ways, so you get a fuller, more accurate picture without double-counting.

Connecting only the pixel works. Connecting both is what Meta recommends and what gives your ads the best signal.

Before you start

You'll need:

• A Meta Business account with access to Events Manager.
• A Meta Pixel (Meta now calls this a "dataset"). If you don't have one, create it in Events Manager → Connect data sources → Web → Meta Pixel.
• Your Pixel ID: the 15–16 digit number shown under your pixel's name in Events Manager.

Step 1: Add your Pixel ID in Creator Studio

1. In Creator Studio, open Integrations from the left sidebar.
2. Under Available to connect, find Meta Pixel and click Connect.

3. The card expands to show a Pixel ID field. Paste your Pixel ID from Events Manager.

4. Click Save. You'll see a "Meta Pixel saved" confirmation, and the card moves to Already connected.

From this point on, your pixel is loaded on your Curios marketplace pages and browser-side events start flowing to Meta.

Step 2: Connect the Conversions API

Once your Pixel is saved, a Conversions API access token section appears below it, showing Not connected.

Generate the token in Meta

1. Go to Events Manager and select your pixel from the Data Sources list.
2. Open the Settings tab.
3. Scroll to the Conversions API section and, under Set up manually, click Generate access token.
4. Copy the token. Meta shows it once; if you lose it, generate a new one.

You need admin access to the pixel to generate a token. If you don't see the option, check your role in Business Settings.

Paste it in Creator Studio

1. Back in Creator Studio → Integrations, paste the token into the Conversions API access token field.
2. Click Connect.

The status changes to connected. The token is stored encrypted and is never displayed again, so keep your own copy somewhere safe if you'll need it for other tools.

What Curios sends to Meta

With both pieces connected, Curios reports a Purchase event to your pixel for every completed order, including the order value and currency. That's what lets Meta attribute revenue to your campaigns, report ROAS, and optimize delivery toward higher-value buyers.

When the same purchase is reported both from the browser and from Curios' servers, Meta recognizes it as one event. You won't see doubled purchase counts in Ads Manager.

Step 3: Verify events are arriving

1. In Events Manager, select your pixel and open the Test events tab.
2. Visit one of your Curios product pages. Within a minute you should see events listed, with the Connection method column showing Browser and, once CAPI is active and a purchase occurs, Server.
3. Check the Overview tab a day later. Each event should show an Event match quality score and a Deduplication rate. Green across the board means everything is wired up.

If purchases show up as Browser only, the CAPI token isn't connected or has been revoked; regenerate it in Meta and paste it again.

Using the data in your ads

With conversions flowing, you can:

• Optimize for Purchase. In your campaign's ad set, set the conversion event to Purchase on your Curios pixel so Meta delivers ads to people most likely to buy.
• Build a retargeting audience. Create a Custom Audience from people who visited your Curios pages in the last 30 days but didn't purchase.
• Build a Lookalike audience. Seed it with your Curios purchasers to find new readers who resemble your best customers.
• See real ROAS. With purchase value reported, Ads Manager shows return on ad spend per campaign, not just cost per click.

Managing or removing the integration

The Meta Pixel card under Already connected lets you update your Pixel ID (edit and Save) or disconnect entirely with Remove. Removing the pixel also stops server-side events. To rotate the CAPI token, generate a new one in Meta and paste it in; it replaces the old one.

FAQ

Can I use more than one pixel?
One pixel per Curios account. If you run separate ad accounts for different pen names or brands, share a single pixel across them in Meta Business Settings.

Does the pixel fire on traffic from my affiliate links?
Yes. Any visitor who lands on your Curios product or storefront pages is tracked, regardless of how they arrived. The pixel doesn't distinguish affiliate traffic from other traffic; use the Partners dashboard for affiliate-specific reporting.

Will this slow down my product pages?
No. The pixel script is the standard lightweight Meta loader, and CAPI events are sent server-to-server after the sale, with no effect on page load.

Is buyer data shared with Meta?
Curios sends the minimum needed for Meta to match a purchase to an ad, and nothing more. Buyers whose browsers block tracking are still counted via the Conversions API for the purchase itself, not for their browsing behavior.

Do I need a developer to set this up?
No. Both steps are copy-and-paste. The only place you'll leave Creator Studio is Meta's Events Manager.