The transactionID variable uniquely identifies a transaction so the hit can tie to data uploaded through Data Sources. This variable is valuable in cases where you want to use data from other channels and link it to data collected with AppMeasurement.
Make sure that Transaction ID Storage is enabled in a report suite before using this variable. See General Account Settings in the Admin user guide for more information.
When you set transactionID on a hit, Adobe takes a "snapshot" of all Analytics variables set or persisted at that point in time. Data uploaded through Data Sources with a matching transaction ID is permanently tied to those variable values.
By default, Adobe remembers all transaction ID values (linked and unlinked) for up to 90 days. If your offline interaction process is longer than 90 days, contact Customer Care to have this limit extended.
Transaction ID in Adobe Experience Platform Launch
You can set transaction ID either while configuring the Analytics extension (global variables) or under rules.
- Log in to launch.adobe.com using your AdobeID credentials.
- Click the desired property.
- Go to the Rules tab, then click the desired rule (or create a rule).
- Under Actions, click an existing Adobe Analytics - Set Variables action or click the '+' icon.
- Set the Extension dropdown to Adobe Analytics, and the Action Type to Set Variables.
- Locate the Transaction ID section.
You can set transaction ID to any string value, including data elements.
s.transactionID in AppMeasurement and Launch custom code editor
The s.transactionID variable is a string containing a unique identifier for a transaction. Valid values include alphanumeric characters up to 100 bytes in length. Its default value is an empty string.
s.transactionID = "ABC123";
If you have more than one transaction ID for a hit, you can delimit each with a comma. Multiple transaction IDs are still subject to the 100-byte limit.
s.transactionID = "ABC123,XYZ456";
If you integrate multiple offline channels using this variable, make sure that different channels don't overlap transaction IDs. For example, if you have a call center transaction ID value of 1234 and a sales lead transaction ID value of 1234 , they can conflict and cause unexpected results. Make sure that transaction IDs contain unique formats per offline channel and differentiate them if necessary. For example, set your call center transaction ID to call_1234 and your sales lead transaction ID lead_1234 in both Data Sources and AppMeasurement.