Server-side tagging demo

Same store. Same tags. Different place to run them.

Every version of Larkspur & Ladle sends the same marketing data to the same vendors. Version A runs every vendor's tag in your browser. Version C runs one Google tag in your browser, which sends a single stream to a server that forwards it to the vendors. Version B, in between, is the migration we'd recommend: C, plus the few browser pieces vendors need next to their server tags.

A · Client-side onlyEvery vendor's tag runs in the browser through a regular GTM container. B · Realistic mixLike C, but Meta's pixel, LinkedIn's Insight Tag, Criteo's ID sync and The Trade Desk's pixel stay in the browser next to the server tags. C · Mostly server-sideOne Google tag in the browser sends events to a server-side GTM container, which sends them on to the vendors (all but The Trade Desk, which has no server option).

Why server-side tagging · See the measured results · Run it yourself

Fake store, fake products, fake tag IDs. Built for a booth demo.