> For the complete documentation index, see [llms.txt](https://help.smartico.ai/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smartico.ai/welcome/products/crm-automation/activities-of-flows/activity-save-state.md).
# Activity: Save State
Save State is a campaign flow step used to **capture and store dynamic data at a specific moment**. Once saved, this data becomes accessible throughout the rest of the flow and can be reused for logic checks, personalization, or tag replacement inside creatives.
When triggered, Save State stores the current value of a property - whether it's a campaign-triggered value (like Bonus Amount, Casino Bet) or a user attribute (such as First Deposit Date, Registration Date, or Language). These saved values can then be referenced using tags like {{campaign.xxx}}, allowing operators to inject them into assets, communications, or conditional logic.
{% hint style="warning" %}
Campaign tags can't be used in Java Script functions, only public tags (markers) can.
{% endhint %}
Save state is especially useful when you need to preserve a value at a specific point in time and ensure consistency across later stages of the campaign, even if the original source changes.
### Use case scenario
There are many cases when the campaign starts on some particular action but the communication about it only comes way later. Let’s say the campaign starts on a minigame win, and then you want to use the name of the minigame prize won in the communication to users. But first you need to check for the preferred communication method, unsubscription, etc. So there’s bound to be at least one step between the campaign start and the communication sendout. And to enable the usage of a dynamic property “Minigame: prize name“ - we can use the “save state” step.
\
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.smartico.ai/welcome/products/crm-automation/activities-of-flows/activity-save-state.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.