⚠️ Cuidado en GA4 con las métricas que hagan uso de las transacciones.
Para GA4 una devolución (refund) también es una transacción y dependiendo del negocio os podría causar ruído en los datos y en los análisis si no se tiene en cuenta.
🛑🤚Hey, #devs ¡GUARDEN ESTO!
Aquí está la guía para Desarrolladores de Google con todo el material para mejorar sus habilidades técnicas, complementar sus cursos y prepararse para entrevistas.
📚Clic aquí: https://t.co/0ZVzPXYF8x
𝐏𝐨𝐰𝐞𝐫𝐬𝐡𝐞𝐥𝐥 𝐂𝐡𝐞𝐚𝐭 𝐒𝐡𝐞𝐞𝐭
Powershell no solo es una shell muy potente, también es un lenguaje de scripting.
Todos los que nos dedicamos a alguna disciplina técnica hemos tenido que utilizar powershell en algún momento y muchas veces es difícil acordarse de todas las funcionalidades que tiene.
Por aquí os dejo un resumen de su funcionamiento básico que me gusta tener siempre a mano.
Here is how you can fix unassigned traffic issues while using #GA4 GTM server-side tagging...
It is common for the unassigned traffic to considerably increase when setting up GTM server-side tagging.
The two most common reasons for this behaviour are:
1) The 'page_view' event fires before the 'session_start' event.
2) Cookies and Client Identification Settings in GA4 Client in Server GTM was set to "Server Managed".
.
.
Solutions:
1) Change the GA4 Configuration Tag in the Client-side GTM container to fire on All initialization events instead of All Pages. This way, the 'session_start' event fires before the 'page_view' event.
2) Change the Cookies and Client Identification Settings in GA4 Client in Server GTM to JavaScript-managed
This should resolve the unassigned traffic issues related to server-side tagging.
.
.
Following are some other methods to fix the unassigned traffic in GA4 (not necessarily related to server-side tagging):
1) Use UTM parameters to tag URLs
2) Always supply source, medium and campaign information when tagging URLs with UTM parameters.
3) Create UTM parameters that strictly follow GA4 default channel rules wherever possible.
4) Use auto-tagging to tag URLs.
5) Use system-defined traffic sources and system-defined traffic mediums wherever possible.
6) Memorize channel rules and definitions for accurate tagging.
7) Make sure that the source and medium information are not dropped because of technical issues.
8) Always send measurement protocol requests with all the required parameters.
9) Use the standard implementation of GA4 to avoid unassigned traffic.
10) Minimize the use of Audience triggers.
How to remove not set in #GA4.
GA4 uses a placeholder called (not set) whenever it does not receive information for a particular dimension.
There are many reasons for having (not set) values in reporting, which vary from report to report depending on the dimension selected.
.
.
The following are the top three reasons:
1) The number 1 reason for (not set) appearing in your GA4 reports is that you are not tagging ad URLs correctly.
Tag ad URLs using the UTM tracking parameters (manual tagging) or the auto-tagging feature.
Regularly monitor and validate your tagged URLs to identify and fix any (not set) issues that may impact your GA4 data.
.
.
2) The second most common reason for (not set) appearing in your GA4 reports is using measurement protocol (MP) to send data.
When using MP, you may not always provide all the data the standard GA4 tracking code collects automatically.
If certain data is not included in the MP request, GA4 will use the placeholder (not set) in your reports.
Make sure the parameter values are formatted correctly, as GA4 may not be able to process incorrectly formatted values, leading to (not set) entries.
Regularly monitor your MP requests to identify and fix any (not set) issues that may impact your GA4 data.
.
.
3) The Server side tracking can also result in (not set) data in GA4 reports if not implemented correctly.
If your server-side tracking implementation is not complete or does not track all user interactions, GA4 might not receive the necessary data for certain dimensions, leading to (not set) values in your reports.
When using server-side tracking, you must include all relevant parameters in your requests to GA4.
.
.
If the values for the parameters you send from the server are not formatted correctly or don’t match GA4’s expected format, GA4 might not be able to process the data, resulting in (not set) values.
Regularly monitor your server-side tracking implementation to identify and fix any (not set) issues that may impact your GA4 data.
.
Learn more >> https://t.co/7bpAb9RZVt
Duplicate events (inflated event count per user, inflated conversions) plague almost every #GA4 property and many users are not even aware of them.
To make it worse, users import the inflated conversion event data to Google Ads to optimize their ads and then expect high ROI.
Duplicate events occur largely due to the event-based measurement model of GA4.
.
.
In the event-based model, virtually any user interaction can be captured as an event, and events no longer need to fit into the strict categories of "Pageviews," "Events," "Ecommerce," and "Social" as they did in Universal Analytics.
However, this flexibility comes at a cost.
The cost is a high risk of recording duplicate events in a GA4 property.
.
.
The following techniques can fix duplicate events in GA4.
1) Use a unique ‘event_id’ parameter.
2) Don’t do double tagging.
3) Check the configuration settings of your GTM triggers.
4) Be careful when using generic GTM triggers.
5) Track State Changes.
6) Use the dataLayer.push() method correctly.
7) Check for built-in events before you create a new event.
8) Keep detailed documentation of your tracking setup.
9) Use a unique transaction ID.
10) Monitor GA4 reports for anomalies.
11) Use debouncing techniques.
12) Use throttling techniques.
Learn more >> https://t.co/7kdwaX1tVx
¡No pierdas esta oportunidad de mejorar tus habilidades de programación y hacer más eficiente tu trabajo con TypeScript!
Hoy aprendemos RECORD
https://t.co/5X7yMbHm0X
#typescript#developer
The function accepts the currency code of the source and target currencies and returns the exchange rate.
For instance, the formula =GOOGLEFINANCE("CURRENCY:USDINR") will fetch the current exchange rate of US Dollars to Indian Rupees.
https://t.co/o2EdMbT9Pm
Talk with your GA4 BigQuery data in plain English without needing SQL knowledge.
You can also view the underlying query and use it in your project.
@SphinxMind has been trained to understand the nested nature of the GA4 BigQuery exports and the calculation logic.
Hey PPC Geeks, here's another of my GAds Scripts for you.
To help you stay up to date on Gender performance in your accounts I’ve created this free Google Ads script.
Here's the link:
https://t.co/UtYH1T1hJU
Happy scripting!
#ppcchat#googleads
El archivo Robots.txt, hay gente en #SEO quien dice que Google se lo pasa por el forro (y a veces es verdad) pero es de vital importancia que lo conozcas y cómo configurarlo.
👇 Descubre para qué sirve este archivo y cómo usarlo en tu beneficio
https://t.co/LwNQOzPDFu
A common mistake I often see in #GA4 reporting is that marketers do not take all the relevant referrers into account when reporting the performance of a marketing channel, or they do not consider grouping referrers as ongoing maintenance work.
.
.
GA4 can report the performance of a marketing channel via several different referrers.
And the number of such referrers often increases or changes when you use user-defined traffic sources/mediums.
.
.
For example, GA4 can report traffic from Facebook via several referrers.
But GA4 is not going to automatically consolidate all of this data and report it to you as Facebook traffic.
This is something you would need to do manually.
You would need to identify all the traffic sources (referrers) that belong to Facebook.
Then, you would need to consolidate the data from different Facebook referrers.
Similarly, you would need to identify all the referrers that belong to Google Ads, emails, affiliates, etc.
Then, you would need to consolidate the data from different referrers.
.
.
This act of consolidating the data from different referrers is called channel grouping.
When you use custom channel groups, you can:
1. Report the performance of marketing channels much more accurately.
2. You make the GA4 reports much easier to understand, esp. for your clients.
.
.
You should create and use custom channel groups when:
1. GA4 reports the performance of a marketing channel via several different referrers.
2. You are using a user-defined traffic source and/or user-defined medium.
3. Different traffic sources are part of the same marketing channel.
4. You want to make a GA4 report easier to understand for your clients.
.
.
And channel grouping is not a one-time activity, as the referrers can often change over time.
Maybe someone in your company started tagging the ad campaigns differently.
Maybe they introduced new user-defined traffic sources/mediums which you did not take into account.
.
.
You can use the in-built GA4 custom channel groups feature for this purpose. I prefer to use the exploration report.
For example,
To see all of the Facebook traffic in your GA4 report, you can create the following exploration report (using the blank template).
Make sure to apply the highlighted filter.
This Google Ads script uses GPT to summarize account performance: Use this script to provide GPT with facts about your account and get a performance summary that can be shared with clients and stakeholders.
The post This Google Ads script uses GPT to… https://t.co/ANVhazoKrC
Bueno, vamos a hablar de indexación.
Que Google indexe todas tus URLs es cada vez menos frecuente, y no es un problema sólo para webs de nicho.
¿Indexa Google menos páginas, o más lentamente, que antes? Si es así, ¿por qué? Y sobre todo... ¿Cómo solucionarlo?
HILO 🧵 ⤵
1/24
Tutorial de Visual Studio Code, el editor de código más utilizado del mundo.
→ Introducción e instalación
→ Interfaz de usuario
→ Editor de código
→ Extensiones
→ Depuración
→ Acciones
→ Configuración
▶️ https://t.co/npdkPBEqB9