We are working to improve our Meta targeting by using Zapier to automatically update our custom audiences in Meta Ads. We have connected our Meta Ads account and the connection is working according to Zapier. However, when we go to select an audience within our Zaps, none of our custom audiences are showing up.
Our permissions on Meta are Admin level across the board so we are not sure how to troubleshoot in this situation.
Page 1 / 1
Hi, You may need to accept the facebook terms as shown in the above screenshot. After that, trying refreshing and see if the data populates.
Hi, You may need to accept the facebook terms as shown in the above screenshot. After that, trying refreshing and see if the data populates.
Thanks for the suggestion. The goal with this Zap workflow and the others that we are creating like this one are to add a new email/person to an existing custom audience. We don’t want to create a new audience every time a new lead is generated. Hope that makes sense...
Kindly give it a try and let me know how it goes? I'll keep an eye out for your response!
@ken.a I tried entering the Audience ID from Meta Audiences directly as the custom audience field. However, after testing the zap it said it failed.
Hi there, @NUHS_MKTEAM 👋
Just came across this and wanted to check how things were going. Are you still seeing those “Unsupported get request. Object with ID ‘XXXXXXXXXXXXX’ does not exist, cannot be loaded...” errors in your Zap?
If so, it could be that the permissions for the connected Facebook account aren’t quite right. 🤔 Which may also explain why the audiences aren’t being loaded in the Custom Audience field—if the Zap doesn’t have the correct permissions to be able to access the audiences then it won’t be able to load them in that field. I know you mentioned previously that the account has Admin access but can you double-check it definitely has the correct permissions granted? If Admin access was granted after the account was connected then you’ll need to reconnect the account to ensure it’s connecting with the most up to date set of permissions.
If the account permissions are correct then it could be erroring as the value selected for the Email field isn’t an actual email address:
In which case, testing with a valid email address may help to fix the error.
Keen to ensure you’re all set so please keep us updated on how you’re getting on!