search.noResults

search.searching

saml.title
dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
ReferOn The Hidden Cost of Legacy Affiliate Platforms


Legacy affiliate platforms may still function, but the hidden cost of technical debt is becoming harder to ignore. ReferOn COO David Harris explains why outdated infrastructure is slowing onboarding, limiting scalability and restricting commercial agility, and why modern API-first technology is increasingly becoming a competitive advantage for operators looking to grow their affiliate programmes.


David, many operators still rely on affiliate platforms that were built a decade or more ago. Why do so many businesses continue to accept the "it still works" mentality when it comes to affiliate technology?


Simple answer - because it's easy. Tey’re comfortable and do not want to change. It is also possible that they have created workarounds in their operation to compensate for the shortcomings. Moving back to more efficient workflows while learning a new platform can seem disruptive in the short term, even if it saves significant time in the long run.


Technical debt is a phrase that's widely used in software development but less so in affiliate marketing. How would you define technical debt in an affiliate platform, and where does it begin to impact commercial performance?


I think technical debt is much more for software than marketing as it directly relates to code and loading. As software expands and adds more and more, the code must also have the support structure behind it to lift the code without breaking. Imagine you are building a tower and it becomes top-heavy with new floors that are wider and wider. It will eventually fall. Technical debt is the equivalent of that.


As features are added, the foundations also need to be strengthened to keep the platform stable. Resolving technical debt isn't particularly exciting from a client's perspective, but it's essential. To give a Referon example here, the most recent case is the role engine.


To allow the functionality of roles and privileges in the system, every endpoint, every button had to be reviewed. Tat work then has to continue as new functionality is introduced.


104


What are some of the hidden costs that operators often overlook? Is it simply slower technology, or does it extend into recruitment, retention and day-to-day operational efficiency?


I think this is a big topic that can fall into many things, but let's focus on the topic of technology here; yes a slow, cumbersome technology can of course slow things down and create frustrations. Having quicker technology with easy features frees up time for higher-value tasks - performance analysis, negotiating deals and onboarding partners etc. Such examples could be creating campaigns or deals when a simple target is needed or perhaps reviewing data in reports and you can't access the level of reporting you actually need.


Affiliate managers increasingly expect to launch campaigns, create deals and onboard partners almost instantly. How have expectations changed over the last five years, and are legacy systems keeping pace?


As with everything nowadays, everybody wants things quickly. Tere are more programmes, more affiliates and more data points than five years ago and everyone is fighting for positions and communication lines. Affiliates need immediate access to tracking links and everything required to begin driving traffic.


Te quicker an affiliate can be set up, the quicker they can use the brand’s link and start pushing traffic. If a programme experiences delays and has problems with links or postbacks for example then it is simply wasted time. Te best example here is postbacks and real time data demands in the market. More affiliates are demanding postbacks - real-time server-to-server notifications of key events - with richer data fields and more frequent updates, enabling them to analyse campaign performance and optimise traffic as quickly as possible.


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84  |  Page 85  |  Page 86  |  Page 87  |  Page 88  |  Page 89  |  Page 90  |  Page 91  |  Page 92  |  Page 93  |  Page 94  |  Page 95  |  Page 96  |  Page 97  |  Page 98  |  Page 99  |  Page 100  |  Page 101  |  Page 102  |  Page 103  |  Page 104  |  Page 105  |  Page 106  |  Page 107  |  Page 108  |  Page 109  |  Page 110  |  Page 111  |  Page 112  |  Page 113  |  Page 114  |  Page 115  |  Page 116  |  Page 117  |  Page 118  |  Page 119  |  Page 120  |  Page 121  |  Page 122  |  Page 123  |  Page 124  |  Page 125  |  Page 126  |  Page 127  |  Page 128  |  Page 129  |  Page 130  |  Page 131  |  Page 132  |  Page 133  |  Page 134  |  Page 135  |  Page 136  |  Page 137  |  Page 138  |  Page 139  |  Page 140  |  Page 141  |  Page 142  |  Page 143  |  Page 144  |  Page 145  |  Page 146  |  Page 147  |  Page 148  |  Page 149  |  Page 150  |  Page 151  |  Page 152  |  Page 153  |  Page 154  |  Page 155  |  Page 156  |  Page 157  |  Page 158  |  Page 159  |  Page 160  |  Page 161  |  Page 162  |  Page 163  |  Page 164  |  Page 165  |  Page 166  |  Page 167  |  Page 168  |  Page 169  |  Page 170  |  Page 171  |  Page 172  |  Page 173  |  Page 174  |  Page 175  |  Page 176  |  Page 177  |  Page 178  |  Page 179  |  Page 180  |  Page 181  |  Page 182  |  Page 183  |  Page 184  |  Page 185  |  Page 186  |  Page 187  |  Page 188  |  Page 189  |  Page 190  |  Page 191  |  Page 192  |  Page 193  |  Page 194  |  Page 195  |  Page 196  |  Page 197  |  Page 198  |  Page 199  |  Page 200  |  Page 201  |  Page 202  |  Page 203  |  Page 204  |  Page 205  |  Page 206  |  Page 207  |  Page 208  |  Page 209  |  Page 210  |  Page 211  |  Page 212  |  Page 213  |  Page 214  |  Page 215  |  Page 216  |  Page 217  |  Page 218  |  Page 219  |  Page 220  |  Page 221  |  Page 222  |  Page 223  |  Page 224  |  Page 225  |  Page 226  |  Page 227  |  Page 228  |  Page 229  |  Page 230  |  Page 231  |  Page 232  |  Page 233  |  Page 234  |  Page 235  |  Page 236  |  Page 237  |  Page 238  |  Page 239  |  Page 240  |  Page 241  |  Page 242  |  Page 243  |  Page 244  |  Page 245  |  Page 246  |  Page 247  |  Page 248  |  Page 249  |  Page 250  |  Page 251  |  Page 252  |  Page 253  |  Page 254  |  Page 255  |  Page 256  |  Page 257  |  Page 258  |  Page 259  |  Page 260  |  Page 261  |  Page 262  |  Page 263  |  Page 264  |  Page 265  |  Page 266  |  Page 267  |  Page 268  |  Page 269  |  Page 270  |  Page 271  |  Page 272  |  Page 273  |  Page 274  |  Page 275  |  Page 276  |  Page 277  |  Page 278  |  Page 279  |  Page 280  |  Page 281  |  Page 282  |  Page 283  |  Page 284  |  Page 285  |  Page 286