{"section":"known-issues","requestedLocale":"en","requestedSlug":"duplicate-transactions-being-recorded-in-google-analytics","locale":"en","slug":"duplicate-transactions-being-recorded-in-google-analytics","path":"docs/en/known-issues/Post-purchase/duplicate-transactions-being-recorded-in-google-analytics.md","branch":"main","content":"## Summary\n\nTransactions are recorded in Google Analytics based on the confirmed order page (_orderPlaced_). When the customer reaches the page an event is sent to the _Data Layer_, so Google Tag Manager captures this event and triggers the Google Analytics script.\n\nIf the customer visits this page over and over again, or even if they reload/update the page, the event is triggered and the data is re-sent to Google Analytics, creating repeated information.\n\n## Simulation\n\n1. Complete an purchase in the store;\n2. Access the placed order page repeatedly;\n3. Note that these multiple hits have been recorded as completed orders in Google Analytics.\n\n## Workaround\n\nThere is no workaround for this type of integration.\n\nOne possibility is to avoid integrating frontend transactions with GTM/Javascript. Instead, work with a backend integration (middleware) between VTEX order APIs and the Google Analytics transaction APIs."}