Open GTM and add eventID: (select variable for the transaction ID) Add the event_id to the Facebook Purchase GTM eventįor Facebook we need to add in the event_id in the pixel event that is fired on the clientside. ? info "Note: For Facebook we need to add in the eventID in the pixel event that is fired on the clientside. Set up your Facebook Conversion API connection Meaning that without consent of the user, TraceDock will not send over data of that particular user to Facebook. Thus, according to GDPR, you need prior consent from your user, to send over data to the Facebook Conversions API. This means that the data TraceDock sends over is always stitched to a user. In opposite to Google Analytics, Facebook does not allow parties to send over anonymous user data. Why do I have to declare that Facebook is only loaded in with proper consent?
4SHADOW ANALYTICS HOW TO
How to analyse this data in Google Analyticsĭata is stitched with the browser session and forwarded to Google Analytics. This ID can be found in the admin section of your Google AnalyticsĪnd starts with "UA-". You have to add your Google Analytics Property ID. If you didn't do this already during the configuration of our First-party data collection service, Step 1: Forward data to Google Analytics and Facebook Send data to Google Analytics Set up an identify event that runs in the browserĬonnect the server-side event that is setup from your backend On this page you will find instructions how to:įorward data to Google Analytics and Facebook Thus reducing the measurement difference you experience between your backend, and the revenue you measure in TraceDock's Server-side transaction tracking is designed to reduce this measurement error.Īll configured server-side events will be connected to a client session and be forwarded to Google Analytics and Facebook.
IOS 14.5 update: broken customer journeys iOS 14.5 update: Default and in-app Safari browser are analyzed as two different browsersĬonsequence: revenue is attributed to the Thank you page, not to the correct (paid) campaign iPhone visitors start the purchase process in an app (via in-app Safari browser), but are redirected to the default Safari browser after the payment.Visitors start the purchase process in a browser they chose to use on their device, but are redirected to the device's default browser after the payment.
When they close it because the loading time takes too long When they don't open the Thank you page at all
In Google Analytics and Facebook, current Ecommerce transactions rely on client-side events on 'Thank you pages' which results in measurement differences in revenue - and thus broken customer journeys - when:
0 kommentar(er)
