What's the relationship of Order and Payment?

[KiriHong]

Hi there,

When referring to the metrics 'Order (purchase event)', I only found document shows it relates to the purchase event. I'm wondering if 'Order' contains all the purchases, or only those with full payment? Is there further information of the relationship between order and payment?

Best regards

[EurosIMS · Accepted solution]

Hi @KiriHong,

Orders is only incremented when scPurchase is present in the events string (assuming this is Classic Analytics). 

All Orders are counted towards this; Adobe doesn't care on the amount of revenue, be it 0, half, full, etc.- it would be whatever is being passed as part of the product string. So for a day date range, Orders will count every order for that day, ie. every time someone visited a page where scPurchase was present in the events string.

There are many, many other things that come into play for the orders, events, & products variables, however I'm not sure if you need that level of detail for your question.

https://experienceleague.adobe.com/en/docs/analytics/implementation/vars/page-vars/products

[KiriHong]

Hi @EurosIMS & @Jennifer_Dungan ,

Thank you for the detailed explaination. And I will check with the Purchase/scPurchase event to make sure if Order is incremented before a payment or after

Best regards,

[Jennifer_Dungan]

As @EurosIMS said, Orders is driven by the purchase event (note that unlike other product lists events, purchase is not prefixed by "sc")

https://experienceleague.adobe.com/en/docs/analytics/implementation/vars/page-vars/events/events-ove...

There is one thing that will / can prevent the purchase event from counting, and that is a duplicated "purchaseID".

If not purchaseID is provided at the time of the purchase, then Adobe will create it's own temporary purchase id based on the Hit.

Or you could set your own purchaseID, this is typically tied to your system transaction id (but be aware, only the first 20 characters are used... I have been asking for this to be improved for a while, since most transaction ids are GUIDs now, and definitely exceed that character limit)

Basically, if the "temporary purchaseID" matches one of the last 5 values, or the set purchaseID matches any past ID, then the purchase won't be tracked, so as to not inflate your purchase and revenue numbers.

However, you are not obligated to pass payment information to Adobe, or you can opt to track payment information in your own custom tracking (and not use Adobe's Revenue metric).

[EurosIMS]

Ah yes- I still think of it as scPurchase! As a quick addtion here though (in case this starts showing up in Google searches) you are correct that it's not required, however I think that using scPurchase is still backwards compatible with App Measurement, so if someone was to come across an old implementation with scPurchase it should still function as intended even though it's no longer needed- it shouldn't prevent Orders from incrementing. 

[Jennifer_Dungan]

Hahah fair enough, I never used "scPurchase"...  it would be nice if the documentation would address if it is still compatible... but likely, since old s_code is still compatible.