Post by account_disabled on Dec 8, 2023 20:41:26 GMT -8
Mistake Using automation to do things Does it happen to you too? It is a very bad practice to have an automation that does many things. Because? Well, it is much worse in terms of keeping track. A very long automation is much more difficult to “read” . In too extensive automation it is more difficult to test . Also, if your automations are too long, if you need to “turn off” many people will be left “hanging” . You should think of ActiveCampaign automations as if they were Lego pieces . Where you should look for your “pieces” to be as specific as possible.
If you have ever played with Lego pieces, seen them play or at least know photo editing servies what pieces I am talking about, you will know that, for example, if I want to build a car, there are pieces that have the wheels, other pieces will have the doors, etc. They are specific pieces . Well, if you create specific “pieces”, for example, to sell, to invite to a webinar, to manage the placement of a label, etc.
It will be easier for you to replace one of those “parts” when something is not working well . Furthermore, the readings of these new smaller and more specific “pieces” will be much easier and more agile . At any time you will know exactly what each automation does . You won't have to stop and think to see if automation does this, that, and maybe that too. In short, use short, concrete automations and try to make them easy to read.
If you have ever played with Lego pieces, seen them play or at least know photo editing servies what pieces I am talking about, you will know that, for example, if I want to build a car, there are pieces that have the wheels, other pieces will have the doors, etc. They are specific pieces . Well, if you create specific “pieces”, for example, to sell, to invite to a webinar, to manage the placement of a label, etc.
It will be easier for you to replace one of those “parts” when something is not working well . Furthermore, the readings of these new smaller and more specific “pieces” will be much easier and more agile . At any time you will know exactly what each automation does . You won't have to stop and think to see if automation does this, that, and maybe that too. In short, use short, concrete automations and try to make them easy to read.