Quick answer: in Meta Events Manager, open your pixel → Settings → Conversions API → Generate access token. Then in HookPage → Settings → Conversions API (Meta), click + Add pixel and paste the Pixel ID and the token (Pro).
What is the Conversions API?
The Conversions API sends your events to Meta from your server, not only from the visitor’s browser. The browser pixel can be blocked by ad blockers, browser privacy settings or a visitor leaving the page too fast. A server event still arrives.
The access token is a long secret key that lets your website send these server events to your pixel.
Why it matters
- Fewer lost conversions, so Meta’s reports are closer to your real results.
- Better ad optimization, because Meta learns from more complete data.
- No double counting: Meta matches the browser and server copy of the same event.
What HookPage does with it (Pro)
For every event on a page whose pixel has a token, your site also sends the event to Meta’s Conversions API with:
- the event name and the same event ID as the browser event, so Meta keeps only one;
- the page address and the time;
- the visitor’s IP address and browser user agent (sent to Meta, not stored), the Meta
_fbpand_fbccookies, and after a form the hashed email, phone, first name and last name; - the value and currency.
The request has a 5-second time limit and does not slow your page down.
Where to get your access token
- Open Meta Events Manager and select your pixel (dataset).
- Open the Settings tab.
- Find the Conversions API section and click Generate access token (under setting up manually).
- Copy the token right away and keep it somewhere safe.
Don’t see “Generate access token”? Meta only shows it to people with developer access to the business. Ask your business admin to give you that access.
Keep it secret: anyone with your token can send events to your pixel. Don’t share it in screenshots or emails.
Add it to HookPage
- Go to HookPage → Settings → Conversions API (Meta).
- Click + Add pixel. Each row is one pixel:
- Name (for you): any name, for example “Shop pixel”.
- Pixel ID: the same ID as in your Meta Pixel settings.
- Access token: paste the token (it starts with
EAA…).
- Save. Add one row per pixel. There is no limit.
SCREENSHOT TO ADD: HookPage → Settings → Conversions API (Meta), pixel table with “+ Add pixel”
A row is only saved when both the Pixel ID and the token are filled. Otherwise it disappears when you save.
The pixel itself must also be added in All pages tracking, Advanced tracking or the page’s HookPage: tracking panel, so your pages load it. See Meta Pixel ID.
Check that it works
Use a test event code and watch your server events arrive in Events Manager → Test events. In the Overview, you can see whether each event was received from the browser, the server or both.
Learn more
- Conversions API: get started (access token) – Meta for Developers
- Handling duplicate Pixel and Conversions API events – Meta for Developers
- Customer information parameters – Meta for Developers