Tokens allow you to add personal touches to actions and emails within Impact Stack. They might be as simple as adding the supporter's name to the salutation line in a thank you email, e.g.
"Hi John, thanks for signing the petition".
But they can also allow you to do more complex things, like customise the email sent to MPs with details about both the MP and the supporter, e.g.
"Dear *MP salutation*,
Like many people in *Constituency*, I care about this issue. This issue matters to me because *user comment*.”
The tokens themselves are simple pieces of code that act as place-holders for this supporter/target information. Tokens are transformed into the related piece of information before the user sees them, so your supporters will never see them in their ugly code form.
How do they work?
Tokens take a piece of information from the Impact Stack system and allow you to display it in a progress bar,later form step, email to the supporter or an email to target. In order for you to be able to add a piece of information using a token, it has to already be stored either in Impact Stack itself or in the user's session.
This means that when you want to use supporter data, you must have first stored that data in the session. In other words, the user has to have entered this information and clicked on a submit button. So you can only display information using tokens from the second page of your action onwards. They won't work on landing pages.
Finding the right token
The format of the token you need depends on where you're using it. Token formats that work in emails won't work on landing pages for example. Usually default text or contextual help will show you the tokens you can use, but follow the links below to find out more about how the different ways you can use tokens.