Analytics for Target (A4T) reporting
ÃÛ¶¹ÊÓÆµ Target supports A4T reporting for both on-device decisioning and server-side Target activities. There are two configuration options for enabling A4T reporting:
- ÃÛ¶¹ÊÓÆµ Target automatically forwards the analytics payload to ÃÛ¶¹ÊÓÆµ Analytics, or
- The user requests the analytics payload from ÃÛ¶¹ÊÓÆµ Target. (ÃÛ¶¹ÊÓÆµ Target returns the ÃÛ¶¹ÊÓÆµ Analytics payload back to the caller.)
Pre-requisites
- Configure the activity in the ÃÛ¶¹ÊÓÆµ Target UI with ÃÛ¶¹ÊÓÆµ Analytics as the reporting source, and ensure the accounts are enabled for A4T.
- The API user generates the ÃÛ¶¹ÊÓÆµ Marketing Cloud Visitor ID and ensures this ID is available when the Target request is executed.
ÃÛ¶¹ÊÓÆµ Target automatically forwards the Analytics payload
ÃÛ¶¹ÊÓÆµ Target can automatically forward the analytics payload to ÃÛ¶¹ÊÓÆµ Analytics if the following identifiers are provided:
supplementalDataId
: The ID that is utilized to stitch between ÃÛ¶¹ÊÓÆµ Analytics and ÃÛ¶¹ÊÓÆµ Target. In order for ÃÛ¶¹ÊÓÆµ Target and ÃÛ¶¹ÊÓÆµ Analytics to correctly stitch data together, the samesupplementalDataId
needs to be passed to both ÃÛ¶¹ÊÓÆµ Target and ÃÛ¶¹ÊÓÆµ Analytics.trackingServer
: The ÃÛ¶¹ÊÓÆµ Analytics Server.
code language-js line-numbers |
---|
|
code language-java line-numbers |
---|
|
User retrieves analytics payload from ÃÛ¶¹ÊÓÆµ Target
A user can retrieve the ÃÛ¶¹ÊÓÆµ Analytics payload for a given mbox, then send it to ÃÛ¶¹ÊÓÆµ Analytics via the . When an ÃÛ¶¹ÊÓÆµ Target request is fired, pass client_side
to the logging
field in the request. This request returns a payload if the specified mbox is present in an activity that is using Analytics as the reporting source.
code language-js line-numbers |
---|
|
code language-java line-numbers |
---|
|
Once you have specified logging = client_side
, you will receive the payload in the mbox field.
If the response from Target contains anything in the analytics -> payload
property, forward it as it is to ÃÛ¶¹ÊÓÆµ Analytics. ÃÛ¶¹ÊÓÆµ Analytics knows how to process this payload. This can be done in a GET request using the following format:
https://{datacollectionhost.sc.omtrdc.net}/b/ss/{rsid}/{content_type_num}/{code_ver}/{session}?pe=tnt&tnta={payload}&c.&a.&target.&sessionId={sessionId}&.target&.a&.c&mid={mid}
Query string parameters and variables
rsid
content_type_num
code_ver
session
pe
tnt
tnta
analytics -> payload -> tnta
sessionId
mid
Required header values
adobeags421.sc.omtrdc.net
)Sample A4T data insertion HTTP Get call
Non-URL-encoded version For Readability (format not to be used for API calls):
https://demo.sc.omtrdc.net/b/ss/myCustomRsid/0/MOBILE-1.0/0?tnta=253236:0:0|0,253236:0:0|2,253236:0:0|1,253613:0:0|0,253613:0:0|2,253613:0:0|1&c.&a.&target.&sessionId=45c08980-f4b9-4e11-96db-067d58e49f74&.target&.a&.c&pe=tnt&mid=69170113867710665996968872592584719577
URL-encoded version (format to be used for API calls):
https://demo.sc.omtrdc.net/b/ss/myCustomRsid/0/MOBILE-1.0/0?tnta=253236%3A0%3A0%7C0%2C253236%3A0%3A0%7C2%2C253236%3A0%3A0%7C1%2C253613%3A0%3A0%7C0%2C253613%3A0%3A0%7C2%2C253613%3A0%3A0%7C1&c.%26a.%26target.%26sessionId=45c08980-f4b9-4e11-96db-067d58e49f74%26.target%26.a%26.c&pe=tnt&mid=69170113867710665996968872592584719577