Agentic Commerce

Convertmax can classify events and sessions as agentic commerce when the request includes explicit attribution hints or when the worker recognizes known AI-driven referrers.

This guide focuses on how to send those hints intentionally so downstream reporting stays clean and explainable.

Normalized fields stored on each event

When agentic attribution is present, Convertmax stores these fields on the event record:

• agentic_source
• agentic_confidence
• agentic_session
• agentic_protocol
• agentic_channel
• agentic_evidence

Typical normalized sources include chatgpt, copilot, google_ai, perplexity, shopify_agentic, acp, ucp, and unknown.

Accepted request shapes

You can provide agentic hints in any of these forms:

• root-level request fields such as agentic_source and agentic_channel
• data.agentic_* aliases inside the event payload
• a nested object at data.agentic
• request headers such as X-Agentic-Source and X-Agentic-Protocol

Detection order

Convertmax applies attribution in this order:

1. Explicit metadata from your integration, protocol, or commerce channel
2. Known AI referrers such as ChatGPT, Copilot, Perplexity, or Gemini
3. Lower-confidence heuristics reserved for future use

That means your server-side hints win over referrer inference.

Preferred payload example

{
  "event_type": "convert",
  "visitor": "visitor_123",
  "session_id": "session_abc",
  "data": {
    "page": "https://example.com/checkout/success",
    "agentic": {
      "source": "chatgpt",
      "confidence": "high",
      "session": true,
      "protocol": "acp",
      "channel": "shopify_agentic",
      "evidence": ["protocol:acp", "channel:shopify_agentic"]
    }
  }
}

Header-based example

curl -X POST "https://event.convertmax.io/v1/track/" \
  -H "Authorization: Bearer <api_key>" \
  -H "Content-Type: application/json" \
  -H "X-Agentic-Source: chatgpt" \
  -H "X-Agentic-Confidence: high" \
  -H "X-Agentic-Session: true" \
  -d '{
    "event_type": "convert",
    "visitor": "visitor_123",
    "session_id": "session_abc",
    "data": {
      "page": "https://example.com/checkout/success"
    }
  }'

Protocol and channel behavior

Some values trigger strong attribution automatically:

• agentic_protocol=acp or agentic_protocol=ucp promotes the event to a high-confidence agentic session
• agentic_channel=shopify_agentic does the same
• channels containing agentic, chatgpt, copilot, or perplexity also contribute evidence

If a valid source is provided, Convertmax defaults the session to agentic and records evidence for that source.

Recommended implementation pattern

• send explicit agentic metadata from the system that knows the order source best
• use agentic_protocol for standards like acp or ucp
• use agentic_channel for commerce-platform labels such as shopify_agentic
• pass agentic_evidence when you want to preserve why the attribution was assigned

If you already send standard Convertmax events, you do not need a new endpoint. Add these fields to your existing track, server, or pixel requests and the worker will normalize them for storage.