Wix Meta Pixel and Conversions API Configuration
Budget: $10 – $30 USD
Title
Configure Meta (Facebook) Pixel + Conversions API (Advanced Matching) on Wix
---
Project Overview
I need an expert to properly configure Meta Pixel and Conversions API (CAPI) on a Wix site so that all required customer data & tracking parameters are sent with every event (not just Purchase). Advanced Matching must follow Meta best practices.
Important:
We’re seeing event fragmentation through Wix, but customer data is not being passed consistently. This must be fixed.
The Madgicx Cloud integration has been removed — we will proceed using native Wix + custom code only.
---
Critical Developer Note: fbclid vs fbc (We Need Both Supported)
fbclid = Facebook Click ID from ad clicks; appears in the landing page URL (e.g., ?fbclid=IwAR...).
fbc = Value expected by Meta in CAPI payloads; derived from fbclid (or the Meta Pixel cookie _fbc).
Required Behavior:
1. If fbclid exists in the URL:
Capture & store it (localStorage/session/Wix Storage).
Generate fbc in Meta format:
fb.1.<unix_timestamp_in_seconds>.<fbclid>
Store fbc (cookie _fbc + storage) for reuse on all subsequent events.
2. If no new fbclid on later pages:
Reuse the stored fbc (do not generate fake IDs).
> Goal: Ensure every eligible Pixel/CAPI event includes fbc when available to improve attribution & matching.
---
Scope of Work
1. Send Customer & Tracking Data with Every Event (Pixel + CAPI)
fbclid (capture, persist, reuse).
fbc (generated from fbclid or read from cookie).
Email (always pass).
Phone (with country code).
Country.
Region/State.
All form fields (checkout, lead, registration).
First Name / Last Name.
Product identifier (product_id / SKU) for product-level audience building.
---
2. Data Handling & Matching
SHA-256 hash required fields before sending (validate what Wix auto-hashes).
Include Event IDs for Pixel/CAPI deduplication.
Fix duplicate Purchase events (2–4 seen in tests; likely re-fire on back/refresh). Add guard (cookie/session/orderId).
Pass fbc (and fbp if available).
---
3. UI / Form Adjustments (Wix)
Always show Email field (currently hidden for logged-in users; must be visible & required).
Remove or make ZIP optional (not used in target market).
Phone field: add required country code selector limited to +972 and +970; ensure full E.164 number is sent to Meta.
---
4. Event Quality & Consistency
Send the same customer data set with all key funnel events: PageView, ViewContent, AddToCart, InitiateCheckout, Lead, Purchase...
Review interaction events (Chat Open / Chat Close). Recommend:
Track or ignore?
Standard vs Custom Event?
Attribution / retargeting value.
---
5. Technical Implementation Notes (Code)
Example (JS in Wix Site Code):
import {session} from 'wix-storage'; // or local based on persistence needs
$w.onReady(function () {
const params = new URLSearchParams(window.location.search);
const fbclid = params.get('fbclid');
if (fbclid) {
const ts = Math.floor(Date.now()/1000);
const fbc = `fb.1.${ts}.${fbclid}`;
session.setItem('fbclid', fbclid);
session.setItem('fbc', fbc);
// Optional cookie for Meta compatibility:
// document.cookie = `_fbc=${encodeURIComponent(fbc)}; path=/;`;
}
});
When firing a server event (e.g., Purchase via HTTP CAPI):
Read stored fbc.
Include in user_data.fbc.
Use the same event_id as the Pixel event triggered client-side.
---
Deliverables
1. Working full Pixel + CAPI configuration.
2. Screenshots from Events Manager (Test Events, Diagnostics).
3. Proof that Purchase fires once per order (test steps + results).
4. Sample event payload (hashed user data + fbc + Event ID).
5. Light documentation / commented code.
6. Short guide: build product-level audiences using product_id.
---
Include in Your Proposal
1. Fixed price.
2. Actual time required
3. Can you start today? (:
4. Experience summary (Meta Pixel, CAPI, Advanced Matching, Wix custom code).
5. One similar implementation (screenshot or short writeup).
---
Selection Criteria
Competitive pricing.
Proven Pixel + CAPI + Wix experience.
Can start immediately; fast delivery.
Clear communication.
My price is $40 for someone with the required expertise.
If the project is completed as agreed, by implementing all the listed requirements and adhering to the agreed timeline, we will proceed. Otherwise, we will not continue.
Configure Meta (Facebook) Pixel + Conversions API (Advanced Matching) on Wix
---
Project Overview
I need an expert to properly configure Meta Pixel and Conversions API (CAPI) on a Wix site so that all required customer data & tracking parameters are sent with every event (not just Purchase). Advanced Matching must follow Meta best practices.
Important:
We’re seeing event fragmentation through Wix, but customer data is not being passed consistently. This must be fixed.
The Madgicx Cloud integration has been removed — we will proceed using native Wix + custom code only.
---
Critical Developer Note: fbclid vs fbc (We Need Both Supported)
fbclid = Facebook Click ID from ad clicks; appears in the landing page URL (e.g., ?fbclid=IwAR...).
fbc = Value expected by Meta in CAPI payloads; derived from fbclid (or the Meta Pixel cookie _fbc).
Required Behavior:
1. If fbclid exists in the URL:
Capture & store it (localStorage/session/Wix Storage).
Generate fbc in Meta format:
fb.1.<unix_timestamp_in_seconds>.<fbclid>
Store fbc (cookie _fbc + storage) for reuse on all subsequent events.
2. If no new fbclid on later pages:
Reuse the stored fbc (do not generate fake IDs).
> Goal: Ensure every eligible Pixel/CAPI event includes fbc when available to improve attribution & matching.
---
Scope of Work
1. Send Customer & Tracking Data with Every Event (Pixel + CAPI)
fbclid (capture, persist, reuse).
fbc (generated from fbclid or read from cookie).
Email (always pass).
Phone (with country code).
Country.
Region/State.
All form fields (checkout, lead, registration).
First Name / Last Name.
Product identifier (product_id / SKU) for product-level audience building.
---
2. Data Handling & Matching
SHA-256 hash required fields before sending (validate what Wix auto-hashes).
Include Event IDs for Pixel/CAPI deduplication.
Fix duplicate Purchase events (2–4 seen in tests; likely re-fire on back/refresh). Add guard (cookie/session/orderId).
Pass fbc (and fbp if available).
---
3. UI / Form Adjustments (Wix)
Always show Email field (currently hidden for logged-in users; must be visible & required).
Remove or make ZIP optional (not used in target market).
Phone field: add required country code selector limited to +972 and +970; ensure full E.164 number is sent to Meta.
---
4. Event Quality & Consistency
Send the same customer data set with all key funnel events: PageView, ViewContent, AddToCart, InitiateCheckout, Lead, Purchase...
Review interaction events (Chat Open / Chat Close). Recommend:
Track or ignore?
Standard vs Custom Event?
Attribution / retargeting value.
---
5. Technical Implementation Notes (Code)
Example (JS in Wix Site Code):
import {session} from 'wix-storage'; // or local based on persistence needs
$w.onReady(function () {
const params = new URLSearchParams(window.location.search);
const fbclid = params.get('fbclid');
if (fbclid) {
const ts = Math.floor(Date.now()/1000);
const fbc = `fb.1.${ts}.${fbclid}`;
session.setItem('fbclid', fbclid);
session.setItem('fbc', fbc);
// Optional cookie for Meta compatibility:
// document.cookie = `_fbc=${encodeURIComponent(fbc)}; path=/;`;
}
});
When firing a server event (e.g., Purchase via HTTP CAPI):
Read stored fbc.
Include in user_data.fbc.
Use the same event_id as the Pixel event triggered client-side.
---
Deliverables
1. Working full Pixel + CAPI configuration.
2. Screenshots from Events Manager (Test Events, Diagnostics).
3. Proof that Purchase fires once per order (test steps + results).
4. Sample event payload (hashed user data + fbc + Event ID).
5. Light documentation / commented code.
6. Short guide: build product-level audiences using product_id.
---
Include in Your Proposal
1. Fixed price.
2. Actual time required
3. Can you start today? (:
4. Experience summary (Meta Pixel, CAPI, Advanced Matching, Wix custom code).
5. One similar implementation (screenshot or short writeup).
---
Selection Criteria
Competitive pricing.
Proven Pixel + CAPI + Wix experience.
Can start immediately; fast delivery.
Clear communication.
My price is $40 for someone with the required expertise.
If the project is completed as agreed, by implementing all the listed requirements and adhering to the agreed timeline, we will proceed. Otherwise, we will not continue.