Order Confirmation page with NO s.purchaseID | Community
Skip to main content
O
Olivier_Blonste
Level 2
July 26, 2016
Solved

Order Confirmation page with NO s.purchaseID

  • July 26, 2016
  • 2 replies
  • 6854 views

Hi experts,

I would like some clarification regarding the order confirmation page when we do NOT use s.purchaseID.
I found the below in the latest adobe analytics implementation manual (7/19/2016) page 233:

"If a purchase event is called without a purchaseID, a unique one is automatically generated based on the s.products and s.events
variables. This automatically generated purchaseID is stored locally as a cookie value within the visitor's browser, and is not sent
to any report suite tables. Manually defined purchaseIDs on the other hand are sent to a back-end table within the report suite.
The last five purchases made by a visitor (with or without purchaseID) are stored in the local cookie." 

As said, even though we do not use s.purchaseID (I know it's wrong and we will fix that), some legit orders are missing. I suspect the logic described in the manual above might be the reason.
I completely understand the logic but would like to troubleshoot the issue/behavior and have a few more questions:

1. What is the name of the cookie that will automatically generate a purchaseID when s.purchaseID is not set?
2. This ID is based on s.products and s.events. Could you please be more specific and give me an example of automated purchaseID that will be generated based on s.products and s.events?
For instance, if s.products=";shoe;1;19.99" and s.events="event9,purchase", what is the value generated for the automatic purchaseID?
3. For some reasons, my client is not passing any value for the product name or sku for the s.products variable (ex: s.products=";;1;19.99). The actual product name is passed in an eVar...I realize I'm missing out by doing it this way but that's another topic and battle :-)
Do you think this way of doing (no product sku in s.products) would impact the generation of this automated purchaseID, given that it's based on s.products and s.events?

Thanks much for your help, I'm eager to read your responses!
Regards,
Olivier

 

 

 

 

 

 

 

 

 

 

If a purchase event is called without a purchaseID, a unique one is automatically generated based on the s.products and s.events
variables. This automatically generated purchaseID is stored locally as a cookie value within the visitor's browser, and is not sent
to any report suite tables. Manually defined purchaseIDs on the other hand are sent to a back-end table within the report suite.
The last five purchases made by a visitor (with or without purchaseID) are stored in the local cookie.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Gigazelle

Hey there, I know this is an old thread but I wanted to make sure that you're aware that the implementation guide has since been updated around duplicate purchases.

https://docs.adobe.com/content/help/en/analytics/implementation/vars/page-vars/events/event-purchase.html

So, to answer your questions:

  1. There is no cookie
  2. The duplicate purchase is based on information in the hit, and this data is stored by Adobe for each unique visitor.
  3. This isn't a question, so I'm afraid I can't directly answer it.

2 replies

brettk4969641
brettk4969641
August 16, 2016

I am also having this issue but I am having my Transaction ID stored as an eVar so I know that that transaction is happening. The s.purchase event is not firing about 1/3 of the time but the value is being saved as the eVar. Is it possible that this "local cookie" is causing the conversion / success event to not be counted? According to the implementation guide... 

When a visitor makes any purchase, the following checks are made:

  • Does the purchaseID match any of the five cookie values? If so, the image request is considered a duplicate purchase. All conversion variables, including the purchase event, do not appear in reporting.

I am trying to locate this cookie to determine if that is the reason the s.purchase event is not firing.

A
anjalithomas-28
June 24, 2021
Hello, i know this is late but, did you happen to figure out the solution to the above mentioned problem?
Gigazelle
Adobe Employee
GigazelleAdobe EmployeeAccepted solution
Adobe Employee
March 6, 2020

Hey there, I know this is an old thread but I wanted to make sure that you're aware that the implementation guide has since been updated around duplicate purchases.

https://docs.adobe.com/content/help/en/analytics/implementation/vars/page-vars/events/event-purchase.html

So, to answer your questions:

  1. There is no cookie
  2. The duplicate purchase is based on information in the hit, and this data is stored by Adobe for each unique visitor.
  3. This isn't a question, so I'm afraid I can't directly answer it.
Terms & ConditionsAccessibility statement

Loading footer...