Forward to a Friend system token - Dealing with lead partitions
We want to utilise the forward to a friend system token however we utilise lead partitions and workspaces in our instance.
Does anyone else use the forward to a friend token and have lead partitions?
When a lead forwards to a friend who doesn't exist in the database, it creates a record for them, but because we can't put in hidden fields on the little forward a friend form such as country and brand (what we use to dictate who goes to which partition). They are automatically created in the default partition, however the default partition is not visible in the workspace the email was created in and the user has access to, so we can't see them in any reports in that workspace.
Manually managing the leads created in the default partition from the forward to a friend token isn't possible due to the size of our instance. We also have data validity programs constantly running to check the data against all leads created - so these would automatically be deleted due to only having a name and email.
Thanks ![]()