Great concept, but multilingual consent is a dealbreaker

  • cenkcagdas

    (@cenkcagdas)


    3 months ago

    Installation is straightforward and the interface is clean, intuitive, and reassuring to navigate. That said, there are a few limitations that held me back. The Meta test event code — the one you get from Events Manager to verify your setup — cannot be entered anywhere in the plugin, which makes it impossible to properly test events directly within Meta. The plugin does have its own internal log system, but I would have liked to see server-tagged events confirmed as deduplicated on Meta’s end rather than just logged locally.

    The built-in consent popup is a nice touch, but it currently only supports a single language with no option to localize it — this alone was a dealbreaker for me. A multilingual consent banner is essentially a requirement for stores operating across different regions, and without it I couldn’t use the plugin in production. The fact that it sends diagnostic data back to Buildio is another downside worth mentioning, even if the data itself isn’t sensitive.

    • This topic was modified 3 months ago by cenkcagdas.
Viewing 1 replies (of 1 total)
  • Plugin Author Buildio

    (@buildiodev)

    2 months, 3 weeks ago

    Hi, really appreciate the thoughtful review, and thank you for the detailed feedback.

    Great news on the multi-language consent popup. That was the biggest gap you flagged, and it’s just been shipped in v2.6.4. The built-in popup now supports 18 languages out of the box (Spanish, French, German, Italian, Portuguese, Dutch, Polish, Japanese, Chinese Simplified/Traditional, Korean, Turkish, Arabic, Russian, Swedish, Czech and more), automatically matched to each visitor’s WordPress locale. On top of that, you can now fully edit every string in the popup per-language from the admin, so you can match your brand voice, legal wording, or any jurisdiction-specific requirements. It should fully unblock the multi-region use case you had in mind.

    On the other two points:

    • Meta test event code field: noted and on the roadmap. Being able to verify server-side events land in Meta’s Test Events tab is a fair ask and we’ll look to add it.
    • Diagnostic data: thanks for flagging. We’ll take another look at what’s sent and work on making it more transparent (and opt-outable).

    Thanks again for the careful review, it genuinely helps shape where we focus next. If you give v2.6.4 a try and run into any issues, please get in touch through the support forum and we’ll jump on it.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this review.