What improvements can be made to custom pixel migration?

[StrutFitJake]

Hi,

Our app uses custom pixel code to get order data into our system. Our customers, who have Shopify sites, currently add the code to the Additional Scripts section in the Checkout settings. 

I have looked at migrating the code to the new Custom Pixel system. I have noticed that there are a few features missing from the new method of handling Pixels that means we cannot get all the data that we currently get in Additional Scripts.

• We have limited access to properties on objects (such as checkout and order) compared to in Additional Scripts. Is there a reason that we can't access common properties such as the Order Name/Number? 
• We cannot access IndexedDB. I see there are methods to access local storage, that we also use, but our app uses IndexedDB to track some user actions while they are shopping that we want to record on checkout completion. Is there a plan to add an API to securely access IndexedDB, similar to local storage, in the future? 
• Similar to the first point, properties on product variants is limited, so sometimes we won't be able to get the size purchased depending on how the Shopify site organizes their variant data. The liquid objects we have access to in the Additional Scripts is much more complete, and we wonder if these properties will eventually be available in the new system. 

Overall, I guess I'm just wondering if we could get more visibility on the developer roadmap for Pixel support. This might not be the best place for this query either, so if there's another place I should be sending this, I would love to know. 

[Small_Task_Help]

Hi,

Use Google Tag manager

[StrutFitJake]

Our current solution works in Additional Scripts. I'm not exactly sure how using Google Tag Manager would address the points I raised in a Custom Pixel. If you could provide more details as to how Google Tag Manager solves those problems, that would be appreciated.