Articles on: Troubleshooting

How to Solve Problems Receiving Data by Facebook Pixel


View Application Logs


The first step is to check your application logs to identify the issue and apply the appropriate solution based on the identified cause. You can access detailed instructions on how to view the logs at the following link: How to view your integration logs.




🔥 The conversion event does not appear within the campaign



If the events are not showing on the campaign screen, this may have a few causes:


1. Events still in test mode

When events are configured as test, they do not appear in the campaign.


How to fix:

You must go to your pixel integration inside Yay! Forms and clear the Facebook Pixel test field, as shown below:


After that, just trigger a real event for the pixel and your events will appear in your campaign.


2. Event not yet approved

If the event has not been approved, it also will not appear in the list.

How to fix:

  • You will see a ⚠️ icon next to the event.



  • Click this ⚠️ icon to review the event.



  • Then, click on “I acknowledge”.



  • Finally, confirm the event.



3. Meta update time

Even after configuring everything correctly, it may take some time until the events are displayed in the campaign. This happens because Meta needs to process and update the data.


What to do:

Wait a bit — soon the events will appear normally, as in the example below.



🔥 Custom Event Not Created Correctly


Why does this happen?

If the custom event is not created correctly, it may not be recognized by Facebook and may not appear in your campaign.


How to fix?
  1. Access the Facebook Events Manager.
  2. Check if the custom event from Yay! Forms is listed correctly.
  3. If not, create a new custom event with the correct condition based on the form’s URL or the captured data.
  4. Make sure the event was saved and is being registered in the Events Manager.


🔥 Form Subdomain Not Verified and Authorized in Meta


Why does this happen?

If the form subdomain is not verified, Facebook may block the tracking of events, preventing them from being used in campaigns.


How to fix?
  1. Access the Facebook Business Manager.
  2. In the side menu, click on Brand Safety > Domains.
  3. Add the form subdomain used in Yay! Forms.
  4. Choose the verification method via MetaTag: Copy the metaTag generated by Facebook. Paste this metaTag into Yay! Forms and save the changes.
  5. Return to Facebook and click the Verify Domain button.
  6. Facebook will access Yay! Forms to confirm the metaTag and complete the verification.


☝️ Verification via metaTag is immediate, with no need for DNS propagation.




🔥 Assets Not Shared with the Ad Account


Why does this happen?

If the assets (custom events and subdomains) are not correctly shared with the ad account, the events may not be used in campaigns.


How to fix?
  1. In Facebook Business Manager, go to Business Settings.
  2. Navigate to Data Sources > Pixels.
  3. Select the Pixel used in Yay! Forms and share it with the correct ad account.
  4. Repeat the process for custom events and subdomains.



🔥 Test Event Enabled in Yay! Forms Configuration


Why does this happen?

If the test event is enabled in Yay! Forms, the events may not be sent correctly to Meta and will not appear in the campaign.


How to fix?
  1. On the Yay! Forms integration screen, check if the Meta/Facebook Pixel Test Event Code is incorrectly filled.
  2. Make sure the Event Condition has been set correctly to customize the tracking.
  3. In Facebook, create a rule of the type URL contains yayforms.link for generic tracking.
  4. If you want to track a specific form, use URL contains yayforms.link/your_form.
  5. Disable any test event configuration in Yay! Forms and save the changes.


Quick Diagnosis Checklist
  • Was the custom event created correctly?
  • Is the form subdomain verified?
  • Are the assets shared with the ad account?
  • Is the test event disabled in Yay! Forms?


If all the steps above are followed correctly, the problem should be resolved. If it persists, check the official Facebook documentation or contact the platform’s support.

Updated on: 22/09/2025

Was this article helpful?

Share your feedback

Cancel

Thank you!