Importing profiles & accounts
Two spreadsheets fill yeon with identities. One holds your personas — the name, address, and card details typed into forms. The other holds your accounts — the logins, proxies, and per-account settings. yeon links the two, so each account arrives attached to the right persona with its proxy already set.
Both are CSV (comma-separated values), which any spreadsheet app — Excel, Google Sheets — can save.
- "profiles.csv"
- Your personas: the autofill data (name, phone, address, card), one row per persona.
- "accs.csv"
- Your accounts: logins, proxies, and flags. Many accounts can belong to one persona.
How the two files link up
Every account names the persona it belongs to. The Profile column in accs.csv must match
a ProfileName in profiles.csv — that shared name is the link. One persona can own many
accounts; each account points back at its one persona.
profiles.csv ProfileName = "Nejo 1695" ← the persona (name, address, card)
▲
│ joined on the name
▼
accs.csv Profile = "Nejo 1695" ← account 1 (login + proxy)
Profile = "Nejo 1695" ← account 2 (login + proxy)
If an account names a persona that has no row in profiles.csv yet, yeon still keeps the account
under that name — and vice versa. Import one file now and the other later; they merge by name.
Where to import
- Open the Identities settings page
Open the side panel and click Manage in settings (the launcher links there too). This opens Settings → yeon → Identities, where you import and manage everything — or paste
chrome://settings/yeon/identitiesinto the address bar. - Import profiles.csv
Find the "Profiles — per-persona logins" card and use the "profiles.csv…" picker. If you want a template to start from, "Download example" next to it saves a ready-to-edit file with the exact headers yeon expects.
- Import accs.csv as an account set
Your logins go in separately, in the Account sets box further down the same page: name the set, then pick your
accs.csv. yeon joins it to the personas you just imported by profile name. - Check the result
Your personas appear right away, each with its account count. The list has a "Filter profiles by name…" box so it stays easy to search even with hundreds of personas.
profiles.csv — the persona data
One row per persona. ProfileName is required (it is the name everything joins on); every other
column is optional — fill in what you have, and delete the columns you do not use.
| Column | What it holds |
|---|---|
ProfileName |
The persona's name, e.g. Jane Doe. Required — this is the link to accounts. |
Group |
The group the persona is filed under in the profile list, e.g. Presale. A blank cell leaves the persona's current group as it is. All is reserved and cannot be used. |
first_name / last_name |
The persona's name, split. |
full_name |
The whole name in one cell, for forms with a single name box. (A column named name works too.) |
company |
Company / organization name. |
email |
Contact email — the one typed into forms. |
phone |
Phone number. |
address_line1 |
Street address. |
address_line2 |
Apartment / suite / unit. |
city |
City / town. |
state |
State / province / region. |
zip |
ZIP / postal code. |
country |
A two-letter code (US, GB, DE) or a full country name. |
cc_name |
Name on the payment card. It does not fall back to the persona's name — set it if you want a name on the card. |
cc_number |
Payment card number. |
cc_exp_month / cc_exp_year |
Card expiry. Four digits in cc_exp_year is read as a four-digit year; anything shorter as a two-digit one. |
cc_cvv |
Card security code (CVV). |
A complete file reads:
ProfileName,Group,first_name,last_name,full_name,company,email,phone,address_line1,address_line2,city,state,zip,country,cc_name,cc_number,cc_exp_month,cc_exp_year,cc_cvv
Jane Doe,Presale,Jane,Doe,Jane Doe,Example Co,jane.doe@example.com,+12125550100,1 Example Way,Apt 4,Austin,TX,78701,US,Jane Doe,4111111111111111,08,2028,123
Marcus Lee,Resale,Marcus,Lee,Marcus Lee,,marcus.lee@example.net,+13105550188,900 Sample Blvd,,Los Angeles,CA,90028,US,Marcus Lee,4242424242424242,11,2027,456
Ana Ruiz,Presale,Ana,Ruiz,Ana Ruiz,,ana.ruiz@example.org,+13125550142,"Unit 3, 12 Test Street","c/o ""The Annex""",Chicago,IL,60601,US,Ana Ruiz,5555555555554444,02,2029,789
The third row shows how a comma and a literal quote inside a cell are escaped — the file-format rules are on Before you import.
yeon matches headers loosely, so common alternatives work too — address for address_line1,
postal or postcode for zip, cardnumber for cc_number, cvv for cc_cvv, and so on. Case and
_/space/hyphen spelling do not matter. The names above are the ones "Download example" produces,
so they are the safe choice.
accs.csv — the accounts
One row per account. Profile and Email are the ones you will always want; the rest are there
if you use them. Leave Profile blank and yeon files the login under its email address as the
persona name; a row with neither is skipped.
| Column | What it holds |
|---|---|
Profile |
The persona this account belongs to — must match a ProfileName. The join key. |
Email |
The account's login email. |
Password |
The account's password. |
Proxy |
This account's proxy — host:port, host:port:user:pass, user:pass@host:port, or a full scheme://… URL using http, https, socks5 or socks. Blank means the account has no proxy of its own. See Proxies. |
PhoneNumber |
The account's phone number. |
otp_source |
Where this account's sign-in code arrives — see below. |
otp_number |
The number a text code is sent to, when otp_source is an SMS provider. (sms_number is a spelling of the same column.) |
AycdTemplate |
Which AYCD template supplies the code. |
Tags |
Optional labels for this account, separated by ; (for example presale;eu). Spaces around each tag are trimmed, and a tag repeated in a different case is kept once. Use them to find a list or an account by tag in Accounts. A file without this column imports with no tags. |
A complete file reads:
Profile,Email,Password,Proxy,PhoneNumber,otp_source,otp_number,AycdTemplate,Tags
Jane Doe,jane.doe@example.com,ExamplePassw0rd1,203.0.113.10:8080:proxyuser:proxypass,+12125550100,imap,,,presale;eu
Jane Doe,jane.doe+2@example.com,ExamplePassw0rd2,203.0.113.11:8080,,,,,
Marcus Lee,marcus.lee@example.net,ExamplePassw0rd3,http://proxyuser:proxypass@203.0.113.12:8080,+13105550188,sms:smspass,+13105550188,,presale
otp_source — routing the sign-in code
This one column decides where yeon looks for that account's one-time code. Leave it blank for accounts that do not need one.
| Value | Where the code comes from |
|---|---|
imap |
The master IMAP mailbox you set up once in settings. |
aycd |
Your AYCD inbox. |
sms:<provider> |
A text message, read through that provider — sms:smspass, sms:seatheroes, sms:smsgateway, sms:texttrove, sms:textchest, sms:quicktext. Pair it with otp_number. |
The key or login for whichever source you use is entered once in Settings → yeon → Identities → "API keys & Email (IMAP)" — see OTP autofill.
How it powers autofill
Once imported, a persona's details feed the persona autofill hotkey, CmdCtrlShiftF. Focus a checkout or sign-up form, press the hotkey, and yeon types in the persona's name, email, phone, full address, and card details in one shot. (It never types your password into a page for you.) The same details are also loaded into the browser's built-in autofill, so the normal autofill dropdown works too.
The fill always uses the persona that owns the tab you are in. Press the hotkey inside identity A's tab and you get A's details; inside identity B's tab, B's — never a mix-up between accounts.
Good to know
- Your data stays on your machine. Personas and accounts are stored locally in yeon. Nothing is uploaded.
- Re-importing is not the same for both files. A
profiles.csvrow replaces the persona of the same name;accs.csvrows are added without de-duplication. The details are on Before you import. - Extra columns become custom fields. In
profiles.csv, any column yeon does not recognise is kept on the persona as a custom autofill field rather than thrown away — so your own bookkeeping columns survive the import. Inaccs.csv, unrecognised columns are ignored.