Before You Begin
You must have admin access to your Facebook Business Manager and the Pixel you want to connect.
You must have admin access in Dazos CRM (CRM Settings menu).
Set aside approximately 10 minutes for the full setup the first time.
Have your access token ready to be copied immediately — Meta only displays it once.
Steps
Step 1 — Find Your Pixel ID
The Pixel ID is the unique number identifying your Facebook Pixel. It is not a secret, but you will need to copy it into Dazos CRM in Step 3.
Open Meta Events Manager at
business.facebook.com/events_managerIn the left sidebar, click Data Sources
Click the Pixel (or "Dataset") you want to connect to Dazos CRM
Look just under the dataset name — the ID is a 15- to 16-digit number (e.g.
1234567890123)Copy it — you will paste it into Dazos CRM in Step 3
Meta has renamed "Pixel" to "Dataset" in the UI, but the Conversions API documentation and Dazos CRM still refer to it as Pixel ID. They are the same number.
Step 2 — Generate a Conversions API Access Token
This token authorizes Dazos CRM to post conversion events to your Pixel, and only your Pixel. It is non-expiring — you generate it once and paste it into Dazos CRM. If you ever need to revoke access, you can regenerate the token in Events Manager and the old one will stop working immediately.
While still on your Pixel/Dataset in Events Manager, click the Settings tab
Scroll down to the Conversions API section
Under "Set up manually", click Generate access token
Meta shows the token once — copy it immediately to a secure place
Don't see the button? The "Generate access token" button is hidden if your Business Manager role on the Pixel is below admin level. Go to Business Manager → Business Settings → Data Sources → Pixels → [your Pixel] → Add People and grant yourself Pixel Admin, then retry.
Step 3 — Add the Account in Dazos CRM
Open CRM Settings → Integrations → Facebook Ads Settings
Fill in the three fields in the Add Facebook Ads Account card:
Field | What to Enter |
Account Name | Any label that helps you recognize this connection (e.g. Main Clinic — FB Pixel). Only shown inside the CRM. |
Pixel ID | The 15- to 16-digit number from Step 1 |
Access Token | The token generated in Step 2 |
You can click How to find your Pixel ID & Access Token inside the form at any time to expand the in-app help panel without leaving the page.
Step 4 — Test the Connection
Before saving, click Test Connection. Dazos CRM sends a no-op test event to Meta's Conversions API using your Pixel ID and access token. This is the same call the live integration will make — just flagged as a test so it does not count as a real conversion.
If the credentials are valid: You will see a green "Connection successful — Meta accepted the test event" message. The test event also appears in Events Manager → your Pixel → Test Events tab within approximately 30 seconds, with an event_id starting with dazos_test_.
If the credentials are invalid: You will see a red error message forwarding Meta's exact reason — for example "OAuthException: Invalid OAuth access token". Re-check the Pixel ID and the token, and try again. Tokens are case-sensitive.
Once the test passes, click Save Account. The new account appears in the Connected Facebook Ads Accounts list on the same page.
Step 5 — Configure Conversion Rules and Activate
A conversion rule tells Dazos CRM when to fire a Facebook conversion event. You can have as many rules as you need — for example, one for "new lead created" and another for "Opportunity stage changed to Admitted."
Adding a rule:
In the Conversion Rules card, pick the saved Facebook account from the dropdown
The rule builder opens — fill in the following fields:
Field | Description |
Module | Which CRM record type to watch (Leads, Opportunities, etc.) |
Trigger | Record Created or Record Updated |
Field & Condition | For updates: which field change should fire the rule (e.g. Stage has changed to Admitted) |
Facebook Event Name | The standard Meta event name (Lead, Purchase, CompleteRegistration, etc.) |
Amount & Currency | Optional — enter a conversion value if applicable |
Email Field & Phone Field | Which CRM fields hold the contact's email and phone. Meta uses these — hashed — to match the conversion against the original ad click. |
Click Save Rule — the rule appears in the Saved Conversion Rules section below
Activating the workflow:
Once at least one rule is saved, click Activate Facebook Ads Workflow at the top right of the page. From this point on, every CRM record change that matches one of your rules will automatically send a conversion event to Meta in the background.
Verification / Expected Result
Once the workflow is active:
Every CRM record change that matches a saved rule will silently fire a conversion event to Meta
Events appear in Meta Events Manager → your Pixel → Events within a short delay
Each conversion call is logged in Dazos CRM under Settings → Dazos Logger, where you can view the full request payload and Meta's response
A
200response with"events_received": 1confirms the conversion was accepted
Troubleshooting / Common Errors
Conversions are not appearing in Facebook Ads Manager
Conversions can take up to 24 hours to appear in Ads Manager reports, even though test events show up in Events Manager almost immediately
Confirm the workflow toggle reads "Deactivate Facebook Ads Workflow" — that means it is currently active
Confirm at least one rule is saved and its Enabled checkbox is checked
HTTP errors after changing the access token
Re-run Test Connection with the new token before saving — Meta returns a clear error if the token is wrong
If you regenerated the token in Events Manager, the old one was revoked instantly — edit the connected account in Dazos CRM and paste the new token
Where can I see what was sent to Meta?
Go to Settings → Dazos Logger — every conversion call is logged with the full request payload and Meta's response
A
200response with"events_received": 1means the conversion was accepted
Need additional help?
Contact Dazos CRM Support and include the following:
Your Pixel ID
The relevant CRM record ID (e.g. Lead or Opportunity ID)
The approximate timestamp of the event you expected
Do not share your access token over email. Dazos Support already has the necessary admin tools to investigate from Dazos Logger.