Menu

Categories

content management

digital marketing

web development

Tags

accelerated mobile pages

audience design

auto-event tracking

auto-link domains

built-in variables

calculated metrics

campaign tracking

chrome extension

click variables

client template

cloud functions

container export

container snippet

content analysis

content blocker

content engagement

content grouping

content management

content management system

content security policy

content strategy

conversions api

core web vitals

cross-domain tracking

custom dimension

custom dimensions

custom html tag

custom html tags

custom javascript

custom templates

data collection

data engineering

data layer variable

definition of success

developer tools

digital marketing

dynamic content

element visibility

enhanced ecommerce

event listeners

experimentation

google analytics

google analytics 4

google analytics settings

google bigquery

google cloud platform

google tag manager

google-optimize

googletagmanager

history change trigger

history listener

intelligent tracking prevention

internal traffic

measurement protocol

meta description

modular architecture

parameter reporting

personal experience

public speaking

regular expression

search engine optimization

server-side tagging

single-page apps

social interactions

syntax highlight

tag management solution

tag management solutions

technical marketing

tracking protections

transformations

universal analytics

user permissions

variable templates

web development

website redesign

Meta

Add IPv6 Support to Your Server-Side GTM Load Balancer

If you’re running server-side Google Tag Manager on Google Cloud Run behind an External Application Load Balancer, your tagging endpoint is currently reachable only over IPv4 with a default installation.

For most of your visitors, that’s fine. But for users on IPv6 networks, it creates a silent data quality problem that directly affects how well vendor tags like Meta’s Conversions API (CAPI) can match server-side events to their client-side counterparts.

When a user on an IPv6 network fires the Meta pixel on your site, Meta records the event alongside the user’s IPv6 address. Your server-side CAPI tag is then supposed to send the server-side version of that same event, including the client_ip_address field, so that Meta can deduplicate the two and improve match quality.