Give Meta cleaner server-side outcomes for Facebook and Instagram.
Meta signal view
Purchase is prepared for server-side feedback.
Outcome
Purchase
Match keys
fbp + fbc
Value
$96.20
Meta CAPI
server-side delivery
Event ID
dedupe
Match keys
ready
Revenue
sent
Make the pixel and server event agree before Meta learns from it.
event selected
Nitoriq outcome
signal shaped
Payload prepared
platform learns
Meta CAPI
Improve Meta optimization without depending on the browser alone
Send purchase and lead events
Route selected outcomes back to Meta from the server side.
Improve matching context
Use available browser IDs, click IDs, and hashed identifiers to support event matching.
Avoid double counting
Keep browser and server events aligned with deduplication context.
Feedback view
Meta receives the event your team actually trusts.
The point is not to send every possible event. It is to return the outcomes that should influence learning, reporting, and budget decisions.
Event
Purchase
selected outcome
Match keys
fbp + fbc
matching context
Destination
Meta CAPI
server-side delivery
Event
Outcome selected
A purchase, lead, or custom event is chosen for feedback.
Match
Identifiers prepared
Available match and deduplication context is attached.
Deliver
Meta receives CAPI event
The signal is routed server-side to Meta.
From Nitoriq event to Meta CAPI delivery
01
Choose events
Select purchases, leads, registrations, or custom outcomes.
02
Prepare match context
Attach available fbp, fbc, user agent, IP, and hashed identifiers.
03
Deduplicate safely
Use event context to align server and browser signals.
04
Send to Meta
Route the server-side event to the configured Meta destination.
Turn browser-side gaps into server-side feedback
Browser limits
Server-side events add a more durable delivery path.
Match quality
Payloads can include stronger available match parameters.
Optimization
Meta receives selected downstream outcomes and value.
Ready to launch