We publish advertisement on facebook and we have a new domain. The problem is that advertisement click rate on facebook panel is 6193 but only 1682 person enter website accordşng to google analytic.
There are about 4500 hit which is lost. AS you know, users are redirected to our website after click on facebook advertisement but they cannot access to our website. we are waiting your kindly response.
our website: testmastersatinal.com
Try using Google's URL builder to properly code the landing page URL in such a way that GA will recognize the traffic as having come from your FB advertising campaign. Here's a blog describing how it is done.
For reasons that I do not yet completely understand - but apparently have to do with the internal FB redirect process for ads, much of my traffic from Facebook shows up in Google Analytics as (direct)/(none). I've found that setting the GA UTM codes on the landing page URL will help by using Google's URL builder helps with this issue.
More generally, in my experience, advertiser reported clicks are often different from what you see in GA. In fact, I'm working on trying to resolve this issue now with another advertising platform (not FB) who is billing us for 2.5x the number of clicks we are seeing in Google Analytics.
There are many possible causes for this, and you can find relevant discussions on
webmasters, moz.
One thing you should try is segmenting the referrals by device (mobile, tablet, desktop) or operating system, etc. See if the percentage of traffic is much lower from your ad on one particular device or operating system. This may indicate that the GA tracking is not working correctly on that device or OS.
Related
Recently Apple introduced a custom product page feature where multiple different App landing pages can be made.
While running Facebook ads, there is no option to link an ad set to a particular landing page’s Url. It only detects the app and sends to main listing.
Any experience with this?
Can any 3rd party service like Appsflyer help in this case?
Seems there is no chance to do it because Facebook didn't give such an opportunity even with deep links. Only web2app solutions.
We have been trying to get facebook approval for the use of an existing, already approved (with other people using it) third party extension for magento 2 that helps a user design photo albums. We would like to enable our customers to have access to their facebook photos when designing photo albums.
The initial app review was submitted at about the time facebook started making all of it's changes and thus sat idle for three months as they changed some of their internal policies and handled the subsequent backlog. It was even cancelled at one point requiring us to re-submit it.
Most recently, it finally received a review and was rejected because facebook confused the photo behavior with the login behavior.
I'm not trying to re-submit the review request with more details to show that it's a different piece of software performing a different function from the login-with-facebook but now (unlike the first time) I'm getting an error when using one of the test accounts:
Can't Load URL: The domain of this URL isn't included in the app's domains. To
be able to load this URL, add all domains and subdomains of your app to the App
Domains field in your app settings.
This error didn't appear when I created the 'experience' video 3 1/2 months ago so presumably it's something new from facebook's end as the settings in the app haven't changed. I can only guess as to the cause, but the third party app uses an end-point that is not on our domain but is instead one of their domains for their designer hub which actually handles the album design. The plugin is the MediaClip album designer and the end point is on photos.mediacliphub.com
But the facebook app settings won't allow me to add photos.mediacliphub.com to the App Domains saying:
App domains must match the domain of the Facebook
Web Games URL (https), Mobile Site URL, Unity Binary
URL, Site URL or Secure Page Tab URL. Please correct
these domains: photos.mediacliphub.com
Of course since we are the only one of their customers sitting in the middle of a review process at the moment, I'm having a hard time convincing mediaclip that it is a problem with the urls/changes-at-facebook. (especially since I am not entirely sure of that myself)
Facebook, meanwhile has closed itself off from the world in regard to any means to contact support with an actual specific question or inquiry. I've tried joining the Facebook Developers group on facebook and posing the question but so far it hasn't received a single reply or comment.
If anyone knows what might be going on or has any suggestions, it would be greatly appreciated for as of this point, I can't even re-submit the review request if I'm receiving errors in the experience as it will just get rejected.
Good day,
Background: We have a single web application that multiple external websites link to; users visit www.aaa.com or www.bbb.com and can then click through to our web site at www.example.com.
When we send email comms, the users are directed to their respective client URL.
We require a method of tracking these users from email comms using Google Analytics so that we can see their activity in the Campaigns section.
Issue: The problem is that whilst we have Google Analytics enabled on www.example.com, we are not able to install analytics on client URLs. This means that if we affix the Google tags after the URL in emails, these are stripped out when a user then navigates around a client URL before visiting ours. This then means they do not appear in the 'Campaigns' tab of GA. That is:
trackable --> www.example.com?utm_source=offeremail&utm_campaign=testcampaign&utm_medium=email
not trackable -- > www.aaa.com?utm_source=offeremail&utm_campaign=testcampaign&utm_medium=email
Question: Are we able to start the tracking once a user clicks a link in an email but then accesses our site from another site and then show the results in the campaign tab?
Thank you!
Short answer: No. You need to pass the UTM-parameters in the URL for Google Analytics to understand it is campaign traffic. This is usually the issue with redirects between websites, that this UTM-tagging is lost, thus losing the campaign information.
What I would suggest is that you look at referrals or have your clients add tracking to the links back to your website. Then correlate that to the dates of your send-outs. It is a bit of a middleground, but it should do the trick to atleast see trending success.
I have a Facebook app (canvas app), let's say https://apps.facebook.com/test, that redirects and works as expected on the desktop (on all browsers that I have tested).
On mobile phones (both from the FB app and the browser) the path gets redirected to https://m.facebook.com/apps/test/?ref=web_canvas, which gives a "This page cannot be found" error. Why?
This has been reported as a bug to Facebook and Facebook has confirmed it as a bug. They have not provided a date on when the fix will be ready.
You can follow the status of the bug here:
https://developers.facebook.com/bugs/1051463851558493/
Update: Facebook have (since the information struck-out below) completely removed support for this. The thread about this is here:
https://developers.facebook.com/bugs/1051463851558493/
The top-level information is:
We have now deprecated Mobile Canvas URL. This means that you will no
longer be able to direct to a website/app directly within the Facebook
mobile web based upon the external destination URL you have specified
in the 'Mobile Site URL' field for the app on developers.facebook.com.
Furthermore, we have removed the 'Mobile Site URL' field from the app
setup going forward. This deprecation also applies to apps that were
previously whitelisted.
So it's time to move away from this functionality, and either integrate the newer FB Instant Games functionality or just link to an external website as having your canvas app hosted inside the FB mobile app simply isn't possible as it was in years gone by.
Facebook has disabled mobile URLs working by default:
We recently identified a handful of apps misusing our mobile App Center to redirect people to unauthorized sites. As a precaution, we have temporarily turned off the ability for developers to direct to a destination URL for any app in the "Mobile Site URL" field on the dev site.
Now if you wish for this functionality to work, you need to be logged into Facebook and then go to the following URL:
https://www.facebook.com/help/contact/588209321338256
This URL will effectively put your request in a queue, for someone at Facebook to manually verify your app configuration isn't malicious, and then enable the redirection. I do not like posting this answer, as I know it will eventually become invalid, but as of today it is the only answer. As stated by Scott, you can follow progress on this issue here:
https://developers.facebook.com/bugs/1051463851558493/
Please ignore the fact it claims the issue has been 'Fixed' as Facebook count the above workaround as a fix. If you read through the comments on the bug you can note the waiting time to get the URL fixed (on a per app basis) is typically several weeks.
On May 28th, 2017, Facebook confirmed that the Mobile Canvas URL has now been deprecated. Any apps already using (and white listed) will stop working, and no new apps will be accepted.
Hi everyone,
First, please accept my sincere apologies for the delay in getting
back to you with an update on the status of Mobile Canvas URL. I
understand your frustrations, particularly if you submitted your
details via the form and were waiting on a response.
We have now deprecated Mobile Canvas URL. This means that you will no
longer be able to direct to a website/app directly within the Facebook
mobile web based upon the external destination URL you have specified
in the 'Mobile Site URL' field for the app on developers.facebook.com.
Furthermore, we have removed the 'Mobile Site URL' field from the app
setup going forward. This deprecation also applies to apps that were
previously whitelisted.
The Mobile Canvas URL feature is a vestige of a long ago deprecated
product called Mobile Canvas. Facebook maintains a high commitment to
quality, so we don't want to leave unsupported products active —
especially when they continue to cause bugs for our developers. Going
forward, we're recommending you take advantage of the well-supported
Facebook Games on Web product to drive traffic to your app.
We've also introduced Instant Games which lets people play mobile
games within Messenger and Facebook News Feed. We invite you to sign
up for our closed beta program. We believe letting people play games
together on Facebook is a powerful experience for both players and
developers.
If your app is still set up to rely on Mobile Canvas URL
functionality, we recommend taking the following actions:
If you're using Mobile Canvas to link to a page on mobile web, you need to update your app to handle the redirection in the desktop
iframe. User interaction is required to redirect away from web canvas
as our Platform Policy does not allow automated redirects from canvas.
If your app was previously whitelisted, you will need to take action as this deprecation supersedes any workarounds you have in place.
Thank you for your understanding as we continually improve the
products and services we offer to both developers and players. Again,
please accept my apologies for the wait in getting back to you with
this information
Best regards,
Tim
See this thread https://developers.facebook.com/bugs/1051463851558493/
This question has been around but my scenario is pretty tricky. I'm in the half-way of developing and launching a pretty large Facebook application (website) in Google App Engine and brought my own custom domain to point to the app id.
In the Facebook apps panel I registered :
1 application for the custom domain
1 application for the subdomain given by google app engine
Few days I've been testing the application through the custom domain. I forgot to change the redirect URL in my authentication URL, its value was still left as the subdomain URL given by app engine. So, the login process used to start from my custom domain and reach the subdomain in the address bar.
Facebook has been showing notifications that the custom domain is pretending to be a website that it is not and asked my testers to reset their Facebook password. I didn't promote that URL any longer. We continued testing OK with the subdomain URL.
Now in the Facebook apps dashboard. I can't make any configuration changes in my custom domain configurations. Its showing
Error
App Domains: li__ke__2__marry.c__om (without __) is not a valid domain.
Site URL has been been identified as malicious and/or abusive.
It's basically a misunderstanding, the Facebook algorithm must have assumed that my custom domain must be doing something malicious after tracking its activity. Actually, it is not, and I'm not blaming Facebook algorithm for this mishap.
My question is : How to apply to have this negative rating removed? Facebook is a very reputed product, and I hope they follow the most basic principle : every in should be made with an out. If they have a feature to blacklist I'm hoping to get a place where I can file a False Detection/Re-Classify Requests. It hasn't cheated anybody and all the few people that used it were my friends and to my laziness I was not testing it in sandbox mode nor did I register/configure any of them as application testers! But that doesn't mean my URL is malicious.
A similar request in the bug report feature of Facebook was rejected marking that it should be put in the Stack Overflow community and even in the Stack Overflow community, I found someone authoritative closing a similar question asking them to post it in the bugs section of Facebook. This link from the community for the exact problem forwards the user to Stack Overflow itself.
Here is a form for appealing blocked content (in your case URL). However there are very few chances of getting unblocked your URL but still you may try this form and hoping to get reply from Facebook. In any case if your URL is unblocked there is a high probability that your future users will see a captcha when visiting your app from mobile devices. So I can recommend to change the URL and continue developing with other URL.