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!
pydubreucq•2w ago
Really interesting idea.
The first question that comes to mind, and which may raise some concerns, concerns support for sender domains/subdomains. Is it possible (or planned) to customize this?
In terms of deliverability, it's an advantage to be aligned.
The graphical interface looks clean and well thought out.
To be honest, I wonder if people are willing to pay for a service that an ESP provides natively.
But I've never been confronted with the problem you seem to be solving because we develop two ESPs ourselves (Mindbaz & Sweego).
Another question I have is about integrating these events into the platform that sends emails or marketing automation. Because if we want to target based on an activity or event, we'll need to import those events.
My feedback is direct and well-intentioned; I think it can always be helpful.
Megas_UA•2w ago
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!
pydubreucq•2w ago
The graphical interface looks clean and well thought out.
To be honest, I wonder if people are willing to pay for a service that an ESP provides natively. But I've never been confronted with the problem you seem to be solving because we develop two ESPs ourselves (Mindbaz & Sweego).
Another question I have is about integrating these events into the platform that sends emails or marketing automation. Because if we want to target based on an activity or event, we'll need to import those events.
My feedback is direct and well-intentioned; I think it can always be helpful.
In any case, congratulations on your solution.