- This topic has 7 replies, 3 voices, and was last updated 9 years, 6 months ago by .
Viewing 8 posts - 1 through 8 (of 8 total)
Viewing 8 posts - 1 through 8 (of 8 total)
- You must be logged in to reply to this topic.
Support site for Tips and Tricks HQ premium products
by
Tips and Tricks HQ Support Portal › Forums › WP eStore Forum › eMember – {first_name} {last_name} on automated bulk email not working
Tagged: first name
Our first e-member automated emails went out last week for – ‘Email Before the Account Expires’. However the {first_name} {last_name} did not work and names were not substituted. How can I rectify this?
Email tags are not available for bulk messages:
If that is the case why is this set as the default for this type of email?
What do you mean by “set as the default for this type of email?”
When this plugin was installed the these shortcodes were already written into the default email messages. This works fine for new registration and other automated emails but does not appear to work for the reminder emails before and after membership expires.
That’s because certain email tags are only available when an IPN is being processed. The email messages you want to use the tags in are batch messages, which are not the result of an IPN being processed:
I am having the same issue. It was very embarrassing. Can these be changed to be IPN, rather than bulk? Would even pay a fee to do so!
This information is only available during IPN processing, which only takes place at the time of purchase.
In the case of eMember, please realize the name of the person captured during the IPN (purchase) is not necessarily going to be the same as the name of the registered member; which is captured during the registration process. Case in point; the name returned during the IPN might be “Calvin Broadus,” because that’s the name on his credit card, but you can be sure he’ll put down “Snoop Dogg” after he clicks the registration link.
And because we allow you to make member first/last names optional on the registration form, imagine the embarrassment that would result if some members did not fill in those fields; and we added {profile_first_name} and {profile_last_name} email tags.