Troubleshooting Facebook Ad Reporting in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

Most Facebook Ad Reporting issues come from inactive integrations, UTMs placed on the wrong field, duplicate ad-set names, or the wrong Facebook Page selected when mapping lead forms.

Facebook Ad Reporting only works when the integration is active and UTMs are configured the way Sparkforge expects. Here are the five settings to check first.

1. The Facebook Ad Account integration must be active

In the sub-account, go to Settings > Integrations and confirm the Facebook Ad Account is connected with admin permissions. If the page is missing from the integration list, the connecting user needs Page admin or equivalent role.

To advertise for a Facebook Page or Instagram account in Meta Ads Manager, the connecting user needs Page admin (recommended), editor, moderator, advertiser, or jobs manager role. Accounts using the new Pages experience can manage ads through Ads Manager or Meta Business Suite when task access is granted.

2. UTMs go on Tracking, not Destination

Add the UTM template under the Tracking field at the ad level. UTMs placed on the Destination URL break attribution because Facebook overwrites the click URL.

3. Use unique names for Campaigns, Ad Sets, and Ads

Duplicate names cause duplicate contact entries across ad-sets in reporting.

Wrong

Campaign: New Restaurant in Town · Ad Set: Dish 1 · Ad: Fresh Red Pasta

Campaign: New Restaurant in Town · Ad Set: Dish 2 · Ad: Fresh Red Pasta

Right

Ad Set: Dish 1 Starter · Ad: 1.1 Fresh Red Pasta with extra sauce

Ad Set: Dish 2 Main Course · Ad: 2.1 Fresh Red Pasta with no sauce

4. Renaming an existing ad will not fix attribution

UTMs lock to the original Campaign, Ad Set, and Ad name when the contact was created. If you rename later, the list view updates but Sparkforge still attributes sales, leads, and ROI to the old name. To change naming cleanly, create a new Campaign, Ad Set, and Ad — do not rename.

5. Map the correct Facebook Page on Lead Forms

When connecting Facebook Lead Form Mapping, pick the page the form actually lives on, then mark the mapping active. Notes on field mapping:

  • Standard text fields and most custom fields map cleanly.
  • Radio custom fields cannot be mapped to Facebook Lead Forms.
  • Timezone fields cannot be mapped.

Frequently Asked Questions

Why are my Facebook leads not showing up in Sparkforge?
Most often the Lead Form mapping is inactive or pointed at the wrong Facebook Page. Re-check the page selection and toggle the mapping active.
I renamed an ad set and now my data looks wrong. How do I fix it?
You cannot retroactively fix it. Existing UTMs still reference the old name. Create a new ad set with the correct name going forward and let the old data age out.
Why are some Facebook custom fields missing from the mapping?
Radio fields and Timezone fields are not supported by Facebook Lead Form Mapping. Use text or single-select fields instead.
Where do UTM parameters need to go on a Facebook ad?
On the Tracking field at the ad level, not on the Destination URL. Facebook rewrites the destination, which breaks attribution.

Was this article helpful?