"This is the third time you've asked me for my phone number.
It feels kind of inefficient."
But as you can see, this is one of those people going through the program we created, and, unfortunately, Heartbeat doesn’t have enough functionality to meet the needs of the people in this program.
As for the embed code, I don’t know how well it will work, I’m just worried it won’t work on Apple smartphones, because none of the videos work except for these ones.
I’d like it to work, but it just doesn’t.
Another point is that - as this person pointed out - the issue is that when redirecting to an external link, you haven’t configured the ability in any way, nor have you provided me with an explanation of how to do it or how it’s implemented, so that any existing client identifier can be passed along in some way, so that it could at least be tracked more effectively, or even just so I’d have an external identifier that I could link to. I mean, to have some kind of identifier within the Heartbeat system that could, say, be attached to links - which, in principle, can be any kind of link.
Or when we insert a link, so that they generate a tracking link. Why?
Because when I ask a person for their email address upon entry, they’re then redirected to the website, since there isn’t enough functionality on Heartbeat. They go to the website, and we ask them for their email address and phone number again. Then they go back to Hartbeat, go through a few more lessons, and there’s the same form again, asking for their email and phone number. Why? Because we have no way to verify that the person who clicked on this particular lesson is actually the same person who clicked on that link, or that it was this specific customer who clicked on that link.
Conversely, when a customer returns to the site - or, conversely, when a visitor returns to our customer's or partner's site - that person is on our site, and we embed a link with an additional identifier so that this person is redirected to Heartbeat, thereby closing the loop. First, we receive the ID of the person who arrived and who left, and when they click on the links, they send a signal to Heartbeat confirming that the person has returned. I understand that, again, Apple devices may block certain identifiers when clicking on links, but having this option, the ability to capture information about the current user in some way, is essential.
Perhaps it would be great if you could implement microlinks, that is, micro-links, so that, for example, there are various link-tracking services, such as pxl .to.
The convenience there is that when a user clicks, they’re simply redirected. In other words, they’re simply redirected, and everything works smoothly. They follow a unique link without any identifiers, and as far as I recall, these links don’t get lost on iPhones or other devices where they’re usually cut off immediately. So you click a direct link, and then it goes through the affiliate link, and everything works. This needs to be verified, but that’s the general idea, and it seems to me that it’s worth giving this some serious thought, perhaps to find a way to incorporate additional features after all.
Log in to comment and vote
Comments1
Social Capital System
Aug 30
"This is the third time you've asked me for my phone number.
It feels kind of inefficient."
But as you can see, this is one of those people going through the program we created, and, unfortunately, Heartbeat doesn’t have enough functionality to meet the needs of the people in this program.
As for the embed code, I don’t know how well it will work, I’m just worried it won’t work on Apple smartphones, because none of the videos work except for these ones.
I’d like it to work, but it just doesn’t.
Another point is that - as this person pointed out - the issue is that when redirecting to an external link, you haven’t configured the ability in any way, nor have you provided me with an explanation of how to do it or how it’s implemented, so that any existing client identifier can be passed along in some way, so that it could at least be tracked more effectively, or even just so I’d have an external identifier that I could link to. I mean, to have some kind of identifier within the Heartbeat system that could, say, be attached to links - which, in principle, can be any kind of link.
Or when we insert a link, so that they generate a tracking link. Why?
Because when I ask a person for their email address upon entry, they’re then redirected to the website, since there isn’t enough functionality on Heartbeat. They go to the website, and we ask them for their email address and phone number again. Then they go back to Hartbeat, go through a few more lessons, and there’s the same form again, asking for their email and phone number. Why? Because we have no way to verify that the person who clicked on this particular lesson is actually the same person who clicked on that link, or that it was this specific customer who clicked on that link.
Conversely, when a customer returns to the site - or, conversely, when a visitor returns to our customer's or partner's site - that person is on our site, and we embed a link with an additional identifier so that this person is redirected to Heartbeat, thereby closing the loop. First, we receive the ID of the person who arrived and who left, and when they click on the links, they send a signal to Heartbeat confirming that the person has returned. I understand that, again, Apple devices may block certain identifiers when clicking on links, but having this option, the ability to capture information about the current user in some way, is essential.
Perhaps it would be great if you could implement microlinks, that is, micro-links, so that, for example, there are various link-tracking services, such as pxl .to.
The convenience there is that when a user clicks, they’re simply redirected. In other words, they’re simply redirected, and everything works smoothly. They follow a unique link without any identifiers, and as far as I recall, these links don’t get lost on iPhones or other devices where they’re usually cut off immediately. So you click a direct link, and then it goes through the affiliate link, and everything works. This needs to be verified, but that’s the general idea, and it seems to me that it’s worth giving this some serious thought, perhaps to find a way to incorporate additional features after all.