GA4 Properties are still not linkable.
Having said that, the method for linking GA to GSC has changed and it's now referred to as an Association.
For GA, it must be done from within the GSC interface, not from within GA.
As of Feb 2021 you can now link GSC domain properties to GA (it's now recommended).
To get to the GSC Associations page:
It's not possible as of now, and it's one of the SEO community's largest complaints about the new (cough cough...beta) GA4 experience so far.
It's perfectly fine to use both, and I encourage it. I've had clients ask about moving to GA4 and for now I'm not moving anyone completely away from the universal (stable) analytics.
Here's how to use both GA and GA4 ...
As of now, Google recommends creating both UA and GA4 properties together. So this linking is not possible at the moment
Go to Conversions in Google Ads, you'll see a list of existing conversions (if you have any) and a button to add new ones (either saying, "+New Conversion Action" or just a + symbol, depending on if you're viewing the Summary page or the All Conversions page).
Clicking that button gives me four choices of type of conversion, the fourth of which is &...
I don't know how / if you can do it in GA4 as I do not use it. However in Universal GA you can accomplish this by leveraging query parameters and a user-scoped custom dimension.
Here's a guide: Simple Way to Exclude Internal Visits From Google Analytics
With Google Tag Manager, you can take this query parameter and send it as a User-scoped Custom Dimension ...
Well, if you're using GTM, then why do you use gtag directly? You're not supposed to touch gtag ever. You can, but it's confusing. It's easier to have one point of interaction with gtag and that point is GTM. It will make it much easier to debug issues in the future.
Instead, you can pass all the needed information to your window.dataLayer, using a .push() ...
Sounds like you possibly created a new property as opposed to upgrading an existing UA property. Upgrading doesnt create a new UA property, just a GA4 property to work in tandem with the existing UA property.
Few things going on here. Regarding real time reporting, the two property types work differently to each other. Real time reporting for GA4 batches ...
In this Google documentation page about adding the gtag.js tag, under the "if the setup wizard did not use your existing tagging" section, under the "add your tag directly to your web pages" accordion, Google says:
Don't remove the old analytics.js tag; it will continue to collect data for your Universal Analytics property. The gtag.js ...
There is no way to migrate historical data from Universal Analytics (UA) to Google Analytics 4 (GA4). When you migrate, you can avoid data loss by dual-tagging. That is include both GA4 tags and UA tags in your site going forward.
That way your data will continue to be logged in UA and you can compare historical data against fresh data. You will be ...
Not sure if this will work as I don't have a setup to test it on atm.
In the Web Data Stream Settings, try adding the cd parameter name in the GA4 Site Search settings in the Additional Query Parameters field
page_location is automatically sent on all events. I don't see page_path being sent at all but it is available in some reports including the analysis hub. I tested a few events and saw it was set. Maybe it is calculated.
Not sure what happens if you try to manually set it in the gtag.