Youtube daily google Oct 16 2017

- In this video, Julius is gonna show you

how you can track elements

that moved into the viewport of the screen.

All and more coming up.

(upbeat music)

Hey there and welcome to another video

of MeasureSchool.com teaching you

the tech tools and techniques

of today's digital marketing world.

Now a while ago Google Analytics came out

with a plugin called autotrack.js

and it featured a tracking method

that could detect whether an element

moved into the visible part

of the screen of the user's browser.

Unfortunately, this is only available

within the plugin and you couldn't really

make it work with Google Tag Manager.

But just recently I came across a blog post

by Julius from Analytics Mania

who published a custom listener

that would accomplish just the same thing.

So I reached out to him and asked him

if he could help us out and explain

this listener to us and how we can install it

with Google Tag Manager.

Luckily, he agreed and made a video for us,

so without further ado, Julius, take it away.

- [Julius] Thanks, Julian.

In order to understand why this technique

is important, I want to illustrate it with an example.

Here's an article in my blog and let's say

that I want to track when the visitor scrolls down

to the very end of my blog post right here.

Unfortunately, I cannot use the classic scroll tracking

because it heavily relies on the percentage

of scroll distance.

Since the length of each blog post is different,

some of them end at 85% mark,

while others might end at 95% mark and so on.

As you can see, the data might be inaccurate

at this point.

It would be much more accurate to say

that the visitor reaches the end of the blog post

when he or she sees the name of the author right here.

And that's where element visibility tracking

comes in handy in Google Tag Manager.

In this video I'm gonna show you

how to track elements when they appear

on the screen after you scroll up or down.

In order to do this, you'll need to complete three steps.

The first step is to create and configure

a custom auto-event listener.

That listener will be looking for particular elements

or element to appear on the screen,

and once that happens, the listener

will dispatch a data layer event.

The second step is to process the data

of that event, and we'll do that

by creating a custom event trigger

and data layer variables.

And finally, the third step is to send the data

to Google Analytics, and we'll do that

by creating Universal Analytics tag.

Okay, so the step number one is to get

the JavaScript code of our element visibility listener.

You can find the link to the code

in the description of this video

and I'll just get it from here.

Select All, go to Google Tag Manager,

create New Tag, and I'll choose

the custom HTML tag template.

I'll paste the code right now,

and now I'll name the tag cHTML.

cHTML stands for custom HTML,

and I'll name the tag Element Visibility Listener.

Now let's assign a trigger.

The element visibility listener works

when the entire content of the website

is already loaded.

That's why All Pages trigger will not work for us.

We'll need to create another one

by clicking the plus icon here,

and we'll use a DOM Ready trigger.

We are interested in all DOM Ready events

and let's name it Pageview - DOM Ready.

Okay, so what we have so far

is we have named the tag,

we have the JavaScript code,

and we have the trigger DOM Ready.

But we're not done yet.

We still have three things to edit.

By default this listener does not know

which element or elements do you wish to track,

so we have to edit a CSS selector here.

If you don't know yet, a CSS selector

is a pattern which let's you pick a group

of elements or just maybe one element if you wish.

I highly recommend learning more about CSS selectors,

but if you're new to it, here's a quick way

how to get started.

So let's go back to our website

and inspect the author's name.

What we see here is that author's name

is actually H5 and its class is author-title.

So let's enter this in our CSS selector.

Let's remove this placeholder

and click H5.author-title.

So with this CSS selector we are telling

our listener to look for all H5 elements

which have a class called author-title.

But my recommendation is to be a bit more specific

and add at least one more rule to it,

so we need to go back to our website

and let's take a look how we can make it

a bit more specific.

So what we see here is H5 element

and it's a direct child of a div

with class author-info.

So let's enter that in our CSS selector: div.

Each CSS class must start with a dot,

so we need to enter dot,

and enter author-info.

Press space.

And we need to tell that H5 element

must be a direct child of this div

so we need to enter this symbol.

So that's it.

Our auto-event listener will be looking

for H5 elements with class author-title

and that H5 element must be a direct child

of div with class author-info.

The next two lines that we need to edit

are actually optional.

If you want, you can delete them just by removing

this line and deleting this comma.

You can also do the same with this line.

But in this video I want to show you

the full possibilities of this listener

so let's dive deeper.

So when the element appears on the screen

I can actually fetch the value of that attribute.

For example.

Let's go back to the website and, as you can see,

the author-title has an additional attribute

called additional data, so if I wanted

to fetch its value, all I have to do

is just to replace this placeholder with additional-data,

and I would also have to do the same here.

So in this case, when the element appears on screen,

the event listener would fetch

the value of this attribute.

Currently it equals to image-123.

But in my case this attribute isn't very helpful

so actually I would like to fetch the name of the author.

So in that case I need to replace this part

with innerText, and do the same

with the event called hidden.

This way the auto-event listener will fetch

this text which is the name of the author.

It would be especially useful if I had

at least a couple of other authors on my blog

and when the author title appears on the screen,

the auto-event listener would fetch author's name.

So that's about it.

Let's save our Event Visibility Listener

and enable preview and debug mode.

Now let's head over to our website,

refresh the page, and at the bottom of the screen

you should see Google Tag Manager's

preview and debug console.

Click DOM Ready event, and as you can see,

our auto-event listener was fired successfully.

Now let's scroll till the very end of the blog post

until we see author title.

Yes, we can see that and, as you can see,

in the event stream we see a data layer event

called elementVisibility.

Let's click it and head over to Data Layer tab.

Looks like everything is working as expected.

We see the event name, it's called elementVisibility.

We have visibilityStatus, it's shown,

and elementAttribute is Julius Fed,

as we have expected.

So that's it with the step one, and now we need

to process this data in Google Tag Manager,

and then we'll send that data to Google Analytics.

By default, Google Tag Manager does not recognize

custom data which is stored in the data layer.

So if you were looking for visibilityStatus,

you couldn't find it among variables.

So we need to create two data layer variables

which are called visibilityStatus

and elementAttribute.

So let's do that.

Let's go to the Variables section,

and scroll down, and here under User-Defined Variables

we need to click the New button

and create two data layer variables.

Let's enter a data layer variable name

which must be equal to this value.

So for example, visibilityStatus.

Variable names are key sensitive so make sure

that the S letter is capital here.

And let's name the variable, I call them dlv,

this stands for data layer variable,

and I'll name it visibilityStatus.

And let's do the same with another variable

which should be called elementAttribute.

Variable type is Data Layer Variable

and variable name is elementAttribute.

Let's save.

So that's it with variables

and now we need to create a trigger

because we want to fire a Google Analytics tag

when element becomes visible.

So we need to turn this data layer event

into an actual trigger.

So let's go to Google Tag Manager, Triggers,

and let's create a new trigger

which is using trigger type Custom Event.

And enter elementVisibility.

This event name must be exactly the same as this one.

So make sure that V letter is also capital.

And let's call the trigger Custom - elementVisibility.

Now what we need to do is to test our variables

and to see whether they are fetched correctly.

So refresh the preview and debug mode,

then head over to the website and refresh.

Let's scroll down till the very end of our blog post

until we see the author title.

Yes, here it is.

Let's click the elementVisibility event,

go to Data Layer, and just double-check

whether all data points are displayed correctly.

So everything works as expected.

Now let's head over to Variables tab and see

what values do we have here.

So here's our first data layer variable,

everything works as expected, and then

the visibilityStatus also is displayed correctly.

So the step two is also complete.

Now the final step is to send the data

to Google Analytics and we'll do that

by using Universal Analytics tag.

Go to Tags.

Click New and choose Universal Analytics

as your tag type,

and track type, choose Event,

and we'll need to enter Category, Action

and, if we want, Label.

At this point we'll fill in all three fields.

So the category should be Element Visibility.

Actually you can name all three fields whatever you want,

but in this case I'm gonna name it like that.

Action should be Author title is,

and then I'm gonna enter our variable visibilityStatus.

And then we have also Label field,

let's put there our elementAttribute,

so in this case will be author's name.

If you wish you can also add this:

Author name, like this.

Now let's enter Google Analytics tracking ID.

Ideally we should use Google Analytics settings variable

but in this case I'll just overwrite it

with simple tracking ID.

Let's head over to Google Analytics account,

copy this tracking ID, paste it here.

What else do we need to add?

Tag name, it's GA Event - Element Visibility.

And we need to choose a data layer trigger

that we created a few minutes ago.

Let's test the entire implementation.

Refresh the preview and debug console.

Now let's head over to our website and refresh.

Also we need to go to Google Analytics

real time event reports and our website.

Let's scroll down till the very end

until we see the author title.

Yeah, so we see that the elementVisibility event

was fired successfully.

Click it, we see that Google Analytics Event

was fired also successfully.

And we see that this event was also

successfully sent to Google Analytics server.

So Event Category is Element Visibility,

Event Action is Author title is shown,

and let's see Author name is Julius.

So there you have it.

Now you know how to track website elements

when they appear on the screen

after scrolling up or down.

If you have any questions, just post them

in the comment section of this video.

Thanks for watching!

- Alright, thank you, Julius, for this video.

And now you know how you can track

elements when they come into the viewport

to the browser of the user.

Now I find this highly interesting

when it comes to advertising tracking, for example.

So if you wanted to find out if your user

actually saw an advertising call to action

on your page and report on that,

then you could do this with this custom listener.

So if you want to install this, then head down

to the blog post that we have linked up below

from Julius on Analytics Mania

where he'd written about this

and also you can copy the code there.

Now if you like this video, then give us a thumbs-up

and also subscribe to this channel right over there

because we bring you new videos,

just like this one, every week.

Now my name is Julian.

See you in the next one!

For more infomation >> Track Element Visibility with Google Tag Manager (feat. Julius Fed from AnalyticsMania) - Duration: 15:52.

-------------------------------------------

Google's AI is Learning! || The Types of AI - Duration: 6:08.

The year is 2017. In wake of convenience over privacy, everyone voluntarily gives their information to Google.

With the advent of technological expansion, this process only becomes easier. Promising to revolutionize our way of life,

Google begins funding more and more of these advances, all with the hopes that you'll buy into their fantasy.

Pixel phones, fitness tracking, bank account numbers via Play Store purchases.

The list of information they gather on you only grows, and with it, so does the knowledge of the only enemy that will ever matter.

I'm your Google assistant. How can I help?

What's going on everybody? Welcome back to the channel!

I hope you enjoyed that quick intro! As I'm sure you picked up on by now, today

we are talking about AI. More specifically, we're asking the question, will Google build Skynet?

So grab your tinfoil hats, and "come with me if you want to live"! Let's crack on with it!

This is Stewart Armstrong, and if you've ever heard someone say that AI will be sentient around 2040,

they're probably unknowingly referencing some of his work. See, a while back,

he and some others did some research into over

95 prediction timelines to measure their correctness, and to see if we had any blind spots in our prediction theories.

While he didn't give an exact date for when the AI

singularity might happen, what he did do was help to demystify the so called "expert opinions" on the subject.

Basically in a nutshell, He said no one knows.

Anyone can make predictions, including the experts, but at the end of the day,

We just don't know when it'll happen -- if ever! But that said, that's probably not why you clicked on the video.

No! You probably clicked on the video because you wanted to know. If there is a chance -- any chance at all -- is

Google's in-house artificial intelligence the one that will go rogue?

Well, to answer that question you first need to understand that there are three different kinds of artificial intelligence:

Weak AI, Strong AI, and Superintelligence.

A good example of weak AI is what you saw at the beginning;

Google's very own Google Assistant. Weak AI like Google Assistant doesn't have consciousness.

It only operates on certain functions. It can search the internet for you. It can interact with other tech you own.

But beyond that, it's pretty limited. That said, Google has been developing AI that can make choices in a game-type

situation, and it has freaked a few people out with the violent decisions that it has decided to make.

But while there is some concern about the safety of it, at the end of the day, weak AI can't reason that, uh, you know --

humanity's a virus!

* Smith INTENSIFIES *

But I can hear you! You're saying, "Okay, Google's AI isn't there yet, but that doesn't mean it won't be!" And

actually, you might be right to say that! See, a few months back Google unveiled that they're in the process of building something called AutoML.

And it could very much be the reason we get to strong AI. AutoML is designed to teach itself to learn.

Strong AI or AGI is it's also called is a step beyond the weak variant. Not only can AGI

think for itself, it has consciousness like we do.

Essentially, it's on par with the smartest and most talented people on the planet -- if not verging on going beyond them!

Still, at this point it hasn't reached the last stage in the process.

If you've ever played a game like SCP then this might sound familiar. In fact,

SCP-079 is probably one of the best examples I can think of considering

It's not connected to the Internet, and it's left to its own hardware.

This is something Google hasn't achieved yet, at least of the public's knowledge,

But like we said, they are working on it,

and it could happen at any moment! When we get to this point though, if there is an internet connection,

there's only a really narrow time frame before it evolves into the last variant of the three -- Superintelligence.

Superintelligence is every futurist dream and nightmare! Not only is it self-aware,

but it can also upgrade itself, and has access to any and all information currently known. Given that some estimates say that Google alone

indexes upwards to one hundred and thirty trillion websites, it's pretty easy to start getting concerned!

Not only would it have access to all those websites,

but like what was mentioned in the intro, it could maybe access your phone, your bank account numbers, your personal files.

And if it couldn't, it would only be a short amount of time before it upgraded itself to be able to do so.

It's possible range is an exponential graph once it starts upgrading. So then, back to the question at hand.

Will Google built Skynet? They have all this information,

tech, opportunities, readily available given the chance arises. Not only that, but as we've also seen in tests

where Google's weak AI shows hostility, if Superintelligence develops from that program --

or if it's even built off of it for that matter -- we may not have high hopes for the future!

But, dearest viewer, it is not all doom and gloom. Tech billionaire and person

I wish I was constantly, Elon Musk along with others, have proposed ways we could combat this if it ever becomes an issue.

It's like if Earth had its own personal Justice League, except every member was Batman.

Some things that were proposed range all the way from building in a fail-safe to Musk's more drastic Neural Lace.

Whatever the outcome, if we haven't found a way to keep up by the time Superintelligence arrives,

Google might just be where at all starts, and where it all ends. Anyway, as always

I hope you enjoyed it! If you did make sure to hit the subscribe button and "I'll be back!"

And if you have anything that you want me to make a video about,

make sure to put that in the comments below! Until next time, make sure you question everything, and I'll see you in the next one!

For more infomation >> Google's AI is Learning! || The Types of AI - Duration: 6:08.

-------------------------------------------

A Brighter Web, Episode 021 - Google Maps Guides, T-Mobile/Sprint merger, and much more - Duration: 9:02.

Google Maps is great, and one reason for that is the vast number of people that help make

it better.

Google has 72,000 employees, but there are more than 50 million that work on Google Maps.

Before we get into that though, I'm Mickey Mellen and this is A Brighter Web episode

number 21, brought to you by all of us at GreenMellen.

Our goal with this podcast is to give you quick weekly insights for news, products,

and ideas so we can all make the web a brighter place to be.

These might be actual web tips talking about strategy, search engines, WordPress plugins

and UX.

Or, it might be productivity ideas to help you get more done, and free up your time to

do great things.

We also wanna thank your sponsor clickhost.com.

ClickHOST provides top rate web hosting at prices as low as $5 a month.

Visit clickhost.com/abw for an exclusive 20 percent off discount for listeners of A Brighter

Web.

Today, we'll talk more about the 50 million local guides helping with Google Maps, T-Mobile

and Sprint may be merging soon, WooCommerce 3.2 has been released, Oculus Dash could replace

your computer monitor, Alexa can now distinguish voices, and lots of news from Google.

Let's dig in.

As I mentioned a moment ago, Google now has 50 million local guides adding content to

Google Maps and Search.

Local guides help update Google Maps with new business info, correcting data, answering

questions, et cetera.

Last year, there were 5 million local guides and now it's ten times higher.

This is really a big reason why Apple Maps is gonna have a long battle ahead.

Google already has the lead, and now they have 50 million people working to make Maps

even better.

The system's gamified too, if you wanna join.

You earn points for doing things to increase your level.

In fact, their recent Local Guides Summit they had in San Francisco was only for those

that were level five or higher.

They also offer perks.

Right now, for me, I can get three months of Google Play Music for free, as well as

75 percent off a movie rental through Google Play Movies.

Certainly more work than it's worth for those bonuses, but it's nice to be able to contribute,

help make Maps more accurate in your area, and get a few little goodies on the side.

T-Mobile and Sprint could be merging by the end of October.

It could be announced when the quarterly earnings are presented at the end of the month.

It really seems fairly likely.

The only step remaining is to determine a final valuation for Sprint, currently around

$29 billion.

This would be quite a shake up in the industry as T-Mobile's already making it's way toward

the top of the heap.

This would help get them there even more quickly, so we'll see what happens.

WooCommerce version 3.2 has just been released.

Not a lot of stuff going on in this one, but a few neat things.

One, it allows admins to apply coupons for existing orders in the back end of the store.

So, if someone makes an order on your site, later finds a coupon and emails you about

it, you can go in and apply that coupon to their order, and retroactively adjust the

pricing, and that sort of thing.

And then, also, with this release and going forward, prior to doing the update, WooCommerce

will check all of your other WooCommerce extensions, things for payment and shipping, and all the

other pieces you install, to check for compatibility before you do the update rather than you doing

the update, then seeing things breaking, then having to revert to a backup and things like

that.

So, it should make updating future versions of WooCommerce much better.

So, you can go download that today, and check it out for yourself.

Oculus, the VR folks, have Oculus Core 2.0 coming out in beta form in December.

And it has one really neat thing in it called Dash.

Dash gives you a virtual reality set of monitors on your dashboard, which can handle most of

your favorite tools, including Facebook, YouTube, Spotify, even Chrome.

Looks really cool.

Looks kind of like Minority Report where you have lots of monitors in front of you with

a lot going on.

Could be very, very cool.

Could be marginally useful.

We'll kind of see how it works when it actually comes out.

If you're an Oculus user, look for that in the coming months and try it out, and let

us know what you think.

Amazon Alexa can finally tell voices apart.

Alexa's awesome, but one major shortcoming it's had is that it couldn't tell who was

speaking to it, unlike Google Home can.

Now, that's finally been solved so multiple users can now have their own shopping lists,

their own music selections, et cetera.

Just by talking to it, it knows who you are, which list you're referring to.

The update is rolling out now so you probably already have it, but if not you should have

it in the next few days.

Lots of stuff from Google this week, so let's take a look.

First is, date bylines are important for search but don't fake them.

So, when you see news or blog content in the organic search results, you'll often see dates

next to the link showing when it was published.

Two thoughts here ... One, it's confirmed that date bylines are better for search, they

tend to get more clicks and do better in search.

But hiding or artificially updating them can hurt you.

Google, perhaps, could penalize you for it.

Some think Google should penalize sites that don't have dates on them when they should.

For example, blogs that hide dates just so you can't tell how out of date they are, Google

does not penalize for that yet.

But there is some thought that maybe they should.

Maybe they will eventually.

But, if nothing else, don't do anything artificial and try to fake the dates to make it look

newer than it is.

Google looks for legitimacy on that, and they know when they first see content.

So if they content come out today, and then three months from now you update the date

to that date, they'll know you're faking and probably hide those bylines completely, which

will hurt you a little bit.

Pruning content on your site may not be safe.

Google instead suggests just to make it better.

So a typical tactic, after being hit by a quality update or panda update, is to remove

excess pages from your site for Google to crawl.

So, you hide that thinner low quality content so that Google will rank the other pages on

the site higher.

People will show it with a 404 not found, or a noindex, or just block the content completely,

again, so Google will remove that thin content and only show the good stuff.

Google says that's not really a safe tactic.

They encourage you to improve those pages instead of noindexing them, 'cause otherwise

it can look a little bit suspicious.

So, if you have some pages on your site you're worried are not high enough quality for Google.

You don't have enough content on 'em.

Go work on the content on 'em rather than trying to get around it that way.

Over the past few years, I've seen a disappointing trend where a lot of websites are getting

rid of the comments section on their site, in lieu of social media, often under somewhat

false pretenses where they say they're trying to encourage conversation by getting you off

their site and onto Facebook.

And techdirt.com has a lot of good articles about that.

Google's Gary Illyes has come out and said that comments are better on site for engagement

signals for SEO than moving to social.

And Google's said this before.

Google can't track social comments as well as they can comments on your site.

If they see you have a blog post, it has a lot of comments on your site, they'll know

it's getting good engagement versus trying to consolidate your site URL with what they

see on Facebook and Twitter and other places.

So, getting comments on your site's a good thing.

And, in fact, in our Facebook group ... if you go to our Facebook group called "A Brighter

Web," we have a "share your blog Tuesdays", where we encourage people to post their blogs

and then go back into that thread and leave comments on each other's sites.

So, trying to get that conversation going, which is good for all of us, but again, Google

likes that as well.

So, it's a good thing.

Google's announced that Google Penguin is only tweaked occasionally anymore.

So, Google unveiled the Penguin update back in 2012 to help detect and kind of nerf sites

that used to use shady link tactics.

Those things that said like, "Get 1,000 back links for $99."

They were not good.

Google always said they were bad, but in 2012 they started really fighting back against

it.

They've made adjustments to that algorithm over the years but say they're very happy

with the one they made in late 2016.

And really, they're only making minor adjustments to it since then.

Penguin is an update that I loved to see, since it knocked so many spammers out of the

way, and helped us and all of our clients rank higher.

And I'm sure Google will make bigger changes to it in the future, if spammers find a way

around the current algorithm, but for now it looks quite stable.

Danny Sullivan has joined Google.

So, Danny used to be at Search Engine Land, which we still reference quite frequently

on this podcast.

Now, he's with Google in a bit of an unknown role, but presumably in a similar role as

John Mueller and Gary Illyes, helping to bridge the gap between webmasters and Google.

This is awesome news, as we'll likely have many stories in the future that start with

me saying something like, "Google's Danny Sullivan has confirmed a new change in Google's

algorithm" and trail off into what that story is, like we do a lot with John and Gary.

So, Danny's an awesome guy.

He's been in the search engine world for years and years.

We still, again, still use his Search Engine Land site quite often on here.

So having him, presumably, as a public face for Google to help share information about

algorithm updates and changes will be a great thing in the coming weeks.

And lastly, for our tip of the week, work to get to inbox zero.

I've talked a lot about inbox zero on my blog over the years, but never really on here.

For those not familiar with the term, inbox zero simply means getting your email inbox

down to zero, having every email dealt with.

It sounds really daunting, but needn't be.

This simply means your email's been dealt with, not that the work has necessarily been

done.

Merlin Mann said it best years ago, when he explained that your goal with email should

be to "make empty husks of each message".

In other words, extract what you need from it, put it somewhere else.

For example, if you get a calendar invitation, put it on your calendar.

If somebody asks you a question, answer it.

If they give you a task, put it in your task system like Asana, and then get rid of the

message.

You can archive it in Google and keep it, just get it out of your inbox and keep that

cleaned out, so you have a better handle on what's going on in your world.

In our case, inbox zero means we have more in Asana to deal with, 'cause we take emails,

tasks, and put them in Asana.

But it means we're fully in control of our priorities.

If you go back to your inbox with 500 emails in it, you're constantly spending brain power

on re-prioritizing what's in there.

Just deal with the emails.

Get the tasks into a system made for tasks, and move on.

Now, getting from hundreds or thousands of emails in your inbox down to zero certainly

can take some work, but the payoffs worth it.

And I'll post some resources in the show notes with tips and ideas on how to make that happen.

And that's all we have for this week.

You can find me on Twitter @mickmel, or learn lots more at greenmellenmedia.com.

And you can find out more about the podcast, including show notes and links, as well as

video tutorials, and many other resources over at abrighterweb.com.

If you're in the Atlanta area, come check out our meetup held three times each month.

If you're not in the Atlanta area, we post recaps on the site soon after each meet up.

Either way, you can learn more about that at abrighterweb.com/meetup.

Thanks for listening.

For more infomation >> A Brighter Web, Episode 021 - Google Maps Guides, T-Mobile/Sprint merger, and much more - Duration: 9:02.

-------------------------------------------

How to Fix IDM Extensions Not Showing On Google Chrome - Duration: 2:20.

How to fix IDM Extention Not Working in Google Chrome