Meta Pixel/Conversions API Specialist Needed
Budget: ₹600 – ₹1,500 INR
We require an experienced Meta tracking and analytics specialist to set up Meta Pixel and Conversions API (CAPI) from scratch in a clean, scalable, and future-proof manner.
This setup must support website, lead ads, WhatsApp, and CRM (Odoo) and follow Meta best practices for browser-side and server-side tracking with proper deduplication.
This is a technical tracking project, not an ad management or marketing strategy task.
Scope of Work (Strict and Non-Negotiable)
Initial Architecture & Cleanup
Audit the existing Meta Business Manager
Remove or disable unused or incorrectly configured datasets, pixels, and test integrations
Design a single, unified tracking architecture before implementation
Dataset & Pixel Creation
Create one master dataset only
Create one Meta Pixel only inside that dataset
No duplicate pixels
No parallel datasets for different channels
Meta Pixel Installation
Install Meta Pixel on the website (via Google Tag Manager or native method)
Ensure browser events are firing correctly
No unnecessary events (no PageView, Scroll, Button Click, etc.)
Server-Side Tracking (Conversions API)
Implement Conversions API using:
CRM: Odoo
Middleware: Zapier (or equivalent if justified)
Configure proper event deduplication between browser and server events
Events to be sent to Meta:
Lead
QualifiedLead
No additional or vanity events
CRM Event Logic
Lead event must trigger when a new lead is created in Odoo
QualifiedLead must trigger only when a lead moves to a defined “Qualified” stage
Event logic must be documented and validated
Validation & Testing
Verify all events using Events Manager → Test Events
Confirm:
Browser events
Server events
Deduplication working correctly
Confirm ad account can optimise using the configured events
Deliverables Required
Screenshots from Events Manager showing:
Single dataset in use
Pixel connected to the dataset
Browser and server events firing
Deduplication in effect
Written summary explaining:
Dataset and pixel structure
Event logic (Lead and QualifiedLead)
How deduplication is handled
Confirmation that no extra datasets, pixels, or events were created
Technical Requirements
Proven experience with:
Meta Pixel and Conversions API (CAPI)
Server-side tracking implementations
Zapier-based Meta CAPI integrations
CRM-driven event logic (Odoo experience preferred)
Strong understanding of:
Event matching and attribution
Browser vs server tracking
Clean analytics architecture
Timeline & Budget
Timeline: 3–5 working days
Budget: Fixed, to be agreed before starting
Payment released only after verification of setup
Important Notes (Read Carefully)
Please do not apply if you:
Create multiple datasets or pixels
Add unnecessary events
Skip Test Events verification
Treat this as a basic pixel or ad setup
This project requires precision, discipline, and technical accuracy.
How to Apply
Please include:
A brief explanation of how you design a clean Meta Pixel + CAPI architecture from scratch
One example of a similar full setup you have completed
Confirmation that you will implement one dataset and one pixel only
This setup must support website, lead ads, WhatsApp, and CRM (Odoo) and follow Meta best practices for browser-side and server-side tracking with proper deduplication.
This is a technical tracking project, not an ad management or marketing strategy task.
Scope of Work (Strict and Non-Negotiable)
Initial Architecture & Cleanup
Audit the existing Meta Business Manager
Remove or disable unused or incorrectly configured datasets, pixels, and test integrations
Design a single, unified tracking architecture before implementation
Dataset & Pixel Creation
Create one master dataset only
Create one Meta Pixel only inside that dataset
No duplicate pixels
No parallel datasets for different channels
Meta Pixel Installation
Install Meta Pixel on the website (via Google Tag Manager or native method)
Ensure browser events are firing correctly
No unnecessary events (no PageView, Scroll, Button Click, etc.)
Server-Side Tracking (Conversions API)
Implement Conversions API using:
CRM: Odoo
Middleware: Zapier (or equivalent if justified)
Configure proper event deduplication between browser and server events
Events to be sent to Meta:
Lead
QualifiedLead
No additional or vanity events
CRM Event Logic
Lead event must trigger when a new lead is created in Odoo
QualifiedLead must trigger only when a lead moves to a defined “Qualified” stage
Event logic must be documented and validated
Validation & Testing
Verify all events using Events Manager → Test Events
Confirm:
Browser events
Server events
Deduplication working correctly
Confirm ad account can optimise using the configured events
Deliverables Required
Screenshots from Events Manager showing:
Single dataset in use
Pixel connected to the dataset
Browser and server events firing
Deduplication in effect
Written summary explaining:
Dataset and pixel structure
Event logic (Lead and QualifiedLead)
How deduplication is handled
Confirmation that no extra datasets, pixels, or events were created
Technical Requirements
Proven experience with:
Meta Pixel and Conversions API (CAPI)
Server-side tracking implementations
Zapier-based Meta CAPI integrations
CRM-driven event logic (Odoo experience preferred)
Strong understanding of:
Event matching and attribution
Browser vs server tracking
Clean analytics architecture
Timeline & Budget
Timeline: 3–5 working days
Budget: Fixed, to be agreed before starting
Payment released only after verification of setup
Important Notes (Read Carefully)
Please do not apply if you:
Create multiple datasets or pixels
Add unnecessary events
Skip Test Events verification
Treat this as a basic pixel or ad setup
This project requires precision, discipline, and technical accuracy.
How to Apply
Please include:
A brief explanation of how you design a clean Meta Pixel + CAPI architecture from scratch
One example of a similar full setup you have completed
Confirmation that you will implement one dataset and one pixel only