What Is Meta Pixel?
When you run Meta ads, it is easy to see how many clicks you received. But clicks alone do not tell you what people did next.
Meta Pixel is a tool that tells Meta what people do after they arrive on a page from an ad. You do not need to think of it as complicated code. It simply sends signals when visitors take actions on a DocuRise page, such as:
- They opened a page
- They viewed content or a product
- They submitted a lead form
- They started checkout
- They completed a purchase
Once these signals start coming in, you can move beyond “Did people click the ad?” and answer “Which ads actually led to inquiries, leads, or purchases?” Meta can also use these signals to show your ads to people who are more likely to convert.
What Changes When You Connect It to DocuRise?
Connecting Meta Pixel to DocuRise lets you follow what happens after an ad click in one continuous journey.
For example, if someone sees a Meta ad, opens a DocuRise document, submits a lead form, or buys a product, DocuRise sends that action to Meta as a conversion signal. This lets you review results that are much closer to real business outcomes than click counts alone.
DocuRise can send these key actions:
- PageView: when someone opens a page
- ViewContent: when someone views content or a product
- Lead: when someone submits a lead form
- InitiateCheckout: when someone starts checkout
- Purchase: when someone completes a purchase
Why Is It Easier with DocuRise?
Installing a pixel often means editing website code or asking a developer for help. With DocuRise, you only need to connect your Meta Dataset ID once, so you can complete the setup without knowing how to code.
After you connect it:
- Browser tracking is enabled by default on document, form, and folder pages.
- You can turn tracking off individually on pages where you do not need it.
- If you already use a dataset for your ads, you can connect the same one and keep your ad and DocuRise conversion history together.
In short, DocuRise connects the journey from ad click to content view, lead capture, checkout, and purchase with Meta.
Two Terms to Know Before You Start
You only need to understand these two terms before setting up the connection.
- Dataset ID (Pixel ID): a 15- or 16-digit number issued by Meta. In this guide, Dataset ID and Pixel ID refer to the same value.
- Browser pixel: the basic tracking method that sends actions such as page views and form submissions from a visitor’s browser to Meta.
You do not need to know how to code. Follow the screens below in order to connect everything.
Meta Pixel Connection Guide
This guide explains how to connect the Dataset ID (Pixel ID) from your Meta business account to DocuRise. You only need the Dataset ID for this connection.
Events Sent After You Connect
- PageView: sent when someone opens a page
- ViewContent: sent when someone views content or a product
- Lead: sent when someone submits a lead form
- InitiateCheckout: sent when someone starts checkout
- Purchase: sent when someone completes a purchase
Before You Start
- Permission to manage integrations in your DocuRise workspace
- Access to your Meta business portfolio and Events Manager
- The Dataset ID already used by your ads, if you have one
Important: If your ads already use a dataset, do not create a new one. Use the existing dataset instead. Splitting data between datasets can prevent your ad campaigns from learning from DocuRise conversions.
1. Open Meta Pixel Settings in DocuRise
1) Go to the DocuRise Integrations page.
2) Select Connect on the Meta Pixel card.
2. Find or Create a Meta Dataset
Open Meta Events Manager and select the business portfolio you want to connect.
If You Already Have a Dataset
Select the dataset your ad account already uses. It is fine if the same pixel is installed on another website.
If You Do Not Have a Dataset
1) Select Connect data in Events Manager.
2) Choose Web as the data source, then select Next.
3) Select Create a new dataset.
4) Enter a name that will be easy to recognize, such as DocuRise Sales Funnel.
5) If a restricted category applies to your business, select it accurately.
6) Review Meta’s terms and privacy information, then create the dataset.
3. Copy the Dataset ID
On the Events Manager overview or dataset details page, find the ID shown below the dataset name. Example: 123456789012345
- Enter the 15- or 16-digit numeric ID in DocuRise.
- The Dataset ID is used as the Pixel ID.
- Do not enter your business portfolio ID or ad account ID.
4. Save Basic Browser Tracking
1) Return to the DocuRise page and paste the copied ID into Dataset ID (Pixel ID).
2) Add a note if it will help you identify the connection later.
3) Select Save settings.
After you save, browser tracking is enabled by default on all document, form, and folder pages. You can turn it off only where you do not need it.
Turn Tracking Off or Back On for Individual Pages
- Documents and forms: open the content, then set Meta Pixel under Lead collection settings > After submission. Forms use the same setting as documents.
- Folders: use the Meta Pixel setting in Folder settings. The folder toggle applies only to the folder page and is not inherited by documents inside the folder.
New pages without an individual setting are treated as enabled by default.
5. Confirm That Events Are Arriving
1) Select the dataset in Meta Events Manager.
2) Open the Test events tab.
3) Open a public DocuRise page with tracking enabled in a new tab.
4) Check the following actions in order.
- Open a page: PageView
- View content or a product: ViewContent
- Submit a test lead: Lead
- Start a test checkout: InitiateCheckout
- Complete a safe test order: Purchase
6. If Visitors See Your Website Before DocuRise
If an ad sends people to your website first and they then continue to DocuRise, expand Does the ad go through another website first? in the DocuRise settings.
Add the displayed code across your existing website, not to DocuRise. This code helps carry each visitor’s Meta click identifier between domains. Never hard-code one visitor’s _fbc value into a link.
Privacy and Policy Checklist
- Provide any notices and obtain any consent required by applicable privacy laws and the Meta Business Tools Terms.
- Do not send sensitive information such as health, financial, or password data in event names or parameters.
- Use the same dataset for your ads and DocuRise so your conversion data stays together.
Troubleshooting
The Save Settings Button Is Disabled
- Confirm that the Dataset ID contains 15 or 16 digits.
No Events Appear
- Confirm that you are viewing the correct business portfolio and dataset.
- Confirm that Meta Pixel is not turned off on the document, form, or folder page.
- Keep the Test events tab open, then visit the page again.
- Check whether a browser extension or consent setting is blocking the pixel.
Events Are Counted Twice
- Confirm that you did not install another copy of the pixel on the public DocuRise page.
- Confirm that your ads, existing website, and DocuRise all use the same dataset.
Edit Settings or Disconnect
Go to DocuRise Integrations > Meta Pixel > Manage to edit the Dataset ID and note. Disconnecting stops pixel events from being sent from DocuRise pages for that account.
Optional: Use the Conversions API for More Reliable Tracking
At this point, your basic Meta Pixel connection is complete. For most businesses, connecting the Dataset ID is enough to get started.
The Conversions API is not required. You can add it later if you actively run Meta ads and want to measure important results such as lead submissions or purchases more reliably.
What Is the Conversions API?
A browser pixel sends actions to Meta from the visitor’s browser. The Conversions API lets the DocuRise server send important conversions directly to Meta.
Browser settings, ad blockers, and privacy features can sometimes prevent pixel signals from being delivered. Adding the Conversions API can reduce the chance of missing these important conversions:
- Lead: when someone submits a lead form
- InitiateCheckout: when someone starts checkout
- Purchase: when someone completes a purchase
The Conversions API does not replace the basic pixel. It supplements important conversion signals. PageView and ViewContent continue to be sent through the browser pixel.
Consider Using It If:
- You consistently generate leads or purchases through Meta ads.
- There seems to be a large gap between ad clicks and your actual lead or purchase count.
- You are concerned that ad blockers or browser settings may cause some conversions to be missed.
- You want Meta to learn from actual conversions and improve ad delivery.
If you are still testing ads or only need to measure page visits, it is fine to set this up later.
1. Create an Access Token in Meta
1) In Meta Events Manager, select the same dataset you connected to DocuRise.
2) Open Settings.
3) In the Conversions API section, select Generate access token.
4) Copy the generated token immediately and store it somewhere secure.
If the Generate access token button does not appear, you may not have sufficient permission for the dataset. Ask your business portfolio administrator for access.
2. Connect the Token to DocuRise
1) Go to DocuRise Integrations > Meta Pixel > Manage.
2) Expand Optional: Server-side conversion tracking.
3) Turn on Use server events.
4) Paste the Conversions API access token you copied.
5) Select Save settings.
3. Confirm That It Is Connected
1) Select the same dataset in Meta Events Manager.
2) Open the Test events tab.
3) Submit a test lead or complete a safe test checkout on a DocuRise page with tracking enabled.
4) Confirm that Lead, InitiateCheckout, and Purchase appear.
Server events can take a few minutes to appear. When the same conversion is sent from both the browser and server, DocuRise uses the same event ID so Meta can deduplicate it and count it once.
Treat the Access Token Like a Password
A Conversions API access token is secret information.
- Do not share it outside your team.
- Do not include it in screenshots.
- DocuRise does not display a saved token again.
- If you are editing other settings, leave the token field blank to keep the existing token.
- If the token is exposed, revoke it in Meta and generate a new one.