By Google adsense/adwords, after pasting some code scripts in one website, then google will push the ads. to the website automatically.
How google do this? What is the core technology of pushing ads. to the website?
The core tech is HTTP!
When a user visits your site, the user's browser loads your page. As it loads your page the browser also loads the Google ad script. When this ad script loads it makes a HTTP request off to Google servers. When they Google gets the request they provide a suitable ad back to the user. Google have a bunch of technology internally that decides which ad to show to your user, but that doesn't affect how the ad gets to your site.
This all happens in a very short time - fractions of a second - so it looks seamless to our eyes.
Related
I'm trying to make a chatbot with Dialogflow for Google Home. It requires the user to input a URL. Now it will definitely be a long and complicated URL which I can't recreate and I can't have the user speak into the google home.
The idea I had was that the user would input the URL on an agent on messenger. I store this on a Firebase database and then access it with a second agent.
Now the issue I have is authentication, I was hoping to use account linking on my google action with facebook. But I can't login to Facebook with google home. Or if I can, I can't find any documentation specific to that case. Facebook doesn't provide the necessary client ID and secret(as far as I can see).
I managed amazon and Gmail account linking with Alexa and an Amazon Echo. In those cases, you would have to login to google or amazon on the Alexa app or webpage. Then this will be integrated with your Echo and the skill will become usable.
Anyone have an idea of how I can make the link happen, if not then anyone have an idea as to how I can solve the overall problem?
This question has been left unanswered on other forums, but I was hoping to either get it solved or find an alternative.
There are three approaches to solving your overall problem - getting the URL manually entered and available to your Action. Two of them tackle it the way you've suggested - involving authenticating to Facebook and tying that to the Assistant account somehow. One solves it entirely inside the Assistant.
Account linking to the Facebook account
You've tagged firebase-authentication, so I'm going to assume that you're using it to do the auth and you've enabled Facebook login through it. This means your user has a "Firebase Account", but they log into that account using Facebook.
I will assume you have a way to get the URL from messenger once they're logged in.
The trick in this case is to setup Account Linking between their Firebase account and their Assistant account. This is done by setting up an OAuth2 server that has access to the Firebase accounts and will create authorization and refresh tokens that are given to the Assistant.
In the Action, you'll send the user to the Sign In helper, which will redirect them to your login page and send back a one-time auth code to the Assistant. The assistant will then use your OAuth2 server to exchange this code for auth and refresh tokens. Periodically it will use the refresh token to get new auth tokens.
When the user returns to the conversation through the Assistant, you'll be handed an auth token and you can use this to lookup the user. Since you also know their Facebook account, you can get the URL via however you planned to do so.
There are drawbacks to this method - it is very complicated, and setting up your own OAuth2 server is not for the faint of heart. You may be able to use something like Auth0 instead of Firebase Authentication to accomplish the same thing, but then you don't have the ease of access to the Firebase database.
Account linking to both Facebook and Google
In your Firebase account, however, you don't need to limit them to just logging into Facebook. You can have them use Firebase to record both the Facebook and Google accounts that they're using. This would "link" the two accounts together in your system.
With this, you don't need to setup an OAuth2 server. Instead, you can have the Assistant use Google Sign In for authentication. If the Google Cloud Project that Firebase is using and the Assistant are using are the same project, then once the user has logged in to your project's web page with their Google account, you'll get an identity token on the Assistant which will contain their Google ID. You can use this to match up with their Firebase account and get the Facebook ID and proceed from there.
But this is still a lot of work and kinda messy, jumping between systems.
Using just the Google Assistant (and maybe a web page)
If you're willing to make some assumptions about the devices your users are using, then you may be able to do it all just using the Assistant. The Assistant doesn't just run on the Google Home and other smart speakers, it also works on most current Android and iOS devices.
So you can detect if they have such a device available and, if they do and they're not currently on it, direct them to switch to that device when you need the URL.
If they don't have such a device available (perhaps because their version of Android is older), and you think this may be a common scenario, you may need to make another entry source available. This could be one of the solutions above, or you may want to just have a simple web page (done via Firebase Hosting and Firebase Functions, perhaps) where they log in using their Google account (so you get their ID) and you let them enter the URL. If you just need a URL - going through Dialogflow may be more complexity than you need.
Just to verify, noone can view anything on Linkedin without having an account on Linkedin?
I was planning on hosting all my professional articles on Linkedin but if I can't fetch them via the REST api to display them on my own website, I find that a non-starter.
Thanks in advance for clarification.
In general, I think you've just got things a bit backward. People don't usually make a website in order to drive traffic to their LinkedIn. If you've got a website, why are you not hosting your articles/blog on your site, and then posting those articles on LinkedIn?
However, in general, if you wanted your website to grab your LinkedIn info, it would have nothing to do with your viewer. You would essentially be logging your app/site behind the scenes (essentially as you), grabbing whatever fields are available that you want to display, and then popping them on the screen as static content.
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.
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.
My company uses Google Apps, and we've built a single sign-on application to do our custom authentication.
It's been working just fine for several months.
I've noticed that with certain Google features (like switching accounts), the user is often supposed to get redirected back to a certain web page.
If the user isn't logged into any of our Google Apps accounts, then this works fine. However, if they're logged into one of our Google Apps accounts, then it ends up dead-ending at our sign-out page, because I don't know where I'm supposed to send the user at that point.
We actually don't even use the sign-out page for anything at all, it's only there because it's a required field when setting up SSO for Google Apps.
So my question: Where am I supposed to send the user after they've come to my custom sign-out page?
Where do you send them? Wherever you want them to be after sign out! :)
There are typically two places you get redirected to after sign out: the company's main page, or the sign in page.
For example, if I built a SSO for the Stanford Med School, after sign out, I'd probably redirect to med.stanford.edu or med.stanford.edu/signin (hypothetical).
In your case, I'd either redirect to your company's main page, or redirect back to your custom sign in page.