Reserved fields that can't become custom fields

When importing a subscriber list into beehiiv, some data fields are reserved and can’t be used or renamed as custom fields. These reserved fields are built into beehiiv for core functionality — but they can still be used as merge tags to personalize your email posts.

Use the lists below to identify which fields are reserved so you can rename or adjust your data before importing. Click each section to view details.

Reserved custom fields related to subscriptions

active_subscriber_count

api_subscription_id

email

hostname

jwt_token

list_unsubscribe_token

live_url

opt_in_token

publication_alphanumeric_id

publication_name

publication-name

publication_name_param

report_abuse_token

resource_id

reward_promo_code

subscriber_email_hash (uses MD5 encryption)

subscriber_email_hash_sha1

subscriber_email_hash_sha256

subscriber_id

subscriber_preferences_url

subscriber_refer_url

subscriber_referral_hub_url

subscription_id

subscription_uuid

Reserved custom fields related to the Referral Program

rp_display_with_milestone_styles

rp_display_with_no_milestone_styles

rp_next_milestone_name

rp_num_referrals

rp_num_referrals_until_next_milestone

rp_next_milestone_image_styles

rp_next_milestone_image_url

rp_personalized_text

rp_referral_hub_url

rp_referral_code

rp_refer_url

rp_refer_url_no_params

rp_upcoming_milestones

Reserved custom fields related to analytic tracking

app_version

browser

city

country

current_date_dmy

current_date_mdy

current_date_ymd 

device_type

landing_page

latitude

longitude

open_tracking_pixel

os

os_version

platform

referrer

referring_domain

region

user_agent

utm_campaign

utm_content

utm_medium

utm_source

utm_term