Over-writing contact records

Options

Hi! I'm interested in talking to other TeamRaiser users to hear how you have overcome the known issues with auto-login and overwriting contact records both in Luminate Online and outside LO via the Connector/Service Bus. Anyone out there?

Tagged:

Comments

  • Any pointers to info on this issue? I've not heard of it, nor noticed it happening with our events...but sounds worrisome.

  • Andrew Beyer:

    Any pointers to info on this issue? I've not heard of it, nor noticed it happening with our events...but sounds worrisome.

    Hey, Andrew,

     

    My colleague actually posed this problem to community a while back.  Here is the summary of the issue: http://community.convio.com/t5/Luminate-Online/Autologin-and-over-writing-of-constituent-data/m-p/64568#M14483

     

    Is autologin is enabled and emails are forwarded, the recipient can overwrite the sender's contact information in Convio when they register for an event.  We can turn off autologin, but I am nervous about how that will impact our registration rates.  

  • Rabia Syed:

    Hey, Andrew,

     

    My colleague actually posed this problem to community a while back.  Here is the summary of the issue: http://community.convio.com/t5/Luminate-Online/Autologin-and-over-writing-of-constituent-data/m-p/64568#M14483

     

    Is autologin is enabled and emails are forwarded, the recipient can overwrite the sender's contact information in Convio when they register for an event.  We can turn off autologin, but I am nervous about how that will impact our registration rates.  

    Oh, I see...you mean if a message w/ autologin gets forwarded to other people who then use the links.

     

    I typically just avoid using autologin when possible. If we do use it, I push the content people to write all the links w/ some personalization. That tends to catch peoples eye more than just a "don't forward this" note in the message. (though that should probably be there too.)

     

    eg make the text of your autologin links things like: "Bob's personal invitation to join us" or "Access Judy's Participant Center"

  • Andrew Beyer:

    Oh, I see...you mean if a message w/ autologin gets forwarded to other people who then use the links.

     

    I typically just avoid using autologin when possible. If we do use it, I push the content people to write all the links w/ some personalization. That tends to catch peoples eye more than just a "don't forward this" note in the message. (though that should probably be there too.)

     

    eg make the text of your autologin links things like: "Bob's personal invitation to join us" or "Access Judy's Participant Center"

    Great ideas there Andrew.

     

    Rabia, what kind of data are you losing? (We don't use autologin much at all.) I thought that accessing the participant center or user profile required authenticating even with an autologin link, for this very reason. I do think this is an issue with unsubscribes, and probably surveys. Where else is this problematic?

     

    Honoring a do-not-forward flag should be a standard feature on all email clients.

     

    I've often wondered if there was some change we could exploit to modify content in forwards. Perhaps encoded characters are no longer encoded in forwards or something like that.

     

    I've also thought it would be cool if Convio sent a confirmation email in response to unsubscribes from forwards. That should be easy to do. What are your opinions on that idea? Email confirmations to people not wanting email are annoying, but in this case it seems worth it.

Categories