For school administrators using GiveCampus Outreach. Controls can differ between the classic email editor and the newer Composer editor.
A valid recipient token can coexist with supported designation URL parameters. Current precedence is retained session designations, then URL/legacy-token designation values, then personalized-workflow designations, then tier/form defaults. Values must resolve on the target form and are limited by its maximum selections. Test in a fresh session. The current token resolver loads a person and workflow at request time, and the workflow supplies its current personalization and ask configuration; creating a token should not be described as freezing all donor information forever. Invalid tokens, missing records, cross-school records, or incompatible forms do not guarantee personalization. Keep links recipient-specific and private. Imported and dynamic ask configurations require the workflow's supported controls.
Comments
0 comments
Please sign in to leave a comment.