How Kevin changed the worldHow Kevin changed the world
How would you design a notification push for a Web community product?
For web products, we usually use EDM or browser push as message reminder due to special product usage scenarios (in PC scenarios, not mobile). At present, mobile terminal products consider that message reminder will be based on the product system of ios or Android, and the message of Web products is based on the in-site message or EDM to reach.
The push background of in-site letter is similar to that of APP products, and the push background should contain the push content of system and operation.
System push includes:
-
Business content
-
Social content
-
System Message content
Business content is hard to distinguish from system messages. For example, when we do bracelet binding, the disconnection reminder after bracelet disconnection belongs to the system message content. It also belongs to the user service scenario in the health management service.
Social content refers to content created by other users in the product, such as likes, comments, retweets, and following….. Social content is more of a community product than a web product, and it is hard to find a Web product that is a tool product. Regardless of the link to the user
Note that in personal Center, added whether to allow message notification function. System messages should also be closed. For example, system message content is not allowed to be closed.
I made a mistake when I led my team to do EDM. Let the team do their own EDM messages. As a result, the following problems emerged
-
Email sending failure
-
Message failed to arrive
-
The message arrived in garbled characters
-
Email editing is not flexible, push crowd customization is not flexible
-
Mail becomes spam
The above five problems, the fourth problem can also be considered from the product optimization. Add corresponding editor functions and crowd customization. But for other problems, technology is required. This cost a lot of development resources and time, resulting in a second release after the final iteration that addressed the delivery failure. But garbled, spam mailbox is still hard to avoid.
I suggest that product managers should first investigate third-party resources when making standard modules (such as message push, mall system, OA, etc.). For example, EDM has a mature platform, SendCloud, and a free daily push quota. You only need to connect to the SDK to ensure the use effect of the product.
Of course, if the push volume is large or personalized. You can still consider doing it yourself, but if you do, you may want to avoid the following six problems.
1. Carrier interception.
Pay attention to common channels and marketing channels. Ensure that one of the two channels can be whitelisted on the carrier. Marketing channels should pay attention to the problem of sealing, so to replace multiple accounts sent
2. The frequency of marketing emails.
Marketing email content is usually 1-3 times a week, not at any time
3. It is important to send at a uniform speed.
Triggering a large number of emails at once (10,000 or more) is likely to be considered an attack and the carrier will take direct action. So the total amount can be large, but ideally under 1,000 emails per second.
4. External link display page is a must.
When I have personally checked, a lot of online email display effect is probably not as good as expected, need in the above email plus a “if the mail can’t show, please click (reissue) | 1 month 30 days, 720 hours, 134 product managers do? “(The blue” heading “should point to a link that should be placed on a mail display page on the website)
5. Try not to use a large image as it will load slowly.
Add rich text to the editor whenever possible, and don’t push large images all at once. The loading fails
6. Email tracking problems.
The success rate of opening and sending emails requires background statistics
References:
https://www.pmcaff.com/discuss/index/194062147180608
Well, that’s our original for today. I try to write two original work cases every week
Recommended reading:
Do it for a year and recruit 100 product managers
My first book. Here it is