Audiences
How to create and use Audiences with Studio Apps
Last updated
Manifold Studio
How to create and use Audiences with Studio Apps
Last updated
Manifold Audiences allows you to easily build a customized list of wallet addresses based on token ownership rules that can be saved and re-used at any time to generate new snapshots and gates.
Audience presets allow you to easily indicate your own collectors as a target, whether an individual contract or all your work combined (by network).
The custom audience builder enables rule creation by network and contract address, with additional segmentation options for identifying token IDs/ranges and even individual token attributes.
Multiple rules can be added to an audience combining various networks, contracts, tokens and attributes. Audiences are saved and can be referenced and edited at any time to generate new snapshots and content gates
Since NFTs can change hands at any time itâs important to get the latest picture of on-chain information. This means taking a âSnapshotâ at a specific date and time to understand which wallets meet the criteria of your Audience.
Snapshots can take up to 30 minutes to run. Be sure to add your email address to your studio settings and we'll send you an email notification when your snapshot is complete. Once complete, use the "Preview Audience" button to visualize the wallet and mint value for each address.
The default values from a snapshot will give each wallet the ability to claim one token per token held.
Snapshots generated via Manifold Audiences will always be available for future use via "Existing Snapshot" selector.
CSVs can be uploaded to the Audience Builder as a standalone allowlist or as an addendum to a custom audience/snapshot. Be sure the file includes the following fields:
address: the wallet addresses that are allowed to claim (ENS addresses are not supported)
value: a value indicating how many tokens can each wallet claim.
Check out this CSV as an example.
Note when adding additional entries via CSV to an Audience Snapshot, any duplicated addresses will act as an "override", making the value specified in the CSV the go-forward value for an address for the final allowlist.
