|
psep_admin
|
November 28, 2022 at 6:44 am
I’m trying to reduce the number of emails our clients receive when registering for events by including the Ticket Notification link [TXN_TICKETS_APPROVED_URL] in the Registration Approved email. I’ve transferred the shortcode and surrounding coding directly from the corresponding email (from recipient ticket notice default email to recipient registration approved custom email and from primary recipient ticket notice default email to primary recipient registration approved custom email) but both recipient and primary recipient registration approved custom emails produce a link to all the tickets from the transaction as if they were both primary registrant. How can I change this so recipients only receive their respective tickets when using [TXN_TICKETS_APPROVED_URL]? Does this need to be preceded by the shortcode for the registrant’s name or something?
|
|
Tony
|
November 28, 2022 at 2:21 pm
Hi there,
[TXN_TICKETS_APPROVED_URL] will always pull all of the Approved tickets linked to the transactions regardless of which registrant generates the link.
For specific registrant links you’ll need to use [TICKET_URL] or [RECIPIENT_TICKET_URL] (both are functionally equivalent but RECIPIENT_ is usable in more fields).
|
|
psep_admin
|
November 28, 2022 at 2:49 pm
Thank you.
Will they link all tickets or only tickets for approved registrants?
We have some transactions where people bought multiple tickets, then wanted to cancel/return part of the order. This resulted in some canceled registrants who are still connected to a given transaction because of the return history.
|
|
Tony
|
November 28, 2022 at 3:13 pm
I think we are conflicting with the intended behaviour here.
Will they link all tickets or only tickets for approved registrants?
All tickets? The above should only link to the specific registrant in question so it wouldn’t list all tickets.
Unless I’m misunderstanding the question here, apologies if so.
If you are triggering the registration approved message that the registration in question must be approved and not cancelled, right?
|
|
psep_admin
|
November 28, 2022 at 4:09 pm
Sorry, I am also working on an automated upcoming event email custom template where I am trying to do something similar, and I was mistakenly thinking of that when I asked that question.
|
|
psep_admin
|
November 28, 2022 at 4:14 pm
I can create a separate thread for questions related to automated upcoming events emails tomorrow to avoid confusion.
Thank you for your help with the Registration Approved email!
|
|
psep_admin
|
December 2, 2022 at 1:30 pm
In my registration approved emails, I’ve added [TXN_TICKETS_APPROVED_URL] to the primary recipient email and [RECIPIENT_TICKET_URL] to the recipient email. My hope is to reduce emails by combining elements of registration approved and ticket notice.
I’ve tested these on fake recipients in a fake event. The links produced the appropriate tickets in groups where all recipients registered for a single ticket. However, I had a scenario where one recipient registered for more than one ticket and did not get all of their tickets in the recipient email.
Here’s a description of that scenario: In the same event, I registered a group where User1 bought Ticket A and Ticket B and User2 bought Ticket A.
The primary registrant email went to User1 and linked all three tickets from the transaction, great. The registrant email for User1 linked Ticket A but not Ticket B, not great. The registration email for User2 linked to Ticket A, great.
In this scenario, it’s not a big deal because User1 did get the missing ticket in the primary recipient email. However, we often have large groups where individuals may be registering for more than one ticket and are not the primary recipient, so I want to make sure registrants get all of their correct tickets.
What can I change to correct the issue where a user buying two tickets for the same event receives only one of the two tickets in the registrant email?
|
