How to find out how a tracking pixel got into my site - tags

I can see many tracking pixels on our website. Facebook pixel, TikTok, etc. We also have 2 tag managers implemented (Adobe Launch and GTM).
How can I find out the source of how a tracking pixel got implemented on my site. Was it added natively in the code? Was it pulled in from Adobe Launch?
is there a tool or extension that allows me to see the source and trace all the origin of tags on my site?
I looked at a number of extensions but nothing really helped

I think it's hard to see the source from the pixel event. But you can trace back from the pixel js code
Take Facebook pixel as example
Facebook pixel is coming from the fbevent.js then you can see the initiator from devtool and it is loading from GTM contianer.
But the Facebook event request can not tell the source but only the fbevent.js
So if your 2 tag management tools is well structured. This method might help.
Other way :
Block the gtm.js or adobe launch code in Devtool
Then if the pixel is not firing.
It should prove the pixel is installed from the tool.

Related

Media link of a video available on OTT platform

I am looking to integrate videos freely available on OTT platforms in India.
For example http://www.sonyliv.com/details/full%20movie/4709492313001/The-Butterflies-In-My-Head-%7C-Short-Film
However this is the web link to the video file. I am not able to fetch the media link to this and all such videos. Is it possible to do what I am trying and if so what should my direction of implementation be
I think if you look at the terms of use on that site (which are at the bottom and are, not very helpfully, hidden every time you scroll down) the conditions don't really allow what you are proposing, other than by linking to their site as your link above does, or sharing via their share options (Google + and Facebook for the example you show above).
So you can solve this technically with varying degrees of ease, depending on whether the source sites hide the media manifest URL's or use dynamically generated URL's etc, but it's probably worth making sure you are not going to get into issues over rights first.

Testing Facebook Messenger Scan Code

Facebook recently announced the introduction of messenger codes which can be used to add new contacts and, more importantly, communicate directly with businesses and business pages (which is why I'm interested in it).
It took me ages to find it but on the bottom left of the messages tab on my Facebook page I have the option to download my code in three different sizes - clicking the disc will open a modal window where you can click the Download button and choose from 300, 600 or 1000px PNG file downloads.
NOTE: While they are PNG files the background is not transparent which seems like a bit of an oversight to me but hey ho that's what Photoshop is for I guess.
The problem is that while I can download my code I can't find any way to test it on printed materials (or even electronically at the moment!). The scanning feature doesn't seem to have been rolled out for me yet (I tried re-installing the Messenger app to see if I got a newer version but that didn't work) and nor for anyone I know (I'm in the UK). The codes are bespoke to Messenger so can't be scanned or tested using any other app.
I'm probably too far ahead of the game but is there any way I can test to see if my code scans correctly, or anywhere I can go to find out? I would like to use it on some promotional material which is likely to be long term materials that I don't want to have to update in the near future (several years, by which time it's likely these codes will be more commonplace).
I also need to know what the redundancy is like. For example the high redundancy QR codes I generate can have up to 30% of the code covered while still being usable, which is great for design purposes. I can't find any official documentation as yet for these codes at all, let alone what is required, what the spec. is etc.
I know the most likely option is 'sit and wait' but I really would rather not if possible. I've never been very patient...
Thanks
UPDATE: My Messenger app has now been updated so I can test, but I'm leaving this here in case anyone knows of another way to test perhaps? If someone doesn't have Messenger on their phone for example.

How to prevent differences between facebook object debugger and share dialog data?

For some reason the object debugger displays all the data that I want to share with no issues but the share dialog fails to display the image. I have searched the site looking for answers and most of the solutions recommend clearing the browser cache. I've done this countless times but I still cannot make the share dialog display the image.
According to the open graph specs my image is valid so I do not know what the hell is going on.
How could I approach this? Should I report it as a bug to Facebook?
Is it because my image is not a square?
I have been testing this in a QA environment so it is not because of localhost.
Thanks!

Attach picture to Facebook for Android Share Dialog

I am currently trying out the Facebook for Android Share Dialog(https://developers.facebook.com/docs/android/share-dialog/) that was introduced in Facebook for Android SDK 3.5.
The code for starting the dialog is straight forward:
FacebookDialog shareDialog = new FacebookDialog.ShareDialogBuilder(this)
.setLink("https://developers.facebook.com/android")
.build();
uiHelper.trackPendingDialogCall(shareDialog.present());
Similar to setLink() there is a setPicture(String url) method in FacebookDialog.ShareDialogBuilder. But I can't get this setPicture() method to work. I have tried to put Url to local image files, online images and also FB staged images (fbstage://...) but nothing seems to make any effect on the Share Dialog viewed or the resulting post.
Is there anyone that got the setPicture() method to work?
from documentation of facebook feed
The picture must be at least 200px by 200px.
And even more restriction on image to be, check here
This is an image associated with your media. We suggest that you use an image of at least 200x200 pixels. However, bigger is better, so if you have a 1500x1500 image that you can use, please use it. We'll downsample and crop it for for people using smaller-resolution devices but will use it on a larger device. The larger this image is, the more likely it will be used when sharing stories on Facebook. (Note: image sizes must be no more than 5MB in size.)
With ShareDialogBuilder its not permitted to shared a local file but only remote files.
Currently I think that the only way (via a share dialog) is through the open graph action dialog.
In order for you to call the setPicture() should be used with setLink().
Please refer to the article below.
https://developers.facebook.com/docs/reference/android/current/class/FacebookDialog.ShareDialogBuilder/
You need to use an external URL like:
.setPicture("http://yourdomain.com/images/xyz.png");
Also, it will only display if you've set the link.

Issue with og:image and Facebook Recommendations

We have a site here: http://blistergearreview.com/ which we recently setup the open graph meta tags on. The issue that we cannot figure out is on the homepage we have the Facebook recommendations plugin and even though the og:image displays correctly using Facebook's lint tool (https://developers.facebook.com/tools/debug) for all of the posts in the recommendations box they don't actually display in the box itself. We've tried several things and are stuck. Has anyone else had an issue similar to this?
I also recommend using a jpeg/jpg image instead of png.
You may be able to see it using facebook debugging tools but when a user shares one of your links it may still be showing an outdated image.
It seems that facebook doesnt like png files...
I see your image (http://blistergearreview.com/wp-content/uploads/2011/07/012011_BlisterLogo_white2.png) is 309px x 73px. This is larger than the acceptable 3:1 aspect ratio maximum Facebook accepts. Get the width/height aspect ratio less than 3.0 and your image should appear.
I just wish Facebook would check the size in the linter tool so it would error out on images that don't comply (as you would have seen the error there).
For additional requirements, please see: https://developers.facebook.com/docs/reference/plugins/like/