Integration Data Sources use a transaction ID to tie offline data to an online transaction (like a lead or purchase generated online).
Each unique transactionID sent to Adobe is recorded in preparation for a Data Sources upload of offline information about that transaction. See Data Sources .
Enable Transaction ID Storage
Before transactionID values are recorded, Transaction ID Storage must be enabled for the report suite selected in the Report Suite Manager. This setting is located at
Analytics > Admin > Report Suites > Edit Settings > General > General Account Settings.
To see whether transactionID Storage is enabled for a report suite, go to
Analytics > Admin > Data Sources > Manage
Syntax and Possible Values
The transactionID should contain only alphanumeric characters. If multiple transactionIDs should be recorded in a single hit, you can use a comma to delimit multiple values.
Pitfalls, Questions, and Tips
- If transactionID recording is not enabled, transactionID values will be discarded and unavailable for use with Integration Data Sources. Make sure to set a conversion variable or event (an eVar or the events variable) on the page where transactionID is set. Otherwise, no data is recorded for the transactionID .
- If you are recording transactionIDs for multiple systems, such as purchases and leads, make sure the value in transactionID is always unique. This can be accomplished by adding a prefix to the ID, such as lead_1234 and purchase_1234. Integration Data Sources do not function as expected ( Data Source data will tie to the wrong data) if a unique transactionID is seen twice.
- By default, transactionID values are remembered for 90 days. If your offline interaction process is longer than 90 days, contact Customer Care to have the limit extended.
The transactionID variable can contain any character other than a comma. It should be in the same location where the character limit (100 bytes) is specified. If multi-byte characters are used, multi-byte character support must be enabled in order to avoid problems with unexpected characters in the transactionID .