-
Notifications
You must be signed in to change notification settings - Fork 54
Purchase and InitiateCheckout pixel events not fired #82
Comments
Hello @shue249 , any news omn this issue? |
@papke88 Apologies for the late reply. Can we understand if you are using any 3rd party checkout modules? Our pixel event for InitiateCheckout and Purchase is supporting the default OpenCart checkout module. |
We are using only default ones!
Regards,
Rokas V.
… On 5 Jan 2019, at 05:49, shue249 ***@***.***> wrote:
@papke88 Apologies for the late reply. Can we understand if you are using any 3rd party checkout modules? Our pixel event for InitiateCheckout and Purchase is supporting the default OpenCart checkout module.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@papke88 I see that your checkout and thank you URL is different from the OpenCart default ones. In the default URL, it will follow something like "index.php?route=checkout/checkout". Are you using any SEO mapping to change the checkout and payment URL on your website? |
Yes of course, we use seo tool for friendly urls. Thats very important and most of well made sites use only clean seo urls..
Regards,
Rokas V.
… On 5 Jan 2019, at 10:17, shue249 ***@***.***> wrote:
@papke88 I see that your checkout and thank you URL is different from the OpenCart default ones. In the default URL, it will follow something like "index.php?route=checkout/checkout".
Are you using any SEO mapping to change the checkout and payment URL on your website?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Hello @shue249, can i get a fix for this problem? |
@papke88 We will look into this. Can I understand how do you use the seo tool to setup the friendly URLs, so I am not familiar with this SEO tool. |
@shue249 We use this extension:
https://www.opencart.com/index.php?route=marketplace/extension/info&extension_id=9486&filter_search=Complete%20SEO%20Package
There you can check demo. (go to seo editor > common page url)
<img width="1094" alt="screen shot 2019-01-09 at 16 06 31" src="https://user-images.githubusercontent.com/44572066/50904429-ebdeb800-1428-11e9-9ba2-935587329a6c.png">
Regars,
Rokas V.
… On 2019Jan 9,, at 09:32, shue249 ***@***.***> wrote:
@papke88 <https://github.com/papke88> We will look into this. Can I understand how do you use the seo tool to setup the friendly URLs, so I am not familiar with this SEO tool.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#82 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AqgdojvKbxjo_kCuhqY0KJqCkQH7ScbTks5vBZsCgaJpZM4Zkdt3>.
|
hello @shue249 , any news on this issue? |
@papke88 Apologies for the late reply. As it is a 3rd party extension, we may need more time to figure how best to support this feature. In the meantime, you may want to try to make some changes on our plugin code to be able to send in the events. However, that will require you to have access to development skills. Will you be open to that? |
@shue249 Yes sure write me in which files and what to change and i will do it with no problem!
Regards,
Rokas V.
… On 17 Jan 2019, at 14:39, shue249 ***@***.***> wrote:
@papke88 Apologies for the late reply. As it is a 3rd party extension, we may need more time to figure how best to support this feature.
In the meantime, you may want to try to make some changes on our plugin code to be able to send in the events. However, that will require you to have access to development skills. Will you be open to that?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@shue249 i am waiting for your directions, thanks! |
@papke88 Can you try putting in the below code lines to this file at line 188 on your server. Code lines to be added:
After adding the changes, you can try to make a mock purchase and verify if the InitiateCheckout and Purchase events are successfully fired on your website using the PixelHelper. |
@shue249 hello, added the code using your directions, but pixels are not fired... |
Hello @shue249, any news? |
@papke88 Apologies for the delay. We are still checking on this, pls do give us more time and will update you soonest. |
@shue249 ok thanks, hope to get the solution soon, we cant advertise without pixels on those pages |
@shue249 hello, any news on this issue? |
@papke88 Thank you for the patience and apologies for the delay. We have some initial findings and we want to cross-check with your configuration setup to verify if the findings tally. We like to understand more on how you do the configuration on the SEO editor. Will you be able to share screenshots of your SEO configuration. Please remove away any sensitive information from the screenshot. In particular, we are looking for the below sample examples for the absolute URL and common page URL. Apart from these 2 settings, are you using any other settings and can you share these settings with us? |
Hello @shue249 , here are the screen shots of common page url settings for both LT and US language on the site. Do you need anything else? |
all other settings is default ones, nothing special there that could effect your module i think... the main thing that affects your module i think is friendly urls... |
@papke88 Thanks for the fast response. Your screenshots have confirmed the same findings as us. On the SEO editor plugin, we found 2 possible ways to setup the SEO URL - common page URL or absolute URL. If we use the common page URL, we are able to replicate the exact same problem as what you are facing. See the screenshot on our test servers for the checkout, thank you and shopping cart pages. However, if we switch to use the absolute URL (and retaining the exact same settings), the pixels are able to fire correctly. The below screenshot is using the absolute url on our test servers. Based on our test and findings, we can conclude that Absolute URL is compatible with our plugin and Common page URL is having some incompatibility issues. We will be taking more time to dig into coming out with a proper solution that will make our plugin compatible with both Absolute URL and Common page URL, and release the fix when its ready. In the meantime, do you think you can switch to use the Absolute URL? (this is based on the premise that Absolute URL works properly and firing the pixels on your server. If Absolute URL does not work, we need to dig deeper to determine where could the issue be) Will there be any concerns from your side? Will love to hear your thoughts. |
Thank you for your anwers. Interesting, i guess se could switch to absolute but can you explain the difference between absolute and common urls? Does it make difference to SEO?
Regards,
Rokas V.
… On 2 Feb 2019, at 16:30, shue249 ***@***.***> wrote:
@papke88 Thanks for the fast response. Your screenshots have confirmed the same findings as us.
On the SEO editor plugin, we found 2 possible ways to setup the SEO URL - common page URL or absolute URL.
If we use the common page URL, we are able to replicate the exact same problem as what you are facing. See the screenshot on our test servers for the checkout, thank you and shopping cart pages.
However, if we switch to use the absolute URL (and retaining the exact same settings), the pixels are able to fire correctly. The below screenshot is using the absolute url on our test servers.
Based on our test and findings, we can conclude that Absolute URL is compatible with our plugin and Common page URL is having some incompatibility issues.
We will be taking more time to dig into coming out with a proper solution that will make our plugin compatible with both Absolute URL and Common page URL, and release the fix when its ready.
In the meantime, do you think you can switch to use the Absolute URL? (this is based on the premise that Absolute URL works properly and firing the pixels on your server. If Absolute URL does not work, we need to dig deeper to determine where could the issue be) Will there be any concerns from your side? Will love to hear your thoughts?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@papke88 As we are not the developers for the SEO editor plugin, we are not in the best position to be able to explain the differences between the absolute and common URLs. Perhaps you may want to check in with the developers to understand the differences. Off the hand from their plugin site, it offers a very high level explanation. To the best of my understanding, both absolute and common urls should work in the same way for your use case. However, it may be good to double confirm with the developers to be sure. From SEO side, I will say it does not matter to them. For SEOs, only the url string matters. They do not care how the implementation code looks like, ie be it common url or absolute url or some other implementation methods.. |
Thank you for your explanation! Will try to turn on absolute urls. Please give me a notification when you will update your module for common urls too!
Regards,
Rokas V.
… On 3 Feb 2019, at 04:00, shue249 ***@***.***> wrote:
@papke88 As we are not the developers for the SEO editor plugin, we are not in the best position to be able to explain the differences between the absolute and common URLs. Perhaps you may want to check in with the developers to understand the differences. Off the hand from their plugin site, it offers a very high level explanation.
To the best of my understanding, both absolute and common urls should work in the same way for your use case. However, it may be good to double confirm with the developers to be sure.
From SEO side, I will say it does not matter to them. For SEOs, only the url string matters. They do not care how the implementation code looks like, ie be it common url or absolute url or some other implementation methods..
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@papke88 https://www.opencart.com/index.php?route=marketplace/extension/info&extension_id=32336 We will close out this ticket for now, but pls do reach to us if you still have any further questions or issues. |
Thanks!
Regards,
Rokas V.
… On 23 Feb 2019, at 04:10, shue249 ***@***.***> wrote:
@papke88
We have released a latest version of the plugin, v2.1.4 and can be downloaded from OpenCart marketplace or our github. The new version will resolve the issue with SEO URL.
https://www.opencart.com/index.php?route=marketplace/extension/info&extension_id=32336
https://github.com/facebookincubator/Facebook-For-OpenCart/releases/tag/v2.1.4
We will close out this ticket for now, but pls do reach to us if you still have any further questions or issues.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Hi, I have version 3.0.3.1 (Brasil 1.2.4), with this issue of not registering the checkout and purchase part in the Facebook pixel. Installing this Facebook extension will solve it? Any suggestion? Thanks |
Facebook Business Extension plugin for OpenCart versions 3.1.2 and below has been deprecated and support will not be provided for those versions. That being said, if you are only having issues with Checkout and Purchase Pixel Events, it is usually caused by custom checkout extensions causing the FB plugin to be unable to register the Checkout and Purchase Events. Adjustments to the extension will have to be made to accommodate custom checkout extensions. |
Posting on behalf of papke88
@shue249 Just tried updated extension, looks like it works fine, just cant track the pixel on success page, the pixel helper do not show it. Can you check it?
Success page is here
cr7shop.lt/atsiskaitymas-sekmingas
also cant see the pixel "checkout initianed"
The text was updated successfully, but these errors were encountered: