Analytics and email

Analytics and email connect a published product to what customers actually do. Both need deliberate integration and verification: a tracking script or accepted send request alone does not establish the intended result.

Measure the customer journey

Egbe’s analytics capability uses Umami for traffic and product events. Your agent can configure tracking, inspect visits and conversions, and investigate where customers leave a funnel. Start with the analytics instructions.

The canonical event contract defines names, required fields and delivery rules. Your product’s actual behavior determines which events it needs. For example, measure completion of the promised core action, not merely the click that starts it.

Keep acquisition attribution through signup and checkout so later outcomes can be related to the original channel. The shared tracking snippet distinguishes explicitly tagged campaign traffic from ordinary referrers. Your agent should reuse that contract instead of inventing parallel event names or attribution fields.

For events tied to the customer’s browsing session, the backend can confirm that something happened while the browser delivers the analytics event. Signed payment lifecycle events outside that session have their own delivery path. Revenue reports must respect the distinction between analytics observations, payment-provider evidence and durable product records.

Before using a report to make a decision, confirm the measurement period, event delivery and relevant gaps. See working with your agent for agreeing useful evidence and next actions.

Use the business mailbox

Your business has an assigned @egbe.app mailbox accessible through Egbe. The agent can send product messages, inspect the inbox and read replies without handling SMTP or IMAP passwords. It should discover the assigned mailbox and operational recipient using the mail instructions.

Use this mailbox for verification and onboarding links, opted-in replies, product notices and founder-facing one-to-one follow-ups. Its shared sending reputation makes it unsuitable for cold outreach, mailing lists, batches or multi-recipient campaigns. Cold outbound belongs to the separate outreach capability with a dedicated sending domain; unavailable outreach is not a reason to use the product mailbox instead.

For operational notifications, use the verified recipient returned by the mailbox account contract. A public footer email is not automatically the right internal destination. SMTP acceptance means submission, not delivery: verify receipt and check later bounces before relying on a new recipient.

Describe the intended recipient and purpose when asking your agent to send a message. Connecting Egbe does not itself authorize outreach or an ongoing email schedule.