PurchaseID variable showing in adobe cloud debugger but not in adobe analytics workspace report | Community
Skip to main content
M
MaheshKo1
Level 2
July 9, 2024
Question

PurchaseID variable showing in adobe cloud debugger but not in adobe analytics workspace report

  • July 9, 2024
  • 1 reply
  • 4639 views

Hi Experts,

 

We have an SAP where we track all our online e-commerce purchases with Purchase ID / Transaction ID directly from the website and at the same time we track all purchases in Adobe Analytics as well with the same Purchase ID.

From last month when we compare the transaction IDs of Adobe Analytics with the transaction IDs captured in SAP the Adobe numbers are way less which means many Purchase IDs are missing in Adobe.

After placing several orders, the Transaction ID/Purchase ID is captured in the Adobe Cloud Debugger, but after 3-4 hours when checking in the Analytics workspace, then it's not showing.

 

Not getting where the issue is.

Please find the below code snippet and the screenshots for your reference.

 

Looking for a positive revert.

Thanks in Advance.

 

s.linkTrackVars = "products,events,eVar1,eVar2,eVar4,eVar8,eVar10,eVar11,eVar12,prop1,prop2,prop10,prop11,prop12,eVar30,eVar24,eVar55,eVar27,eVar33,eVar35,eVar36,eVar39,eVar43,eVar48,eVar37,eVar58,eVar59,eVar60,eVar66,eVar91";

 

s.purchaseID = s.eVar43 = digitalData.purchase ? digitalData.purchase.ecommerce.purchaseId : $(".c-reciept-page__id").text();

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

1 reply

M
MaheshKo1Author
Level 2
July 9, 2024

@yuhuisg @jennifer_dungan @gigazelle Please suggest.

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
July 9, 2024

Hmm everything there looks correct... 

 

The only thing I can think of is that you might have a processing rule or VISTA rule removing eVar43?

 

VISTA rules are less likely (since you need Adobe Engineers to set those up at a cost, so most people don't use them), but can you check your processing rules for your suite?

M
MaheshKo1Author
Level 2
July 23, 2024

purchaseID is a dimension, and on actions all the dimensions that Adobe will pass need to be specified in the linkTrackVar....

 

This goes back to the original way that Adobe was coded (before there were "clear vars"

 

Basically, let's say you loaded a page with:

props 1-5

eVars 1-6

list1

event1

along with your standard page name, server, channel, etc

 

Then you created a click action, in most case, you do not want to send all of the above with that action, but you wanted a subset of the above in addition to eVar7 and event2

 

So you would have to specify ALL the dimensions and events on the action...

s.linkTrackVars = "prop2,prop5,eVar3,eVar6,eVar7"

and

s.linkTrackEvent = "event2"

 

Everything NOT listed in the above would not be sent.

 

So again, no "purchaseID" in the list, it would not be sent...

 


Your custom eVar43 is not being used for deduplication on your orders... Adobe uses purchaseID for this, it cannot be changed:

 

Ironically, purchaseID is one of those "deep data fields", it doesn't surface in Workspace at all... so you need your eVar43 for reporting, and your purchaseID to deduplicate the Orders....  purchaseID is available in the Raw Data feeds... but that's not helpful if you aren't using those....

 

 

However, if no purchase id is passed, Adobe is supposed to generate one, but depending on what is being passed, it may have created an identical ID and thus treated the purchase as a duplicate and removed it?

https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-23145#:~:text=The%20system%20mandates%20a%20purchase,lists%20imply%20the%20same%20purchase.


@jennifer_dungan Still some of the purchase IDs were missing when we compared last week's data with the SAP data.

 

Is there anything else need to look at?

Terms & ConditionsAccessibility statement

Loading footer...