Meta Conversion API
Server-side events with deduplication against browser pixel data.
Advertising & Tracking APIs
Conversion API for server-side ad event tracking
Send server-side conversion events to Meta, Google, TikTok and other ad platforms through LOOKME tracking APIs. Measure campaign performance with attribution pipelines — lawful advertising infrastructure, not media buying services.
In Development
lookme-api · Conversion
POST /v1/ads/conversion
Authorization: Bearer <api_key>
{
"event": "purchase",
"campaign_id": "CMP_77",
"value": 999
}
202 Accepted
{ "tracked": true, "deduped": false }
CAPI
Server-side events
Meta
Platform support
Dedup
Event matching
Logs
Delivery audit
Advertising measurement APIs — not media buying
Digital marketers and product teams need reliable event pipelines that combine browser-side tags with server-side conversion API events. LOOKME provides tracking endpoints that forward purchase, signup and custom events to ad platforms with proper attribution.
Server-side tracking improves data accuracy as browser privacy restrictions increase. LOOKME APIs handle event formatting, platform-specific requirements and retry logic so your campaigns receive complete conversion data.
Platform policies from Meta, Google, TikTok and others evolve continuously. LOOKME implementations are designed for updateability, with consent management and data-use rules respected throughout the pipeline.
Important: Tracking must follow platform terms, privacy law and user consent requirements. LOOKME does not make misleading claims about guaranteed advertising results and does not help evade platform integrity systems.
Example API endpoints
Representative REST routes issued after onboarding. Paths and fields may vary per project.
Method
Path
Description
POST
/v1/ads/conversion
Post a server-side conversion event
POST
/v1/ads/events/batch
Send a batch of attributed events
GET
/v1/ads/campaigns/{id}/stats
Internal campaign performance summary
POST
/v1/ads/attribution/link
Link click ID to user or session
GET
/v1/ads/logs
Search event delivery logs for debugging
Advertising technology capabilities
Capabilities your engineering team integrates through REST endpoints and webhooks.
TikTok Events API
Web and app events aligned with TikTok measurement requirements.
Google Ads conversions
Tag, enhanced conversions or server-side setups as the account allows.
Registration events
Signed-up and verified-user events with consistent identifiers.
Purchase events
Order value, currency and transaction IDs for reconciliation.
Custom conversion events
First-deposit or lead events only for lawful products you operate.
Attribution API
Click IDs, UTMs and agreed windows — with known limitations stated.
Campaign analytics API
Internal reporting alongside ad-platform dashboards.
Event log API
Search delivery logs, retries and platform rejection reasons.
Consent hooks
Respect user consent before events leave your infrastructure.
Webhook events
Signed HTTPS callbacks so your backend stays in sync without polling.
ads.event_failed
Platform rejected or failed to accept an event
ads.consent_updated
User consent state changed for a profile
ads.batch_completed
Batch upload finished with per-event results
How integration works
Typical steps from enquiry to live API access.
-
01
Measurement plan
Define events, consent, identifiers and which platforms are in scope.
-
02
Implementation
Tags, APIs, deduplication and test events in staging.
-
03
Validation
Compare platform diagnostics with your own logs.
-
04
Handover
Documentation so marketing and engineering can maintain the pipeline.
Integrate this API with LOOKME
Share your integration requirement, target markets and expected volumes. We will outline endpoints, webhooks and API access steps.