A wishlist purchase was not attributed

A precise connection between interest and purchase

GoScript Advanced Wishlist WordPress Plugin for WooCommerce attributes qualifying purchases when the same account that actively saved a product completes a paid WooCommerce order containing that product. This gives your reports a more trustworthy connection between customer interest and purchase outcomes.

1. Check the qualification path

For a new attribution record to be created, several parts of the customer journey need to line up at the time the order first qualifies as paid.

Same customer accountThe WooCommerce order must belong to the signed-in customer account that saved the product.

Active saved interestThat customer must still have active saved-product interest for the purchased product when the order first qualifies.

Qualifying paid statusThe order needs a WooCommerce paid status and a paid date before it can contribute a wishlist purchase outcome.

Matching parent productOrder items are matched at the product level; a purchased variation is evaluated against its parent product’s active wishlist interest.

2. Common reasons a purchase does not qualify

When an order does not appear as a wishlist purchase, work through these checks in order. Each one describes a precise requirement of the attribution model.

• The order was placed as a guest or under a different WooCommerce customer account from the one that saved the product.
• The product was not actively saved by that customer when the order first reached a paid status.
• The customer removed their final saved reference to the product before the order qualified as paid.
• The order has not reached a WooCommerce paid status or does not have a paid date yet.
• The purchased product does not match the saved product’s parent-product identity.
• The order’s paid date is outside the active 180-day analytics retention window.

3. Check the report view before diagnosing the order

Sometimes the attribution is present but the report view is too narrow to show it. Start with a broader reporting context before changing customer or order data.

1. Open Advanced Wishlist → Reports.
2. Choose a period that includes the order’s paid date-use a broader 30- or 90-day view when needed.
3. Clear Product, Category, and Tag filters to view all matching products.
4. Review the Wishlist Purchases and Attributed Revenue totals, then check the All Products rows.
5. Filter to the relevant product only after confirming the broader view.

4. Run a clean attribution test

A controlled test is the fastest way to validate your store’s complete wishlist-to-purchase path.

1. Create or use a test WooCommerce customer account and sign in.
2. Save a published product to My Wishlist, then confirm it remains in the customer’s wishlist.
3. Add that same product to the cart while using the same customer account.
4. Complete a real qualifying paid order through your normal WooCommerce payment flow.
5. Open the Advanced Wishlist reports and review the reporting period containing the order’s paid date.

5. Understand refund-aware reconciliation

Attribution is reconciled when an order’s payment status or refund state changes. That helps the reports stay aligned with the actual qualifying product outcome rather than leaving a stale contribution behind.

• Changes to an order’s paid status trigger a reconciliation check.
• Order refunds and deleted refunds also trigger reconciliation.
• Attributed revenue uses the product contribution after item-level refunds, not shipping or tax.
• A fully non-qualifying order state can remove the purchase contribution from the reporting summary.
• Use the final order and refund state when reviewing whether a particular purchase should be represented in reports.

Use attribution as a stronger store signal

Precise attribution makes the insight more valuable. By following the same account from active saved interest to a qualifying paid order, Advanced Wishlist gives your store a stronger way to see which wishlist demand is progressing into real purchase outcomes.