Have something to say?

Tell us how we could make the product more useful to you.

fire message.deleted for WhatsApp app-side deletes (both directions), with the original message id

Currently, when a message is deleted ("delete for everyone") in a WhatsApp conversation, we can't tell which message was deleted: Business-side delete (from the WA Business app): arrives as a new message.sent event with text: "[revoke]", a fresh message.id, and a fresh platformMessageId. No reference to the deleted message. Customer-side delete: arrives as a new message.received event with text: null, attachments: [] — again a fresh message.id / platformMessageId, no reference to the original. We are subscribed to message.deleted, but it never fires for either case (confirmed in the webhook logs — only the message.sent / message.received events above appear). The docs say WhatsApp support for message.deleted is limited to deletes issued via the Cloud API, and incoming unsend is Instagram-only. Ask: emit message.deleted for WhatsApp deletes in both directions (app-side business deletes and customer unsends), carrying the original message's id / platformMessageId — same shape as the Instagram unsend payload. Without a pointer to the original message, inbox UIs can't render a "this message was deleted" state and the [revoke] / null placeholder events are effectively noise. Example (business-side delete we received — note the ids don't match any prior message): { "event": "message.sent", "message": { "id": "6a599cbb3d50078defbca0af", "platformMessageId": "wamid.HBgKNjU4MjgzMjYwOBUCABEYFDJBNTdDMUI3M0ZBM0U4ODAyNEI3AA==", "direction": "outgoing", "text": "[revoke]" } }

rae tan 2 days ago

Feature Request: AI-Generated Content Disclosure for Facebook and Pinterest

Hi Zernio team, We're using your API to publish AI-generated affiliate videos across five platforms. You've already added great support for AI disclosure on Instagram (isAiGenerated) and YouTube (containsSyntheticMedia) — thank you for that. We'd like to request the same capability for Facebook and Pinterest: Facebook Facebook's Graph API supports an AI label for Reels and video posts via video_labels: ["LABELED_AI_GENERATED"] on the video endpoint. We're currently posting as contentType: "reel" via FacebookPlatformData and would love a field like isAiGenerated: true (matching your Instagram convention) that maps to this. Pinterest Pinterest supports an is_ai_modified_or_generated: true field on the Pins API for video and image pins. We'd love a matching field in PinterestPlatformData to surface this. Both platforms are increasingly enforcing AI disclosure requirements, and we want to stay compliant without having to manually label every post after the fact. For reference, we're already using: platformSpecificData.isAiGenerated: true for Instagram ✅ platformSpecificData.containsSyntheticMedia: true for YouTube ✅ platformSpecificData.videoMadeWithAi: true for TikTok ✅ Facebook and Pinterest are the only gaps remaining. Would love to see these added — happy to beta test if that's helpful. Thanks!

Scott 4 days ago

Google SERP Monitoring Including AI Results, Business, and Shopping

Zernio could integrate a Google SERP API to analyze not only traditional organic rankings, but also the full range of modern Google search result formats. This could include: organic search results Google AI Overviews and AI-generated answers Google Business Profile and Local Pack results Google Shopping and product listings Featured Snippets, images, videos, and other SERP features This would allow users to understand where their brand, products, and content are actually visible across the entire Google search results page, rather than focusing only on traditional organic rankings. Potential monitoring features could include: visibility trends by keyword brand mentions within AI-generated answers Local Pack rankings Google Shopping visibility compared with competitors changes in individual SERP features automated reports and alerts This could position Zernio as a broader search visibility monitoring platform that combines traditional SEO, local search, shopping visibility, and AI search insights in one place.

Fabian Karsch 9 days ago

Zernio Project Awards & Partner of the Month

Wie wäre es mit einem eigenen PR- und Award-Bereich für besonders erfolgreiche oder kreative Zernio-Projekte? Zum Beispiel könnten regelmäßig ein „Partner of the Month“, ein „Project of the Month“ oder jährliche Zernio Awards ausgezeichnet werden. Kunden und Partner könnten ihre Projekte einreichen, die Community stimmt ab oder eine Jury wählt die besten Umsetzungen aus. Die Gewinner könnten anschließend auf der Zernio-Website, im Newsletter und auf Social Media vorgestellt werden. Das hätte mehrere Vorteile: Kunden erhalten zusätzliche Sichtbarkeit und Publicity. Erfolgreiche Projekte dienen anderen Nutzern als Inspiration. Zernio erhält authentische Use Cases und Referenzen. Partner werden motiviert, besonders hochwertige Projekte umzusetzen. Die Community wird stärker eingebunden. So entsteht eine Win-win-Situation: mehr Reichweite für die Kunden und gleichzeitig mehr hochwertige Erfolgsgeschichten für Zernio.

Fabian Karsch 9 days ago

Payment barrier for Brazilian users (Stripe / Pix suggestion)

Hi Zernio Team, I really like the app and the work you guys are doing, but I’d like to suggest a payment improvement that would massively help your Brazilian user base. Currently, payments on Zernio are processed as international credit card transactions. For users in Brazil, this means our credit card issuers charge an unavoidable government cross-border tax called IOF, plus a bank spread on the currency exchange rate. This makes the final cost significantly more expensive and unpredictable for us. Since you are already using Stripe, would you consider enabling local payment methods for Brazil? Stripe natively supports Pix (our national instant payment system used by 100% of the banked population) and local credit card processing in BRL. Alternatively, using global merchant of record platforms like Paddle, or LATAM-focused processors like EBANX or dLocal, would completely bypass these international taxes for your users. Enabling local acquiring in BRL would remove a huge point of friction, lower your churn rate, and definitely increase your conversion rates in the Brazilian market. Is this something you might have on your roadmap?

Artur Rick 9 days ago