Hi,
Can someone please help evaluate the info https://www.youtube.com/watch?v=Ehnvhq4MrJw&t=633s about Hotjar and Zapier integration for FB pixels, and give a step-by-step of how to set this up for a non-techie?
Also please help advise if this tactic https://www.youtube.com/watch?v=TETr8siYHis would be worth implementing and feasible for Wordpress+Wocommerce sites?
Thank you!
Mmm, I am not sure that video on Hotjar/Zapier will work well.
1. Splits by FBCLID (why tho?) but then doesn't use the output of this step anywhere... the next step with sending data to FB just uses the info from step 1, making step 2 redundant
2. The CAPI requires client user agent to be sent - https://developers.facebook.com/docs...ent-user-agent - but this is not included anywhere in the FB event details in Zapier. They could possibly be available from Hotjar but it makes no sense to not see it in the FB step config, as other triggers/sources would not have it.
3. Overall, not sure that Zapier automation will satisfy Facebook's requirements for solid CAPI event tracking.
As for the other video about using iFrames to fire the FB JS... I haven't really tested this since I have never needed it. But, its absolutely trivial for Javascript to access the value in the address bar.
In their JS, they have full access to the "window" global variable - https://developer.mozilla.org/en-US/docs/Web/API/Window - I can't really navigate FB's minimised JS source code, but they could easily send the values of window.parent (the frame source) or windows.top (the address bar), without any difficulty.
I did some testing just now by embedding an iFrame on funnelflux.com from a different domain/page, where that iFrame fired the pixel event.
The result? Facebook sends the iFrame URL and the parent/address bar URL in the request, as some "dl" and "rl" parameters. So they definitely see both, but I am not sure how they interpret/process it.
Can you please recommend a good solution then? especially for adding a pixel to multiple domains, and adding multiple pixels to a domain.
Does a domain need to be verified even when implementing the CAPI tracking?
Thank you.
Well. Zeno is spot on as to all tiny tech details - yet, iframing is something of the past and certainly not going to solve the issue in a solid way or long term manner.
Additionally, I don’t really see how you can actually get your iframe to fire on your advertiser page or checkout page.
Most importantly, firing a pixel from an iframe means that you are trying to set and read a Cookie from a third party website - which is exactly what browsers are blocking natively.
Let’s put it this way:
1. The FB capi is very complex.
2. Since the api release, there have been at least 5 breaking changes.
3. Since the release there have been several new requirement related to iOS release.
4. If you read the Facebook pixel implementation guide, you will realize that there are quite a few settings that need to be tuned in order to fire the pixel accurately.
As a FB business partner we’ve gone through plenty of updates to fine tune our integration with the api. Still, there are many moving parts, that must be well synced in order to achieve a near perfect attribution.
So here you are trying to find a workaround which might in some instances work, but will probably fail.
Sent from my iPhone using Tapatalk