From google-ads
Evaluate the readiness and benefit of migrating from client-side to server-side tagging.
npx claudepluginhub trueclicks/claude-plugins --plugin google-adsThis skill is limited to using the following tools:
Evaluate the readiness and benefit of migrating from client-side to server-side tagging. Server-side tagging improves data accuracy, reduces page load impact, and provides better control over data flowing to advertising platforms.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Builds scalable data pipelines, modern data warehouses, and real-time streaming architectures using Spark, dbt, Airflow, Kafka, and cloud platforms like Snowflake, BigQuery.
Builds production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. For data pipelines, workflow orchestration, and batch job scheduling.
Evaluate the readiness and benefit of migrating from client-side to server-side tagging. Server-side tagging improves data accuracy, reduces page load impact, and provides better control over data flowing to advertising platforms.
Data Source: Standard (plus external assessment)
Standard Data:
data/account/conversion_actions.md - Conversion tracking setupdata/account/account_summary.md - Account configurationNote: Full server-side tagging assessment requires website/infrastructure access beyond Google Ads data.
Reference GAQL:
SELECT
conversion_action.name,
conversion_action.type,
conversion_action.origin
FROM conversion_action
WHERE conversion_action.status = 'ENABLED'
Use /google-ads:get-custom to check conversion action origins.
| Condition | Severity |
|---|---|
| GDPR/CCPA strict requirements + no server-side | Critical |
| Estimated >20% tracking loss to ad blockers | Critical |
| Page speed heavily impacted by tags (>500ms) | Warning |
| No server-side tagging but high traffic | Warning |
| Simple tracking setup, low traffic | Info (may not need) |
Short (default):
## Server-Side Tagging Assessment
**Account:** [Name] | **Recommendation:** [Proceed/Wait/Not Needed]
### Current State
| Factor | Status | Impact |
|--------|--------|--------|
| Tracking method | [Client-side/Server-side] | - |
| Privacy requirements | [High/Medium/Low] | [Assessment] |
| Estimated ad blocker impact | [%] | [Assessment] |
### Critical ([Count])
- **[Issue]**: [Description] -> [Fix]
### Recommendations
1. [Priority action]
2. [Secondary action]
Detailed adds: