Connect the Meta pixel and Conversions API
Add your pixel ID and a Conversions API access token so every registration reaches Meta from the browser and from Bottega's server.
On this page6 sections
Bottega loads the Meta pixel on your landers and sends the same events to Meta from its server through the Conversions API. Both copies carry one event ID, so Meta counts each event once and still sees registrations that ad blockers hide. Setup takes about ten minutes and needs a Space admin in Bottega and someone with developer access to your Meta business.
- You need the Admin role in the space. Other members see the page read-only with the note Only admins can change tracking settings.
- GOATEDX decides whether your space can edit tracking. If the page header shows View only · managed by GOATEDX, send them your pixel ID and they will enter it for you.
- In Meta, only people with developer privileges for the business can see the link that generates an access token. If you can't find it, ask whoever manages your Meta business to add you or to generate the token.
- Publish at least one lander first, so you have somewhere to test.
Open your pixel in Events Manager
Choose the pixel your ads use. Meta's newer screens and docs also call a pixel a dataset, and Bottega's hints use that word too. It is the same thing.
Copy the pixel ID
The pixel ID is a long number made only of digits. Keep it somewhere handy for the next section.
Open the Settings tab
Scroll to the Conversions API section.
Generate an access token
Click Generate access token, under Set up manually. Copy the token straight away. You paste it into Bottega once, and Bottega never shows it again.
The Set up Meta tracking card is a five-step checklist. Each step turns green when it is done, and your progress saves as you go.
Paste the pixel ID
In step 1, Add your Meta pixel ID, paste it into Pixel ID. If you also use Google Analytics, paste your measurement ID (it starts with
G-) into Google Analytics 4 ID. Bottega then adds Google Analytics to your landers and sends it button clicks, form and scroll events.Paste the access token
In step 2, Connect the Conversions API, paste the token into Access token.
Click Save
The Unsaved changes bar at the bottom has Save and Discard. After saving, step 2 shows Access token saved with a padlock, and landers load the pixel within a minute.
Test the connection
Steps 3 and 4 check that events reach Meta. Follow Test your Meta tracking with Test Events, then come back for step 5.
Go live
Step 5, Go live, asks you to clear the Test event code field and save. When it reads No test code set, so server events count toward your ads. you are done.
With the defaults, Bottega reports page views, engaged visits, button clicks, registrations and WhatsApp bonus clicks, each from both the browser and the server. You can change the event names and channels on the Events sent to Meta tab. See Choose what each action sends to Meta.
Registrations carry hashed customer details (email, phone, first and last name, city, country), the visitor's IP address and browser name, and Meta's click and browser IDs where they exist. Hashing turns each detail into a code Meta can match against its users without receiving the raw value. Bots, crawlers and repeat submissions are never sent.
The saved token can't be viewed, only replaced. In step 2, click Replace, paste the new token and save. Cancel keeps the old one.
To disconnect the Conversions API, click Remove. The row turns red and reads Token will be removed when you save. Click Keep token if you change your mind, or Save to remove it. The pixel keeps working in the browser without it.
| What you see | Why | What to do |
|---|---|---|
| Pixel IDs are 6–20 digits | Something other than the pixel ID was pasted, such as a URL or the token. | Copy the numeric ID from your pixel in Events Manager. |
| Looks like G-XXXXXXX | The Google Analytics field has a property number or a tag ID that doesn't start with G-. | Use the measurement ID from your Google Analytics web stream, or leave the field empty. |
| Settings saved, but the access token couldn't be stored. | The pixel ID saved, the token didn't. | Paste the token again and save. |
| No Generate access token link in Meta | Your Meta user doesn't have developer privileges for the business. | Ask a Meta business admin to give you access or generate the token for you. |
| Fields are greyed out | You aren't a Space admin, or GOATEDX manages tracking for this space. | Ask an admin, or send the details to GOATEDX. |
| Server events are rejected | Meta refused the token or the pixel ID. The reason is in the log. | See Check that tracking is healthy. |
Read next
Something here out of date? Tell us and we'll fix the guide.