"We really need the ability to manually choose the correct tribute in webview when multiple exist" -- yes, this 100%!

The current NXT Tribute match process, which occurs before we have a chance to review submissions, is causing a significant increase in daily clean-up work. With the high volume of tributes we receive, the lack of a review step is making it difficult to manage accuracy and data integrity efficiently.

It would be extremely helpful to have an option that allows users to choose between automatic matching or a review-first process. This added flexibility would streamline our workflow and reduce unnecessary corrections.

If the ability to review before matching is not implemented, we may need to reconsider using the NXT forms altogether.

I was batching two tribute gifts this morning in NXT. The tributes needed to be created before I could link the hon/mem (which I did in DBV to save time), and I had such a hard time trying to get the name of the hon/mem to populate in the search bar. Searching by last name and/or using an asterisk ("Do*, Joh*) is essential. It also wouldn't recognize the relationship under the hon/mem as being the notification recipient, no matter that it came up as a suggested duplicate.
I also had a donor who passed away in Feb 2025, but all the gifts were linking to a different donor that passed in 2020 (granted they did have the same name). I believe we should be able to review every tribute gift before it is linked, and also be able to edit it while editing the batch.

Thanks Samantha! Appreciate this and all you do!

This feature has been shipped. I see some comments have been added since release - I am passing those onto the product manager for this area. We are also actively reviewing feedback from the survey that pops from the Online Data Review tool, and encourage additional ideas to help us further refine reviewing and matching tributes in Online Data Review!

I appreciate the intent behind the Match Tribute Gifts in Online Data Review feature, but like you, I’ve found it’s not saving time and may even introduce more risk of error. We really need the ability to manually choose the correct tribute in webview when multiple exist—auto-assigning just isn’t reliable in complex cases.

Also, I’m looking for a simple way to view all gifts associated with a specific tribute in webview. In database view, it’s easy under the “Honor/Memorial” tab, but I haven’t found an equivalent in webview yet. If anyone has a workaround or insight, I’d love to hear it!

According to this blog post, the Match Tribute Gifts in Online Data Review feature has been turned on.

Suggestion: Please allow users to select the correct tribute from a list when multiple tributes exist on a record — rather than auto-assigning. This would save time, reduce errors, and give us better control over gift processing.

I dealt with my first gift using this tool this morning, and unfortunately, it didn’t save me any time.

The gift was for a record with 18 tributes (our school’s main record – we use separate tributes for faculty, departments, classes, etc.). At no point was I able to select the correct tribute. It defaulted to the only inactive tribute out of the 18.

To complete the process, I had to:

• Go to the record and make the inactive tribute active,

• Approve the gift batch (still unable to change the tribute),

• Then open the gift in database view to delete the incorrect tribute and manually add the correct one.

So, while it didn’t create a duplicate record, it was actually less functional. At least when a new record was created, I knew something needed fixing. Now I might easily miss that the tribute is wrong.

While having 18 tributes is unusual, having both an “in honor of” and “in memory of” tribute for the same person is common. When someone passes, we inactivate the “in honor of” – which this tool seems to default to.

I’ve opened a case and said I would share this in the idea bank. If you haven’t already, please vote!

This is getting extremely cumbersome to keep merging duplicates that are added as Tributes and/or those needing to receive Acknowledgement of the tribute gift. You have to let the tribute information be editable within gift processing and not auto add these as new Constituent records.

When a constituent makes a donation in honor / memory of someone outside of our database there is not a way to record this tribute. The tribute section only allows it to be in the constituents honor / memory. We would like to record if the constituent makes a donation in someone's honor or memory so we can pull this information for our end of year records.

Hi Samantha - for all tributes we would ask to capture the title and honor memorial name in separate first and last name fields. For in honor of tributes we currently capture address and would ask to add an option for email, as well as an email for the acknowledgee. If I am correct, constituent matching currently looks for name, email and address? Are there any additional recommended fields for a memorial tribute without that information? Anything that the data review tool would look for we would be open to capturing to have the best match results.

We are currently in development adding tribute matching into the Online Data Review, with a planned release last Q1/early Q2.

What additional fields would you want to collect related to a tribute honoree/acknowledgee?