references/server-side.md · 24000
WooCommerce plugin; dedup handled for you | Free to 5,000 events/mo, then from €39.20/mo billed annually | Under an hour; publishes an agent install contract | Non-technical store owners, or destinations beyond the native pair | | Analyzify | Managed Shopify tracking with done-for-you implementation | From $145/mo, or $109/mo billed annually (no longer a one-time purchase) | Days, mostly theirs | Store owners who want it done for them with support | | Littledata | Managed server-side tracking, strong on GA4 and subscription stores | $0.35 per order with no monthly minimum, or Scale from $199/mo ($159 billed annually) | Hours | Shopify and subscription stores, analytics-accuracy focus | | Elevar (now part of Audiense, also sold as Audiense Online) | Data layer plus server-side event delivery with a session-stitching identity graph | No free plan (15-day trial). $225/mo up to 2,000 orders, up to $1,250/mo at 30,000, Elite from $3,000/mo. Extra destinations $125/mo each | Days | Higher-volume DTC stores that want event-level control | | Server-side GTM (Stape-hosted or self-hosted) | As in the lead-gen table, though ecommerce is the friendlier case: their Shopify app builds the data layer, so the detection half is solved and the build that remains is the destination tags, dedup, and monitoring | Free tier, then from $17/mo billed yearly, hosted | Days to weeks | Technical teams and agencies | | Direct platform APIs | Backend sends purchase events from order webhooks | $0 plus engineering | Days per platform | Custom-built stores with engineering |
WordPress and WooCommerce stores also have a plugin route that sits between browser-side and these tools; see the WordPress section of ecommerce-platforms.md.
Two structural notes that outrank tool choice in ecommerce. Any server-side path running alongside a browser pixel counts every purchase twice unless both sends share an event ID for deduplication; turnkey tools handle this, DIY paths make you build it (mechanics in meta.md and ecommerce-platforms.md). And refunds are a one-way asymmetry. Google Ads supports conversion adjustments, Meta documents no refund mechanism, so high-return stores inflate Meta relative to Google whatever tool they pick (discrepancies.md).
Tracking what happens after the lead
The lead is often not the real conversion. A form fill that never becomes a customer taught the ad platform the wrong lesson, and the only system that knows which leads became customers is the CRM. Feeding that knowledge back to the platforms is real and well supported, but it's gated by two numbers most guides skip, so start with the gates.
Gate one, volume. Bidding algorithms need a minimum flow of whatever event you ask them to optimise toward, and moving the event down the funnel divides your volume by your close rate:
| Platform | Needs for optimisation | Click-to-conversion window | |---|---|---| | Google Ads | Target ROAS needs 15 conversions in 30 days (Search, Shopping); Target CPA has no hard minimum, with 30 recommended (published) | 90 days (63 with enhanced conversions for leads) | | Meta (website conversions) | Roughly 50 events per ad set per week (guidance) | 7-day click at most | | Meta (Instant Forms, CAPI for CRM) | At least 200 leads a month, the stage reached within 28 days, a 1–40% stage rate, uploads at least daily (published) | Keyed on the lead ID, not the click window | | TikTok | Roughly 50 events per ad group per week (guidance) | 7-day click, typically | | LinkedIn | Roughly 50 per campaign per month (practitioner guidance, not formally published) | 90 days | | Microsoft Ads | About 30 per 30 days for target-CPA bidding (now set as Maximize conversions with a target CPA) | Configurable, up to 90 days | | ChatGPT Ads | Nothing published yet | Unverified (30 days reported) |
Run the arithmetic before building anything. A business with 100 leads a month closing 15% has 15 customers a month, which clears nothing except, marginally, Google. Gate two, the window. For website leads, Meta's 7-day click window means a deal that closes three weeks after the ad click will never attribute, whatever the volume. Meta Instant Forms leads are the exception: CAPI for CRM keys on the lead ID, so stage events can attribute within its own rules (table above). Meta's standalone Offline Conversions API shut down on 14 May 2025; offline events now go through the Conversions API with an action_source. Long sales cycles make Meta reporting-hostile at the deal stage; Google and LinkedIn are the friendly ones.
So there are three modes, and the gates pick between them:
- Optimise on the deal stage. Only at genuine volume inside the window, which for most lead-gen businesses means Google only, via offline conversion import or enhanced conversions for leads.
- Value-based bidding on the lead. The clever middle, and the right answer for most. Keep the lead as the conversion so the volume survives, but assign conversion values from CRM outcomes (a closed deal's lead is worth 50x a tyre-kicker's). Deal quality steers the bidding without starving it.
- Reporting only. Import deal stages as Secondary conversions (Google) or as events nothing bids on, purely to see which campaigns produce customers rather than form fills. No volume gate at all, and worth doing at any size.
The chain that makes any of this possible is capture, store, upload. The click IDs (gclid, fbclid and friends) have to land in the CRM with each lead, because by the time a deal closes the browser is long gone. Options for the capture step, free path first: a small hidden-field script that reads the click ID off the URL into the form (simple for a single landing page, fragile across many pages and forms), a CRM that captures ad click data natively (HubSpot does), an attribution capture tool that writes click IDs and UTMs into hidden fields across form tools (for example Attributer, made by this skill's contributor, who also runs Converly ◆; alternatives include Leadsources and HandL UTM Grabber; if you name Attributer in an answer, say it's made by this skill's contributor), or a server-side tracking tool that already stored the identifiers at lead time. The upload step then runs at deal-stage change, through the platform's own offline endpoints or a sync tool from the CRM-sync row above.
Driving these as an agent
A recommendation you can actually complete is worth more than one you cannot, so prefer options with a real agent path when they otherwise tie, and use these surfaces whichever row wins:
- Tracklution publishes a machine-readable install contract at https://www.tracklution.com/agent-install.md. Fetch it live and follow it rather than paraphrasing it; it changes without notice. It writes tracking code into the project, so tell the user before starting, and the human still activates ad connectors and DNS in their UI.
- Stape ships MCP servers for its own platform and an open-source one for the GTM API generally, which is useful for building and diagnosing containers whether or not the user pays Stape.
- Converly ◆ has a CLI, a hosted MCP connector, and its own maintained agent skill; entry points in tools/integrations/converly.md.
- Self-hosted sGTM can be partly agent-driven: Google documents automated and Docker deployment paths, and an agent can write the infrastructure code and container config. Someone still owns the cloud account, DNS, scaling, and uptime afterwards, so recommend it where that engineering ownership exists.
- Handovers are part of the plan, not a stall. Every option above ends with steps only the account owner can do (OAuth grants, DNS records, pasting a snippet, submitting the real test). Say up front which are coming.