June 03, 2026
Personalizing large language models requires adapting model behavior to individual users while preserving robustness and deployment-scale efficiency. Existing approaches typically personalize LLMs either at the input level, by retrieving user histories or constructing profile prompts, or at the parameter level, by maintaining user-specific parameter-efficient modules. The former makes personalization sensitive to retrieval quality and prompt design, whereas the latter incurs storage and maintenance costs that grow with the user population. To address these limitations, we propose TAP-PER (Temporal Attentive Prefix for PERsonalization), a prefix-based framework that encodes user preferences as learnable representations, eliminating explicit prompt construction and replacing heavy per-user adapters with lightweight user-state prefix embeddings. Inspired by personalized recommendation systems, TAP-PER decomposes user modeling into user-state and query-conditioned components, and incorporates temporal signals to capture the evolving nature of user interests. Experiments on six LaMP tasks show that TAP-PER consistently outperforms prompt-based and model-based baselines across classification, rating, and generation settings. Moreover, TAP-PER uses \(130\times\) fewer per-user parameters than OPPU and roughly half the total parameter footprint of PER-PCS at the 1,000-user scale, demonstrating that scalable LLM personalization can be achieved without explicit prompt construction or heavy per-user adapters.
Large language models (LLMs) [1]–[3] have achieved strong performance across a wide range of natural language processing tasks, yet their outputs often remain generic: the same input is typically answered in the same way regardless of the user’s long-term interests, stylistic preferences, or task-specific goals. This limitation has motivated growing interest in personalized LLMs [4]–[6], which aim to adapt model behavior to individual users while retaining the general capabilities of pretrained language models.
Existing approaches to LLM personalization largely fall into two categories. The first category personalizes LLMs at the input level. Retrieval-augmented generation (RAG) methods retrieve relevant user histories and prepend them to the query, while profile-augmented generation (PAG) methods summarize user histories into natural-language profiles [5], [7]–[9]. These methods are flexible and require no parameter updates, but personalization is delegated to how user context is retrieved, summarized, and serialized into the prompt. The second category personalizes LLMs at the parameter level, typically through parameter-efficient fine-tuning (PEFT). For example, One PEFT Per User (OPPU) trains a dedicated adapter for each user [10], while PER-PCS reduces redundancy by decomposing and recombining personalized adapter components [11]. More recent methods use progressive LoRA-based mixture-of-experts or hypernetworks to generate personalized adapters from user profiles [12], [13]. These methods provide a parameterized route to personalization by encoding user preferences directly in model parameters. Despite recent progress, existing personalized LLM methods still face three practical limitations.
Prompt-based methods such as RAG and PAG are sensitive to retrieval and prompt quality. Table 1 shows that the optimal RAG/PAG setting varies across tasks, suggesting limited robustness and possible privacy risks from exposing user histories.
PEFT-based methods often allocate dedicated parameters (e.g., LoRA modules) for individual users, resulting in a parameter footprint that grows with the user population. Representative approaches such as OPPU [10] and Profile-to-PEFT (P2P) [13] either maintain user-specific parameters or generate them on-the-fly via a hypernetwork. PER-PCS [11] reduces the number of user-specific modules through collaborative decomposition, but still requires maintaining a sizable pool of personalized parameters. Moreover, all three still rely on RAG or PAG to capture user preferences, coupling two personalization mechanisms and adding system complexity.
Most methods treat histories as static context and overlook preference evolution, although recent interactions are often more indicative of current intent.
These limitations lead us to ask: Can we achieve LLM personalization without prompt construction or heavy per-user parameters, while remaining scalable to large populations?
Inspired by personalized recommendation systems, which model user preferences as learned embeddings, we propose TAP-PER (Temporal Attentive Prefix for PERsonalization), a dual-track prefix framework for scalable LLM personalization. Recommendation systems have long shown that user preferences are multi-timescale, with persistent interests and transient, context-dependent intents [14], [15], and that temporal dynamics are crucial for sequential user modeling [16]. As illustrated in Figure 1, TAP-PER follows this principle by decomposing personalization into a user-state prefix for long-term preferences and a query-aware record prefix for dynamically activating relevant historical records. It further incorporates relative time gaps and sequence order into record selection, and uses a shared LoRA-based bridge to integrate the prefix signals end-to-end, eliminating explicit prompt construction while keeping per-user parameters lightweight. In summary, our contributions are as follows:
To address the retrieval sensitivity of prompt-based personalization and the scalability limitations of per-user model adaptation, we propose TAP-PER, a prefix-based framework that represents user preferences as compact learnable states. Instead of constructing prompts or maintaining heavy per-user adapters, TAP-PER shifts personalization toward end-to-end optimized preference representations.
We design a personalized prefix mechanism that decomposes user preferences into two complementary signals: a user-state prefix for persistent preferences and a query-aware record prefix for instance-specific historical evidence. The record prefix uses temporal attention with learned time-gap and order-gap biases to capture evolving user interests, while a shared bridge LoRA integrates the personalized prefix signals into the task-adapted backbone.
Across six LaMP tasks, TAP-PER consistently outperforms both prompt-based and model-based baselines while shrinking per-user storage by \(130\times\) relative to OPPU and cutting the total parameter footprint to roughly half of PER-PCS at the 1,000-user scale; its compact per-user prefix state additionally supports lightweight online adaptation from streaming feedback without retraining the shared backbone.
Following prior work [10], we consider a personalized text generation setting over a set of users \(\mathcal{U}\). Each user \(u \in \mathcal{U}\) is associated with an interaction history \(\mathcal{H}_u\). Given an input query \(q\), the goal is to generate an output \(r\) that reflects the user’s preferences.
Formally, we learn a conditional generator: \[r = \mathrm{LLM}(q, u, \mathcal{H}_u;\, \theta),\] where personalization is achieved by incorporating both user identity and historical interactions.
TAP-PER adopts a two-stage training paradigm: Stage 1 (Task Adaptation) fine-tunes the backbone on data aggregated across users to acquire shared task capabilities, and Stage 2 (Personalized Prefix Learning) introduces user-specific prefixes jointly optimized with a shared LoRA-based bridge. Figure 2 illustrates the Stage 2 pipeline.
In the first stage, we adapt the backbone model to the target task using data aggregated from all users. Each task is trained independently with its own Stage 1 pipeline. Specifically, we fine-tune the base LLM with Low-Rank Adaptation (LoRA) [17] on query–response pairs \(\{(q_i, r_i)\}\), optimizing the cross-entropy loss \[\mathcal{L}_{\text{task}} = \sum_i \mathrm{CE}\big(\mathrm{LLM}(q_i; \theta_{\text{task}}), r_i \big),\] where \(\theta_{\text{task}}\) denotes the task-adapted parameters (i.e., the base model with LoRA updates), and \(\mathrm{CE}(\cdot)\) is the cross-entropy loss. Following LoRA, the weight update for each target matrix is parameterized as \(\Delta W = B^{(t)} A^{(t)}\), where \(A^{(t)} \in \mathbb{R}^{r \times k}\) and \(B^{(t)} \in \mathbb{R}^{d \times r}\) with rank \(r \ll \min(d, k)\), while the backbone parameters remain frozen. After optimization, the learned LoRA parameters are merged into the backbone: \[W_{\text{task}} = W + B^{(t)} A^{(t)},\] which serves as the initialization for the subsequent personalization stage. Detailed hyperparameter settings are provided in Appendix 7.1.
In Stage 2, we freeze the task-adapted backbone \(\theta_{\text{task}}\) and learn user-specific adaptations through a lightweight prefix-based parameterization, together with a shared bridge LoRA. By merging the Stage 1 LoRA into the backbone before this stage, we decouple task adaptation from personalization: the backbone retains general task capabilities, and the Stage 2 parameters focus exclusively on modeling user preferences without risking catastrophic forgetting of the learned task knowledge.
We model persistent user characteristics via a learnable embedding table \(\mathbf{E} \in \mathbb{R}^{|\mathcal{U}|\times (L d)}\). For each user \(u\), the embedding \(\mathbf{e}_u\) is reshaped into a prefix matrix \(\mathbf{P}_u \in \mathbb{R}^{L\times d}\), which captures long-term preferences shared across queries.
Given a query \(q\) and the user’s full interaction history \(\mathcal{H}_u=\{h_1,\dots, h_j, \dots, h_n\}\), we first obtain the representation \(\mathbf{z}_{h_j}\) for each record \(h_j\) by mean-pooling its token embeddings from the frozen backbone’s embedding layer. Since the embedding layer is frozen, these record representations are pre-computed once and cached, so that no per-step encoding of history records is required during training or inference. The query representation \(\mathbf{z}_q\) is obtained in the same manner. We then compute relevance scores over all historical records using a DIN-style attention mechanism [14], dispensing with the separate retriever (e.g., BM25) used by RAG-style baselines: \[s_j = \mathrm{MLP}\!\big(\mathbf{z}_q \| \mathbf{z}_{h_j} \| (\mathbf{z}_q - \mathbf{z}_{h_j}) \| (\mathbf{z}_q \odot \mathbf{z}_{h_j})\big),\] where \(\|\) denotes concatenation, \(\odot\) denotes element-wise product, and the MLP consists of two linear layers with GELU activation. The scores are then augmented with temporal bias: \[\tilde{s}_j = s_j - \lambda_t \log(1+\Delta t_j) - \lambda_o \log(1+\Delta\pi_j),\] where \(\Delta t_j\) denotes the time gap between the query and record \(h_j\), and \(\Delta\pi_j\) denotes the order index gap between the query and record \(h_j\) in the user history. The decay coefficients \(\lambda_t\) and \(\lambda_o\) are learnable scalar parameters.
We normalize scores and aggregate historical signals: \[\alpha_j = \mathrm{softmax}(\tilde{s}_j),\] and construct the query-conditioned prefix as \[\mathbf{P}_q = \mathrm{MLP}\!\left(\sum_{j=1}^{n} \alpha_j \mathbf{z}_{h_j}\right),\] where the MLP projects the aggregated representation into the prefix space \(\mathbb{R}^{L\times d}\). Letting the attention range over the full history rather than a pre-selected top-\(k\) subset removes the dependence on an external retriever and lets the model learn end-to-end which records are relevant to the query; we empirically validate this design choice in §4.5.
We combine persistent and query-conditioned signals via element-wise addition: \[\mathbf{P}_{u,q} = \mathbf{P}_u + \mathbf{P}_q.\]
Since prefix tokens interact with the backbone only through the attention mechanism, their influence on intermediate representations is limited. To enable deeper integration of personalized signals, we introduce a shared bridge LoRA \(\Delta\theta_{\text{bridge}}\), applied to the query, key, value, and output projection layers of each transformer block. Unlike the Stage 1 LoRA, which is merged into the backbone to encode task knowledge, the bridge LoRA is initialized from scratch and trained jointly with the prefix parameters in Stage 2, conditioning the backbone’s internal representations on the prefix signals while keeping the number of additional shared parameters small. We empirically validate this design in Section 4.2, where removing the bridge causes the largest performance drop. Detailed hyperparameter settings including LoRA ranks are provided in Appendix 7.1.
We optimize the prefix parameters (user embeddings \(\mathbf{E}\), the attention MLP, decay coefficients \(\lambda_t, \lambda_o\), and the projection MLP) together with the bridge LoRA \(\Delta\theta_{\text{bridge}}\): \[\mathcal{L}_{\text{pers}} = \sum_{(u,q,r)} \mathrm{CE} \big(\mathrm{LLM}(\mathbf{P}_{u,q}, q;\, \theta'),\, r\big),\] where \(\theta' = \theta_{\text{task}}+\Delta\theta_{\text{bridge}}\). \(\mathbf{P}_u\) and \(\mathbf{P}_q\) can be viewed as parameterized counterparts of PAG and RAG, respectively, encoded as end-to-end-optimized prefixes rather than natural-language prompts.
| Prompt-based | Model-based | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 3-7(lr)8-17 | Metric | RAG | PAG | OPPU | PER-PCS | P2P | TAP-PER | |||||||||
| 3-5(lr)6-7(lr)8-10(lr)11-13(lr)14-14(lr)15-17 | k=1 | k=2 | k=4 | k=0 | k=1 | base | +rag | +pag | base | +rag | +pag | single | base\(^\dagger\) | +\(\mathbf{P}_q\) \(^\ddagger\) | +\(\mathbf{P}_u\) \(^\S\) | |
| LAMP-1: PERSONALIZED | Acc ↑ | 0.659 | 0.642 | 0.659 | 0.683 | 0.675 | 0.654 | 0.675 | 0.715 | 0.626 | 0.626 | 0.691 | 0.724 | 0.642 | 0.699 | 0.732 |
| CITATION IDENTIFICATION | F1 ↑ | 0.659 | 0.645 | 0.664 | 0.683 | 0.675 | 0.656 | 0.674 | 0.711 | 0.619 | 0.620 | 0.685 | 0.720 | 0.642 | 0.696 | 0.728 |
| LAMP-2N: PERSONALIZED | Acc ↑ | 0.790 | 0.796 | 0.803 | 0.787 | 0.790 | 0.794 | 0.809 | 0.817 | 0.748 | 0.798 | 0.809 | 0.803 | 0.789 | 0.808 | 0.838 |
| NEWS CATEGORIZE | F1 ↑ | 0.542 | 0.560 | 0.571 | 0.532 | 0.546 | 0.544 | 0.596 | 0.600 | 0.505 | 0.589 | 0.608 | 0.598 | 0.528 | 0.575 | 0.622 |
| LAMP-2M: PERSONALIZED | Acc ↑ | 0.586 | 0.592 | 0.598 | 0.592 | 0.596 | 0.679 | 0.542 | 0.521 | 0.440 | 0.520 | 0.551 | 0.645 | 0.595 | 0.657 | 0.751 |
| MOVIE TAGGING | F1 ↑ | 0.545 | 0.549 | 0.553 | 0.550 | 0.552 | 0.584 | 0.438 | 0.422 | 0.400 | 0.450 | 0.471 | 0.601 | 0.551 | 0.596 | 0.682 |
| LAMP-3: PERSONALIZED | MAE ↓ | 0.420 | 0.375 | 0.393 | 0.304 | 0.357 | 0.218 | 0.223 | 0.250 | 0.393 | 0.205 | 0.188 | 0.201 | 0.286 | 0.188 | 0.170 |
| PRODUCT RATING | RMSE ↓ | 0.796 | 0.744 | 0.866 | 0.598 | 0.694 | 0.453 | 0.430 | 0.540 | 0.581 | 0.491 | 0.472 | 0.507 | 0.567 | 0.453 | 0.430 |
| LAMP-4: PERSONALIZED | R-1 ↑ | 0.198 | 0.202 | 0.201 | 0.193 | 0.200 | 0.202 | 0.207 | 0.195 | 0.188 | 0.197 | 0.201 | 0.209 | 0.202 | 0.212 | 0.219 |
| NEWS HEADLINE GEN. | R-L ↑ | 0.178 | 0.182 | 0.182 | 0.173 | 0.179 | 0.182 | 0.188 | 0.175 | 0.173 | 0.181 | 0.184 | 0.192 | 0.182 | 0.191 | 0.198 |
| LAMP-5: PERSONALIZED | R-1 ↑ | 0.503 | 0.502 | 0.516 | 0.491 | 0.512 | 0.502 | 0.510 | 0.491 | 0.457 | 0.472 | 0.470 | 0.495 | 0.512 | 0.507 | 0.538 |
| SCHOLARLY TITLE GEN. | R-L ↑ | 0.451 | 0.454 | 0.464 | 0.441 | 0.463 | 0.450 | 0.460 | 0.439 | 0.405 | 0.422 | 0.421 | 0.450 | 0.462 | 0.459 | 0.485 |
Following prior work [10], [12], we conduct experiments on the Large Language Model Personalization (LaMP) benchmark [18]. LaMP covers a diverse set of personalization tasks spanning classification, regression, and text generation. We adopt the same data split as in OPPU [10]. Detailed task descriptions and dataset statistics are provided in Appendix 7.2 and 7.3.
We compare TAP-PER with two families of personalization baselines: prompt-based methods, including RAG [18], [19] and PAG [9]; and model-based methods, including OPPU [10] and PER-PCS [11]. We use Llama-3.1-8B [2] as the backbone for all methods. BM25 [20] is used for retrieval-based baselines, whereas TAP-PER directly attends over each user’s full history without an external retriever. More details are provided in Appendix 7.4 and 7.1.
Following LaMP [18], we use accuracy and F1-score for classification tasks (LaMP-1, LaMP-2), Mean Absolute Error (MAE) and Root Mean Squared Error (RMSE) for LaMP-3, and ROUGE-1 and ROUGE-L [21] for text generation tasks (LaMP-4, LaMP-5). Higher values indicate better performance for all metrics, except for MAE and RMSE where lower values are better.
We evaluate TAP-PER on the LaMP benchmark through six questions:
Does TAP-PER outperform prompt-based and model-based personalization baselines?
What does each component contribute?
How important are temporal signals?
How scalable is TAP-PER?
How sensitive is TAP-PER to retrieval pre-filtering and prefix length?
Can TAP-PER support online adaptation?
Table 1 compares TAP-PER with prompt-based and model-based personalization baselines. TAP-PER achieves the best performance on all task-metric pairs across the six LaMP tasks.
The gains are especially clear on tasks requiring stronger personalization: compared with the best OPPU variant, TAP-PER improves accuracy by 7.2 points on LaMP-2M and ROUGE-1 by 2.8 points on LaMP-5. We further verify the same trend with an alternative
Qwen3-4B backbone in Appendix 7.5.
The results also expose the instability of prompt-based personalization: the best RAG size, the usefulness of PAG, and whether the two should be combined vary substantially across tasks, and this sensitivity persists when RAG/PAG is stacked on OPPU or
PER-PCS. By replacing prompt-time context with learned prefixes, TAP-PER avoids this brittleness; the incremental gains from base to \(+\mathbf{P}_q\) to \(+\mathbf{P}_u\)
further indicate that query-aware and user-state modeling are complementary (Section 4.2).
To answer RQ2, we ablate the bridge LoRA, the query-aware record prefix \(\mathbf{P}_q\), and the user-state prefix \(\mathbf{P}_u\) from the full TAP-PER model. As shown in Table 2, removing any component degrades performance, confirming that they provide complementary gains. The bridge LoRA is important for integrating prefix signals into the task-adapted backbone (e.g., removing it causes large drops on LaMP-1 and LaMP-5), while \(\mathbf{P}_u\) and \(\mathbf{P}_q\) capture different personalization cues: \(\mathbf{P}_u\) is more helpful on tasks requiring stable user preferences (e.g., LaMP-2M and LaMP-5), whereas \(\mathbf{P}_q\) is especially important when query-specific historical evidence is needed (e.g., LaMP-3).
4pt
| Task | Metric | Base | Full | \(-\)bridge | \(-\mathbf{P}_q\) | \(-\mathbf{P}_u\) |
|---|---|---|---|---|---|---|
| LaMP-1 | Acc \(\uparrow\) | 0.642 | 0.732 | 0.659 | 0.699 | 0.699 |
| F1 \(\uparrow\) | 0.642 | 0.728 | 0.659 | 0.695 | 0.696 | |
| LaMP-2N | Acc \(\uparrow\) | 0.789 | 0.838 | 0.814 | 0.837 | 0.808 |
| F1 \(\uparrow\) | 0.528 | 0.622 | 0.595 | 0.611 | 0.575 | |
| LaMP-2M | Acc \(\uparrow\) | 0.595 | 0.751 | 0.702 | 0.733 | 0.657 |
| F1 \(\uparrow\) | 0.551 | 0.682 | 0.624 | 0.659 | 0.596 | |
| LaMP-3 | MAE \(\downarrow\) | 0.286 | 0.170 | 0.241 | 0.241 | 0.188 |
| RMSE \(\downarrow\) | 0.567 | 0.430 | 0.526 | 0.543 | 0.453 | |
| LaMP-4 | R-1 \(\uparrow\) | 0.202 | 0.219 | 0.211 | 0.218 | 0.212 |
| R-L \(\uparrow\) | 0.182 | 0.198 | 0.190 | 0.198 | 0.191 | |
| LaMP-5 | R-1 \(\uparrow\) | 0.512 | 0.538 | 0.508 | 0.523 | 0.507 |
| R-L \(\uparrow\) | 0.462 | 0.485 | 0.449 | 0.473 | 0.459 |
To answer RQ3, we examine the effect of the temporal biases in the query-aware record prefix through coefficient ablation and attention visualization.
We ablate the time-gap and order-gap decay coefficients, \(\lambda_t\) and \(\lambda_o\), on LaMP-2M and LaMP-5. As shown in Table 3, the full model performs best across all metrics. Removing both biases causes the largest drop on LaMP-2M, while disabling either one gives intermediate results, indicating that both temporal recency and sequence order contribute to personalization. The effect is smaller on LaMP-5, suggesting that the usefulness of temporal cues is task-dependent.
Figure 3 visualizes a representative LaMP-2M example. Without temporal biases, TAP-PER fails to emphasize recent query-relevant records and predicts an incorrect tag, similar to the non-personalized baseline. In contrast, the full model assigns higher attention to recent relevant histories and recovers the ground-truth tag. This qualitative pattern is consistent with the ablation results in Table 3.
4pt
| Task | Metric | Base | Full | \(\lambda_t{=}0\) | \(\lambda_o{=}0\) | \(\lambda_t{=}\lambda_o{=}0\) |
|---|---|---|---|---|---|---|
| LaMP-2M | Acc \(\uparrow\) | 0.595 | 0.751 | 0.723 | 0.733 | 0.714 |
| F1 \(\uparrow\) | 0.551 | 0.682 | 0.641 | 0.660 | 0.635 | |
| LaMP-5 | R-1 \(\uparrow\) | 0.512 | 0.538 | 0.516 | 0.511 | 0.513 |
| R-L \(\uparrow\) | 0.462 | 0.485 | 0.464 | 0.452 | 0.464 |
We evaluate scalability from two aspects: storage cost and per-user training time, comparing TAP-PER with OPPU and PER-PCS in Figure 4.
OPPU maintains a dedicated LoRA adapter for each user (\(\sim\)4.2M parameters), whereas TAP-PER stores only a 32K user-state prefix per user, yielding a \(130\times\) reduction in per-user storage. TAP-PER’s remaining footprint is shared across all users: a bridge LoRA (\(\sim\)4.2M) plus the DIN-style attention and projection MLPs (\(\sim\)201M), totaling \(\sim\)205M shared parameters. As shown in Figure 4 (top), with 1,000 users, TAP-PER uses only 5.7% of OPPU’s total parameters and about 53% of PER-PCS’s, showing that it scales mainly through lightweight user embeddings rather than large personalized adapter modules.
For each user, TAP-PER only updates the user-state prefix \(\mathbf{P}_u\), while the query-aware prefix \(\mathbf{P}_q\) is produced by shared parameters. As shown in Figure 4 (bottom), this reduces per-user training time by roughly half compared with OPPU. PER-PCS is faster because it does not perform per-user gradient updates, but TAP-PER offers a stronger accuracy-efficiency trade-off. In addition, the \(\mathbf{P}_q\)-only variant requires no per-user training, providing a lightweight option when online user optimization is impractical.
To answer RQ5, we study two design choices: history scope and prefix length. For history scope, we insert a BM25 pre-filter before temporal attention and vary the retained records \(k \in \{10,20,30,50,\text{All}\}\), where “All” denotes our default setting over the full user history. For prefix length, we vary \(L \in \{2,4,8,16,32\}\). We evaluate on a representative classification task (LaMP-2M) and a representative generation task (LaMP-5), with results shown in Figure 5.
The “All” setting performs best on both tasks. Adding a BM25 pre-filter consistently reduces performance, and varying \(k\) within \(\{10,20,30,50\}\) does not recover the full-history result. This suggests that explicit pre-retrieval is unnecessary: the temporal attention in \(\mathbf{P}_q\) can learn to down-weight less relevant records while preserving useful signals that a sparse retriever may discard.
Performance peaks at a moderate prefix length. Short prefixes underfit user-specific signals, while longer prefixes bring little additional gain. We therefore use the full-history setting with \(L=8\) as the default configuration.
A deployed personalization system should absorb new feedback without full retraining. Since TAP-PER stores user-specific state in a compact \(L\times d\) prefix \(\mathbf{P}_u\) (\(\sim\)32K scalars), it can be updated online by optimizing only \(\mathbf{P}_u\), leaving all shared parameters unchanged. To answer RQ6, we simulate streaming feedback on LaMP-2M and LaMP-5.
For each evaluation user, we split the training history chronologically into two equal halves: the earlier 50% is used for bootstrap (Stage 2) training, and the later 50% is partitioned into \(T{=}5\) equally sized chunks \(\{\mathcal{C}_1,\dots,\mathcal{C}_T\}\) that simulate streaming feedback. The original test set is kept unchanged and used for evaluation throughout. After bootstrap training, chunks arrive sequentially; at step \(t\), each method updates on \(\mathcal{C}_t\) with the same SGD budget and is then evaluated on the fixed test set, yielding a trajectory \(R_0,\dots,R_T\).
We compare four variants initialized from the same bootstrap checkpoint: Static, which performs no online update; Online-Emb, which updates only the per-user prefix \(\mathbf{P}_u\); Online-Full, which updates \(\mathbf{P}_u\) together with the shared \(\mathbf{P}_q\) network and bridge LoRA; and Full-Retrain, which retrains TAP-PER from scratch on all data observed so far and serves as an upper bound.
As shown in Figure 6, Static remains flat, confirming that the model cannot benefit from new feedback without online updates. Online-Full nearly matches Full-Retrain at the final step, with less than \(\sim\)1 point difference on both tasks. This shows that incremental updates can recover most of the benefit of full retraining without replaying past data.
Online-Emb provides a more lightweight alternative. By updating only the \(\sim\)32K-parameter user prefix, it steadily improves on LaMP-5, where each user has dense histories, but gains less on LaMP-2M, where each feedback chunk contains only a few samples. Overall, TAP-PER enables practical continual personalization: dense user histories can be handled by updating only \(\mathbf{P}_u\), while sparse histories may benefit from updating the shared personalization modules, without modifying the backbone or retraining from scratch.
Existing approaches fall into two families [4]–[6]. Prompt-based methods inject user-specific context via retrieval [8], [18] or natural-language profiles [7], [9], which are flexible and training-free but sensitive to retrieval quality and prompt construction and may expose raw user histories. Model-based methods instead encode preferences into parameters via PEFT: OPPU [10] and PROPER [12] train a dedicated LoRA per user, PER-PCS [11] reassembles shared adapter pieces, P2P [13] generates adapters from profiles via a hypernetwork, and black-box variants such as HYDRA [22] factorize behavior without internal access. Their parameter footprint nonetheless grows with the user population, and most still rely on RAG or PAG at the input, coupling two personalization mechanisms. TAP-PER replaces both with lightweight prefix embeddings and a shared bridge LoRA.
Prefix and prompt tuning [23], [24] steer frozen transformers via learnable continuous vectors, and have been extended by many PEFT variants such as LoRA [17], adapters [25], and BitFit [26]. These methods are typically trained per task rather than per user, with no built-in mechanism for selecting user-specific signals from interaction history. TAP-PER adapts prefix tuning to personalization by treating each user as a learnable prefix and pairing it with a query-aware, temporal-attentive record prefix.
Personalized recommendation has long modeled temporal dynamics and query-aware user interests [14], [16], [27]–[29]. DIN [14] introduces query-conditioned attention over user histories, and TiSASRec [16] incorporates time intervals into self-attention to distinguish recent and distant interactions. TAP-PER ports these inductive biases to LLM personalization via DIN-style attention with learnable time-gap and order-gap decays, complementing the user-state prefix with context-dependent evidence.
We presented TAP-PER, a prefix-based framework that reformulates LLM personalization as learned user representation modeling. TAP-PER replaces explicit prompt construction and heavy per-user adapters with lightweight prefix states, combining a user-state prefix for persistent preferences, a query-aware temporal record prefix for historical evidence, and a shared bridge LoRA for effective integration with the task-adapted backbone. Our results suggest that effective LLM personalization need not rely on retrieval-time prompt engineering or user-specific adapter modules: a compact, end-to-end-optimized user representation can match or surpass both families while reducing per-user storage by \(130\times\) over OPPU and the total parameter footprint to about half of PER-PCS at the 1,000-user scale, all while enabling continual adaptation. We hope this perspective encourages further work on representation-centric personalization.
TAP-PER has several limitations. First, although \(\mathbf{P}_q\) attends over the user’s full history without an external retriever, attention quality may still degrade for users with extremely long or noisy histories, and we have not studied how to combine our learned attention with an auxiliary dense or learned retriever in such regimes. Second, our experiments cover Llama-3.1-8B and Qwen3-4B only, and we have not verified whether the gains hold at substantially larger backbone sizes.
TAP-PER is designed with privacy in mind: user preferences are encoded into continuous prefix embeddings and a shared bridge LoRA rather than injected into the prompt as raw text, which reduces the surface area for verbatim leakage of personal content in model inputs [30]. Nevertheless, the per-user embeddings still encode behavioral patterns derived from private histories and should be treated as sensitive artifacts: they require secure storage, access control, and standard data-minimization practices, and users should retain the ability to inspect, update, or delete their personalized representations.
Beyond privacy, personalized LLMs can amplify existing biases or reinforce filter-bubble effects by over-fitting to past behavior, and the temporal decay used in TAP-PER—by design—up-weights recent interactions, which may further narrow the range of content surfaced to a user. We therefore recommend periodic auditing of model outputs across demographic and interest groups, together with transparent controls over the strength of personalization, before deploying frameworks like TAP-PER in user-facing applications. All datasets used in this work are publicly released research benchmarks (LaMP), and no additional user data was collected for this study.
Tables 4 and 5 summarize the hyperparameter settings for Stage 1 (task adaptation) and Stage 2 (personalized prefix learning), respectively. Both stages apply LoRA to the query, key, value, and output projection layers. The Stage 1 task LoRA is merged into the backbone after training, while the Stage 2 bridge LoRA remains as a separate shared module.
| Task | Rank | Epochs | learning rate | batch size |
|---|---|---|---|---|
| LaMP-1 | 8 | 3 | 3e–4 | 8 |
| LaMP-2N | 8 | 3 | 3e–4 | 8 |
| LaMP-2M | 8 | 3 | 3e–4 | 8 |
| LaMP-3 | 8 | 3 | 5e–4 | 32 |
| LaMP-4 | 8 | 3 | 3e–4 | 8 |
| LaMP-5 | 8 | 3 | 3e–4 | 8 |
| Task | Rank | Epochs | learning rate | batch size |
|---|---|---|---|---|
| LaMP-1 | 4 | 3 | 2e–4 | 32 |
| LaMP-2N | 4 | 3 | 1e–4 | 16 |
| LaMP-2M | 4 | 3 | 1e–4 | 8 |
| LaMP-3 | 4 | 3 | 2e–4 | 32 |
| LaMP-4 | 4 | 3 | 2e–4 | 32 |
| LaMP-5 | 4 | 3 | 1e–4 | 16 |
We employ the LaMP benchmark [18], which encompasses a diverse set of personalization tasks covering both text classification and generation. We evaluate on the following tasks:
LaMP-1 (Personalized Citation Identification): A binary text classification task that involves predicting citation choices. Given a new paper and two candidate references, the model determines which paper will be cited based on the user’s historical publications. This task evaluates a model’s ability to capture user-specific citation preferences.
LaMP-2N (Personalized News Categorization): A categorical text classification task that involves classifying news articles into one of 15 categories. Given an article written by a user, the model predicts its category using the user’s history of articles and their corresponding categories.
LaMP-2M (Personalized Movie Tagging): An ordinal text classification task that involves predicting one of 15 tags for a movie based on a user’s tagging history. This task evaluates the model’s ability to assign tags to a movie description using the user’s historical movie-tag pairs.
LaMP-3 (Personalized Product Rating): A text classification task that involves predicting product ratings as a five-class classification problem. The model predicts an integer rating from one to five for a given review based on the user’s historical review-rating pairs.
LaMP-4 (Personalized News Headline Generation): A text generation task that involves generating personalized news headlines for given articles based on the author’s historical article-title pairs. This task evaluates the model’s ability to replicate the author’s stylistic nuances in headline generation.
LaMP-5 (Personalized Scholarly Title Generation): A text generation task that involves generating titles for research articles based on the author’s historical article-title pairs, extending personalized text generation into scholarly domains.
We exclude the following two tasks from our evaluation:
LaMP-6 (Personalized Email Subject Generation): A text generation task that involves generating subject lines for emails based on the user’s historical email-subject pairs. This task is excluded because the corresponding dataset is not publicly available.
LaMP-7 (Personalized Tweet Paraphrasing): A text generation task that involves paraphrasing an input tweet into a personalized version using the user’s historical tweet data for stylistic guidance. This task is excluded due to inconsistent formats between user history and the evaluation query.
Table 6 summarizes the dataset statistics for each stage. Stage 1 uses all users except the most active ones for task adaptation, while Stage 2 trains on the selected most active users with their full interaction histories. The evaluation set shares the same users as Stage 2.
5pt
| Task | Stage 1 | Stage 2 | Eval. | |||
|---|---|---|---|---|---|---|
| 2-3(lr)4-5(lr)6-7 | #User | #Q | #User | #History | #User | #Q |
| LaMP-1 | 6,442 | 7,919 | 100 | 318 | 100 | 123 |
| LaMP-2N | 274 | 3,662 | 49 | 220 | 49 | 6,033 |
| LaMP-2M | 829 | 3,181 | 100 | 56 | 100 | 3,302 |
| LaMP-3 | 19,899 | 22,388 | 101 | 960 | 101 | 112 |
| LaMP-4 | 1,543 | 7,275 | 100 | 270 | 100 | 6,275 |
| LaMP-5 | 14,581 | 16,075 | 101 | 443 | 101 | 107 |
RAG (Retrieval-Augmented Generation) [18]: Following the retrieval-augmented personalization method presented in LaMP, the user’s query is augmented with the top-\(k\) retrieved items from the user’s history corpus using BM25. We take \(k \in \{1, 2, 4\}\) to study the effect of retrieval size. No model parameters are modified.
PAG (Profile-Augmented Generation) [9]: The user’s input sequence is concatenated with a natural language profile summarizing the user’s preferences and behavior patterns. Following the implementation of [10], user profiles are generated using the Vicuna-7B model. We evaluate PAG without retrieval (\(k{=}0\)) and combined with retrieval augmentation (\(k{=}1\)), following the setting of [9]. No model parameters are modified.
OPPU (One PEFT Per User) [10]: A dedicated LoRA adapter is trained for each user using their individual data. We evaluate three variants: base (LoRA only, no prompt augmentation), +rag (LoRA combined with \(k{=}1\) retrieved records), and +pag (LoRA combined with user profile). LoRA is applied to the same target modules as our method with rank 8.
PER-PCS (Personalized Pieces) [11]: A collaborative PEFT framework that selects representative “sharer” users via clustering, trains individual LoRA adapters and post-hoc gating vectors for each sharer, and assembles personalized PEFT parameters for target users by selecting and weighting sharer pieces in an auto-regressive, training-free manner. We evaluate three variants following OPPU: base, +rag, and +pag.
P2P (Profile-to-PEFT) [13]: A hypernetwork-based personalization framework that maps an encoded user profile directly to a full set of LoRA adapter parameters, eliminating per-user training at deployment time. The user profile is first generated by an upstream LLM summarizing the user’s history (following the PAG protocol), then encoded and fed to a hypernetwork that produces a user-specific LoRA. The generated LoRA is loaded into the backbone to produce personalized outputs. We use a single variant per task, since P2P already incorporates PAG (its input is a user profile) and produces a personalized LoRA in one step.
To evaluate whether TAP-PER generalizes beyond the primary backbone used in our main experiments (Llama-3.1-8B), we conduct additional experiments using Qwen3-4B [3] as an alternative backbone. We compare TAP-PER against the same set of baselines on a representative subset of LaMP tasks. Results are shown in Table 7.
| Prompt-based | Model-based | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 3-7(lr)8-17 | Metric | RAG | PAG | OPPU | PER-PCS | P2P | TAP-PER | |||||||||
| 3-5(lr)6-7(lr)8-10(lr)11-13(lr)14-14(lr)15-17 | k=1 | k=2 | k=4 | k=0 | k=1 | base | +rag | +pag | base | +rag | +pag | single | base\(^\dagger\) | +\(\mathbf{P}_q\) \(^\ddagger\) | +\(\mathbf{P}_u\) \(^\S\) | |
| LAMP-1: PERSONALIZED | Acc ↑ | 0.618 | 0.618 | 0.618 | 0.642 | 0.585 | 0.642 | 0.626 | 0.683 | 0.585 | 0.602 | 0.675 | 0.690 | 0.585 | 0.724 | 0.813 |
| CITATION IDENTIFICATION | F1 ↑ | 0.613 | 0.616 | 0.605 | 0.641 | 0.559 | 0.634 | 0.625 | 0.682 | 0.576 | 0.598 | 0.674 | 0.685 | 0.566 | 0.720 | 0.813 |
| LAMP-2N: PERSONALIZED | Acc ↑ | 0.770 | 0.777 | 0.787 | 0.783 | 0.785 | 0.785 | 0.793 | 0.805 | 0.662 | 0.749 | 0.768 | 0.787 | 0.763 | 0.785 | 0.826 |
| NEWS CATEGORIZE | F1 ↑ | 0.520 | 0.530 | 0.550 | 0.537 | 0.555 | 0.557 | 0.600 | 0.604 | 0.430 | 0.521 | 0.541 | 0.547 | 0.488 | 0.550 | 0.609 |
| LAMP-2M: PERSONALIZED | Acc ↑ | 0.520 | 0.536 | 0.539 | 0.565 | 0.550 | 0.427 | 0.468 | 0.464 | 0.491 | 0.534 | 0.538 | 0.683 | 0.545 | 0.580 | 0.690 |
| MOVIE TAGGING | F1 ↑ | 0.475 | 0.486 | 0.482 | 0.520 | 0.499 | 0.358 | 0.362 | 0.368 | 0.402 | 0.432 | 0.434 | 0.525 | 0.505 | 0.527 | 0.620 |
| LAMP-3: PERSONALIZED | MAE ↓ | 0.223 | 0.223 | 0.196 | 0.241 | 0.250 | 0.223 | 0.196 | 0.241 | 0.277 | 0.277 | 0.259 | 0.275 | 0.295 | 0.268 | 0.195 |
| PRODUCT RATING | RMSE ↓ | 0.543 | 0.543 | 0.518 | 0.559 | 0.567 | 0.559 | 0.518 | 0.559 | 0.605 | 0.620 | 0.590 | 0.600 | 0.605 | 0.582 | 0.516 |
| LAMP-4: PERSONALIZED | R-1 ↑ | 0.176 | 0.175 | 0.184 | 0.174 | 0.179 | 0.163 | 0.168 | 0.165 | 0.148 | 0.157 | 0.156 | 0.184 | 0.174 | 0.175 | 0.189 |
| NEWS HEADLINE GEN. | R-L ↑ | 0.157 | 0.156 | 0.164 | 0.154 | 0.159 | 0.146 | 0.152 | 0.148 | 0.134 | 0.140 | 0.140 | 0.166 | 0.154 | 0.154 | 0.168 |
| LAMP-5: PERSONALIZED | R-1 ↑ | 0.489 | 0.512 | 0.506 | 0.459 | 0.481 | 0.504 | 0.501 | 0.499 | 0.477 | 0.490 | 0.493 | 0.480 | 0.495 | 0.499 | 0.495 |
| SCHOLARLY TITLE GEN. | R-L ↑ | 0.422 | 0.449 | 0.449 | 0.401 | 0.419 | 0.439 | 0.447 | 0.446 | 0.407 | 0.421 | 0.429 | 0.426 | 0.431 | 0.428 | 0.430 |
The trends largely mirror those on Llama-3.1-8B: TAP-PER (+\(\mathbf{P}_u\)) is the best on 10 out of 12 task–metric pairs and matches or exceeds every model-based baseline. The only exception is LaMP-5, where RAG with \(k{=}2\) achieves the best R-1 (0.512) and R-L (0.449), narrowly ahead of TAP-PER. We attribute this to the smaller backbone offering limited headroom for prefix-based personalization on short-form scholarly title generation, where surface lexical cues from the retrieved abstracts already provide a strong baseline.
Table 8 lists the prompt templates used for each task. For prompt-based methods (RAG, PAG), the user profile and/or retrieved records are prepended before the instruction. For TAP-PER, the prefix representations replace these textual augmentations.
| Task | Prompt |
|---|---|
| LaMP-1: Personalized Citation Identification | {USER PREFIX + RECORD PREFIX} / ##USER PROFILE: {USER_PROFILE} / ##USER HISTORY: {USER_HISTORY} ##INSTRUCTION: Identify the most relevant reference for the listed publication by the researcher. Select the reference paper that is most closely related to the researcher’s work. paper title: {TITLE} reference: [1]: “{OPT1}” [2]: “{OPT2}” Answer: |
| LaMP-2M: Personalized Movie Tagging | {USER PREFIX + RECORD PREFIX} / ##USER PROFILE: {USER_PROFILE} / ##USER HISTORY: {USER_HISTORY} ##INSTRUCTION: Which tag does this movie relate to among the following tags? Just answer with the tag name without further explanation. tags: [sci-fi, based on a book, comedy, action, twist ending, dystopia, dark comedy, classic, psychology, fantasy, romance, thought-provoking, social commentary, violence, true story] description: {QUERY} tag: |
| LaMP-2N: Personalized News Categorization | {USER PREFIX + RECORD PREFIX} / ##USER PROFILE: {USER_PROFILE} / ##USER HISTORY: {USER_HISTORY} ##INSTRUCTION: Which category does this article relate to among the following categories? Just answer with the category name without further explanation. categories: [travel, education, parents, style & beauty, entertainment, food & drink, science & technology, business, sports, healthy living, women, politics, crime, culture & arts, religion] article: {QUERY} category: |
| LaMP-3: Personalized Product Rating | {USER PREFIX + RECORD PREFIX} / ##USER PROFILE: {USER_PROFILE} / ##USER HISTORY: {USER_HISTORY} ##INSTRUCTION: What is the score of the following review on a scale of 1 to 5? just answer with 1, 2, 3, 4, or 5 without further explanation. review: {QUERY} score: |
| LaMP-4: Personalized News Headline Generation | {USER PREFIX + RECORD PREFIX} / ##USER PROFILE: {USER_PROFILE} / ##USER HISTORY: {USER_HISTORY} ##INSTRUCTION: Generate a headline for the following article. article: {QUERY} headline: |
| LaMP-5: Personalized Scholarly Title Generation | {USER PREFIX + RECORD PREFIX} / ##USER PROFILE: {USER_PROFILE} / ##USER HISTORY: {USER_HISTORY} ##INSTRUCTION: Generate a title for the following abstract of a paper. abstract: {QUERY} title: |
To complement the quantitative comparison, we provide qualitative output examples. Each table shows the query, the gold answer, and the outputs from a representative non-personalized baseline, prompt-based baselines (RAG and PAG), and two TAP-PER variants (without and with temporal biases). marks a correct answer and an incorrect one.
4pt
| Query (qid 81348) | As America recovers from the Civil War, one man tries to put the pieces of his life back together but finds himself fighting a new battle on the frontier. Cable is an embittered Confederate soldier who returns from the war to reclaim his Arizona homestead from rebel pioneers who sympathize with the Union war effort. |
|---|---|
| Gold tag | based on a book |
| RAG top-3 retrieved | based on a book — Photographer Robert Kincaid wanders into the life of housewife Francesca Johnson for four days in the 1960s. |
| based on a book — Eight people embark on an expedition into the Congo … stumble across a race of killer apes. | |
| based on a book — A vampire relates his epic life story of love, betrayal, loneliness, and dark hunger to an over-curious reporter. | |
| Non-Personalized | violence |
| RAG | classic |
| PAG | classic |
| TAP-PER (no bias) | based on a book |
| TAP-PER | based on a book |
| Abstract | Implementing security by design in practice often involves the application of threat modeling to elicit security threats and to aid designers in focusing efforts on the most stringent problems first. Existing threat modeling methodologies are capable of generating lots of threats, yet they lack even basic support to triage these threats, except for relying on the expertise and manual assessment by the threat modeler… |
|---|---|
| Gold title | Risk-based design security analysis. |
| RAG top-3 retrieved | Knowledge-enriched security and privacy threat modeling. — Creating secure and privacy-protecting systems entails the simultaneous coordination of development activities along three different yet mutually influencing dimensions: translating security and privacy goals to design choices, analyzing the design for threats, and performing a risk analysis of these threats. |
| SPARTA: Security & Privacy Architecture Through Risk-Driven Threat Assessment. — The development of secure and privacy-preserving software systems entails the continuous consideration of the security and privacy aspects of the system under development; the SPARTA prototype facilitates capturing security and privacy design decisions, continuous threat elicitation, and risk analysis. | |
| Interaction-Based Privacy Threat Elicitation. — Threat modeling involves the systematic identification, elicitation, and analysis of privacy- and/or security-related threats in the context of a specific system; this approach leads to better process guidance and more concrete interpretation of privacy threat types. | |
| Non-Personalized | Risk-Based Threat Modeling: A Case Study on SecureDrop |
| RAG | Knowledge-enriched security and privacy threat modeling. |
| PAG | Risk-Based Threat Modeling: A Case Study on SecureDrop |
| TAP-PER (no bias) | Risk-Based Threat Modeling: A Case Study on SecureDrop |
| TAP-PER | Risk-Based Security Analysis for Threat Modeling |
All experiments are conducted on a single node equipped with 8 NVIDIA A800 80GB GPUs. Training is distributed across GPUs using HuggingFace Trainer with the accelerate backend [31], launched via torchrun for multi-GPU data parallelism. Stage 1 task adaptation takes approximately 5–30 minutes per task depending on
dataset size, and Stage 2 personalized prefix learning takes approximately 10–30 minutes per task. All models are implemented using PyTorch, HuggingFace Transformers [32], and PEFT.
All artifacts used in this work are publicly released for research use under their original licenses: the LaMP benchmark [18] (MIT), Llama-3.1-8B [2] (Llama 3.1 Community License), Qwen3-4B [3] (Apache 2.0), and baseline implementations of OPPU [10], PER-PCS [11], and P2P [13] released by the original authors. Standard libraries (PyTorch, HuggingFace Transformers [32], PEFT) are used under Apache 2.0. We use each artifact strictly within its intended research purpose and do not redistribute them.
Beyond improving personalization accuracy, future work can further explore the role of diversity in personalized LLMs. A highly personalized model should not simply collapse to a narrow user-specific pattern, since users may hold multiple plausible preferences, writing styles, or decision criteria across contexts. Inspired by recent work on diversity-aware reasoning and reinforcement learning [33]–[37], future extensions of TAP-PER could incorporate diversity-aware objectives to preserve multiple high-quality personalized responses or reasoning trajectories while still adapting to user-specific preferences. This direction may lead to personalized LLMs that are not only accurate and scalable, but also flexible, robust, and less prone to over-personalization.
We used AI assistants in a limited and clearly scoped manner during the preparation of this work. Specifically, AI assistants were used for: (i) code-level autocompletion and refactoring suggestions during the implementation of training and evaluation scripts; (ii) light editorial polishing of author-written text, such as rephrasing for clarity and fixing grammatical issues; and (iii) help in formatting LaTeX tables and figures. All research ideas, experimental design, analysis, and scientific claims were conceived, executed, and verified by the authors. No AI assistant was used to generate experimental results, references, or substantive technical content, and all AI-assisted text was reviewed and edited by the authors before inclusion.
Corresponding author.↩︎