The issue arises because the activated segment in Marketing Cloud contains orders older than 30 days, despite the segment being defined to include only recent orders. The best solution is to apply a filter to the Purchase Order Date to exclude older orders. Here’s why:
Understanding the Issue
The segment includes related attributes from the purchase order data.
Despite filtering for orders placed in the last 30 days, older orders are appearing in the activation.
Why Apply a Filter to Purchase Order Date?
Root Cause :
The related attributes (e.g., purchase order details) may not be filtered by the same criteria as the segment.
Without a specific filter on the Purchase Order Date , older orders may inadvertently be included.
Solution Approach :
Applying a filter directly to the Purchase Order Date ensures that only orders within the desired timeframe are included in the activation.
Other Options Are Less Suitable :
A. Use data graphs that contain only 30 days of data : Data graphs are not typically used to filter data for activations.
B. Apply a data space filter to exclude orders older than 30 days : Data space filters apply globally and may unintentionally affect other use cases.
D. Use SQL in Marketing Cloud Engagement to remove orders older than 30 days : This is a reactive approach and does not address the root cause in Data Cloud.
Steps to Resolve the Issue
Step 1: Review the Segment Definition
Confirm that the segment filters for orders placed in the last 30 days.
Step 2: Add a Filter to Purchase Order Date
Modify the activation configuration to include a filter on the Purchase Order Date , ensuring only orders within the last 30 days are included.
Step 3: Test the Activation
Publish the segment again and verify that the activation in Marketing Cloud contains only the desired orders.
Conclusion
By applying a filter to the Purchase Order Date , the consultant ensures that only orders placed in the last 30 days are included in the activation, resolving the issue effectively.