> For the complete documentation index, see [llms.txt](https://community.commandersact.com/customer-success/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.commandersact.com/customer-success/expand-your-uses/audience-and-activation/smart-re-engagement-via-the-last-product-viewed.md).

# Smart re-engagement via the last product viewed

<figure><img src="/files/lmI4emuwq1hj1c2wwu6S" alt="" width="375"><figcaption></figcaption></figure>

### **1. Business value: Guarantee actionable and certified data**

Using CDP allows you to go beyond the limitations of session cookies to offer persistent, cross-device personalisation.

* **Increased relevance (UX):** Stop treating your loyal customers like strangers. The CDP recognises users when they return, and the TMS instantly displays content that truly interests them.
* **Conversion optimisation**: Dynamically reminding users of past interests reduces decision time and guides them towards finalising their choice (+20% click-through rate on contextual reminders).
* **Unified first-party data**: You capitalise on an internally certified browsing history rather than relying on third-party solutions subject to browser restrictions.

### 2. Implementation methodology

#### **Step A: Collecting intent signals (TMS)**

Use OneTag to capture the details of the product viewed (ID, image, name) and send them in real time to the CDP.

#### **Step B: Profile storage and persistence (CDP)**

The CDP stores the last product viewed as a user profile attribute. This allows the information to be retained even if the user changes browsers or returns several days later.

#### **Step C: Personalisation activation (TMS/On-Site)**

The TMS queries the CDP when the page loads to retrieve the last product viewed and triggers a personalised pop-in or banner.

#### **Step D: Arbitration and exit scenarios**

Define rules to avoid being intrusive (e.g. do not display the reminder if the product has been purchased in the meantime or if the user is already in the conversion funnel).

### 3. Typical use cases

1. **Retail (CDP/TMS synergy):** A visitor views a television on their mobile phone. Two days later, when they return to their computer, the TMS displays the following on the home page: ‘Still interested in the \[TV model]? Continue your exploration’.
2. **Banking & Insurance:** Re-display the last credit simulator used or the last auto quote generated as soon as the user accesses the ‘Individuals’ section of your site.
3. **B2B / Services:** Offer to continue reading a white paper or specific case study that the user had started to view during a previous session.

### Need help making your data flows more reliable?

The CDP + TMS alliance is the driving force behind your real-time personalisation. Our experts will assist you in configuring your profile attributes and display scenarios for maximum efficiency. **Contact our support team:** <support@commandersact.com>

<br>

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://community.commandersact.com/customer-success/expand-your-uses/audience-and-activation/smart-re-engagement-via-the-last-product-viewed.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
