I have developed an app that retargets customers when browsing a website and I have some problem with UTM tracking and Google Analytics.
For example if a client gets a customer to click on a FB ad and lands on their website they will have a custom FB utm. After browsing the website my app will display a pop-up and when a client clicks on it he receives my custom UTM.
The problem is that clients loose conversion rate data for the original traffic source and I need to figure out a solution.
Help is very much appreciate
It's not a good practices track with utm inside your site, if the pop-up is on the same domain, dont do it?
In you example, if the user comes from FB, yes, you need to tack with the utm, but the pop up is on your site... lets check the option?
If the asnwer is yes, try to track the user with a Custom Dimention on a Session Level, that will solve almost all your problems.
If the answer is no, you can only store a single UTM per sessions, that means that there is no option to avoid the overwriting the UTM, even consider the referal exclusion.
More about Custom dimentions:
https://support.google.com/analytics/answer/2709828?hl=en
Related
I have like/share buttons on my website and am not currently using an appid. Finding information on whether this is a necessity for the above configuration is difficult to confirm. When going through the Facebook app "create" forms, I'm really confused by a lot of the requirements as it seems to be more focused around actual apps rather than websites, which login via fb etc.
In the past I have created an app for one of my other websites and I don't believe there was any verification/submission process at this point (about 2-3 years ago). Reviewing my old app configuration now I can see that it is not "live" - does anyone know whether Facebook implemented this submission process in the last couple of years, and then de-activated any live apps that were created prior to this?
I now want to setup a new app for my new website and I'm unsure what the different 'action types' mean and what I would need to simply use like/share buttons on the website. Could someone give me a quick run down of what I'd need and what they are?
Any other info/tips people can provide would be greatly appreciated. I'm finding that the like/share DO still work without the app, but sometimes the share button doesn't work properly (I have a feeling this is something to do with the app).
Thanks
If you are just using the Social Plugins, you don't need to have a Facebook App ID.
If you want more integration, it will be required. Creating an App ID is like registering your App, wether an iOS or Android App or just a website, so that you can make Graph API calls for it.
The easiest way to register your website is to go the quickstart: https://developers.facebook.com/quickstarts/?platform=web (or https://developers.facebook.com/apps). There you can type a name and follow the steps.
You can then follow the "Sharing best practices" (https://developers.facebook.com/docs/sharing/best-practices#tags) on how to use the App ID. For example, by including an fb:app_id meta tag on your pages.
There is a review process, since last April, but that is only needed if you use permissions for your App. If you just use the plugins, that is not needed.
Can you explain more what is exactly not working?
Update
The time you create a page the Facebook crawler does not know yet what the Opengraph data for that one is. This will happen after the first share, but if you want to ensure it is correct from the first share on, you can force a re-scrape.
This section explains how that works:
https://developers.facebook.com/docs/sharing/opengraph/using-objects#update
When an app triggers a scrape using an API endpoint This Graph API
endpoint is simply a call to:
POST /?id={object-instance-id or object-url}&scrape=true
what's the difference between apps.Facebook and Facebook.com/COMPANY_NAME/app_1234567 ?
For example: http://www.facebook.com/AcademyofArtUniversity/app_307555419320340
I'm trying to build a similar contact form page for a client, but I when I create an app, I get apps.facebook.com/APP_NAME rather than the app name at the end. Is there a difference? Are these different types of apps, or is one just an older style name?
Bonus question: Why wouldn't Academy of Art (using the second step from their example above) request User permissions to pull in the Facebook Graph data rather than require users to re-enter it? Is this related to my question above? Is there a best practice around using Permissions vs. New Entry?
apps.facebook.com/[namespace] is the primary url to a Canvas app, while the latter, `www.facebook.com/[pagename]/app_[appid] is your app added to a page as a Page tab app.
For the second question, this app probably doesn't want to ask for permissions (perhaps to lower the friction) since only a few fields would actually be accesible via the graph.
Background:
I am working on a legacy ASP.NET 3.5 Web Forms applications. The application allows users to buy a subscription to a 'white-label' website which is generated for them and they can customize it further. It uses forms authentication.
A typical use-case is that the user creates an account on our system, purchases a website, and then proceeds to customize their website. The URL they will use to edit their purchased website is something like this: https://www.example.com/EditWebsite.aspx. There are many other pages also within our website editing toolbox with other URLs.
Problem:
My team has now been tasked with allowing people to use one account to access multiple website subscriptions. This means that one authenticated user could be trying to access one of many websites to edit if they use the URL mentioned above. Our system can be made aware of multiple subscriptionIds per User but the website editor web app only has support for one subscription.
To clarify with a simpler example: this would be like if Google all of a sudden allowed you to view two different inboxes with one GMail account. How would the system know which one you were trying to access if the URLs were the same for both?
We originally wanted to change the application to use URLs like: https://www.example.com/[subID]/EditWebsite.aspx which would give us all the information we need to send the user to the correct website. We looked into URL Routing to accomplish this but it seems that we would have to change all of the web app's internal links to use the route config to generate the correct URLs. Maybe we have the wrong idea here but it seems like too much work for a legacy application.
Another potential solution we came up with was simply using our systems' control panel web app (where they click links to edit any of their websites) to set a session cookie which our edit website web app can read to know which website to bring up. This has the disadvantage that the pages would not be bookmark-able and you could not look at multiple websites at once in different tabs of the same browser.
Question(s):
Is there any other options we have not investigated or thought of? Is there any other web sites which allow for this kind of behavior; how do they handle it? Is URL Routing the right way to do this and we just need to take the plunge?
Any input is appreciated!
The solution we ended up using was adding a URL parameter to the link which specifies which website you are trying to edit.
https://www.example.com/EditWebsite.aspx?subID=123
This parameter is included in the links to 'Edit Website' from the page which lists all of a user's websites.
When present, this sets a session cookie for the user. If the request parameter is not present, the app looks for the cookie being set; this handles all the internal links within the application. if a cookie doesn't exist and the request parameter was not set, we just pick the authenticated user's first subscription from the list.
This isn't perfect but it has worked without issue so far. The only consequence it has caused is that a user cannot edit multiple websites in the same browser session, e.g. using multiple tabs. This hasn't resulted in any support issues yet though so it is pretty much a non-issue.
I am currently starting to research a project that wants to use Facebook instead of a log in system.
the brief needs to be able to allow users to have their own customisation settings in a user panel, and also be able to connect with facebook friends within the context of the site.
Am I barking up the wrong tree?
Also, how much of the elements we pull from facebook can be styles our way. My designers is starting concepts before I get to that point of development and I don't want to waste their time designing layouts that can not be achieved.
Facebook allows you to pull a wealth of information. The user has to OK the permission for you app to access his/her Facebook profile, but you can get friends lists and their thumbnail pictures too!
Take a look here for a start:
http://developers.facebook.com/docs/authentication/
Its a bit of work, but worth it. You can pull straight data and store it on your server. According to Facebook, you can only keep the data for 24 hours or so (If I remember correctly) so you will need to "refresh" the data every day or so.
I'm not sure why but creating any kind of integration beyond the use of social widgets and buttons on external sites always confuses me.
What I need to do is create a tab on a particular Fan Page. This tab needs to:
Contain an interface for casting a vote in a Poll.
Handle multiple Polls. Only one will be featured in the tab at a time, but there should be an interface for navigating to previous polls.
All polling data needs to be stored on my servers - 3rd party Polling solutions (facebook apps, or embedable services) are not an option unless the data storage location is configurable.
All those requirements are pretty easy to address. Im just confused about how to integrate with FB.
Do i need full FB App for this, or is there another way? This will only be accessible via the Fan Page tab, so I don't necessarily need an App at apps.facebook.com.
If it is an app... is there a way to hide the app page, and the standalone app canvas from everyone except Fan Page admins?
FBML will be discountinue very soon. You might need to find an alternative way to do it. :-)
Check out the Static FBML app that Facebook provides. You can implement it on any Facebook fan page, change the tab title, and specify the content in HTML/FBML (with some limitations, I believe IFRAMES, password inputs, and some other random things are not allowed, but don't take my word on these until you test them). Hopefully this at least gives you a little head start.
Even Tradablebits platform is an option. They give a good functionality and make it simpler to work with Facebook. http://apps.tradablebits.com/ I analyzed this platform for one of my apps.