Ads

MNMxen
Member | Platinum Partner
Member | Platinum Partner

Facebook Ads Contact tracking errorsd

Hi, 

We keep on getting these Engagements and Permissions contact tracking errors (screen capture attached below for reference). 
We already followed the steps recommended in the HubSpot Knowledge Base and did the following actions:
1. Disconnected and Reconnected the ads accounts to refresh tracking,
2.  Clicked the "Fix Error", and "Refresh Tracking"

3. Checked permissions and the user who connected the ad account has admin permissions both in FB Ads and FB Page.

 

Is there anything else we should try doing to resolve this issue? 
Does this error affect HubSpot reporting in Marketing >Ads?

Looking forward to hearing your advice, especially those who encountered the same issue.

 

Thank you in advance. 

 

Ads Tracking Errors.png

 

 

 

 

0 Upvotes
1 Reply 1
bsheen
HubSpot Moderator
HubSpot Moderator

Facebook Ads Contact tracking errorsd

Hi @MNMxen,

 
Thanks for reaching out to the Community!
 
From taking a look at your account, it seems these errors have been resolved. Great!
 
If you are still having experiencing Ad errors, please feel free to DM me and we can take a look together. 
 
For reference, the High Engagement error usually stems from the fact that Facebook uses an algorithm to optimize ads in their network. To prevent interfering with this optimization, HubSpot will not apply tracking to any ads that have more than 20 engagements at the time you connect your Facebook ad account to HubSpot. 
- see Resolve Facebook ad tracking errors - Too many engagements

Regarding the "Invalid Page Account Permissions" error, this usually appears when the user who originally connected the ad account to HubSpot doesn't have sufficient permissions for the account or business page. To resolve this issue, make sure the user who connected your account has the permissions required to sync Facebook leads to HubSpot.
- see Confirm your permissions and settings in Facebook Business Manager

I hope this helps! Looking forward to confirming these errors have been resolved!
 
Best,
Brendan