Reporting and Data Visualization File Specification

At Amsive, we make it easy for clients to deliver clean, consistent data that powers accurate reporting and actionable insights. Whether you’re submitting campaign performance files, lead and conversion data or ongoing reporting feeds, this guide outlines everything you need to ensure your data is received, processed and visualized correctly the first time.

Our goal is to minimize back-and-forth, reduce data discrepancies and keep reporting timelines on track — so you can confidently measure performance and make informed decisions.

From file formatting and naming conventions to attribution standards and secure data transfer, we’ve got you covered. This guide details our supported file types, required field standards and reporting parameters to help your data flow seamlessly into Amsive’s reporting and analytics environment.

Please contact your account manager or reporting representative with any questions or if your data requirements fall outside the standards outlined here.

Standard Reporting Parameters

Data & File Standards

Supported file formats: parquet, delimited (pipe, tab, comma)
Field names: ≤100 characters
Date Fields in YYYY-MM-DD date format
File types & naming conventions:

Conversion file (Conversions): Amsive_[ClientName]_Conversions_YYMMDD.txt

Tracks completed sales
Suggested layout: PDF – CSV

Field Name	Data Type	Required	Notes
TransactionID	String	Yes	The primary key of the conversion (ContractNo,AccountNo, OrderID, etc).  This field is critical for robust processing of reporting data sets that will update automatically over time. If a primary key is not provide, a default of ConversionDate+Individual Identifier will be used.
FirstName	String	Yes
LastName	String	Yes
MiddleInitial	String	No
Suffix	String	No
AddressLine1	String	Yes
AddressLine2	String	Yes
City	String	Yes
State	String	Yes	2 digit postal code.
Zip5	String	Yes
Zip4	String	No
Phone	String	No
EmailAddress	String	No
DateOfBirth	DATE	No	YYYY-MM-DD format.
TransactionDate	DATE	Yes	The date the lead converted into a customer/member. YYYY-MM-DD format is preferred.
LineOfBusiness	String	No
ProductLine	String	No
ProductTypeCategory	String	No
ProductName	String	No
	String	No

Lead file (LeadActivity): Amsive_[ClientName]_LeadActivity_YYMMDD.txt

Tracks non-conversion activities
Suggested layout: PDF – CSV

Field	Data Type	Required	Notes
TransactionID	String	Yes	The unique identifier of the lead’s activity. This field is critical for robust processing of reporting data sets that will update automatically over time. If the CLIENT cannot assign this ID, AMSIVE will define a unique identifier using distinct Name + Address information.
FirstName	String	Yes
LastName	String	Yes
AddressLine1	String	Yes
AddressLine2	String	Yes
City	String	Yes
State	String	Yes	2 digit postal code.
Zip5	String	Yes
Zip4	String	No
EmailAddress	String	No
PhoneNumber	String	No
LeadSourceCode	String	No	Code indicates where the lead responded. Examples are Inbound Call Center phone numbers, Campaign Codes, etc.
DispositionCode	String	No	Code that indicates what action the lead performed when they responded.
TransactionDate	DATE	Yes	Date that the lead activity occurred on. YYYY-MM-DD format is preferred.
	String	No	Not all clients have additional response tracking outside of LeadSourceCode and Disposition Code. These may be left NULL.

Solicit File (CampaignHistory): Only needed if Amsive does not run campaigns Amsive_[ClientName]_CampaignHistory_YYMMDD.txt

Captures marketing touchpoints
Suggested layout: PDF – CSV

Field	DataType	Required	Notes
Client	String	Yes	The name of the client.
CampaignType	String	No	This groups multiple campaigns together for analysis.
CampaignSubtype	String	No
Channel	String	Yes	Valid values are: Direct Mail, Email, Targeted Digital, Outbound Call, or SMS Text.
JobID	String	No	This is populated with the Amsive DirectLink JobNo for mail files printed at Amsive. It is strongly recommended this be populated, even though it is not required.
SolicitDate	Date	Yes	The mail date of the solicitation. YYYY-MM-DD is the preferred format.
FirstName	String	Yes	Should be populated for attribution.
MiddleName	String	No
LastName	String	Yes	Must be populated for attribution.
Suffix	String	No	Should be populated for attribution.
AddressLine1	String	Yes	Must be populated for attribution.
AddressLine2	String	No	Should be populated for attribution.
City	String	Yes	Should be populated for attribution.
State	String	Yes	Must be populated for attribution.
Zip5	String	Yes	Must be populated for attribution.
Zip4	String	No
Model	String	No	The name of the model that drove the solicitation.
ModelDecile	String	No
ModelScore	String	No
TargetAudience	String	No	Valid values are Prospect, Lead, Member, and Winback.
Segment	String	No	Used to group audience segments for reporting.
SubSegment	String	No
AdditionalSegment3	String	No
AdditionalSegment4	String	No
EnvelopeCode	String	No
CampaignID	String	Yes	Populate with a code that groups together all channels that were included in a single Campaign (ie: Drop #, Campaign Identification, etc)
CampaignName	String	No	Optional friendly name of the CampaignID
EmailAddress1	String	No
DateOfBirth	Date	No	YYYY-MM-DD is the preferred format.
SolicitID	String	Yes	The unique ID of the individual solicitation. This ID must be unique across all mail drops for a specific client.
InboundPhoneNumber	String	No	Optional Inbound call number (TFN/DNIS) printed on the piece to be used for report groupings.
ClientCampaignCode	String	No	Optional Client campaign code (often the Salesforce code of the segment, etc) to be used for report groupings.
AttributionStartDate	Date	No	YYYY-MM-DD is the preferred format. If a Start date is not provided, the SolicitDate will be used by default.
AttributionEndDate	Date	No	YYYY-MM-DD is the preferred format. If an End Date is not provided, the SolicitDate + 90 days will be used by default.
CreativeVersionCode	String	No	Define your creative groupings using this field.
PackageTypeCode	String	No	Valid values are Letter, Self-Mailer, PostCard, Greeting Card, Calendar, Magazine, Snap-Pack.

Reporting and Data Visualization File Specification

Standard Reporting Parameters

Data & File Standards

File & Data Transfer Standards

Attribution logic Standard

NEXT STEPS