Overview
Cryptique tracks data from two sources: websites (sites) and blockchain smart contracts. This guide covers how to configure and manage both.Sites
Sites are the websites or web applications you want to track with Cryptique.Adding a Site
Configure Site
- Name: Human-readable name (e.g., “Production App”)
- Domain: Your website domain (e.g.,
app.example.com)
Site Configuration
Multiple Sites
One team can have multiple sites:- Separate production and staging
- Track multiple products
- Different domains for different regions
Domain Whitelist
For security, Cryptique only accepts events from whitelisted domains:Site Settings
| Setting | Description |
|---|---|
| Auto-enhance | Enable/disable wallet enrichment |
| Auto-events | Default auto-event configuration |
| Allowed domains | Domains that can send events |
| Data retention | How long to keep event data |
Smart Contracts
Smart contracts let you track on-chain transactions and link them to user behavior.Adding a Contract
Enter Details
- Name: Human-readable name (e.g., “Swap Router”)
- Address: Contract address (e.g.,
0x1234...abcd) - Chain: Select blockchain network
- ABI (optional): Contract ABI for method decoding
Contract Configuration
Supported Chains
Cryptique supports 35 chains for smart contract tracking:EVM Chains
EVM Chains
- Ethereum
- Polygon
- Arbitrum
- Optimism
- Base
- Avalanche
- BNB Chain
- Fantom
- Gnosis
- And more…
Layer 2s
Layer 2s
- Arbitrum One
- Arbitrum Nova
- Optimism
- Base
- zkSync Era
- Polygon zkEVM
- Linea
- Scroll
- And more…
Contract Naming
Use consistent names across contracts for cross-protocol analysis:- Filter by contract name across all chains
- Compare performance across chains
- Create unified reports
ABI Upload
Upload the contract ABI to decode method names and parameters: Without ABI:Multi-Chain Contracts
For contracts deployed on multiple chains, add each deployment:Data Flow
Site → Contract Attribution
When a user:- Visits your site (tracked via Site ID)
- Connects their wallet (captured via SDK)
- Makes a transaction (tracked via Contract)
Cross-Site Tracking
If a user visits multiple sites with the same wallet:Managing Sites & Contracts
Edit Configuration
- Go to Settings → Sites or Contracts
- Click the item to edit
- Modify settings
- Save changes
Archive vs Delete
Archive: Stops tracking new data but preserves historical data Delete: Removes configuration (historical data retained per retention policy)Status Monitoring
Check health of your sites and contracts:Best Practices
Site Organization
Contract Organization
Security
- Keep Site IDs confidential (treat like API keys)
- Use domain whitelisting
- Regularly audit active sites and contracts
- Remove unused configurations
Troubleshooting
Events not appearing for site
Events not appearing for site
- Verify Site ID in tracking code
- Check domain is whitelisted
- Ensure SDK is loading correctly
- Check browser console for errors
Contract transactions not tracked
Contract transactions not tracked
- Verify contract address is correct
- Check chain selection
- Ensure contract is active on-chain
- Wait a few minutes for indexing
Method names showing as hex
Method names showing as hex
Upload the contract ABI to decode method names and parameters.
Cross-chain data not linking
Cross-chain data not linking
Ensure contracts use the same Name across all chains for unified reporting.
Next Steps
Smart Contract Indexing
Deep dive into contract tracking
Wallet Enrichment
Enrich user profiles with on-chain data