Server‑side A4T (Target to Analytics) not stitching - tnta not appending

How are you sending the tnta payload to the client side for Analytics to pick up?

First determine which A4T mode you are actually using

You need to confirm one of these two patterns:

Option A — Target forwards to Analytics automatically
Use this when the Target server-side request includes:

experienceCloud.analytics.logging = "server_side"
supplementalDataId
trackingServer
In this model:

Target sends the analytics payload server-side
your browser /b/ss pageview does not need manual tnta injection
stitching depends on the same identity + SDID binding

Option B — You retrieve the payload and send it yourself
Use this when Target is configured for payload return:

analyticsLogging = "client_side" in at.js-style flows, or

Target returns analytics.payload from the server-side SDK / delivery response
In this model:

you must send the payload to Analytics yourself
the outgoing Analytics call must include:
pe=tnt
tnta=<payload>
mid=<ECID>
These params must be sent via the analytics data insertion API
Do not mix these two models halfway.

What I think is most likely in your case

the first Analytics beacon is firing before the rule has access to the payload, or

The implementation is configured for server-side logging while you are trying to do manual client-side forwarding.

However, if you still face difficulty, log a support ticket so a detailed review can be done. 
 

Thank you! 

Sarthak Bhatt | Senior Product Consultant | Customer Experience | Adobe