You can retrieve audit report data for off-line analysis, permanent storage, or to build a custom reporting interface.
T&T stores audit data for 4 weeks only. To preserve it, use the Campaign Audit Report API or the Admin interface to store it in a secondary location.
The activity performance REST API allows you to fetch the activity report using the parameters below. This report works for all
activity types except Automated Personalization and Optimizing.
Note: Date times should be specified in the ISO 8601 format. Do not omit the time zone related portion.
Throttling is set to the same value as for other campaign report APIs: 50 requests per minute.
No special permissions are required to access this report (read-only users have access).
Create the URL
For each operation add the parameters and values you need as a filter. For example:
(Required) The T&T client code.
(Required) The Email address associated with the T&T user performing the operation.
(Required) The T&T password associated with the specified email address.
(Required) Identifies the type of T&T action to execute. To generate audit reports, this value is always auditReport.
(Required) The ID of the campaign you want to query. To identify the Campaign List ID, Use the
(Required) The report start date and time. Specify the date using the following format: YYYY-MM-DDTHH:mm. The performance report uses the time zone setting specified in the Web browser.
(Required) The report end date and time. Specify the date using the following format: YYYY-MM-DDTHH:mm. The performance report uses the time zone setting specified in the Web browser.
(Optional) The URL-encoded success metric name (formerly called a step). By default, the step value is last step.
(Required) A URL-encoded host group name, as defined in the T&T Tool. By default, the environment value is Production.
(Optional) The report output format. Currently, the only supported value for this parameter is csv (comma-separated value).
Specify which version of the API you want to use. Set this to version=1 unless there is a different version described in the documentation.
Parameters and values are case sensitive.
Inspect the Query Response
Target generates the audit report in CSV format, which you can import into any spreadsheet program, such as Microsoft* Excel*. For example:
"Campaign: landing campaign RFM"
"Downloaded at: 2007-08-24. Time zone: EST5EDT"
"Campaign Id","Recipe","Order Date","Order Time","Order Id","Amount","Order Flag","Product Ids""worst",""
Parse the Query Response
Optionally, you can use a scripting language, such as Perl, Python, and Ruby, to programmatically manipulate the audit report contents to create custom reports.
|Name||Description||Allowed Values||Default Value
|environmentId||The TnT environment Id||TnT environment Id||Id of the client's "Default for Reporting" environment|
|conversionMetricLocalId||Local ID(s) of the conversion metrics. Can use more than one metric as conversion, e.g. to use metrics with local IDs 11 and 12 as conversion metrics, pass conversionMetricLocalId=11&conversionMetricLocalId=22.||Valid metric local ID||32767|
|metricLocalId||Local IDs of metrics to be included in report. If not specified, only the campaign totals (summary) will be generated. Can specify multiple values as metricLocalId=11&metricLocalId=22. Can use the hardcoded local IDs of 0, 2 and 32767.||Valid metric local IDs||If not specified, only campaign totals will be generated, without metric level data.|
|reportingSegmentLocalId||Local ID(s) of the reporting segments for which reports should be generated. If no value is specified, then only the campaign totals (without any reporting segment) report will be generated. If multiple reporting segments are specified, then, besides the campaign total report, the reports for the indicated reporting segments will be generated. To include all reporting segments enumerate them all as reportingSegmentLocalId=11&reportingSegmentLocalId=22&...||Valid reporting segment local ID||If no value is specified then only campaign totals report will be generated without segment reports|
|reportInterval||Report period. If not specified, then life of campaign will be used. Interval start date will be floor rounded to nearest hour and interval end date bill be ceiling rounded to next hour.||Time interval in ISO format, e.g. 2007-03-01T21:00:00-07:00/2008-05-11T21:00:00-07:00.||Life of campaign.|
|daysOfWeek||List of days of the week to include. All days will be included if not specified. To specify more than one value, e.g. Saturday and Sunday, use: dayOfWeek=6&dayOfWeek=7||1-7, with 1 corresponding to Monday, 2 - Tuesday etc||All days of the week|
|resolution||Resolution to group data by. If it's not specified, then only totals over the entire report period will be shown.||
hour | day | week | month
Maximum number of generated data points for the specified resolution and report period should not exceed 100
|If not specified, then only totals for the entire report period will be generated|
All deleted experiences will be included in the report, even the ones that have no data. Deleted success metrics and reporting segments will not be shown.
Data for all counting methods will be included in the report, as well as corresponding lifts and confidence (with confidence intervals). In order to determine a winning experience, iterate through the list of reports for each experience and find the one with maximal lift.
Response JSON Structure
Thank you for submitting your feedback.