Adobe Target Prefetch and Notification implementation

Hi 

I believe you have completed the feedback loop setup for A4T (passing tnta values through analytics)

If not sure please see the diagram in in this article 

https://shafi.com.au/how-to/adobe-target/adobe-target-api-server-side-implementation/

Now for prefetch you have an extra parameters "eventTokens"

"prefetchResponses":[ 
      { 
         "mbox":"homePageHero2",
         "content": "some content",
         "eventTokens": [...],
         "clientSideAnalyticsLoggingPayload": {
            "pe": "tnt",
            "tnta": "86494:0:0|0,86494:0:0|2,86494:0:0|1"
         }
      }
   ]

 You have to pass this eventTokens via analytics call (same way how you handle tnta into analytics payload)

https://developers.adobetarget.com/api/legacy-api/index.html#a4t-for-batch-delivery-api

Best Practices for Batch Delivery

1. It is not necessary to have all three kind of mboxes in a request. You can make a request for just a single mbox using this API.
2. Note that the profileParameters are set at the top level of a Batch request and all mboxes, prefetch or regular, will be associated with the same visitor profile.
3. When working with multiple mboxes in the batch mbox request, the Target edge will process the mboxes in the sequence specified by the IndexId parameter value.
4. Overriding Parameters: You can override mbox parameters, such as IP, time.
5. Prefetch: Fetch offers associated with an mbox in advance without incrementing the impression or visit/visitor count.
   1. Make sure you manage the eventTokens associated with an mbox for use at the notifications stage.
   2. When the qualifying campaign has a click metric defined for an mbox, then the clickToken will be returned in the response. When the visitor clicks the mbox and a notification request is sent, the notification type should be set to click and the corresponding clickToken should be included.
6. Notifications: There are two kinds of notifications - hit and click.
7. Profile Scripts are executed per each mbox inside mboxes, prefetch and notifications, as per the following logic:
   1. Regular mbox (part of the mboxes array): Profile Scripts are executed and results persisted in the profile immediately. Note that the sequence of execution will be as per the IndexId of the mboxes.
   2. Prefetch mbox (part of the prefetch array): Target will execute the profile scripts and cache it without persisting it to the profile. A profileScriptToken will be returned in the response and should be included in the notification request for this mbox. The results will be persisted into the profile at this time.
   3. Notification mbox (part of the notification array): If the notification has the profileScriptToken, then the profile script values will be written to the profile without re-executing them. If the profileScriptToken is missing then the profile scripts will be executed and again and persisted to the profile.
8. If Response Tokens are enabled, they will be returned for each mbox response in the mboxes and prefetch sections.