Google Search Console Insights For GA4 Properties Now Available

In an update rolling out today, Google addresses a limitation of Google Analytics 4 (GA4) properties by making them compatible with Search Console Insights.

Combining data from Search Console and Google Analytics, Search Console Insights provides a thorough overview of how people discover your content across the web.

Since its launch in June 2021, Search Console Insights has only been compatible with Universal Analytics (UA) properties. If all you have are GA4 properties, your Insights section in Search Console would have been pretty bare.

It was a matter of time before GA4 support was added, however, as Google is sunsetting UA properties next year.

Using Search Console Insights

There are different ways to access Search Console Insights. You can get to it via:

  • A link at the top of the Overview page
  • From the navigation menu of Google’s mobile app
  • Search Google for a query that your site ranks for

Search Console Insights is accessible without Google Analytics, though linking the two together will provide you with more significant amounts of data.

Analyzing Data In Search Console Insights

Google designed GSC Insights to offer a snapshot of content performance within recent weeks. It only shows GA data for the last 28 days, which is sometimes compared to the prior 28-day period.

With that being the case, it’s helpful to check GSC Insights regularly as the data is frequently updated.

If you have a GA4 property and don’t see any data in the Insights section after today’s update, here are a few reasons why:

Your GSC property is not associated with a GA property.
You do not have sufficient permissions on GA.
You have the wrong GA view selected in GSC.

For more information, see: Google Search Console Insights: 7 Questions Answered.

Source: Google Search Central on Twitter

Featured Image: Screenshot from, July 2022. 

Credit: Source link

Apple Announces New Lockdown Mode Coming This Fall

Lockdown Mode is an option for people who might be targeted by digital threats. While it’s designed for a small subset of users, anyone can activate the mode.

Here’s some of the security features in Lockdown Mode according to Apple:

Messages: Most message attachment types other than images are blocked. Some features, like link previews, are disabled.
Web browsing: Certain complex web technologies, like just-in-time (JIT) JavaScript compilation, are disabled unless the user excludes a trusted site from Lockdown Mode.
Apple services: Incoming invitations and service requests, including FaceTime calls, are blocked if the user has not previously sent the initiator a call or request.
Wired connections with a computer or accessory are blocked when iPhone is locked.
Configuration profiles cannot be installed, and the device cannot enroll into mobile device management (MDM), while Lockdown Mode is turned on.

Over time, Apple will strengthen the mode and continue to add features.

Credit: Source link

A Complete Guide for HR Managing Hybrid Teams in Marketing Agencies

A significantly high number of businesses were forced to rearrange their operations because of the Covid-19 pandemic and thousands of workers had to step out of the office and adapt to a remote working environment.

Although things are slowly returning to normal, many companies started to implement a hybrid work model in which their employees can opt to work part-time from home and part-time in the office.
Although this could improve the work-life balance, it has still brought the challenge of managing hybrid teams in marketing agencies into focus.

Marketing agencies are often inundated with time-consuming processes, duplication of work, and miscommunication, and these issues can become even more exacerbated as the marketing teams work remotely.

However, hybrid work is here to stay, so below, we provide a mini-guide for HR managing hybrid teams in marketing agencies and how they can ensure the business is moving in the right direction.

Build Trust and Inclusivity

One of the main challenges when managing hybrid marketing teams is building trust among the scattered team members. It is very difficult to create boundaries of respect and impartiality when most people aren’t present in the same space for most of the working week.

A good way to overcome this challenge is for the marketing leader to try to involve every team member in online or in-person meetings, which can significantly help toward building a sense of belonging and safety. It gives the managers a way to recognize the employees’ efforts, whether they are working remotely or in the office.

Monitor Your Employees’ Work

You want to build trust and inclusivity when managing a hybrid marketing team, but to hold remote employees to high work standards and ensure that assignments are completed on time, you must monitor their work. Since monitoring their work isn’t that easy when they are not under the same roof in the office, you might want to consider using a monitoring software for employees that can ensure that mistakes and misunderstandings are avoided, that deadlines are met, and check how everyone on the marketing team is doing separately.

This type of software solution will tell you exactly how each employee is using their time, you’ll be able to track and analyze their efficiency and behavior. By collecting this useful data, you can also establish good strategies on how to create an even more productive and efficient team.

Offer Flexibility

The marketing landscape is continuously undergoing significant transformations and the HR department that manages hybrid teams in marketing agencies must always be prepared for the changing circumstances and undertake measures to facilitate flexibility and independence.

HR reps should always make it their mission to provide flexibility to everyone on the team by allowing them to select a schedule that works both for the agency and the individual team members.
What is even more important is for every member of the team to clearly understand that progress and results are more important than when and where they work.

Build a Sense of Accountability

HR reps can achieve accountability by working closely with staff and providing continuous support and coaching. So, it’s crucial that employees know their exact job descriptions.
As a result, HR representatives should be clear about setting priorities, clearly articulating goals, and focusing on productivity when managing hybrid teams. In this way, the team members will be able to build commitment and focus on accomplishing shared goals no matter what the working schedules look like.


As we mentioned above, marketing is a challenging field, and miscommunication in hybrid marketing teams is one of the biggest concerns. For this reason, HR should strive to establish good communication, transparency, and collaboration rules and guidelines among remote and in-person team members. Feedback is just as important as it collectively boosts efficiency and eliminates obstacles related to the job.

The HR departments should pay close attention to the personal goals of employees and try to show empathy and genuine care for everyone’s wellbeing and satisfaction. Hybrid team members may worry about not being included in spontaneous workplace discussions and activities and this can lead to them feeling unappreciated and less valued. So, making remote and in-person employees feel seen and included is an important skill that HR reps should have.  

Final Thoughts

The HR department managing hybrid teams faces many diverse challenges but most of those can be easily overcome by implementing the above-mentioned tips. Building trust and inclusivity, using employee monitoring solutions, and ensuring good communication and collaboration among in-house and remote workers can be the key to the success of the hybrid working model in the marketing field.

Credit: Source link

Using Insomnia to Upgrade Dependencies — With Confidence

Demo app: “Is Today My Birthday”
Demo app: “Is Today My Birthday”

Always keep your dependencies up to date. When you don’t upgrade, you miss out on bug fixes, security patches, and new features. You may even be up against an “end of life” deadline if the version of a package you use will soon no longer be supported.

If upgrading dependencies is so important, why don’t many developers do it? They may not know-how, or they may not understand the benefits of upgrading, or they may not feel like they have the time. Or, they may be afraid.

Why would developers be afraid to upgrade their dependencies? Because they think they might break something. And why are they afraid of breaking something? Because they don’t have good tests in place.

When you have a good test suite running against your codebase, you can upgrade your dependencies with confidence.

In this article, we’ll discuss semantic versioning, gotchas when upgrading dependencies, and how to upgrade dependencies with confidence. We’ll also use a small app to demonstrate how a good test suite can help you catch breaking changes from dependency upgrades before you deploy your app.

Semantic Versioning

Let’s briefly talk about semantic versioning and how it works. JavaScript packages typically follow semantic versioning, which is a set of three numbers representing the major, minor, and patch versions of the package. So if a package is set at version 2.4.1, then that’s major version 2, minor version 4, and patch version 1.

Patch versions typically include bug fixes and security patches. Minor versions can include new features. But neither patch versions nor minor versions are supposed to break or change the existing API of the package. Major versions can come with breaking changes, usually through removing an API method or significantly reworking the underlying architecture of the code.

Gotchas When Upgrading Dependencies

If package developers follow semantic versioning properly, it’s generally safe for consumers of those packages to upgrade minor and patch versions in their app, since by definition breaking changes are not allowed in those releases. However, some package maintainers may not follow this standard very well or may accidentally release breaking changes without realizing it, so you never know for sure. But generally speaking, upgrades to patch and minor versions of a dependency should go smoothly.

It’s the major version that you need to be more careful with. When upgrading a package from one major version to the next, it’s always a good idea to consult the change log or release notes to see what’s changed.

Sometimes, the breaking changes in a major release don’t impact you, like if you aren’t using an API method that’s now been removed. Other times the changes will be relevant, and you’ll need to follow a migration guide to see what changes you need to make in order to use the new major version correctly. For massive breaking changes, sometimes developers will be kind enough to provide you with a codemod, a script that performs most or all of the changes for you.

The good news is that upgrading dependencies, even major versions, doesn’t need to be a scary experience.

Upgrading Dependencies With Confidence

A test suite with high code coverage will benefit you greatly as you upgrade your dependencies. If your code is well covered by tests, then the tests should give you confidence that your app will still work properly after upgrading. If all the tests pass, you should feel confident that the upgrades went off without a hitch. If any tests fail, you know which areas of your app to focus on.

If you don’t have tests for your app, start writing them now! A good set of tests goes a long way — not just when upgrading dependencies, but also when refactoring existing code, writing new features, and fixing bugs.

Even with a good test suite, a small amount of manual testing after upgrading dependencies is also a good idea, just as an added safety measure. After all, there may be gaps in your test coverage or edge cases you hadn’t considered.

If you do find gaps in your test suite during manual testing, you should write a quick test for what you find and then go fix the issue. That way you now have an automated test to ensure that the particular bug you found doesn’t happen again in the future.

Demo Time

Let’s now consider a small demo app that will help these abstract ideas become more concrete. Here we have a mind-blowingly useful app, Is Today My Birthday. This app is the best, easiest, and fastest way to determine if today is your birthday. Simply input your birth date and today’s date, and the app will tell you if today is in fact your birthday.

Demo app in action: “Is Today My Birthday”
Demo app in action: “Is Today My Birthday”

Okay, I kid. But, we needed a simple app for demo purposes, so here we are.

This app is built with a Node.js and Express backend and a simple HTML, CSS, and vanilla JavaScript frontend. I used the date-fns package for working with dates, and I wrote API tests using Insomnia. I’m able to run the API tests from the command line using the Inso CLI, and I’ve even integrated them into a continuous integration pipeline with GitHub Actions. Pretty fancy, I know. You can view all of the code for this app on GitHub.

The relevant part of the code that determines if today is your birthday is reproduced below:

const format = require('date-fns/format');
const express = require('express');

const router = express.Router();

router.get("", function (req, res) {
  if (!req.query.birthday) {
    return res.json({ data: 'Please provide your birthdate' });

  const todaysDate = new Date( || new Date();
  const birthDate = new Date(req.query.birthday);

  const todaysMonthAndDay = format(todaysDate, 'MM-DD');
  const birthdayMonthAndDay = format(birthDate, 'MM-DD');

  const isTodayMyBirthday = todaysMonthAndDay === birthdayMonthAndDay;

  return res.json({ data: isTodayMyBirthday });

module.exports = router;

The output from the three tests we’ve written looks like this:
All three Insomnia tests are passing
 All three Insomnia tests are passing

So let’s consider for a moment what we might do when upgrading the version of date-fns that our app uses. I’ve purposefully used v1.30.1, to begin with, so that we can upgrade to v2.28.0 later. Going from v1 to v2 is a major release with breaking changes, and we’ll want to be sure that our app still works properly after we do our upgrades. If our app breaks after the upgrades, how will people ever be able to know if today is their birthday?

We’ll begin by changing the version of date-fns in our package.json file from v1.30.1 to v2.28.0. Then, we’ll run yarn install to install that new version.

After that, we can run our tests to see how things look:

Two tests are failing after upgrading the date-fns package
Two tests are failing after upgrading the date-fns package

Oh no — we have some failures! Two of our three tests have failed, and it looks like we have a bad JSON response coming from our API. While it’s no fun to deal with failing tests, our tests have proved useful in detecting an issue when upgrading date-fns from v1 to v2.

If we investigate further, we’ll find the following error from date-fns: “RangeError: Use `dd` instead of `DD` (in `MM-DD`) for formatting days of the month.”

Looking back at our code, we have indeed used MM-DD as our date format. Consulting the change log for the 2.0.0 release of date-fns, we can see that one of the breaking changes is that the use of uppercase DD has been replaced with lowercase dd when formatting months and days together. Thanks for the helpful tip, change log!

We can now make that simple change in our code so it looks like this:

const format = require('date-fns/format');
const express = require('express');

const router = express.Router();

router.get("", function (req, res) {
  if (!req.query.birthday) {
    return res.json({ data: 'Please provide your birthdate' });

  const todaysDate = new Date( || new Date();
  const birthDate = new Date(req.query.birthday);

  const todaysMonthAndDay = format(todaysDate, 'MM-dd');
  const birthdayMonthAndDay = format(birthDate, 'MM-dd');

  const isTodayMyBirthday = todaysMonthAndDay === birthdayMonthAndDay;

  return res.json({ data: isTodayMyBirthday });

module.exports = router;

We’ll then run our test suite again, and voila — all three tests are passing again. The order has been restored, and we’ve successfully upgraded one of the dependencies in our app.


Upgrading dependencies is important. Staying up to date means you have the latest bug fixes, security patches, and features. By frequently updating your dependencies at regular intervals (perhaps once per month or once per quarter), you can avoid the panic of needing to upgrade end-of-life packages at the last minute.

Remember that tests help you upgrade with confidence. So what are you waiting for? Go write some tests and upgrade your app’s dependencies now!

Credit: Source link

Google Clarifies Course Structured Data Requirements

Google updated the Course structured data requirements for appearing in the Course rich results. Failure to follow the guidelines may result in not qualifying for the rich result.

While the added requirement is not new, it was previously missing from the Course structured data requirements page.

Course Structured Data

The Schema structured data for courses is what schools use to appear in the associated rich results, which can appear as a carousel.

The official website defines the Course structured data as:

“A description of an educational course which may be offered as distinct instances at which take place at different times or take place at different locations, or be offered through different media or modes of study.

An educational course is a sequence of one or more educational events and/or creative works which aims to build knowledge, competence or ability of learners.”

As long as schools follow the Google Search Central structured data guidelines and requirements for the Course structured data, students can find courses they’re looking for in the rich results triggered by educational course search queries, and everyone wins.

Unfortunately, the Course structured data guidelines were incomplete because they were missing an essential requirement.

Google Clarifies How to Be Eligible for Rich Results

The change to the Course structured data was to add a requirement missing from the guidelines.

The change is described in a Google changelog:

“Clarified that you must add three courses to be eligible for the Course rich result. This is not a new requirement; it was previously only documented in the Carousel documentation.”

Google added additional sentences to the section of the Course structured data guidelines that is titled Technical Guidelines.

The new wording that was added is:

“You must mark up at least three courses. The courses can be on separate detail pages, or in an all-in-one page.

You must add Carousel markup to either a summary page or an all-in-one page.”

Previous to this clarification, developers and SEOs who followed the Course guidelines would not have known about this requirement unless they had looked at the Carousel structured data requirements.

All schools that failed to mark up three courses and add Carousel markup will not qualify for the Course rich results.

Additional Changes to Structured Data Guidelines

Previous to Google’s clarification of the Course structured data requirements, the word “carousel” appeared only two times.

After the change, the word “carousel” appears six times in the new documentation.

The Carousel structured data requirements were important all along, but the previous documentation did not communicate that importance to the search community.

Check Your Structured Data

If the Course structured data has failed in the past to result in a rich result, it may be helpful to review the current structured data that’s on the pages to ensure that there are at least three courses marked up and that the Carousel markup is also used.


Read the Updated Course Structured Data Guidelines

Use Schema for Course Carousel

View an Archive of the Previous Guidelines Snapshot of Google Course Structured Data Guidelines

Image by Shutterstock/Maxim Gutsal

Credit: Source link

Jump Into the Fragmented World of Incoherence

Credit: Source link

Modern app dev is about more than tools, platforms and languages

Credit: Source link

Flatirons Fuse: Simplifying data imports

Credit: Source link

Transferring workload automation is one of the most difficult parts of cloud migration

Credit: Source link

Google Ads Rolls Out Diagnostic Insights

Google Ads is rolling out a new data set to the Insights page highlighting any issues found during diagnostic checks.

Diagnostic insights will help you identify problems preventing campaigns from showing, causing low engagement, making it hard to measure conversions, and more.

This data can be found on the Insights and Overview page for Performance Max campaigns, allowing you to troubleshoot issues as soon as they’re detected.

Google Ads will provide a detailed breakdown of the following insights:

  • Account status
  • Billing status
  • Policy review
  • Conversion tracking
  • Campaign budget
  • Bid strategy target
  • Campaign status
  • Ad strength

Tailored recommendations will take the guesswork out of fixing the issues Google finds, so you can get your campaign back to performing optimally in no time.

Diagnostic insights in Google Ads were previewed in May with an announcement they’d be rolling out soon. Two months later, the launch is now underway.

Google Ads Diagnostic Insights

Diagnostic insights only show when a campaign has not received traffic or conversions.

If your campaign is running and people are seeing the ads and clicking on them, then there will be no diagnostic issues to report.

Keep in mind Google hasn’t given everyone access to the Insights page yet, as it’s currently in beta.

Google is gradually rolling out each insight type to randomly chosen people, which means you may have the Insights page with limited data.

Currently, diagnostic insights are available for Performance Max campaigns. The new dataset will expand to other campaign types over the next few months.

Source: Google Ads Help

Featured Image: PixieMe/Shutterstock

Credit: Source link