Timeline for Journey uses engagement split but number of opens are not getting captured accurately
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 3, 2019 at 23:16 | answer | added | Jackson Chen | timeline score: 1 | |
| Mar 29, 2019 at 9:42 | comment | added | Johannes Schapdick | AFAIK tracking pixels are inside the standard templates of salesforce. When you decide to create an own template you should be knowing what you do. tracking pixels and other functionalities are very easy to see when you edit a template. HTML editor -> </> Symbol -> and you find many of the system snippets of salesforce when you scroll down past your own. | |
| Mar 29, 2019 at 9:38 | comment | added | Krati Garg | In that case, we cannot rely on Engagement Split, right? SFMC should specify this in their documentation because if anyone refers this: help.salesforce.com/… and uses engagement split, they will almost never get expected results. According to me this is a major loophole in this functionality. They haven't even mentioned about tracking pixel in the above documentation, so if someone doesn't go through this help.salesforce.com/articleView?id=000249050&type=1, they will end up getting inaccurate results. | |
| Mar 29, 2019 at 8:10 | answer | added | Markus Dang - formerly Slabina | timeline score: 1 | |
| Mar 29, 2019 at 7:17 | comment | added | Johannes Schapdick | You can never accurately monitor opens. That should be something you should be aware of. First people with active AdBlocker will never show an open state, neither do people where you had to respect their wish to be not tracked (DoNotTrack Newsletter criteria). Furthermore many firewalls inspect emails and therefore open them. That said you cannot be sure if a person has open or not opened an email. And one extend: You can change an email within a running journey and put your tracking code inside of it and update the activity. | |
| Mar 29, 2019 at 6:54 | history | asked | Krati Garg | CC BY-SA 4.0 |