Connect Hardal to Meta Pixel using Conversions API for improved tracking accuracy
Meta Conversions API (CAPI) integration with Hardal enables server-side event tracking for improved accuracy and reliability of your Meta Pixel data. This integration provides more reliable conversion tracking for your Facebook/Instagram ads.
Before setting up the CAPI integration, ensure you have:
Completed Hardal setup on your website
Access to Hardal Dashboard
A Meta Business Manager account
A Meta Pixel
You must have admin access privileges in your Meta Business Manager to generate the required access token.
Generate Meta Access Token
Log into your Meta Business Manager
Go to Events Manager
Select your Pixel
Navigate to the Settings tab
Copy Dataset ID and save it (marked as step 3)
Copy Business ID and save it (marked as step 2)
Find the “Conversions API” section
Click “Generate access token”
Copy the generated token
Keep your access token secure and don’t share it publicly. It provides direct access to your Meta Pixel data.
Deploy CAPI Server in Hardal
Log into your Hardal dashboard
Navigate to “Server-Side Hosts”
Click on “Deploy” button to create a CAPI server
Connect Hardal to Meta Pixel
Continue with Manuel Connection
Insert all information into related spaces
Enable First-Party Tracking
Congratulations! You have succesfully deployed a Meta CAPI connection to your Meta Pixel via Hardal.
We highly recommend setting up Meta CAPI tag via sGTM if you are using Google Tag Manager for best Meta CAPI performance. This will dramatically improve the Meta CAPI performance.
Events Not Showing in Meta Events Manager
If events aren’t appearing in your Events Manager:
Verify Access Token:
Ensure your access token is valid
Check if token has required permissions
Generate a new token if needed
Check Domain Configuration:
Verify domain matches between Hardal and Meta Pixel
Ensure domain is verified in Business Manager
Check for any domain-related errors in Hardal logs
Event Configuration:
Confirm events are being received by Hardal
Check event mapping configuration
Verify event parameters match Meta’s requirements
Duplicate Events
If you’re seeing duplicate events in Meta:
Check Implementation:
Ensure you’re not sending both browser and server events
Check for multiple pixel installations
Configure Deduplication:
Use consistent event_id values
Set appropriate deduplication window