Posts under category Facebook Other

⚠️Ad Library Report
⚠️Some disruptions: Ad Library Report Sep 11 2024 12:43 AM GMT+6
We have identified an issue with the spend calculations being incorrectly reflected in the Ad Library Report for some advertisers. We are currently working to resolve the problem and will provide an update here when resolved.

Hello, right now the threads API always return an error for my app when I try to access any of the GET endpoints, for example
curl --location 'https://graph.threads.net/v1.0/me?access_token=MY_TOKEN
The error looks like this:
{
"error": {
"message": "An unknown error occurred",
"type": "THApiException",
"code": 1,
"fbtrace_id": "AFng8FXzbvPZTDsF7GIAhqx"
}
}

I am trying to post a video through the Threads API in a single-thread post.
I upload the video to a public URL, using Vercel Blob, and I have verified that the video is there.
I use the POST /{threads-user-id}/threads endpoint to create a media container successfully.
When I use the POST /{threads-user-id}/threads_publish endpoint to publish the container, I get an error, stating: "The media with id {container-id} cannot be found."
The Threads API Troubleshooting page says: "If you are able to create a container for a video but the POST /{threads-user-id}/threads_publish endpoint does not return the published media ID, then you can get the container's publishing status by querying the GET /{threads-container-id} endpoint. ... We recommend querying a container's status once per minute, for no more than 5 minutes."
So I waited for 60 seconds and then queried the GET /{threads-container-id} endpoint, but it returns the following error:
{
status: 'ERROR',
error_message: 'UNKNOWN',
id: '{threads-container-id}'
}
The same code successfully publishes a single-thread post with an image (using the image_url parameter instead of video_url, of course).
I have also verified that the video conforms to Threads' Video Specifications (screenshot attached).
Any suggestions are welcome.
Thanks, Michael

We have a problem using Meta Pixel with advanced matching parameters in our single-page application. The problem lies in the fact that we cannot initialize Pixel multiple times (call fbq(‘init’) method) - we’d simply get an error in the console and the previous version of initialized Pixel would remain the active one. Our scenario is the following: at first the customers perform the signup on our website and from that we know several data points that can be sent alongside with «CompleteRegistration» standard event through advanced matching parameters - namely «email», «external_id» and «country». Later on customers complete PII and we start sending «PageView» and «Purchase» events, but at this point it’s no longer possible to update advanced matching parameters list with newly gathered information. Is there any possibility we can call fbq(’init’) with advanced matching parameters multiple times? We are aware that there’s a possibility to perform 2 ‘init’ methods - first being without advanced matching parameters and the second with advanced matching parameters, but we don’t want to make sacrifices during «CompleteRegistration» event sending.