No this is most likely a setup-related issue; log a support ticket, please. 

Target itself doesn’t require Analytics consent to render experiences.With at.js or Web SDK, Target can run without Analytics at all. Adobe explicitly recommends you control when Target fires via Launch rules or the ECID Opt-in service, not via Analytics cookies   So if your activities only show aft...

Yes, for your getOffers()-based integration you must either: 1) let Target/at.js render the content via applyOffers() / applyOffer(),   or2) if you render everything yourself, explicitly call sendNotifications() (at.js 2.1+) or a Delivery API notifications call so that impressions/conversions are co...

@Perrin_Ennen is correct,  There is no out‑of‑the‑box functionality like this. You need your own tracking design if you want per‑content impression and click reporting.  

Yes, this appears to be a valid use case for a regional mbox.   As part of this approach, you would create an activity in the Adobe Target UI with the mbox name  like "test". You would then configure the same mbox name in your Delivery API request. This ensures that only the activity associated with...

Which sdk are you using, Optimize or only Mobile Core? Also how are you using the timeout? Can you please provide some more information? 

You should be good with one token only; after that is done, it is cached in your cookie for all pages

These kind of errors occur mostly due to either 1) Incorrect format of feed file 2) The file is missing from your server   Also  Target’s “Google Product Feed” expects Google Product Search XML, not a raw sheet Refer to DOC: https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/...

That flag is only used for rendering. Even if it is unchecked, the activity will still always be returned in the response; however, when unchecked, the content will not be displayed.

The code looks correct, is the activity live inside target UI? Is the same mbox server-side-mbox used in your activity?