How to Use Detected Attributes on Privy

Privy’s current documentation calls this area Profile Attributes. Find it in a display’s Settings → Show Advanced Settings. Use these fields to inspect signup context and prepare data for later segmentation or a connected service.

This guide follows Privy’s Profile Attributes documentation, checked September 6, 2026. It replaces the old hidden-field screenshots with the current settings terminology; it does not assume every historical builder control still exists.

Decide which information you need

Privy defines a session as ending after 30 minutes of inactivity. Its Current URL description is not a promise of original acquisition attribution. Keep initial landing context and signup context separate in your reporting.

Configure and submit a controlled test

1. Open the intended display’s advanced settings and inspect Profile Attributes.
2. Configure the relevant attributes or custom field for your use case, then save the display.
3. If data should go to another service, review that display’s Sync Integrations rules and destination mapping.
4. Submit a new test contact from a page whose URL and campaign context you recorded.
5. Inspect the resulting contact in Privy before checking any downstream destination.

For example, you could test a page with utm_medium=email and record the exact URL used. This is a diagnostic example, not a recommendation to overwrite production attribution. Do not infer a value from an earlier landing page without checking what the contact actually stores.

Verify each destination separately

Privy documents attributes on contact records, CSV exports and linked-account data when syncing signups. That gives you three checkpoints; it does not guarantee that every destination accepts every field without configuration.

Use one identifiable test record through the whole flow. An address arriving successfully does not prove its custom properties arrived. Likewise, a correct property does not by itself establish email subscription status or successful follow-up delivery.

Avoid confusing attributes, tags and targeting

Profile Attributes concern collected context. Signup tagging applies Privy tags when a person signs up. Audience Targeting controls who is eligible to see the display. Choose the setting that matches your objective rather than expecting a saved field to automatically change campaign visibility.

The current source lists specific Profile Attributes but does not provide a complete hidden-field implementation contract. If you need an unlisted value or custom browser-side collection, confirm the supported method before implementing it.

Continue with Privy audience targeting or review Privy integrations for destination-specific setup.