Main issue: A custom pixel listening to checkout_completed only receives order.id, not order.name. The team needs order.name to match return partners’ references and requests Shopify include this field in the event payload.
Proposed workaround: Use order.id to query the Admin GraphQL Orders API to retrieve order.name. This requires an app and API key for authenticated calls; the Admin API cannot be called directly from a pixel.
Current blocker: While attempting to implement an App Pixel, the team cannot get the web pixel app extension to update during development/deploys. They reference a prior community report about pixels not updating automatically on deploy and ask for an official update and any available workarounds.
Status and open questions:
No commitment to add order.name to checkout_completed was provided.
The suggested API-based workaround is acknowledged but depends on app credentials.
Pixel update/deploy issue remains unresolved; the team is blocked from migrating checkout scripts to pixels.
Key terms:
App Pixel: A web pixel delivered via an app extension.
Admin GraphQL API: Shopify’s authenticated API for store data (e.g., orders).
We’re trying to migrate our custom checkout script to use a custom pixel, but we’re missing some key information.
We’re using the checkout_completed event and need the order.name at this point. All we get on the object is the order.id.
We’d like to put in a request to add this missing data. Without this information, the order names that our return partners are passing us cannot be correlated to the orders.
Thanks for the response. I figured that might be a solution, but if i understand it correctly, we’d need an app (or our partner to give us an API key) and then we’d have to call the API for each order? We can’t just call the admin API from a pixel can we?
We’re trying to roll this into an App Pixel, but we’re stuck unable to update the pixel during development. We came across this other issue, which aligns with what we’re seeing