Ahhh, OK, I just tried it and think I have discovered my potential challenge and reason why I thought tags on the fly might be a solution.
If I understand the process correctly, the data (in this case a Query Ref No) which I would like captured in the webform e.g. 2019abc123, will need to be added to an existing default or custom field. Thereafter it can be referenced in an email sequence via a merge field.
My challenge is that a contact may have multiple Query Ref No’s which will be referenced throughout various parts of different email sequences so, if the field value is changed on a subsequent form submission, all emails, including those already in a sequence will reference the changed field value which is undesirable.
- Consultant submits a Webform with Contact FName, Contact LName, Contact Email and Contact Query Ref No. details
- The “Web Form Submitted” initiates an email automation sequence to the Contact containing the Query Ref No in Subject and Body of a series of sequence emails based on decision diamonds
- Contacts may have multiple Query Ref No’s and be in multiple sequences simultaneously but there will only be one Query ref No per sequence they are in.
I hope that this better explains my scenario and that there is still a workable solution?