Purchase completed hits missed in reports | Community
Skip to main content
OscarMartinezM
OscarMartinezM
Level 3
February 6, 2023
Solved

Purchase completed hits missed in reports

  • February 6, 2023
  • 3 replies
  • 1823 views

Hi community,

I have some days dealing with an issue and I haven't get a clue what is wrong. We have a site having purchase process. All process events are tracked, but the  last step when user completes the purchase is not reflecting in reports. This is an example of working Payload (reflected in reports) and an non-working Payload.

 

Working Payload

AQB: 1
ndh: 1
pf: 1
t: 5/1/2023 23:15:22 0 360
mid: xxxxxxxxxxxxxxxx
aamlh: 7
ce: UTF-8
cdp: 2
pageName: commerce-test.site.com>cart
g: https://commerce-test.site.com/cart
cc: USD
events: scView,scAdd
products: material;oscar test-2 1.4;3
v2: commerce-test.site.com/cart
v3: D=pageName
c23: commerce-test.site.com/cart
c26: internal
v45: dfb6b95c-2fb4-4077-a08b-9ff3faf0025c-1675454489174
v46: GRV
c56: D=pageName
v59: material order|cart addition
v61: IN HCP Dev Portal
c62: D=v59
v65: IN
c67: IN
v70: 2.20.0
v72: D=c26
pe: lnk_o
pev2: material order|cart addition
s: 3440x1440
c: 24
j: 1.6
v: N
k: Y
bw: 1720
bh: 1304
mcorgid: xxxxxxxxx@AdobeOrg
lrt: 317
AQE: 1

 

Non-Working Payload

AQB: 1
ndh: 1
pf: 1
t: 5/1/2023 23:15:20 0 360
mid: xxxxxxxxxxxxxxxx
aamlh: 7
ce: UTF-8
cdp: 2
pageName: commerce-test.site.com>cart
g: https://commerce-test.site.com/cart
cc: USD
purchaseID: 1e05e256-10ac-427c-8018-95d160f95a3d
events: purchase
products: material;oscar test-2 1.3;1
v2: commerce-test.site.com/cart
v3: D=pageName
c23: commerce-test.site.com/cart
c26: internal
v43: 1e05e256-10ac-427c-8018-95d160f95a3d
v45: dfb6b95c-2fb4-4077-a08b-9ff3faf0025c-1675454489174
v46: GRV
c56: D=pageName
v59: material order|completed
v61: IN HCP Dev Portal
c62: D=v59
v65: IN
c67: IN
v70: 2.20.0
v72: D=c26
pe: lnk_o
pev2: material order|completed
s: 3440x1440
c: 24
j: 1.6
v: N
k: Y
bw: 1720
bh: 1304
mcorgid: xxxxxxxxx@AdobeOrg
lrt: 105
AQE: 1

 

Thank you,

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 yuhuisg

There are 2 things that stood out to me in your "purchase" hit:

  1. purchaseID is "1e05e256-10ac-427c-8018-95d160f95a3d". That ID is 36 characters in length. But purchaseID can only accept up to 20 bytes, or 20 alphanumeric characters. (Ref: https://experienceleague.adobe.com/docs/analytics/implementation/vars/page-vars/purchaseid.html?lang=en#s.purchaseid-in-appmeasurement-and-the-analytics-extension-custom-code-editor) As a result, AA is only able to track your purchaseID as "1e05e256-10ac-427c-8". So there is a possibility of collision with earlier purchases that could have the same 20-character string.
  2. products is "material;oscar test-2 1.3;1". There is no price value in this string. I'm not sure if that's an error or not. Also, I think omitting the price from the string should not be an issue. Nonetheless, I suggest that you make your string to be complete with the price, e.g. "material;oscar test-2 1.3;1;0.00".

3 replies

VaniBhemarasetty
Adobe Employee
VaniBhemarasettyAdobe Employee
Adobe Employee
February 6, 2023

Hi @oscarmartinezm , Sometimes, even though a server call fires, It does not guarantee the data to be accepted at the server end, the hit can get excluded at the server end, because of various reasons.

 

The best way to debug is to use data feeds and run for the specific day and see post columns, like post_event_list and post_event_list should contain the "1" in them. "1" indicates that the hit is a purchase hit, if the post_event_list does not contain 1 that means, the server has excluded that purchase. Please check for duplicate purchases, prouduct_list columns

Here is my blog where I put in some tips to debug using data feeds

http://bitly.ws/zUBb

 

For further assistance you can reach out to client care for help and in-depth assistance in debugging the issue

 

    Pablo_Childe
    Community Advisor
    Pablo_ChildeCommunity Advisor
    Community Advisor
    February 6, 2023

    Hi so your 2 beacons are a bit different and at different stages of purchase flow.

     

    Beacon one is pretty easy looks good.

     

    What makes me suspicious Beacon 2, I am wondering how are you creating a purchase event/transaction on the same page?

     

    I would expect once cart add is done you then have user process the transaction and complete on a sort of confirmation page. What type of page /app is it angular or some SPA type of app? Might be you have rules that don`t update correctly as you haven`t got a confirmation page working as expected.(not that you must have a confirmation page but seems odd).

     

     

     

      yuhuisg
      Community Advisor
      yuhuisgCommunity AdvisorAccepted solution
      Community Advisor
      February 6, 2023

      There are 2 things that stood out to me in your "purchase" hit:

      1. purchaseID is "1e05e256-10ac-427c-8018-95d160f95a3d". That ID is 36 characters in length. But purchaseID can only accept up to 20 bytes, or 20 alphanumeric characters. (Ref: https://experienceleague.adobe.com/docs/analytics/implementation/vars/page-vars/purchaseid.html?lang=en#s.purchaseid-in-appmeasurement-and-the-analytics-extension-custom-code-editor) As a result, AA is only able to track your purchaseID as "1e05e256-10ac-427c-8". So there is a possibility of collision with earlier purchases that could have the same 20-character string.
      2. products is "material;oscar test-2 1.3;1". There is no price value in this string. I'm not sure if that's an error or not. Also, I think omitting the price from the string should not be an issue. Nonetheless, I suggest that you make your string to be complete with the price, e.g. "material;oscar test-2 1.3;1;0.00".
        OscarMartinezM
        OscarMartinezMAuthor
        Level 3
        February 6, 2023

        Thank you for your response.

        I just sent some test adding price and truncating purchaseID to only 20 chars and creating a new ID. I will wait some hours for data reflected in Adobe.

        The interesting is it seems whole request is ignored. I mean, if I search for eVar59, I don't find the value "material order|completed". So, we are not missing only the purchase. We're missing whole hit.

        Terms & ConditionsAccessibility statement

        Loading footer...