CoreXUpload Print for WooCommerce
This page explains how CoreXUpload Print works with WooCommerce from a merchant perspective: the customer journey, who owns order data, when purchase tracking fires, and what attribution information is available.
Order flow
A typical Upload Print purchase follows this path:
Customer opens Upload Print on a product page
→ uploads artwork and configures print options
→ adds the configured item to the Woo cart
→ completes Woo checkout
→ Woo creates the order
→ payment is captured or confirmed
→ Woo marks the order paid
→ confirmed purchase event is available to your analytics setupUpload Print runs on the product page in the same browser session as your WordPress store. The configured item is added through WooCommerce’s cart. Checkout, payment gateways, and the order-received page are standard Woo flows.
WooCommerce remains authoritative
WooCommerce owns the commercial truth for every order, including Upload Print orders:
- Final order totals
- Coupons and discounts
- Tax and shipping
- Payment state and paid date
- Refunds and order lifecycle
CoreXUpload Print observes the final Woo order when reporting a paid purchase for analytics. It does not recalculate discounts, tax, or shipping for conversion reporting.
If you change an order in Woo admin (coupons, line adjustments, status), analytics should follow whatever Woo recorded at the time the purchase event is emitted on the thank-you page.
Paid-order behaviour
CoreXUpload Print reports a purchase only after WooCommerce considers the order paid.
- Submitting checkout or creating an unpaid order does not count as a purchase conversion.
- Orders that become paid later — for example moving from a pending payment status to a paid status — are supported. Reporting runs when Woo’s paid state is satisfied.
Only orders that include at least one Upload Print line item qualify. Regular Woo orders without Upload Print configuration are not reported through this mechanism.
Technical note
Payment confirmation is guarded by WooCommerce’s own paid-order state (paid flag and paid date). CoreXUpload Print does not treat checkout submission or order creation as payment completion.
Order attribution
CoreXUpload Print reuses WooCommerce Order Attribution. It does not create a second attribution cookie, session model, or parallel attribution storage.
When Woo has stored attribution on the order, the purchase payload may include fields such as:
| Field | Typical meaning |
|---|---|
| source | Traffic source (for example UTM source) |
| medium | Marketing medium |
| campaign | Campaign name |
| content | Ad or content variant |
| term | Search or keyword term |
| referrer | Referring URL where captured |
| session entry | Landing or session entry page |
| source type | Woo’s classification of the source |
Only values already present on the Woo order are forwarded. Missing fields are omitted — CoreXUpload Print does not invent “direct” or “unknown” attribution.
Attribution depends on WooCommerce’s Order Attribution feature and your site’s tagging setup. Campaign parameters must reach Woo’s order record for them to appear in the purchase event.
Google click IDs
Google Ads click identifiers (such as gclid) are not documented here as a verified live behaviour. UTM-based campaign attribution through Woo Order Attribution is the supported, verified path today.
Privacy
Purchase analytics for Upload Print do not include:
- Customer name, email, phone, or postal address
- Uploaded artwork, filenames, or file URLs
- Thumbnails or storage paths
- Payment or card information
Reported data is limited to commerce and campaign fields suitable for conversion measurement — for example transaction ID, currency, merchandise revenue, tax, shipping, product identifiers, and Woo attribution fields listed above.