Leeberty
Forum Replies Created
-
Hi @korvak ,
Thanks for messaging us! I’ll close this ticket and let’s continue the conversation there.
Hi @korvak ,
I understand that you’re seeing 0% from the Purchase confirmation page reached per gateway in your debug info. Allow me to help you with this.
We have tested with CheckoutWC, and it’s even recommended in one of our blog posts here: Best WooCommerce Plugins to Increase CRO and Maximize Ad ROI.
The issue you’re seeing is more about your customers not getting redirected back to the purchase confirmation page after payment. This part of the debug info is only to confirm where an issue is coming from, but must be fixed from your payment gateways.
For reference, see: https://sweetcode.com/docs/wpm/setup/requirements#payment-gateways
That said, please send the full debug info directly to our suppport form here so we can check further. See: https://sweetcode.com/support/
Due to inactivity, I’m closing this thread for now.
Feel free to add a new reply to continue the conversion for this support request.Hi @mdc2957 ,
Thanks for getting back.
You’re right that UTMs can help you see where orders are coming from, but you don’t need another plugin to capture them. WooCommerce already has its own built-in order attribution feature that records UTM parameters and the referrer directly in each order. It’s useful, but keep in mind it uses last-click attribution, so it won’t always match what Meta reports.
If you’re looking for a more accurate, data-driven view of which campaigns are actually contributing to sales, Pixel Manager Pro includes GA4 attribution via the GA4 Data API. That gives you a more complete picture than UTMs or WooCommerce’s built-in method. See: https://sweetcode.com/docs/wpm/plugin-configuration/google-analytics#ga4-data-api
I hope this helps.
Let me know if you have further questions.
Hi @mdc2957,
Thanks for the post! Allow me to help provide some clarification.
Facebook does not provide a way to list the specific WooCommerce order numbers that came from your ads. The Meta Pixel and CAPI simply send purchase event data to Meta, and Meta uses its own attribution model to decide which purchases should be counted under your ad results. This means the number you see in Ads Manager is Meta’s attribution count, not a direct one-to-one list of your WooCommerce orders.
Because of this, it is normal for the numbers in WooCommerce and the numbers in Ads Manager to differ. Some orders that you see in WooCommerce may not be attributed by Facebook to the ad, depending on their attribution rules.
You can use the Meta Events Manager to confirm that all purchase events are being tracked correctly and that deduplication between pixel and CAPI is working. However, Events Manager cannot tell you which specific events came from ad clicks.
The attribution side happens only inside Ads Manager, based on your campaign settings. Facebook looks at your configured attribution window and whether you are counting click-through conversions, view-through conversions, or both. All of these settings can change how many purchases Facebook attributes to your ad.
I hope this helps.
Feel free to reach out if you have further questions.
Due to inactivity, I’m closing this thread for now.
Feel free to add a new reply to continue the conversion for this support request.Hi @demian85 ,
I understand that you’re seeing a long _gl code parameter. Allow me to help provide some clarification.
If you see very long URLs with a
_glparameter while browsing your website, don’t worry. This appears when you enable the Google Consent Mode and explicit tracking mode in the Pixel Manager.You can find more information in our documentation here. See: https://sweetcode.com/docs/wpm/faq#suddenly-very-long-urls-with-a-_gl-parameter-show-up
Please let us know if you have further questions.
HI @wood1e ,
Thanks for your cooperation.
We’ll keep this ticket open as we await your updates.
Let us know if you have further questions. We’d be happy to assist!
Hi @wood1e ,
I understand that you’re experiencing some issues with tracking in both GA4 and Google Ads. Let’s sort this out.
Can you please clarify if you have followed our documentation regarding plugin configuration? If not, we do highly recommend having a look and checking again after.
See:
- https://woocommerce.com/document/pixel-manager-pro-for-woocommerce/pmw-plugin-configuration/google-ads/
- https://woocommerce.com/document/pixel-manager-pro-for-woocommerce/pmw-plugin-configuration/google-analytics/
Please let us know how it goes.
Due to inactivity, I’m closing this thread for now.
Feel free to add a new reply to continue the conversion for this support request.Hi @pabloblanco,
Thanks for the post! Allow me to help you with your questions.
Yes, the plugin is fully compatible with HPOS (High-Performance Order Storage).
There are no special requirements or known issues as it works out of the box.
See: Is the Pixel Manager compatible with the HPOS (High-Performance Order Storage)?
I hope this helps clarify.
Feel free to reach out if you have further questions.
Due to inactivity, I’m closing this thread for now.
Feel free to add a new reply to continue the conversion for this support request.Due to inactivity, I’m closing this thread for now.
Feel free to add a new reply to continue the conversion for this support request.Hi @leonardoscalco ,
Thank you for the post! Allow me to help you with this.
It’s likely that you are referring to Meta or other paid ad platforms.
For GA4 transactions, the conversion is only sent once the order status changes to Paid, particularly when the GA4 Measurement Protocol is enabled.
See: https://sweetcode.com/docs/wpm/plugin-configuration/google-analytics#ga4-api-secret
For Meta and other paid ads, however, Pixel Manager sends the Purchase event immediately, both through the browser pixel and the Conversion API, even if the order is still in Pending or Processing status. These platforms don’t currently offer a way to properly process delayed purchase conversions in the same way GA4 does.
I hope this helps clarify.
Feel free to reach out if you have further questions.
Due to inactivity, I’m closing this thread for now.
Feel free to add a new reply to continue the conversion for this support request.
