GTM. Custom template gallery. Ship CAPI tags without reinventing the wheel.

What this means for your store

Hand-rolling server-side fetch calls for every ad platform burns agency hours and breaks on the next API change. The community template gallery hosts reviewed Custom Templates for Meta Conversions API, Snapchat, Pinterest, and other vendor-maintained connectors. Import once, configure instances like built-in tags, and keep secrets in GTM constants instead of page source.

Scenario on a real storefront

Your UK homeware brand already fires browser purchase to Meta. iOS and ad blockers undercount conversions, so you add server-side CAPI from the gallery instead of writing HTTP tags from scratch:

Templates → Search Gallery → "Facebook Conversions API"
  Import → Approve permissions (read/write dataLayer, send HTTP)

New tag: Facebook ConAPI (Gallery)
  Pixel ID: {{CONST - Meta Pixel ID}}
  Access token: {{CONST - CAPI token}}
  Event name: purchase
  Trigger: Custom Event purchase (dataLayer)

// Gallery templates version independently - read changelog before publish

What to do next

• Check permissions and publisher before import - unofficial forks sometimes request full dataLayer read access.
• Note the template version in your publish comment; silent auto-upgrades can remap event parameters mid-quarter.
• Gallery CAPI still needs a matching event_id from the browser tag - the template does not dedupe by itself.

Bottom line

The gallery cuts weeks off CAPI plumbing for stores running browser plus server tags. Import maintained templates, lock tokens in constants, and keep event parameters aligned across both sides.