We are seeing a Facebook Pixel event with the name of PageView%0A. Is this %0A at the end just the newline character that is being included for some reason?
This event only appears maybe once or twice in a 30 day period, but I'm curious whether anyone else has experienced this and how they dealt with it.
Related
I have a Facebook Pixel on my website that is tracking events. I saw on the Ads Manager dashboard, that the pixel logs my events in a categorized way, i.e.:
PageView, ViewContent, InitiateCheckout, etc.
Although when logging stats, I include some extra parameters like the product_id maybe or other things, that way when the PageView is being logged, at least I will know which product_id it refers to.
The problem is that the Facebook Ads Dashboard doesn't show any of the extra parameters, it only displays the Count field.
After doing some research, I found this link on Facebook Pixel Stats, where they claim:
Use the Facebook Pixel Stats edge to get pixel statistics.
I tried using the Graph API Explorer, and even the iOS FB SDK for it (API Here) they both return an empty data array:
{
"data": [
]
}
I tried multiple parameter combinations, fields, and everything else to no avail.
If anyone knows whether I'm looking at the wrong place, or what not, all I'm interested in is reading those "extra" parameters that I'm appending to every FB Pixel event I log. Thank you!
You need specifing the parameters for it.
Example:
{fb_pixel_id}/stats?aggregation=url
The answer is displayed for a specific period of time in the past - I would say 24 hours.
You can use paging at the bottom of the json response for going back in time: use the link provided in the content of the field 'previous', and you can step back day by day.
This has been asked a few times over the past couple of years but as Facebook tells me "Facebook engineers actively participate on StackOverflow.." So I'm hoping get get some joy here.
We have uploaded a video to youtube, passed it round and made sure we are happy with it, made it public and tried to change the title from 'xxx - final' to the actual title. However, Facebook shares are showing the old prerelease title but not the actual title, leading to much confusion amongst our subscribers and those trying to share the video. I should add the time between clicking the 'public' button to updating the title was a matter of minutes and seconds.
I have run it through the Facebook debugger and the scraper can see the changes but the problem persists along with the following debugger message:
"Attempted Frozen Title Change It appears that you are trying to change the property og:title from xxx to xxx. If so, you are not allowed to for this object because too many actions have been published against it."
This is obviously a real problem for us. Has anyone come up with a definitive solution or course of action? We can't simply delete the video because its for a band and there have been numerous post to not only Facebook but fan forums and elsewhere already and deleting and re-uploading the video would require an alternative url.
Many thanks
I managed to talk to a FB developer about this. Is seems that its a protective measure to stop click baiting, fake links and so on. His advice was make sure you upload the file as you want to see it when it goes live - ie. Don't use 'video 4.. final version' or some similar 'temporary' title because as soon as people start to view click or comment it becomes locked.
The engineer I spoke to was kind enough to unfreeze the video so all was well in the end, but looking at the comments of others who have had the same problem I was pretty lucky as it was a long standing Youtube account with 100,000's views and hundreds of links pointing to it meaning they were comfortable that I wasn't 'trying it on'.
So the bottom line is: if you want to upload a video and share it with your Facebook account, make sure the you have set the titles, tags and any metadata on the video immediately and before you paste to, or, share on youtube or there is a strong possibility that even though you can update that info on Youtube, Facebook won't recognise the changes and instead use the information it has in its database when the video was first scraped.
I've created custom open graph sentences for my story.
There is an open-graph action called Send and an open-graph object called Treat.
The story is called Send a Treat.
This issue is that after a day or so, the custom sentences are reverted to their previous values!
For example, for One to One:
I changed it to Simon has sent a treat.
However after a day when we started testing it, it changes back to Simon has sent {treat.title}
Is it because our custom sentences contain the word 'treat'? Has anyone else had this problem? Is there a way around it?
Update
Response from Facebook bug report:
This is by design. If you want to trigger the "One to One - Without Object Title" story, you need to leave the og:title tag empty. More info:
https://developers.facebook.com/docs/opengraph/using-objects/#objects-without-titles
What?
Every time I change a sentence in the OpenGraph->Stories section, it just reverts back to its previous value. This can't be 'by design'...
Okay so first off, sorry if the title doesn't make much sense...I'm not sure how else to summarize it!
So here's the issue:
I am using jQuery to attach a click event to my form's submit button. The jQuery click event triggers some GA code to track a virtual page view so I can use it as a step in a Goal funnel.
But what happens is that there's no delay between the GA code executing and the submit, so I'm concerned that GA isn't actually getting the data.
When I look at what's happening in firebug or httpfox (browser addons that look at the requests/response) vs. charles proxy (external sniffer, separate from browser) I am seeing two different things.
With firebug/httpfox I see the GET request to GA but status of 0 and it is showing up as
(Aborted) NS_BINDING_ABORTED
...though it does show bytes having been sent etc.. just nothing for response.
But with charles proxy, I am seeing the same GET request with a status of 200 and the 1x1 pixel response.
So my theory here is that GA is receiving the data, but that the browser is moving on before it gets the actual response - which I'm okay with, as long as GA is getting the data, I'm okay with this. But it is just my theory and I don't know...
I know I can write the code to simply delay the execution of the submit by 500ms or whatever as insurance, but I don't wanna have to do that if it's not necessary..
And I know if nothing else I can just see if the data is showing up in GA but GA has a 24-48 hour delay on data so it is hard to QA.
Does anybody know or have any suggestions from experience...has anybody else experienced this "abort" thing and can say one way or the other if it is necessary to delay the submit or whatever?
HTTPFox is not a real sniffer. It just tries to mimic one. So the data you see on it is not always what is really happening in the background. Charles should get you a better picture. If you're seeing the 200 code in Charles. So the chances are that the hit is going through.
The bad news is that when you fire hits at the time the page unloads. (Outbound clicks, insite link clicks, form submissions, window.unload, etc) they won't go through every now and then. This happens because the Google Analytics JS Call basically appends a GIF to the page. And it returns after that. Than the browser will load the gif. When the code returns the browser is free to go, and if it goes away from the page it will cancel any pending requests that it may have, including that small GIF image. So the browser might haven't sent the tracking code, or might have sent it, but the TCP connection didn't go through and the browser would need to resend the package, but he's not willing to do it anymore.
So if accuracy is a need for you, you should add a 200-500 ms delay to it. But remember that Google analytics is not an Accuracy Tool, and if some events don't go through it won't probably affect the final outcome of your analysis.
According to the informatin on this page: Sending Data to Google Analytics there is a possibility that your data is not really being sent (the bad news, as Eduardo said). Transcribing the most important information of that page, related to your doubts:
Many browsers stop executing JavaScript as soon as the page starts
unloading, which means your analytics.js commands to send hits may
never run.
An example of this is when you want to send an event to Google
Analytics to record that a user clicked on a form's submit button. In
most cases, clicking the submit button will immediately start loading
the next page, and any ga('send', ...) commands will not run.
The solution to this is to intercept the event to stop the page from
unloading. You can then send your hit to Google Analytics as usual,
and once the hit is done being sent, you can resubmit the form
programmatically.
I have a timed page that I need to use to submit a form upon the end of a specified time period.
The usage would be: User visits page, 90 seconds later all form data is submitted and user is redirected to next page.
The user is well aware that the page they are on is timed (its for a web-only experiment), so I'm not worried about "unfriendly" browser behavior on this page.
Ideally, I'd like to avoid using JavaScript (some of our targeted users are using no-script for various reasons, but if its the only way, so be it), and would also like to avoid just passing variables through the URL (to cut down on the possibility of spoofing). It is easy enough to set a META refresh tag to do the redirecting, but at the end of the time period I need some way for the response header to be set as if the submit button was clicked, whether or not it actually was.
Thanks in advance for any thoughts you might have.
Can't be done.