Missing cart additions

[jantzen_belliston-Adobe]

Some cart additions are not showing up in analytics. I have several triggers for the add to cart page view and one of them is not showing up. The call looks identical in the debugger, apart from a single evar value in the products string (eVar42=quickview instead of eVar42=yes or eVar42=no or evar42=variant), and the network shows it going to the same Adobe server. I'm at a loss for how to debug this. Any pointers?

The Only difference I can see is that the page views with eVar42 for a particular value just don't seem to register.

Thanks

[jantzen_belliston-Adobe]

Do any of the answers below answer your initial question? If so, can you select one of them as the correct answer? If none of the answers already provided answer your question, can you provide additional information to better help the community solve your question?

[nxdevn78913286 · Accepted solution]

Verify that your s.products string has been formatted correctly. See the examples at products | Adobe Analytics.

[nxdevn78913286 · Accepted solution]

...

[nxdevn78913286 · Accepted solution]

Please ignore this comment

[nxdevn78913286 · Accepted solution]

Thanks for the reply

This one works -

;87215078;;;event11=8.63;eVar15=welcome_topn|eVar32=No|eVar33=No|eVar34=Yes|eVar35=No|eVar66=Available stock shown|eVar38=None/Natural Add|eVar41=Yes|eVar42=No

This one doesn't

;87215078;;;event11=8.63;eVar15=welcome_topn|eVar32=No|eVar33=No|eVar34=Yes|eVar35=No|eVar66=Available stock shown|eVar38=None/Natural Add|eVar41=Yes|eVar42=quickview

I can't see what would make any difference.

[yuhuisg · Accepted solution]

Do you have any Processing Rules that apply to eVar42?

[nxdevn78913286 · Accepted solution]

No, There are no processing rules set up at all.

[yuhuisg · Accepted solution]

Working the other way around, start with a table that uses eVar42 as the dimension and Occurrences as the metric. Do you see "quickview" as a value?

[nxdevn78913286 · Accepted solution]

No, it doesn't appear as a value. The other 4 possibilities do.

[yuhuisg · Accepted solution]

in your report suite's setting for eVar42, what are the Allocation and Expire After settings?

[nxdevn78913286 · Accepted solution]

Allocation is 'Original Value(first)' and Expire After is 'Visit'

[yuhuisg · Accepted solution]

Interesting that Allocation is "Original Value (First)". In your implementation, is it possible that eVar42=quickview is always sent in hits that are after hits where eVar42=something else ?

E.g.

Hit 1 = ...

Hit 2 = ..., s.products = ";87215078;;;event11=8.63;eVar15=welcome_topn|eVar32=No|eVar33=No|eVar34=Yes|eVar35=No|eVar66=Available stock shown|eVar38=None/Natural Add|eVar41=Yes|eVar42=No"

Hit 3 = ...

Hit 4 = ...

Hit 5 = ..., s.products = ";87215078;;;event11=8.63;eVar15=welcome_topn|eVar32=No|eVar33=No|eVar34=Yes|eVar35=No|eVar66=Available stock shown|eVar38=None/Natural Add|eVar41=Yes|eVar42=quickview"

Hit 6 = ...

Because if that is the case, then AA is only reporting the value of eVar42 that it first received in the visit, i.e. from Hit 2 in my example. All subsequent values from that visit, e.g. from Hit 5, though tracked, are never reported.

[nxdevn78913286 · Accepted solution]

Yes, I think that's probably it. I will see if I can tweak it to fgive us what we want. It seems to me that it should maybe expire on Cart Add instead of by visit. I'll need to talk to the suite owner before I change it. Thanks very much for your assistance.

[yuhuisg · Accepted solution]

Alternatively, if you're brave enough, you could use "Linear" allocation too https://experienceleague.adobe.com/docs/analytics/admin/admin-tools/conversion-variables/conversion-...