Skip to main content

At the moment, custom fields can only be created for a specific network or blend. This is a bit complicated if you’d like to do the same for multiple networks or blends (e.g. filtering something out of a campaign).

It would be great, if you could use universal custom fields, where you specifiy the field inside the custom field. I.e. if(network=Facebook){filter facebook campaign for regex}, if (network=Google){filter google campaign for regex}, else{return “other network”}

This custom field could then be used in all tables and transfers.

It would greatly improve maintainability as well as improve clarity in the custom fields section, because it would reduce the number of custom fields.

Hey ​@tibormartini,

That's a fantastic suggestion, thank you! Speaking as part of the product team, you're right that this would be a huge improvement.

To be transparent, it's something we'd love to implement. The challenge is always how to balance it with the projects already on our roadmap, and we haven't been able to prioritize this one just yet.

Hearing this directly from customers is super helpful for us to make the case for it, and I've shared your feedback with the team.