Hey @sebastienpowell
This is an interesting one. The Facebook & Instagram by Meta app is actually developed by Meta themselves so we wouldn’t have the ability to extend its functionality to include additional custom properties like the vendor field.
Your best path forward is to submit this feature request directly through the app in your Shopify admin. Click on the support option within the Meta app, select the pixel topic, and you can provide this feedback directly to Meta’s support team.
Hi Kyle,
Thank you for getting back to me so quickly! I’ll give that a go. In the event they’re not able to support this, I’m thinking this could potentially be achieved by disabling the app and relying on webhooks to ‘manually’ send the events to Meta, along with any other additional information.
On that note, and appreciate this is a little off-topic – if I wanted to go down that route, is ‘Order creation’ the event we’d want to listen out for? https://help.shopify.com/en/manual/fulfillment/setup/notifications/webhooks
Thanks again, appreciate you dealing with this so quickly.
Happy to help!
Yes, the ORDER_CREATE webhook looks to be the best one. You can see an example of the payload that is sent with it. It does include the line item Vendor. Order Create webhook
Dont do it via webhook, webhooks don’t get any cookie or localstorage/sessionstorage and effectively will not match if it is fired already (unless you REALLY know what you are doing). Deduplication is nearly impossible (as you dont have FBQ_ etc)
If you are looking to customise events, use GTMserver. Use Customer events to get cookie data and send to GTMweb > GTMserver.
Hey Chris,
Good shout! I was however thinking of disabling the app completely, meaning de-duplication would (I think?) not be an issue as we would simply fire the event whenever a webhook comes in (presumably, the same webhook for the same order isn’t fired multiple times?). If I went about it that way, do you think de-duplication could still be an issue? (and if so, why?)
Thank you!
duplication wouldn’t be an issue (as there is only one source).
but, I don’t think it would work at all. The webhook doesn’t have the _FBC and _FBQ data or any browser related stuff that identifies the users or campaign that triggered the transaction. so sure you will get purchases into meta as an event, but it wont know what campaign actually did it (I don’t think).
Ah, that’s a great point. Will give this more thought. Thank you, that’s really helpful!
