Adobe Analytics Ghost Transactions

[Rafael_Sahagun]

Hello,

We are seeing transactions in AA that aren't in the back end system, about 60% aren't registered in the tool that actually charges for the orders.

Can you think of reasons why?

The transaction IDs that are captured in both the back end system and AA have a match of 96%.

Thanks,

Rafael

[Rafael_Sahagun]

Building a report showing transaction IDs and selecting one, looks like the same ID is being used from dates 6 months apart.

[Rafael_Sahagun]

But the count of those transactions with 2 dates is not more than 140, so although it can be part of the issue, there could be something else adding to it.

[PoornimaThakur5]

Hello @Rafael_Sahagun,

The discrepancy between transactions in Adobe Analytics and your backend system could stem from several issues, most notably duplicate or reused transaction IDs as you've seen, some IDs appear months apart, which can inflate AA's transaction count if not properly deduplicated.
Additionally, AA tracks data client-side, so transactions may be recorded if the purchase confirmation page is triggered before payment is completed or if users abandon the process after the beacon fires, while the backend only logs finalized orders. Test orders, bot activity, or tracking from development environments can also inflate AA numbers if not excluded.
Lastly, delayed or batched hits from apps or unstable connections can cause timestamp mismatches, making it appear that the same transaction occurred on multiple dates, further complicating reconciliation.

So, I would do all the above checks to narrow down on the issue.