I built Trackkit because I was tired of integrating heavy CRM SDKs or navigating through complex dashboards just to see if a transactional email was opened.
I wanted something provider-agnostic that works with any SMTP or even personal mail.
How it works: You send a POST request to the API, get a tracking token, and embed it as a pixel or a link. When someone interacts with the email, you get a webhook.
Technical bits:
- No SDK: It's just a pure HTTP API.
- Security: Webhooks are signed with HMAC (SHA256) to prevent spoofing.
- Bot Filtering: I implemented logic to filter out pre-fetches and automated opens from Gmail/Outlook/Office365, which usually skew tracking data.
- Privacy: We don't store the email content or personal data, only the event logs.
I'm currently in "pre-revenue" mode and just looking for feedback from fellow developers. Does the documentation make sense? What features are missing for your workflow?
I built Trackkit because I was tired of integrating heavy CRM SDKs or navigating through complex dashboards just to see if a transactional email was opened.
I wanted something provider-agnostic that works with any SMTP or even personal mail.
How it works: You send a POST request to the API, get a tracking token, and embed it as a pixel or a link. When someone interacts with the email, you get a webhook.
Technical bits:
- No SDK: It's just a pure HTTP API.
- Security: Webhooks are signed with HMAC (SHA256) to prevent spoofing.
- Bot Filtering: I implemented logic to filter out pre-fetches and automated opens from Gmail/Outlook/Office365, which usually skew tracking data.
- Privacy: We don't store the email content or personal data, only the event logs.
I'm currently in "pre-revenue" mode and just looking for feedback from fellow developers. Does the documentation make sense? What features are missing for your workflow?
I'll be around to answer any questions!