Use Atune with server-side GTM

Server-side GTM can forward product telemetry to Atune without installing the Atune SDK first.

Use this when your team already routes events through GTM and wants a quick pilot. Native Atune capture is still the recommended long-term path for agent-led installs.

Target URL

Create an HTTP request from your server-side GTM container to:

https://useatune.com/api/segment

Set these headers:

Authorization: Bearer <ATUNE_API_KEY>
Content-Type: application/json

Payload shape

Send a Segment-style track message. The important part is account attribution. Include accountId on the top level or in properties.

{"type": "track","messageId": "{{event_id}}","event": "{{event_name}}","userId": "{{user_id}}","properties": {  "accountId": "{{account_id}}",  "route": "{{page_path}}"}}

Identity

Forward identify or group only when your workspace DPA is accepted and you intentionally want Atune to store personal or company traits.

For most first pilots, start with track only. Once behavior is landing on the right accounts, add group so the account names become human-readable.

Verify

Open Settings → Events in Atune. Segment and GTM traffic appears with source segment/track, segment/identify, or segment/group.

If events are rejected, check these first:

• Missing Authorization header.
• Missing account mapping.
• Unsupported message type.
• DPA not accepted for identify or group.