Post_Tnt_Action Not Populating post-MobileSDK | Community
Skip to main content
U
user000111
Level 1
February 20, 2026
Question

Post_Tnt_Action Not Populating post-MobileSDK

  • February 20, 2026
  • 1 reply
  • 39 views

Hello - 

Has anyone else had a similar experience that when you made the transition to the MobileSDK your post_tnt_action field in your data feed no longer was populating? 

 

Looking for any type of troubleshooting ideas -- checkboxes that we might be missing, a step that is often overlooked, something new that needs to be setup, etc. 

 

Thanks!

1 reply

P
PrasanthV
Level 3
April 15, 2026

Hi ​@user000111,

 

Here is a troubleshooting checklist for the Mobile SDK:

 

1. Check the "Identity" Extension

For post_tnt_action to work, Analytics and Target must agree on who the user is.

  • The Check: Ensure the Identity extension is registered and starting correctly before any Target or Analytics calls are made.

  • Why: If the ECID (Experience Cloud ID) isn't consistent across both calls, Analytics won't know which Target activity belongs to which session.

2. Enable "A4T" in the Target Extension Configuration

In the Adobe Data Collection UI (Tags/Launch), go to your Adobe Target Extension configuration.

  • The Check: Look for a checkbox or setting related to A4T (Analytics for Target) or "Assurance."

  • The Step: Ensure that the "Target Reporting Source" is set to Adobe Analytics. If this is set to "Target," the SDK won't bother sending the metadata that populates the post_tnt fields.

3. Ensure "Shared State" is Working

The Mobile SDK uses a "Shared State" system. When Target gets an experimental offer, it creates a "Shared State" that the Analytics extension is supposed to "read" and attach to the next hit.

  • Troubleshooting Idea: Use Adobe Experience Platform Assurance (formerly Project Griffon).

  • What to look for: Look at the Analytics events in Assurance. Check the "ACPPrefetchToken" or "Target Payload." If you don't see Target activity IDs inside the Analytics event data in the debugger, the Analytics extension isn't "hearing" what Target is doing.

4. Check the Sequence of Calls

In mobile, timing is everything.

  • The Problem: If you send an Analytics trackAction or trackState before the Target retrieveLocationContent (or getOffers) call has finished, the Analytics hit will go out "empty" because it doesn't have the Target data yet.

  • The Fix: Ensure your Analytics tracking call happens after the Target callback has successfully returned the offer.

5. Review the Data Feed Version

Sometimes, when moving to the new SDK, your data feed might need a refresh.

  • The Check: Verify that your Data Feed includes the "Target" column group.

  • The Step: If you recently changed your reporting suite or how you identify users (switching to a 3rd party ID), the Data Feed might be filtering out those rows because of a mismatch in the "VisID" (Visitor ID).

Terms & ConditionsAccessibility statement

Loading footer...