The Disappearing Conversions: A Tracking Code Mystery
A retail client reports that their 'Purchase' conversion has dropped by 40% over the last two weeks, while their analytics traffic reports show a 10% increase in overall site visits. The implementation uses Adobe Experience Platform Launch (Launch) with a single rule that fires the purchase event on the order confirmation page. The rule uses a custom script to read the order ID from the page's data layer. The client's IT team recently deployed a new front-end framework that changed the timing of when the data layer is populated. The analytics team has not changed any tagging. The client is concerned that the drop is due to a real decline in sales and wants to pause all marketing campaigns.
1. What is the most likely cause of the drop in purchase conversions, and what immediate diagnostic steps should you take?
Read the worked answer
The most likely cause is a data collection issue, not a real sales decline. The timing change in the data layer population means the Launch rule may be firing before the order ID is available, resulting in the purchase event not being sent or being sent without the order ID. Immediate diagnostic steps: 1) Use the Adobe Experience Platform Debugger to inspect the purchase event on the confirmation page and verify if the 'purchase' event is firing and if the order ID is populated. 2) Check the Launch rule's trigger and conditions; if it fires on page load, it may need to be changed to fire on a data layer event (e.g., a custom event) or use a delay. 3) Compare the number of order confirmation page views (from a page view rule) to purchase events to see the gap. 4) Review the browser console for JavaScript errors. 5) Check the Adobe Analytics real-time report for the purchase event to see if it's still firing at all. Do not pause campaigns until you confirm whether the drop is real; the traffic increase suggests the issue is tracking-related.
2. How would you adjust the implementation to be more resilient to future data layer timing changes?
Read the worked answer
To make the implementation more resilient: 1) Modify the Launch rule to trigger on a custom data layer event (e.g., 'orderComplete') that the front-end fires after the data layer is fully populated, rather than on page load. 2) Use a data element with a fallback mechanism (e.g., check for the order ID in multiple locations) and set a default value. 3) Implement a 'data layer ready' flag and have the rule wait for it. 4) Add error handling and logging to capture when the order ID is missing. 5) Consider using Adobe's Web SDK with a schema that enforces data structure. 6) Document the data layer contract with the IT team to ensure future changes are communicated. 7) Set up alerts in Adobe Analytics for sudden drops in key events.