Channel
@PersonalizeCDP
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
197subscribers
-6 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001152273923 |
|---|---|
| Type | Channel |
| Username | @PersonalizeCDP |
| Created | Between 1 October 2018 and 30 June 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 10 October 2026 |
| On Telegram | t.me/PersonalizeCDP |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 24 September 2026 and assigned it the closest of 31 fixed categories, at 98% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Oct 2026, 20:00 | 197 | -2 |
| 7 Sept 2026, 23:01 | 199 | -2 |
| 23 Aug 2026, 04:08 | 201 | -2 |
| 8 Aug 2026, 11:19 | 203 | no change |
| 7 Aug 2026, 22:57 | 203 | first reading |
20 posts held, back to 4 March 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 1 May 2025. An engagement rate over an empty window would be a number about nothing.
3 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 66.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 2 | 66.7% | |
| 👏 | 1 | 33.3% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 4 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 3 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 4 March 2024 to 1 May 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Use Sitecore Content Hub assets in Sitecore Personalize web templates and offers If you have licenses for Sitecore Personalize and Sitecore Content Hub, you can now integrate these products to use your approved images inside your web templates and offers. This integration helps you maintain a set of centralized assets for consistency when building personalized content. To get started, enable the Content Hub integra…
Connect audience exports in CDP to Sitecore Connect recipes You can now connect audience exports in Sitecore CDP directly to Sitecore Connect recipes, making it easier to automate data transfers to third-party systems. This feature removes the need to manually create a Sitecore Connect connection in CDP, copy webhook URLs, or switch back and forth between CDP and Connect, so it's simpler and faster to manage your au…
👍1
Sitecore Cloud SDK v0.5 - enables you to integrate Sitecore Search capabilities into your Next.js and Angular JSS apps connected to XM Cloud. You can now build search experiences such as search results pages, recommendations, and search suggestions by requesting content from your instance of Sitecore Search. As part of unified tracking, you can also track the events that occur inside those experiences and send the e…
Sitecore Cloud SDK v0.4 If you haven't heard of Cloud SDK, you must definitely check it here - https://tinyurl.com/2yroqfzt. New version 0.4 brings lots of so expected features: - Web experiences: run Sitecore Personalize web experiences and experiments in your app. If you previously chose the Engage SDK because of the support for web experiences, consider switching to the Cloud SDK. - Unified tracking: set up tr…
SESSION TRAITS Session Traits could be used in CDP to: - Enhance Audience Targeting: Filter segments for audience exports and activate targeted audiences outside of Sitecore CDP, for more targeted marketing efforts. -Standardize Data Handling: Automatically calculate and store session traits after each session, ensuring consistent data usage and eliminating the repeated calculations. Session Traits could be use…
Session Traits - The new CDP and Personalize feature Session Traits enable you to aggregate events from a web session, along with guest data, to apply custom logic and store the results as a Session Trait attribute in the guest profile. Session traits are calculated at the end of each web session and are available for identified guests. With Sitecore CDP, Session Traits empowers you to: - Enhance Audience Targeti…
Custom goals in Sitecore Personalize You can now configure custom goals with support for multiple attributes, allowing for more precise and detailed goal tracking. By setting multiple attributes for events, you can track your interactions in much more detail, making it easier to measure success. Currently, multiple attributes are evaluated using AND logic by default when you configure your custom goals. We’re explo…
Creating an Experience with the Sitecore Personalize SDK: https://tinyurl.com/25qbx92v
New Country Region condition now available in Personalize Personalize introduced a new condition that allows you to combine country and region for better personalization. This significantly improves the user experience by enabling tailored content for visitors. Initially, this condition supports the United States as a country and all its states as regions. Example Condition: - “The visitor is in United States wher…
New Date and time conditions to XM Cloud and Personalize addresses the need for more precise control over date and time personalization within a single condition. This reduces the need for adding multiple conditions to set-up personalization. Link: https://tinyurl.com/2xq6st38
👍1
Create Experiences with Multiple Layouts in Sitecore Personalize Read: https://tinyurl.com/23c3b3nd
Personalize: Tips & Tricks For Decision Models And Programmable Nodes - Remember to return a value from programmable nodes - Set the correct return type in programmable nodes - Avoid leaving empty lines in decision tables - Name Decision Table output columns carefully - Pay attention to workflow in decision model - Save decision model versions with comments - Use the right case in input columns - Use decision templa…
Showing the 12 most recent of 20 posts we hold for @PersonalizeCDP. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 10 October 2026 — this entry's latest reading, not the date you are reading this.
“SmartHub (CDP / Personalize)” (@PersonalizeCDP), 197 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/PersonalizeCDP.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.