I'll be upfront about the complete lack of coding experience I have, so any and all help is appreciated.
My Facebook pixel was tracking traffic without any problems for my client's site...up until he moved the registration page to a sub-domain. The tracking then immediately cut off.
This wouldn't usually be a problem b/c we can rely on Google Analytics for conversion data, but in this case, it matters since our campaigns were optimized around the conversion data acquired in Facebook.
According to the FB rep I talked to earlier, our sub-domain is recognized as a completely different site and therefore, can't be tracked.
I don't buy this...I can't be the first person to come across such a simple problem. Any FB developers out there with a workaround?
I know it's been a few months since you asked the question, but I thought I'd update (found this myself via a Google Search).
Something you could look at doing is putting the Facebook Tracking pixel on the main domain, then including it in an iframe on the registration page. You can then use the iframe URL for the "conversion URL" on the Facebook end:
Here's a JSFiddle with some sample code you can use: https://jsfiddle.net/dxz68suw/
HTML:
<div id="fb-pixel-outer">
<iframe src="http://mainsubdomain.yoursite.com/track-conversion.html" id="fb-pixel-inner">
</iframe>
</div>
<!-- track-conversion.html should be a basic HTML page containing your Facebook Pixel code -->
CSS:
/** Outer container, this prevents scrollbars from appearing due to iframe positioned outside of viewport **/
#fb-pixel-outer {
overflow: hidden;
position: absolute;
top: 0px;
left: 0px;
}
/** this styling ensures that the iframe is miles outside of the viewport, and loaded by browser **/
#fb-pixel-inner {
position: absolute;
left: -9999px;
top: -9999px;
overflow: hidden;
display: block;
width: 1px;
height: 1px;
}
It's a bit hacky, and not ideal, but should work.
Where does the above code go? On your main domain header?
Does this look right to you?
<div id="fb-pixel-outer">
<iframe src="https://botox.everyoungmed.com/track-conversion.html" id="fb-pixel-inner">
</iframe>
</div>
<!-- track-conversion.html should be a basic HTML page containing your Facebook Pixel code -->
Related
I am a New DFP User. I have added two adverts for my different sites. In DFP, adverts shows as delivering, but still now my advert is not placed in my site. what can i do next? why my advert is not displaying? Please reply me and explain what mistake i have done?
waiting for your kind response.
i herewith attached my Site & DFP screenshot with this. Kindly refer this
in inspect-element of my site, it shows the below code.. but it seems to hidden!
<iframe id="google_ads_iframe_/41172323/Thakkali_Test_0__hidden__" name="google_ads_iframe_/41172323/Thakkali_Test_0__hidden__" width="0" height="0" scrolling="no" marginwidth="0" marginheight="0" frameborder="0" src="javascript:"<html><body style='background:transparent'></body></html>"" style="border: 0px; vertical-align: bottom; visibility: hidden; display: none;"></iframe>
The only thing I can do is help you help yourself. Adtech is complicated, lots of moving parts, lots of places where a small error can cause big and unpredictable problems. I don't see any obvious problems in the information that you provided but there can still be problems with tagging or targeting. You have 442 criteria for targeting the line item, big chance that the problem is there.
But to check this you can use the GPT console. Enable this by by adding:
?google_force_console
to the URL when loading your site. This tells you if you have correctly tagged the page and you can also open 'Delivery diagnostics' which gives you an overview line items that where considered/rejected for a specific ad unit.
More information about the GPT console:
https://support.google.com/dfp_sb/answer/181070?hl=en
Besides that; be patient. There is a time lag between DFP telling you that it's delivering and the actual delivery. Changes are rarely instantaneous with DFP.
OK, this is my first question on SO, so be gentle. Doing my best to be thorough. :)
We want users to be able to share URLs specific to ordering photos of their children on our site. We currently have no interest in implementing Open Graph on our site. We're not trying to track that data at this time, and it's more work than I have time for anyway. So I opted for the quickest route: the sharer.php link.
I realize that FB's sharer.php is deprecated in favor of 'og:' tags, but see no indication at https://developers.facebook.com/docs/reference/plugins/share-links/ - which was updated three weeks ago, so it obviously should still work.
I followed the instructions in these blog posts to customize the links:
http://ar.zu.my/how-to-really-customize-the-deprecated-facebook-sharer-dot-php/
http://www.therykers.net/?p=37
However, we only get thumbnails to properly display in the FB Share dialog when using our site's demo subdomain, even though the source code for our sharer.php link is identical in all instances (aside from the image/name of the child, the site's subdomain, and the photography studio name).
This source code (demo site) properly displays the image:
<a href="https://www.facebook.com/sharer.php?
s=100
&p[url]=https://demo.mysmilecentral.com/public/show?link_code=funankizwd
&p[images][0]=http://assests0_bop_heroku_com.s3.amazonaws.com/images/sp00/sp00-001-1/0106_022_0028.jpg
&p[title]=Order%20Pictures%20of%20CASEY%20at%20Sample Studio's%20MySmileCentral!
&p[summary]=View%20images%20and/or%20order%20pictures%20of%20CASEY." target="_blank">
<img src="https://assests0_bop_heroku_com.s3.amazonaws.com/images/fb-share-btn2.png" style="margin-top: -35px; margin-right: 126px; float: right" />
</a>
But this ('live' site) doesn't:
<a href="https://www.facebook.com/sharer.php?
s=100
&p[url]=https://rowlandphoto.mysmilecentral.com/public/show?link_code=2cols21uogpx
&p[images][0]=http://assests0_bop_heroku_com.s3.amazonaws.com/images/bj20/bj20-bb2013-1/1448_img_0128.jpg
&p[title]=Order%20Pictures%20of%20Gabrielle%20at%20Rowland Studio's%20MySmileCentral!
&p[summary]=View%20images%20and/or%20order%20pictures%20of%20Gabrielle." target="_blank">
<img src="https://assests0_bop_heroku_com.s3.amazonaws.com/images/fb-share-btn2.png" style="margin-top: -35px; margin-right: 126px; float: right" />
</a>
Both images meet the dimension requirements of FB Share, and are publicly viewable.
I've spent several hours trying to find an answer (Googling, searching here), and haven't come up with a logical reason for this.
If you open up your web inspector you would realize that https://www.facebook.com/sharer.php deprecated redirects to https://www.facebook.com/sharer/sharer.php, which only has one supported parameter u for the url being shared which depends on Open Graph meta data (which you have opted not to use).
The p array (p[url], etc) is not supported in the new Facebook Share dialog. By using deprecated features, you should expect unstable behaviour or no results at all. There isn't anything much more to say about that.
Is it possible that several mail applications (e.g. Hotmail, Thunderbird, OSx Mail) replace the whole <img> tag?
In the generated newsletter i have e.g.:
<img style="padding: 0px 10px 0px 0px; outline: none; " class="editor-img" src="/upload/11/2_5.jpg" alt="image" width="165" height="107">
and in the received newsletter i got something like:
<img src="foo" border="0">
Can someone explain me that and how i can prevent this?
Thanks
Yes this is absolutely possible. For instance T-Online in Germany exchanges images ending on .php with a dummy image. Many webmailers parse and adapt email code before it is finally rendered in the inbox. Like Gmail tel:-links numbers of which it thinks it's a phone number. In your case, the relative path doesn't make any sense. Try an absolute image path like src="http://www.YOURDOMAIN/upload/11/2_5.jpg".
Facebook Share Button breaks my SSL/HTTPS connection in Chrome. Chrome is displaying a red HTTPS with a (/) slash displaying acroess the https.
Its states:
Your connection to XXXXXXXXXX.com is encrypted with 256-bit encryption. However, this page includes other resources which are not secure. These resources can be viewed by others while in transit, and can be modified by an attacker to change the behavior of the page.
The connection uses TLS 1.0
The connection is encrypted using AES_256_CBC, with SHA1 for message authentication and DHE_RSA as the key exchange mechanism
The connection is not compressed.
How can I fix this issue? My code for Facebook is listed below:
name="fb_share"
share_url="https://mysexywear.com/product_details.php?prodId=<?php echo $prodId;?>&catId=<?php echo $catId;?>"
href="https://www.facebook.com/sharer.php">Share
src="http://static.ak.fbcdn.net/connect.php/js/FB.Share" type="text/javascript"
Try using a relative protocol, like so:
name="fb_share" share_url="//mysexywear.com/product_details.php?prodId=&catId=" href="//www.facebook.com/sharer.php">
try this url ;)
https://facebook.com/connect.php/js/FB.Share
src="https://static.ak.fbcdn.net/connect.php/js/FB.Share" type="text/javascript"
Surely that would work?
use this codes:
<script>
function fbs_click()
{
u=location.href;
t=document.title;window.open('http://www.facebook.com/sharer.php?u='+encodeURIComponent(u)+'&t='+encodeURIComponent(t),'sharer','toolbar=0,status=0,width=626,height=436');
return false;
}
</script>
<style>
html .fb_share_link {
height:18px;
display:block;
float:right;
margin-top:1px;
width:57px;
background:url(https://www.kiraguru.com/images/fbshare.png) no-repeat top left;
}
</style>
<a rel="nofollow" href="http://www.facebook.com/share.php?u=<;url>" onclick="return fbs_click()" target="_blank" class="fb_share_link"></a>
Change the " https://www.kiraguru.com/images/fbshare.png " field and change style code for your custom design.
!!! Important -> You have to use https:// for share button image.
Thanks.
Referencing this link to the Share Button JavaScript code will return a Security Certificate error warning in each of the major web browsers:
https://static.ak.fbcdn.net/connect.php/js/FB.Share
Until Facebook resolves the issue it is not possible to acheive a satisfactory user experience that uses the JavaScript-implemented Share button within a website served over https.
I'd suggest one of two workarounds:
1) Implement a "fake" Share button by creating a Share URL and applying it to an image:
<a href="https://www.facebook.com/sharer.php?u=http%3A%2F%2Fwww.your_url_encoded_webaddress.com" target="_blank">
<img src="../images/Share_Button.png" border="0" />
</a>
2) Use one of Facebook's non-deprecated Social Plugins ("Like" or "Send") to achieve similar functionality. Both of these are still fully supported and work over https:
http://developers.facebook.com/docs/plugins/
I have a facebook 'Like' button on my page and it's working fine. But when the visitor is logged in as a 'Page' at facebook it includes a photo and breaks my design. I guess this is because Pages aren't allowed to like things.
I pretty much have an iframe like this: http://developers.facebook.com/docs/reference/plugins/like-box/
Any ideas of how I get rid of this image? Any way to alter the design, disable this "feature" or check if the user is logged in as a page (to hide the whole thing)?
Thanks
Edit:
Screenshot of the issue: i.imgur.com/gLa7Q.png
In the top one I'm logged in as a regular user and the bottom I'm "Using facebook as Page"
The code I'm using: <iframe class="facebook" src="http://www.facebook.com/plugins/like.php?href=<?=urlencode('http://www.mysite.com')?>&layout=standard&show_faces=false&width=210&action=like&colorscheme=light&height=45" scrolling="no" frameborder="0" allowTransparency="true"></iframe>
You can use the 'overflow' element in your css to stop it breaking the design. This at least keeps the like box the same size whatever somebody is logged in to Facebook as.
1) Wrap your like box in a div and give it an id (in the HTML)
<div id="mylikebox"> Facebook like Box Code in here </div>
2) Add to CSS (adjust height and width if you need to)
#mylikebox {
height: 70px;
width: 210px;
overflow: hidden;
}
Let Me Know if it works out!
I just noticed the exact same issue. Seems a bug on FB's part, as they provide an insertion code for their like button that breaks under a particular but perfectly normal condition (i.e. signed in to FB as a page.) I would love a solution too. In the meantime the bug has prompted me to remove the FB like button altogether from my blog, which unfortunately seems to be the only solution at the moment.
I found this to be true on the facebook developers like box configuration page. Definitely a facebook bug.
The answer provided by Nathaniel works for me. I have all my social icons in a line: http://www.cg-its.com
By setting a div height of 30, and adding the overflow: hidden attribute, if someone is logged in as a page rather than personal account they can see part of the red box, and the 'switch' URL allowing them to log back in as personal.
It's not perfect, but for the amount of users it will affect it is a good fix.