gtm-server-conversion-enhancement

Configure server-side Google Ads and Floodlight conversions with hashed user data and consent forwarding.

1|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/scumunna/programmatic-skills --skill gtm-server-conversion-enhancement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gtm-server-conversion-enhancement
Source: https://github.com/scumunna/programmatic-skills/tree/main/skills/gtm-server-conversion-enhancement
Command: npx skills add https://github.com/scumunna/programmatic-skills --skill gtm-server-conversion-enhancement

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gtm-server-side-tagging, gtm-consent-mode-v2, google-ads-conversion-tracking-and-attribution, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps with moving Google Ads and Floodlight conversions server-side, setting up server-side Enhanced Conversions, sending hashed user-provided data, and ensuring consent-aware forwarding.

Core Features & Use Cases

  • Server-side Conversions: Route conversions through a server-side GTM container for better control and data integrity.
  • Enhanced Conversions: Implement server-side Enhanced Conversions for precise user matching and conversion recovery.
  • Consent Management: Forward conversions based on user consent, ensuring compliance with privacy regulations.
  • Use Case: If you need to recover conversions lost due to cookie deletion, ITP, or consent denial, this skill can help by forwarding conversions server to server and using Enhanced Conversions.

Quick Start

Use the gtm-server-conversion-enhancement skill to set up server-side Enhanced Conversions for Google Ads conversions.

Frequently Asked Questions about gtm-server-conversion-enhancement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up server-side Enhanced Conversions for Google Ads to recover lost conversions?

Server-side Enhanced Conversions recover lost conversions by routing Google Ads tracking through a server-side GTM container and sending hashed user-provided data for precise user matching. This setup requires a server-side GTM container and Enhanced Conversions configuration.

What is server-side conversion tracking and when do I need it for Google Ads?

Server-side conversion tracking routes Google Ads and Floodlight conversions through a server-side GTM container for better data control. You need it to recover conversions lost due to cookie deletion, ITP, or consent denial.

Do I need a Consent Management Platform to forward server-side conversions based on consent?

Yes, forwarding server-side conversions based on user consent requires a Consent Management Platform. This ensures compliance with privacy regulations by only sending Google Ads and Floodlight conversions when consent is granted.

How do I send hashed user-provided data for Enhanced Conversions in server-side GTM?

You send hashed user-provided data for Enhanced Conversions by configuring server-side GTM to process and forward the data. This implements precise user matching and improves conversion recovery for Google Ads.

Can I route Floodlight conversions through a server-side GTM container?

Yes, you can route Floodlight conversions through a server-side GTM container. This skill manages server-side Floodlight conversions, ensuring better data integrity and consent-aware forwarding.

Why are my Google Ads conversions dropping due to ITP and how can server-side tracking help?

Google Ads conversions drop due to ITP restricting cookie tracking. Server-side tracking helps by forwarding conversions directly from your server to Google, bypassing browser restrictions and recovering lost conversion data.