Squarespace Meta Tracking Fix
Budget / SalaryA$30–250
TypeFreelance project
LocationRemote
Posted1 hour ago
I already run Meta ads and have a working Squarespace site that pushes purchase data through Zapier into Facebook Conversions API, Brevo, and a Google Sheet. The basic flow works, but Meta still flags every event as “Missing user parameters” because four values never make it through: _fbc, _fbp, visitor IP address, and user agent.
Here is what needs to happen next:
1. Add a lightweight JavaScript snippet to my Squarespace site (Code Injection is fine) that, on page-load, reads the existing Meta cookies (_fbc and _fbp) and also captures the visitor’s IP address and user-agent string.
2. Make those four items available to my Zap. I want them stored in a dedicated column for each field inside the same Google Sheet row that already holds the buyer’s email—email will remain the unique key. The sheet can be expanded with new columns if needed.
3. Fix the Facebook Conversions step inside Zapier so the correct columns feed directly into the matching parameters (fbc, fbp, client_ip_address, client_user_agent). They currently pull from the wrong columns (“Source” and “Date”), so those mappings have to be updated.
4. Validate everything in Events Manager: once done, the Test Events tab should show each purchase event arriving with all four parameters populated.
I do not need a full rebuild—just the focused work above, plus a brief note or Loom explaining where the code lives and how you wired the new columns so I can maintain it later.
Here is what needs to happen next:
1. Add a lightweight JavaScript snippet to my Squarespace site (Code Injection is fine) that, on page-load, reads the existing Meta cookies (_fbc and _fbp) and also captures the visitor’s IP address and user-agent string.
2. Make those four items available to my Zap. I want them stored in a dedicated column for each field inside the same Google Sheet row that already holds the buyer’s email—email will remain the unique key. The sheet can be expanded with new columns if needed.
3. Fix the Facebook Conversions step inside Zapier so the correct columns feed directly into the matching parameters (fbc, fbp, client_ip_address, client_user_agent). They currently pull from the wrong columns (“Source” and “Date”), so those mappings have to be updated.
4. Validate everything in Events Manager: once done, the Test Events tab should show each purchase event arriving with all four parameters populated.
I do not need a full rebuild—just the focused work above, plus a brief note or Loom explaining where the code lives and how you wired the new columns so I can maintain it later.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.