# Server-side conversions and consent

> Send a client's conversions to Google Ads, Meta, LinkedIn and ChatGPT ads through server-side Google Tag Manager, under a strict advertising-consent policy or Google Consent Mode, with QA before anything goes live.

Source: https://mavendata.ai/docs/tag-management/server-side

Maven can send a client's conversions through a server-side Google Tag Manager container, as well as from the browser. The client's site sends one event. The server container forwards it to GA4 and to each ad platform you choose, with the same event ID so platforms can deduplicate browser and server conversions. Every deployment respects the visitor's consent and is QA'd before you approve it.

## Supported ad platforms

| Platform | How conversions are sent | What Maven needs |
|---|---|---|
| Google Ads | Server-side conversion tag | Conversion ID and conversion label |
| Meta | Conversions API | Pixel ID |
| LinkedIn | Conversions API | Conversion rule ID |
| ChatGPT ads | Browser pixel and server-side event | Pixel ID |

For each platform, you also choose which event to send, for example `purchase` or `generate_lead`.

## Consent policies

Each deployment records one of two consent policies: **strict advertising consent** (the default) or **Google Consent Mode**, for sites that run Consent Mode. Whichever you choose, the deployment follows the same consent rules:

- **Meta, LinkedIn and ChatGPT ads** only receive an event when the visitor has granted advertising consent. They never receive one when the visitor's browser sends a Global Privacy Control (GPC) signal.
- **Google Ads** only receives user data when the visitor has granted it. Otherwise it gets a restricted version of the conversion with no user data.

Maven reads consent from the client's consent management platform (CMP) through the data layer: the advertising consent category, the GPC signal and the ad user data signal. It works these out from the client's real CMP setup rather than assuming them.

## Set it up

1. Make sure both of the client's GTM containers are connected: the web container and the server-side container. The server container's tagging server must be reachable on an HTTPS URL. See [Connect your tag manager and check tracking](https://mavendata.ai/docs/tag-management).
2. From your AI tool, submit a tagging request describing what you want, for example "Send Acme's purchase conversions server-side to Google Ads and Meta under strict advertising consent." Include the conversion IDs, pixel IDs or conversion rule IDs if you have them.
3. Maven prepares the deployment. It works out the source event and consent fields, stages the server-side tags, and runs QA.
4. Review the staged changes and QA evidence, then approve or reject. See [Review and approve staged changes](https://mavendata.ai/docs/tag-management/approvals).

```prompt
Submit a tagging request to send Acme's purchase conversions to Google Ads and Meta through server-side GTM under Google Consent Mode.
```

## What the QA checks

Before you're asked to approve, Maven runs test journeys and records whether:

- The browser sends the source event once, and the tagging server receives it.
- GA4 receives the event once.
- Each selected ad platform receives the event once, with the same event ID as the browser.
- Before any consent choice, after the visitor rejects, and when GPC is set, non-Google platforms receive nothing.
- After the visitor accepts, every selected non-Google platform fires.
- Google Consent Mode is observed.

If any check fails, the QA outcome is a fail, and you'll see which check failed at the review checkpoint.

## FAQ

**Will this double-count conversions?** The browser and server events share one event ID, which the ad platforms use to deduplicate. The QA confirms the IDs match.

**Can we use our own consent banner?** Yes. Maven reads consent from the CMP's values in the data layer. It doesn't replace your banner.

## Related

- [Tracking health and the daily brief](https://mavendata.ai/docs/tag-management/tracking-health)
- [MCP security](https://mavendata.ai/docs/mcp/security)
