in simple terms we just wanted to improve the complex part of the old UI and make it a lot more seamless and help our you know smbs have a call back setup that's a lot simpler everybody I'm nefu I'm a senior front-end engineer here at tenen I'm Jaz I'm the senior product manager at tenin I'm Ryan I'm a senior fulltech engineer in this video we want to share with you how we've updated our call back setup process so Jazz why did we update our callback setup UI that's a good question so we had our old UI where it was template based so every time you want to add a call back you do it one at a time and then you do it you do that process for every single channel so some of our customers started having issues basically they had to set up a few call backs for a process to be successful on the ad Network side and that process was failing so on the product side we've
always wanted to focus on making a very intuitive UI and a very simple product like our tagline is growth Made Simple so we wanted to do something that helped our users our end users use the setup in a more efficient and more accurate way so we wanted to build this new UI where a it was faster for them B it was more accurate and C it was more intuitive what they were used to than before Ryan could you walk us through the new UI and show us how it's changed sure uh before I do that I think I'd like to show the old process just to kind of give a reminder of um how it used to be and why we chose to make a lot the changes we did I think that after seeing that the new process will seem a lot more simple by comparison awesome sounds good take it away so here I have my app and I want to add a Tik Tok install call back click on new callbacks I can search for Tik Tok find the Tik Tok install callback
um you can see here we have a rails form that has a lot of fields that are actually not relevant to this call back as well as here I need to set my Tik Tok app ID once I set that it'll take me to the Callback Details page and once that's done I can um jump back to my app page and I'm going to have to do that a couple more times if you're familiar with Tik Tok callbacks um there's multiple versions of each and you need to add all of them or it can impact the performance um this is something that I'm sure you all care about you don't want lower performance and the networks care about this as lot as well so for the case of Tik Tok we actually had a weekly script that would run I'll find anyone who had for say um an install call back without a Sam call back and we would add that in but in our old um setup it was quite difficult to find those and uh it was not very very
repeatable to other networks which we had requests from other networks for similar things as well and so the changes we've made have made it much easier to uh get all the callbacks that you need created at once and also speed up the process a bit uh just adding these three callbacks wasn't too bad but let's say for instance that I also need an inap purchase for this app and look up Tik Tok again and I can add this Tik Tock purchase but then after I add this to my TK to app ID again once I add this I'm going to have to go back through and add the Tik Tok sand purchase and then what if I have several custom events um it could take quite a long time to add all these callbacks and um if you missed one that could impact your performance and the networks also aren't very happy with tension when there were callbacks that weren't set up correctly and so with our new format we would to make it faster and easier to make callbacks and also
make it so that without thinking about it you had correct call back now let's take a look at the new format so instead of being at the bottom of this page the callbacks tab is now up here so we can click on this and the callbacks are also now split up by channel so I want to look at Tik Tok for now click in here and whereas previously for every call back we had to add this Tik Tok app ID now we just add it once for this app app so now any call back I add will have this Tik Tok app ID applied to it this should make set up much faster for you I think whereas before we had to go and add five separate callbacks to get our Tik Tok install and Tik Tok purchase set up correctly uh we're done now that's all the setup it takes so I think this should be a lot faster and I think it'll be much easier to have your setup correct now because just by clicking on this one Tik Tok install you have the three callbacks
that you had to create manually before create it automatically and bundled together so if you turn this back off all three of those are off so this way the partners will be happy your compaign performance will be better and our data will also be a little bit cleaner so I think it works better for everybody uh there's a few settings you can change here uh you can change the user filter uh it was a little bit complicated I think in our past view uh here it'll send out this call back for every user this setting means it will send the call back only for users who are attributed to Tik Tok and this means we'll send it for users who are attributed to Tik Tok and organic users if you click on the edit there's uh different settings here depending on which call back you're looking for here I might want to change the name say say this is uh I JS 50 is this event name you might be noticing that we have the in that purchase we have the open the ilr Callback but we don't have the custom callback here if you click on add events you'll see the
custom call back here and you might see other calls for other AD networks and that's for an important reason these custom callbacks not only do they have our tangent event which you have to select but for instance for Tik Tok you have this Tik Tok event and for other nadworks they might have other settings you have to change these be different for every callback and so you can't just set them automatically like you can for other callbacks but I think that they're still pretty easy to create relative to others uh whereas before you have had to go and create two separate call backs the Tik Tok custom event and the Tik Tok s custom event now it's just one and they're bundled together you can also come up to this page for callback health and uh for in our case none of our callbacks are failing and so uh there's nothing to look at here there are a lot of uh behind the scenes Tech improvements which are encapsulated in this uh new slick UI um one of which is that we don't have any scripts running weekly to make sure no one's missing callbacks anymore uh since the callbacks are now bundled together on the back end
if you create a Tik Tok install you can't be missing a sand install I'm using Tik Tok as the example but many ad networks have these kind of settings and now you can be sure that if you have your callback set up here it's being done correctly and this is also going to enable us to do a lot of interesting things in the future that ad networks have been requesting um a few examples uh that we've already been requested and have implemented now that we have this format some networks wanted different countries data to go different endpoints some networks wanted attributed and unattributed customers to go to different endpoints this would have been uh hard to set up in our old format and would have required all our customers to go and add new callbacks and now we can just add those behind the scenes and you don't have to do anything to meet Network requirements the the old UI didn't have a lot of issues it wasn't bad you know it wasn't like a deal breaker it had some good points um like it was easier to set up uh on the product side and engineering side and
also for AES to set things up it did have some issues which is why we wanted to explore a new UI some issues for example one it did have more complexity than we liked so we were showing a lot of um API details for example that our customers didn't necessarily need specifically our smbs which like Indie devs for example they're not going to do much with it all they care about is come there go to our page set up something super fast basically have have our product tell them what needs to be done then being an expert into something and then doing that setup so that's the mindset we had on the product side that we wanted to reduce complexity and we want to ensure that SMB specifically Indie devs can grow their apps with a lot of simplicity so that was one issue related to this issue it introduce some inaccuracy for example if someone needed to send call backs to to a partner and
for those call backs to work properly and accurately they needed to set up two callbacks right so they had to go on our Dash and then set up those call backs manually one at a time and again this is the complexity I'm talking about we realize that they don't need to do that they can just go on our Dash enable a toggle and be done with it so in in simple terms we just wanted to improve the complex part of the old UI and make it a lot more seamless and help our you know smbs have a call back setup that's a lot simpler because they had to set up you know one call back at a time for different partners it did take them longer to do that setup but with the new UI we improveed that setup time uh considerably I had to set five call backs for instance to do essentially two actions on our old setup it took me a little bit over a minute uh being very familiar with the UI on our new UI it was and 20 seconds and repeat that
across a bunch
Auto-generated captions from YouTube — names and numbers may be misheard.
Distilling the key insights…
Tenjin · 2026
Deconstructor of Fun · 2026
Comments