Forum Discussion
Monitoring Subdomain Send Volume + Warmth
Hi Bonfire Community,
We're in a bit of an odd situation where we have a few businesses (with their own subdomains) in our portfolio that send emails on a somewhat infrequent basis. Our previous ESP used shared pools, so email warmth wasn't something we had to worry about.
Up to this point, we've been tracking the volume of sends (and date we sent) from those subdomains and the approximate warmth of the domain in our head, which isn't scalable as we add team members working on the email program.
How is everyone tracking the volume/date of sends by subdomain? I had hoped to do this in Mixpanel, but the event payload passed doesn't contain the subdomain as a field, so it's effectively useless. I've done a bunch of googling, but I can't seem to turn up anyone talking about this. My fallback plan is to manually input sends to excel, but this seems archaic. Braze didn't seem to have any solutions when I reached out to support.
Appreciate any ideas!
D
Hi, something I thought you could do, it maybe be tedious depending how many campaigns and canvas you have currently running is just adding tags naming the subdomain connected to the campaign/canvas itself. From there create an engagement report of each tag of subdomain and have them automatically sent to you every week or month so you can see email volume send.
There might be an easier way I am missing but just thought I could give my thoughts.
Hi Malcolm,
This is probably the most simple solution - great idea. I'll give it a whirl!
Thanks,
D
I would try reaching out to Braze regarding this. They do have a dashboard-wide Deliverability report that they can send you (which won't be helpful in this situation), and from what I remember, they were working on a dashboard that breaks down the report by subdomain.
Please keep us posted if you were able to obtain a helpful resource!
Best,
Allan
Hi Allan,
Yes, I've connected with Braze, but they didn't have a solution, they just directed me to the deliverability report. Perhaps a future feature?
Dev
If I hadn't just checked the docs, I'd have sworn that there was something in there regarding sending address/domain.
Similar to Malcolm's suggestion, you can add extra data using liquid - which should then manifest in Mixpanel/wherever via Currents - though that would require effort per campaign/canvas step.
I'm wondering if you could abuse the name of the ip_pool for this as well - it's a bit hacky, but might work if you only have the one pool per domain/customer. Again, that should externalise via currents.Hi Bob,
Yes, we discussed both of these approaches, but the liquid will just be too disruptive to workflow and the ip_pool wont work because of the way we have those distributed.
I appreciate the suggestions, though!
D
