stape.ioReviews of stape.io

Response from stape.ioOct 6, 2025

Thank you for sharing your feedback. We have a feeling this review might not come from a genuine user — please correct us if we’re mistaken. Some details you mentioned don’t match how our products work, and we’ve already reached out on Trustpilot asking for more information to look into your case. If you did experience any difficulties, we’d be happy to help you personally! Let’s clarify a few things: - Our Connections feature doesn’t include Meta/Facebook integration. You can check all available options here: https://stape.io/helpdesk/documentation/connections-feature - If you were referring to Meta Conversions API Gateway, the setup takes just about 1 minute — here’s a quick video guide: https://www.youtube.com/watch?v=OhQpU3jOgwc - For Facebook server-side tracking, our Setup Assistant can automatically create and import a pre-built template into your GTM container — setup usually takes under 5 minutes. More details here: https://stape.io/blog/setup-assistant-by-stape We truly aim to make server-side tracking as simple and automated as possible. If you’d like us to guide you through the setup or check your configuration, please reach out — we’ll gladly assist at [email protected]

Response from stape.ioSep 25, 2025

Thank you for sharing your feedback 🙏 We’re truly sorry that you had a frustrating experience with the payment process. After reviewing the situation with our Finance team, it appears the issue stems from the payment gateway being 𝗯𝗹𝗼𝗰𝗸𝗲𝗱 𝗯𝘆 𝘆𝗼𝘂𝗿 𝗰𝗮𝗿𝗱 𝗶𝘀𝘀𝘂𝗲𝗿, possibly due to account limits or compliance-related restrictions. Unfortunately, this is 𝗯𝗲𝘆𝗼𝗻𝗱 𝗼𝘂𝗿 𝗰𝗼𝗻𝘁𝗿𝗼𝗹, and we 𝗿𝗲𝗰𝗼𝗺𝗺𝗲𝗻𝗱 𝗿𝗲𝗮𝗰𝗵𝗶𝗻𝗴 𝗼𝘂𝘁 𝘁𝗼 𝗣𝗮𝘆𝗣𝗮𝗹 for further clarification. We regret that the issue was not resolved to your satisfaction, and we sincerely hope 𝘆𝗼𝘂 𝘄𝗶𝗹𝗹 𝗰𝗼𝗻𝘀𝗶𝗱𝗲𝗿 𝗿𝗲𝘀𝗼𝗹𝘃𝗶𝗻𝗴 𝘁𝗵𝗲 𝗺𝗮𝘁𝘁𝗲𝗿 𝘄𝗶𝘁𝗵 𝗣𝗮𝘆𝗣𝗮𝗹. Stape offers unique solutions, and we'd be happy to welcome you back in the future once this issue is addressed. Thank you again for your feedback, and we hope to serve you better next time.

Response from stape.ioSep 3, 2025

Thank you for sharing your feedback. We understand your frustration and want to clarify that our team strives to provide comprehensive support, from setup to troubleshooting. As part of our service, we offer guidance on the integration of Meta CAPI Gateway with your website, but it’s important to note that we primarily focus on ensuring the 𝐬𝐞𝐫𝐯𝐞𝐫-𝐬𝐢𝐝𝐞 𝐭𝐫𝐚𝐜𝐤𝐢𝐧𝐠 𝐰𝐨𝐫𝐤𝐬 𝐚𝐬 𝐞𝐱𝐩𝐞𝐜𝐭𝐞𝐝. While the Meta Pixel and Events Manager setup 𝐟𝐚𝐥𝐥𝐬 𝐰𝐢𝐭𝐡𝐢𝐧 𝐌𝐞𝐭𝐚’𝐬 𝐝𝐨𝐦𝐚𝐢𝐧, our support team made every effort to assist by thoroughly checking your setup and recommending the next steps. Regarding the issue you experienced with Lead events, our team investigated and confirmed that the core functionality of the Meta CAPI Gateway was working 𝐜𝐨𝐫𝐫𝐞𝐜𝐭𝐥𝐲 on the pages we tested. The problem appeared to be you simply did not see the events in the hub. We understand that out support team recommended you to reach out to Meta support prematurely, but please understand that it was made in good faith, as they manage the Meta Pixel and its custom event handling. We understand that Meta support may have limitations, but we did our best to guide you through this process and confirmed that the events were being sent successfully afterwards. We recognize the frustration of feeling unsupported, especially when you’ve followed the instructions provided. However, we want to emphasize that 𝐨𝐮𝐫 𝐭𝐞𝐚𝐦 𝐝𝐢𝐝 𝐩𝐫𝐨𝐯𝐢𝐝𝐞 𝐚𝐜𝐜𝐮𝐫𝐚𝐭𝐞 𝐢𝐧𝐬𝐢𝐠𝐡𝐭𝐬 into what was happening on your setup and 𝐬𝐮𝐠𝐠𝐞𝐬𝐭𝐞𝐝 𝐭𝐫𝐨𝐮𝐛𝐥𝐞𝐬𝐡𝐨𝐨𝐭𝐢𝐧𝐠 𝐬𝐭𝐞𝐩𝐬. We also escalated the issue to our developers for further investigation, and we continue to monitor this case closely. We remain committed to assisting you with your tracking setup. As we can see that the ticket is still open, we are happy to explore additional solutions or clarify any remaining concerns. Please feel free to reach out, and we’ll ensure that you receive the attention needed to resolve this matter.

Response from stape.ioAug 20, 2025

We sincerely apologize for any frustration you have experienced, and we truly appreciate your patience. You are correct in noting that the issue was reported to our development team, and they are actively working on resolving it. We apologize for the delay and understand your concern regarding the timeline. Regarding the migration suggestion, our support team provided an alternative solution, and we requested further clarification on this matter. This was because we had only received the email address for “Account A” and not the email for “Account B”, which was crucial to ensure the correct migration. We’re glad that we could move forward with your request once the necessary details were clarified. Regarding the annual subscription, we have thoroughly reviewed the tickets, and at no point did our team suggest or request that you pay for an additional annual subscription. Our team offered you two options: (1) to connect your Pixel to the existing paid Meta CAPI Gateway, and remove the one without an active subscription, or (2) to receive a full refund and connect to a new Meta CAPI Gateway. There was never any intention or even a hint to ask you to pay for two subscriptions. Please be assured that we are here to support you and resolve any remaining issues. We can see that your ticket is still open, and we would be more than happy to assist you further to ensure everything is properly set up.