Repeated setup work
Each account requires another round of scripts, webhooks, field mapping, and testing.
Built for client tracking operations
Stop rebuilding Meta CAPI from scratch for every client.
Create a repeatable server-side conversion workflow for landing pages, CRMs, forms, and booking systems across your client portfolio.
Separate client endpoints Repeatable payload standard Simple installer handoff
Client endpoints
N
Northstar DentalLead event · Dataset connected
HealthyA
Atlas RoofingSchedule event · Dataset connected
HealthyS
Summit CoachingLead event · Dataset connected
TestingE
Electric GuysLead event · Dataset connected
HealthyDemo workspace · fictional client names4 active
Where tracking breaks
The implementation should scale better than the client list.
An agency setup becomes expensive when every launch depends on one person remembering a slightly different collection of scripts and webhook fields.
Inconsistent payloads
Different developers and funnel builders send different versions of the same conversion event.
Credentials spread across tools
Dataset IDs, tokens, and endpoint details become difficult to audit and maintain.
Reactive troubleshooting
Tracking problems are often discovered after campaign reporting already looks wrong.
Messy client handoff
The installer receives a technical workflow instead of one controlled script.
No shared checklist
Launch quality depends on memory rather than a repeatable standard.
The controlled path
Move from a loose collection of signals to one traceable event.
Simple CAPI keeps the implementation focused: capture the useful data, connect it to the conversion, send it through a protected endpoint, and validate the result.
Create the client endpoint
Keep the client name, dataset, event, and generated installation clearly separated.
Connect client-owned credentials
Use the dataset and token approved for that client’s Meta account.
Install the generated script
Add the controlled implementation to the landing page, form, or custom workflow.
Send a test conversion
Check browser context, identity fields, source details, and event ID before launch.
Document the final setup
Record the event source, owner, validation result, and any client-specific field mapping.
Required
event_name
event_id
event_time
action_source
event_source_url
When available
email, phone, external_id
fbp, fbc, user_agent, ip_address
value, currency, UTM parametersPractical coverage
Designed for the systems agencies inherit.
Use accurate values, preserve ownership, and validate the event before relying on campaign reporting.
GoHighLevelHubSpotCustom React formsWordPress formsWebflowShopifyZapier workflowsCustom backends
Built for controlled implementation.Keep client credentials out of page code, collect only permitted data, and preserve a clear boundary between client configurations.
Review privacy principles Frequently asked questions
The parts people usually discover after launch.
Resolve the implementation details before the campaign starts spending money.
Can I manage multiple clients?+
Yes. The workspace organizes separate endpoints by client so configurations do not have to live inside one shared script.
Does every client use a separate dataset?+
Each endpoint should use the dataset approved for that client. Whether a business uses one or several datasets depends on its Meta setup.
Can I use different events for different clients?+
Yes. Lead and Schedule are separate event-specific scripts, and each client setup can use the event it requires.
Can this work with client-owned Meta accounts?+
Yes. Use client-approved dataset credentials and keep access ownership clear in your documentation.
How should agencies handle access tokens?+
Use the least access required, keep tokens out of page code and shared documents, and rotate or revoke them when access changes.
Can I test an event before launching ads?+
Yes. Send test events and inspect the exact parameters in Events Manager before relying on production reporting.
Does Simple CAPI replace an analytics specialist?+
No. It reduces implementation work for supported Meta events, but measurement strategy, consent, debugging, and broader analytics still require qualified judgment.
Simple CAPI workspace
Build the event once. Hand off one controlled installation.
Create a client-specific Lead or Schedule endpoint and validate the exact event Meta receives.
Create your endpoint First eligible script is free after account verification.