By sending order data to Triggerbee, you will be able to analyze how your campaigns are performing in terms of generating sales.
Logging order data to Triggerbee can be done in three ways:
Scripting order data using the Triggerbee script API
Not very technical? Check out our GTM Template for Event logging - it can't get any easier!
When you have Revenue coming into Triggerbee, you can add Attribution to your campaigns to see exactly how much revenue flows through your campaigns. Read more about Attribution and Assisting Sales here.
Not seeing the Attribution option in your account? Reach out to Triggerbee Support to activate it.
How to log Order Data
Log Order Data via Triggerbee JavaScript API
On your Orderconfirmation page, call the Triggerbee JavaScript API using the event method like this:
triggerbee.event({
type: 'purchase',
id: 123,
data: {
revenue: 1500
}
})
Revenue should be entered in the same currency as in your Triggerbees account settings. The ID (123 in the example) can be an Order ID or any unique ID associated with the purchase.
Note: Only use dots to separate decimals in the revenue variable.
Correct example:
triggerbee.event({
type: 'purchase',
data: {
couponCode: 'welcome15',
revenue: 1500.0,
identity: {
email: 'someone@triggerbee.com'
}
}
});Incorrect example:
triggerbee.event({
type: 'purchase',
data: {
couponCode: 'welcome15',
revenue: 1500,0,
identity: {
email: 'someone@triggerbee.com'
}
}
});If done correctly, revenue will be stored on the session like this:
Setting identity
You should also pass the customer's identity to the event in the data object. And optionally, if a coupon code/voucher was used, pass it along so that Triggerbee can calculate attribution on campaigns.
A more complete example would be like this:
triggerbee.event({
type: 'purchase',
id: 123, // Order ID or similar
data: {
couponCode: 'welcome10',
revenue: 1500,
identity: {
email: 'john@triggerbee.com',
firstname: 'John',
lastname: 'Doe'
}
}
});