Orders tracking incremental due to page refresh

Avatar

Avatar
Level 1
ishank_tewari
Level 1

Likes

0 likes

Total Posts

3 posts

Correct reply

0 solutions
View profile

Avatar
Level 1
ishank_tewari
Level 1

Likes

0 likes

Total Posts

3 posts

Correct reply

0 solutions
View profile
ishank_tewari
Level 1

11-11-2020

Hi All,

 

We are facing issues in some transactions where a user might have refreshed the page after successful payment multiple times because of which we are observing more number of orders whereas the actual orders are lesser.

 

Request someone to please suggest a resolution to this issue?

Thanks in advance, will be great help.

Accepted Solutions (0)

Answers (2)

Answers (2)

Avatar

Avatar
Boost 25
Level 3
amgup
Level 3

Likes

26 likes

Total Posts

132 posts

Correct reply

16 solutions
Top badges earned
Boost 25
Affirm 10
Boost 5
Boost 3
Boost 10
View profile

Avatar
Boost 25
Level 3
amgup
Level 3

Likes

26 likes

Total Posts

132 posts

Correct reply

16 solutions
Top badges earned
Boost 25
Affirm 10
Boost 5
Boost 3
Boost 10
View profile
amgup
Level 3

23-11-2020

Hello @ishank_tewari 
I will suggest to use event serialization as it prevents de-duplication of event. For more information you can check this link :- https://experienceleague.adobe.com/docs/analytics/implementation/vars/page-vars/events/event-seriali...

Avatar

Avatar
Seeker
Level 3
jkm-disco
Level 3

Likes

24 likes

Total Posts

130 posts

Correct reply

15 solutions
Top badges earned
Seeker
Contributor
Shape 1
Give Back
Affirm 10
View profile

Avatar
Seeker
Level 3
jkm-disco
Level 3

Likes

24 likes

Total Posts

130 posts

Correct reply

15 solutions
Top badges earned
Seeker
Contributor
Shape 1
Give Back
Affirm 10
View profile
jkm-disco
Level 3

12-11-2020

Hi @ishank_tewari ,

 

It sounds like you may want to add/interact with some development logic on the page to make it clear when a page load corresponds to the actual transaction.

As an example, there may be logic on the previous page which determines whether a transaction is successful and routes users to the new page. Using the logic of a successful payment on the previous page, one solution would be to temporarily set a flag in the client's local storage which is read and removed on the successful payment page. Then on a refresh, it would no longer find the flag in local storage and wouldn't set the custom event.

 

Actually, the solution on your duplicate post, here, seems sufficient as long as there aren't any other custom events being set at the same time.

 

This question may be more appropriate to ask in the Launch sub forum.

 

All the best,

J